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>Creating, updating and checking debian/copyright semi-automatically
</title>
11 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
13 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
14 <description><p
>Making packages for Debian requires quite a lot of attention to
15 details. And one of the details is the content of the
16 debian/copyright file, which should list all relevant licenses used by
17 the code in the package in question, preferably in
18 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
19 readable DEP5 format
</a
>.
</p
>
21 <p
>For large packages with lots of contributors it is hard to write
22 and update this file manually, and if you get some detail wrong, the
23 package is normally rejected by the ftpmasters. So getting it right
24 the first time around get the package into Debian faster, and save
25 both you and the ftpmasters some work.. Today, while trying to figure
26 out what was wrong with
27 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
28 zfsonlinux copyright file
</a
>, I decided to spend some time on
29 figuring out the options for doing this job automatically, or at least
30 semi-automatically.
</p
>
32 <p
>Lucikly, there are at least two tools available for generating the
33 file based on the code in the source package,
34 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
35 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
36 not sure which one of them came first, but both seem to be able to
37 create a sensible draft file. As far as I can tell, none of them can
38 be trusted to get the result just right, so the content need to be
39 polished a bit before the file is OK to upload. I found the debmake
41 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
42 blog posts from
2014</a
>.
44 <p
>To generate using debmake, use the -cc option:
47 debmake -cc
> debian/copyright
48 </pre
></p
>
50 <p
>Note there are some problems with python and non-ASCII names, so
51 this might not be the best option.
</p
>
53 <p
>The cme option is based on a config parsing library, and I found
55 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
56 blog post from
2015</a
>. To generate using cme, use the
'update
57 dpkg-copyright
' option:
60 cme update dpkg-copyright
61 </pre
></p
>
63 <p
>This will create or update debian/copyright. The cme tool seem to
64 handle UTF-
8 names better than debmake.
</p
>
66 <p
>When the copyright file is created, I would also like some help to
67 check if the file is correct. For this I found two good options,
68 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
69 to focus on license types and file matching, and is able to detect
70 ineffective blocks in the copyright file. The latter reports missing
71 copyright holders and years, but was confused by inconsistent license
72 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
73 fix all issues reported by them before uploading. But I do not know
74 if the tools and the ftpmasters agree on what is important to fix in a
75 copyright file, so the package might still be rejected.
</p
>
77 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
78 will read through the source and try to find all copyright statements.
79 It is not comparing the result to the content of debian/copyright, but
80 can be useful when verifying the content of the copyright file.
</p
>
82 <p
>Are you aware of better tools in Debian to create and update
83 debian/copyright file. Please let me know, or blog about it on
84 planet.debian.org.
</p
>
86 <p
>As usual, if you use Bitcoin and want to show your support of my
87 activities, please send Bitcoin donations to my address
88 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
90 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
91 on how to use licensecheck and cdbs to create a draft copyright file
94 licensecheck --copyright -r `find * -type f` | \
95 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
96 </pre
></p
>
98 <p
>He mentioned that he normally check the generated file into the
99 version control system to make it easier to discover license and
100 copyright changes in the upstream source. I will try to do the same
101 with my packages in the future.
</p
>
103 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
104 against using -quiet for new users, so I removed it from the proposed
105 command line.
</p
>
110 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
111 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
113 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
114 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
115 is taking shape in Debian, and one provided feature is a very
116 convenient way to tell you which package to install to make a given
117 firmware file available when the kernel is looking for it. This can
118 be done using apt-file too, but that is for someone else to blog
121 <p
>Here is a small recipe to find the package with a given firmware
122 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
123 picked from the set of firmware announced using appstream in Debian
124 unstable. In general you would be looking for the firmware requested
125 by the kernel during kernel module loading. To find the package
126 providing the example file, do like this:
</p
>
128 <blockquote
><pre
>
129 % apt install appstream
133 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
134 awk
'/Package:/ {print $
2}
'
137 </pre
></blockquote
>
139 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
140 appstream wiki
</a
> page to learn how to embed the package metadata in
141 a way appstream can use.
</p
>
143 <p
>This same approach can be used to find any package supporting a
144 given MIME type. This is very useful when you get a file you do not
145 know how to handle. First find the mime type using
<tt
>file
146 --mime-type
</tt
>, and next look up the package providing support for
147 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
148 and you can find all packages handling this type like this:
</p
>
150 <blockquote
><pre
>
151 % apt install appstream
155 % appstreamcli what-provides mimetype image/svg+xml | \
156 awk
'/Package:/ {print $
2}
'
178 </pre
></blockquote
>
180 <p
>I believe the MIME types are fetched from the desktop file for
181 packages providing appstream metadata.
</p
>
186 <title>Creepy, visualise geotagged social media information - nice free software
</title>
187 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
189 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
190 <description><p
>Most people seem not to realise that every time they walk around
191 with the computerised radio beacon known as a mobile phone their
192 position is tracked by the phone company and often stored for a long
193 time (like every time a SMS is received or sent). And if their
194 computerised radio beacon is capable of running programs (often called
195 mobile apps) downloaded from the Internet, these programs are often
196 also capable of tracking their location (if the app requested access
197 during installation). And when these programs send out information to
198 central collection points, the location is often included, unless
199 extra care is taken to not send the location. The provided
200 information is used by several entities, for good and bad (what is
201 good and bad, depend on your point of view). What is certain, is that
202 the private sphere and the right to free movement is challenged and
203 perhaps even eradicated for those announcing their location this way,
204 when they share their whereabouts with private and public
207 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
209 <p
>The phone company logs provide a register of locations to check out
210 when one want to figure out what the tracked person was doing. It is
211 unavailable for most of us, but provided to selected government
212 officials, company staff, those illegally buying information from
213 unfaithful servants and crackers stealing the information. But the
214 public information can be collected and analysed, and a free software
215 tool to do so is called
216 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
217 discovered it when I read
218 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
219 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
220 November
2014, and decided to check if it was available in Debian.
221 The python program was in Debian, but
222 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
223 Debian
</a
> was completely broken and practically unmaintained. I
224 uploaded a new version which did not work quite right, but did not
225 have time to fix it then. This Christmas I decided to finally try to
226 get Creepy operational in Debian. Now a fixed version is available in
227 Debian unstable and testing, and almost all Debian specific patches
229 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
231 <p
>The Creepy program visualises geolocation information fetched from
232 Twitter, Instagram, Flickr and Google+, and allow one to get a
233 complete picture of every social media message posted recently in a
234 given area, or track the movement of a given individual across all
235 these services. Earlier it was possible to use the search API of at
236 least some of these services without identifying oneself, but these
237 days it is impossible. This mean that to use Creepy, you need to
238 configure it to log in as yourself on these services, and provide
239 information to them about your search interests. This should be taken
240 into account when using Creepy, as it will also share information
241 about yourself with the services.
</p
>
243 <p
>The picture above show the twitter messages sent from (or at least
244 geotagged with a position from) the city centre of Oslo, the capital
245 of Norway. One useful way to use Creepy is to first look at
246 information tagged with an area of interest, and next look at all the
247 information provided by one or more individuals who was in the area.
248 I tested it by checking out which celebrity provide their location in
249 twitter messages by checkout out who sent twitter messages near a
250 Norwegian TV station, and next could track their position over time,
251 making it possible to locate their home and work place, among other
252 things. A similar technique have been
253 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
254 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
255 tool to discover lying governments, and a useful tool to help people
256 understand the value of the private information they provide to the
259 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
260 it depend on several python modules currently missing in Jessie (at
261 least python-instagram, python-flickrapi and
262 python-requests-toolbelt).
</p
>
264 <p
>(I have uploaded
265 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
266 screenshots.debian.net
</a
> and licensed it under the same terms as the
267 Creepy program in Debian.)
</p
>
272 <title>Always download Debian packages using Tor - the simple recipe
</title>
273 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
275 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
276 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
277 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
278 that those listening on the Internet lines would have good reason to
279 believe a computer have a given security hole
</a
> if it download a
280 security fix from a Debian mirror. This is a good reason to always
281 use encrypted connections to the Debian mirror, to make sure those
282 listening do not know which IP address to attack. In August, Richard
283 Hartmann observed that encryption was not enough, when it was possible
284 to interfere download size to security patches or the fact that
285 download took place shortly after a security fix was released, and
286 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
287 to always use Tor to download packages from the Debian mirror
</a
>. He
288 was not the first to propose this, as the
289 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
290 package by Tim Retout already existed to make it easy to convince apt
291 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
292 aware of that package when I read the blog post from Richard.
</p
>
294 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
295 sysadmins, and he set up a Tor hidden service on one of the central
296 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
297 it possible to download packages directly between two tor nodes,
298 making sure the network traffic always were encrypted.
</p
>
300 <p
>Here is a short recipe for enabling this on your machine, by
301 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
302 urls with tor+http and tor+https, and using the hidden service instead
303 of the official Debian mirror site. I recommend installing
304 <tt
>etckeeper
</tt
> before you start to have a history of the changes
305 done in /etc/.
</p
>
307 <blockquote
><pre
>
308 apt install apt-transport-tor
309 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
310 sed -i
's% http% tor+http%
' /etc/apt/sources.list
311 </pre
></blockquote
>
313 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
314 the sed commands for these too. The sed command is assuming your are
315 using the ftp.debian.org Debian mirror. Adjust the command (or just
316 edit the file manually) to match your mirror.
</p
>
318 <p
>This work in Debian Jessie and later. Note that tools like
319 <tt
>apt-file
</tt
> only recently started using the apt transport
320 system, and do not work with these tor+http URLs. For
321 <tt
>apt-file
</tt
> you need the version currently in experimental,
322 which need a recent apt version currently only in unstable. So if you
323 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
325 <p
>Another advantage from this change is that your machine will start
326 using Tor regularly and at fairly random intervals (every time you
327 update the package lists or upgrade or install a new package), thus
328 masking other Tor traffic done from the same machine. Using Tor will
329 become normal for the machine in question.
</p
>
331 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
332 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
333 enabled. It would be great if it was the default on any Debian
339 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
340 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
342 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
343 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
344 call the car license plate numbers in those days. I would write the
345 numbers down in my little book and compare notes with the other kids
346 to see how many region codes we had seen and if we had seen some
347 exotic or special region codes and numbers. It was a fun game to pass
348 time, as we kids have plenty of it.
</p
>
350 <p
>A few days I came across
351 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
352 project
</a
>, a free software project to automatically discover and
353 report license plates in images and video streams, and provide the
354 "car numbers
" in a machine readable format. I
've been looking for
355 such system for a while now, because I believe it is a bad idea that the
356 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
357 number plate recognition
</a
> tool only is available in the hands of
358 the powerful, and want it to be available also for the powerless to
359 even the score when it comes to surveillance and sousveillance. I
360 discovered the developer
361 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
362 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
363 help him get it into shape to get the package uploaded into the Debian
366 <p
>Today we finally managed to get the package into shape and uploaded
367 it into Debian, where it currently
368 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
369 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
371 <p
>I guess you are wondering why on earth such tool would be useful
372 for the common folks, ie those not running a large government
373 surveillance system? Well, I plan to put it in a computer on my bike
374 and in my car, tracking the cars nearby and allowing me to be notified
375 when number plates on my watch list are discovered. Another use case
376 was suggested by a friend of mine, who wanted to set it up at his home
377 to open the car port automatically when it discovered the plate on his
378 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
379 capable of placing his license plate number of a piece of cardboard to
380 open his car port, men replied that it was always unlocked anyway. I
381 guess for such use case it make sense. I am sure there are other use
382 cases too, for those with imagination and a vision.
</p
>
384 <p
>If you want to build your own version of the Debian package, check
385 out the upstream git source and symlink ./distros/debian to ./debian/
386 before running
"debuild
" to build the source. Or wait a bit until the
387 package show up in unstable.
</p
>
392 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
393 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
395 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
396 <description><p
>Around three years ago, I created
397 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
398 system
</a
> to get a more practical solution in Debian for handing
399 hardware related packages. A GUI system in the isenkram package will
400 present a pop-up dialog when some hardware dongle supported by
401 relevant packages in Debian is inserted into the machine. The same
402 lookup mechanism to detect packages is available as command line
403 tools in the isenkram-cli package. In addition to mapping hardware,
404 it will also map kernel firmware files to packages and make it easy to
405 install needed firmware packages automatically. The key for this
406 system to work is a good way to map hardware to packages, in other
407 words, allow packages to announce what hardware they will work
410 <p
>I started by providing data files in the isenkram source, and
411 adding code to download the latest version of these data files at run
412 time, to ensure every user had the most up to date mapping available.
413 I also added support for storing the mapping in the Packages file in
414 the apt repositories, but did not push this approach because while I
415 was trying to figure out how to best store hardware/package mappings,
416 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
417 appstream system
</a
> was announced. I got in touch and suggested to
418 add the hardware mapping into that data set to be able to use
419 appstream as a data source, and this was accepted at least for the
420 Debian version of appstream.
</p
>
422 <p
>A few days ago using appstream in Debian for this became possible,
423 and today I uploaded a new version
0.20 of isenkram adding support for
424 appstream as a data source for mapping hardware to packages. The only
425 package so far using appstream to announce its hardware support is my
426 pymissile package. I got help from Matthias Klumpp with figuring out
427 how do add the required
428 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
429 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
430 this content:
</p
>
432 <blockquote
><pre
>
433 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
434 &lt;component
&gt;
435 &lt;id
&gt;pymissile
&lt;/id
&gt;
436 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
437 &lt;name
&gt;pymissile
&lt;/name
&gt;
438 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
439 &lt;description
&gt;
441 Pymissile provides a curses interface to control an original
442 Marks and Spencer / Striker USB Missile Launcher, as well as a
443 motion control script to allow a webcamera to control the
446 &lt;/description
&gt;
447 &lt;provides
&gt;
448 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
449 &lt;/provides
&gt;
450 &lt;/component
&gt;
451 </pre
></blockquote
>
453 <p
>The key for isenkram is the component/provides/modalias value,
454 which is a glob style match rule for hardware specific strings
455 (modalias strings) provided by the Linux kernel. In this case, it
456 will map to all USB devices with vendor code
1130 and product code
459 <p
>Note, it is important that the license of all the metadata files
460 are compatible to have permissions to aggregate them into archive wide
461 appstream files. Matthias suggested to use MIT or BSD licenses for
462 these files. A challenge is figuring out a good id for the data, as
463 it is supposed to be globally unique and shared across distributions
464 (in other words, best to coordinate with upstream what to use). But
465 it can be changed later or, so we went with the package name as
466 upstream for this project is dormant.
</p
>
468 <p
>To get the metadata file installed in the correct location for the
469 mirror update scripts to pick it up and include its content the
470 appstream data source, the file must be installed in the binary
471 package under /usr/share/appdata/. I did this by adding the following
472 line to debian/pymissile.install:
</p
>
474 <blockquote
><pre
>
475 debian/pymissile.metainfo.xml usr/share/appdata
476 </pre
></blockquote
>
478 <p
>With that in place, the command line tool isenkram-lookup will list
479 all packages useful on the current computer automatically, and the GUI
480 pop-up handler will propose to install the package not already
481 installed if a hardware dongle is inserted into the machine in
484 <p
>Details of the modalias field in appstream is available from the
485 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
487 <p
>To locate the modalias values of all hardware present in a machine,
488 try running this command on the command line:
</p
>
490 <blockquote
><pre
>
491 cat $(find /sys/devices/|grep modalias)
492 </pre
></blockquote
>
494 <p
>To learn more about the isenkram system, please check out
495 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
496 blog posts tagged isenkram
</a
>.
</p
>
501 <title>The GNU General Public License is not magic pixie dust
</title>
502 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
503 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
504 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
505 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
506 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
507 GPL is not magic pixie dust
</a
>" explain the importance of making sure
508 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
509 I quote the blog post from Paul in full here with his permission:
<p
>
513 <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
>
516 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
518 The first step is to choose a
519 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
522 The next step is, when someone fails to follow that copyleft license,
523 <b
>it must be enforced
</b
><br/
>
525 and its a simple fact of our modern society that such type of
528 is incredibly expensive to do and incredibly difficult to do.
531 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
532 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
533 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
534 0x57</a
></small
></p
>
536 <p
>As the Debian Website
537 <a href=
"https://bugs.debian.org/
794116">used
</a
>
538 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
539 imply, public domain and permissively licensed software can lead to
540 the production of more proprietary software as people discover useful
541 software, extend it and or incorporate it into their hardware or
542 software products. Copyleft licenses such as the GNU GPL were created
543 to close off this avenue to the production of proprietary software but
544 such licenses are not enough. With the ongoing adoption of Free
545 Software by individuals and groups, inevitably the community
's
546 expectations of license compliance are violated, usually out of
547 ignorance of the way Free Software works, but not always. As Karen
548 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
549 Freedom
">FaiF
</a
>
550 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
551 copyleft is nothing if no-one is willing and able to stand up in court
552 to protect it. The reality of today
's world is that legal
553 representation is expensive, difficult and time consuming. With
554 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
555 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
556 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
557 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
558 of the Linux project, Debian and other groups against GPL violations.
559 In March the SFC supported a
560 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
561 by Christoph Hellwig
</a
> against VMware for refusing to
562 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
563 with the GPL
</a
> in relation to their use of parts of the Linux
564 kernel. Since then two of their sponsors pulled corporate funding and
566 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
567 or cancelled their talks
</a
>. As a result they have decided to rely
568 less on corporate funding and more on the broad community of
569 individuals who support Free Software and copyleft. So the SFC has
570 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
571 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
572 a community of folks who stand up for copyleft and the GPL by
573 supporting their work on promoting and supporting copyleft and Free
576 <p
>If you support Free Software,
577 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
578 what the SFC do, agree with their
579 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
580 principles
</a
>, are happy about their
581 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
582 work on a project that is an SFC
583 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
584 just want to stand up for copyleft, please join
585 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
586 Allan Webber
</a
>,
587 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
589 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
590 Bacon
</a
>, myself and
591 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
593 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
594 next week your donation will be
595 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
596 by an anonymous donor. Please also consider asking your employer to
597 match your donation or become a sponsor of SFC. Don
't forget to
598 spread the word about your support for SFC via email, your blog and or
599 social media accounts.
</p
>
603 <p
>I agree with Paul on this topic and just signed up as a Supporter
604 of Software Freedom Conservancy myself. Perhaps you should be a
605 supporter too?
</p
>
610 <title>PGP key transition statement for key EE4E02F9
</title>
611 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
612 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
613 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
614 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
615 set it up properly. I wanted to generate it offline and have it
616 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
617 smart card
</a
> for daily use, and learning how to do it and finding
618 time to sit down with an offline machine almost took forever. But
619 finally I
've been able to complete the process, and have now moved
620 from my old GPG key to a new GPG key. See
621 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
622 full transition statement, signed with both my old and new key
</a
> for
623 the details. This is my new key:
</p
>
626 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
627 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
628 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
629 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
630 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
631 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
632 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
635 <p
>The key can be downloaded from the OpenPGP key servers, signed by
636 my old key.
</p
>
638 <p
>If you signed my old key
639 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
640 I
'd very much appreciate a signature on my new key, details and
641 instructions in the transition statement. I m happy to reciprocate if
642 you have a similarly signed transition statement to present.
</p
>
647 <title>The life and death of a laptop battery
</title>
648 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
650 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
651 <description><p
>When I get a new laptop, the battery life time at the start is OK.
652 But this do not last. The last few laptops gave me a feeling that
653 within a year, the life time is just a fraction of what it used to be,
654 and it slowly become painful to use the laptop without power connected
655 all the time. Because of this, when I got a new Thinkpad X230 laptop
656 about two years ago, I decided to monitor its battery state to have
657 more hard facts when the battery started to fail.
</p
>
659 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
661 <p
>First I tried to find a sensible Debian package to record the
662 battery status, assuming that this must be a problem already handled
663 by someone else. I found
664 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
665 which collects statistics from the battery, but it was completely
666 broken. I sent a few suggestions to the maintainer, but decided to
667 write my own collector as a shell script while I waited for feedback
669 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
670 blog post about the battery development on a MacBook Air
</a
> I also
672 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
673 available in Debian.
</p
>
675 <p
>I started my collector
2013-
07-
15, and it has been collecting
676 battery stats ever since. Now my
677 /var/log/hjemmenett-battery-status.log file contain around
115,
000
678 measurements, from the time the battery was working great until now,
679 when it is unable to charge above
7% of original capacity. My
680 collector shell script is quite simple and look like this:
</p
>
685 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
687 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
688 logfile=/var/log/hjemmenett-battery-status.log
690 files=
"manufacturer model_name technology serial_number \
691 energy_full energy_full_design energy_now cycle_count status
"
693 if [ ! -e
"$logfile
" ] ; then
695 printf
"timestamp,
"
697 printf
"%s,
" $f
700 )
> "$logfile
"
704 # Print complete message in one echo call, to avoid race condition
705 # when several log processes run in parallel.
706 msg=$(printf
"%s,
" $(date +%s); \
707 for f in $files; do \
708 printf
"%s,
" $(cat $f); \
710 echo
"$msg
"
713 cd /sys/class/power_supply
716 (cd $bat
&& log_battery
>> "$logfile
")
720 <p
>The script is called when the power management system detect a
721 change in the power status (power plug in or out), and when going into
722 and out of hibernation and suspend. In addition, it collect a value
723 every
10 minutes. This make it possible for me know when the battery
724 is discharging, charging and how the maximum charge change over time.
725 The code for the Debian package
726 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
727 available on github
</a
>.
</p
>
729 <p
>The collected log file look like this:
</p
>
732 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
733 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
735 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
736 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
739 <p
>I wrote a small script to create a graph of the charge development
740 over time. This graph depicted above show the slow death of my laptop
743 <p
>But why is this happening? Why are my laptop batteries always
744 dying in a year or two, while the batteries of space probes and
745 satellites keep working year after year. If we are to believe
746 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
747 University
</a
>, the cause is me charging the battery whenever I have a
748 chance, and the fix is to not charge the Lithium-ion batteries to
100%
749 all the time, but to stay below
90% of full charge most of the time.
750 I
've been told that the Tesla electric cars
751 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
752 the charge of their batteries to
80%
</a
>, with the option to charge to
753 100% when preparing for a longer trip (not that I would want a car
754 like Tesla where rights to privacy is abandoned, but that is another
755 story), which I guess is the option we should have for laptops on
758 <p
>Is there a good and generic way with Linux to tell the battery to
759 stop charging at
80%, unless requested to charge to
100% once in
760 preparation for a longer trip? I found
761 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
762 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
763 80%
</a
>, but could not get it to work (kernel module refused to
766 <p
>I wonder why the battery capacity was reported to be more than
100%
767 at the start. I also wonder why the
"full capacity
" increases some
768 times, and if it is possible to repeat the process to get the battery
769 back to design capacity. And I wonder if the discharge and charge
770 speed change over time, or if this stay the same. I did not yet try
771 to write a tool to calculate the derivative values of the battery
772 level, but suspect some interesting insights might be learned from
775 <p
>Update
2015-
09-
24: I got a tip to install the packages
776 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
777 packages instead of the tp-smapi-dkms package I had tried to use
778 initially, and use
'tlp setcharge
40 80' to change when charging start
779 and stop. I
've done so now, but expect my existing battery is toast
780 and need to be replaced. The proposal is unfortunately Thinkpad
786 <title>New laptop - some more clues and ideas based on feedback
</title>
787 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
789 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
790 <description><p
>Several people contacted me after my previous blog post about my
791 need for a new laptop, and provided very useful feedback. I wish to
792 thank every one of these. Several pointed me to the possibility of
793 fixing my X230, and I am already in the process of getting Lenovo to
794 do so thanks to the on site, next day support contract covering the
795 machine. But the battery is almost useless (I expect to replace it
796 with a non-official battery) and I do not expect the machine to live
797 for many more years, so it is time to plan its replacement. If I did
798 not have a support contract, it was suggested to find replacement parts
799 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
800 might present a language barrier as I do not understand French.
</p
>
802 <p
>One tip I got was to use the
803 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
804 compare laptop models. It seem to have more models available than
805 prisjakt.no. Another tip I got from someone I know have similar
806 keyboard preferences was that the HP EliteBook
840 keyboard is not
807 very good, and this matches my experience with earlier EliteBook
808 keyboards I tested. Because of this, I will not consider it any further.
810 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
811 newest Thinkpad X model. The keyboard reintroduces mouse buttons
812 (which is missing from the X240), and is working fairly well with
813 Debian Sid/Unstable according to
814 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
815 got on the keyboard quality are not consistent. Some say the keyboard
816 is good, others say it is ok, while others say it is not very good.
817 Those with experience from X41 and and X60 agree that the X250
818 keyboard is not as good as those trusty old laptops, and suggest I
819 keep and fix my X230 instead of upgrading, or get a used X230 to
820 replace it. I
'm also told that the X250 lack leds for caps lock, disk
821 activity and battery status, which is very convenient on my X230. I
'm
822 also told that the CPU fan is running very often, making it a bit
823 noisy. In any case, the X250 do not work out of the box with Debian
824 Stable/Jessie, one of my requirements.
</p
>
826 <p
>I have also gotten a few vendor proposals, one was
827 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
828 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
829 The latter look very attractive to me.
</p
>
831 <p
>Again, thank you all for the very useful feedback. It help a lot
832 as I keep looking for a replacement.
</p
>
834 <p
>Update
2015-
07-
06: I was recommended to check out the
835 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
837 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
838 thinkpad X models
</a
>, and provide one year warranty.
</p
>
843 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
844 <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>
845 <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>
846 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
847 <description><p
>My primary work horse laptop is failing, and will need a
848 replacement soon. The left
5 cm of the screen on my Thinkpad X230
849 started flickering yesterday, and I suspect the cause is a broken
850 cable, as changing the angle of the screen some times get rid of the
851 flickering.
</p
>
853 <p
>My requirements have not really changed since I bought it, and is
855 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
856 described them in
2013</a
>. The last time I bought a laptop, I had
858 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
859 where I could select at least a few of the requirements (mouse pin,
860 wifi, weight) and go through the rest manually. Three button mouse
861 and a good keyboard is not available as an option, and all the three
862 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
863 G2) lack three mouse buttons). It is also unclear to me how good the
864 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
865 the keyboard, even if the quality and robustness in the X series have
866 deteriorated since X41.
</p
>
868 <p
>I wonder how I can find a sensible laptop when none of the options
869 seem sensible to me? Are there better services around to search the
870 set of available laptops for features? Please send me an email if you
871 have suggestions.
</p
>
873 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
874 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
875 of endorsed hardware
</a
>, which is useful background information.
</p
>
880 <title>How to stay with sysvinit in Debian Jessie
</title>
881 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
882 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
883 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
884 <description><p
>By now, it is well known that Debian Jessie will not be using
885 sysvinit as its boot system by default. But how can one keep using
886 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
888 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
889 Schubert
</a
> and
890 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
893 <p
>If you already are using Wheezy and want to upgrade to Jessie and
894 keep sysvinit as your boot system, create a file
895 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
896 you upgrade:
</p
>
898 <p
><blockquote
><pre
>
899 Package: systemd-sysv
900 Pin: release o=Debian
902 </pre
></blockquote
><p
>
904 <p
>This file content will tell apt and aptitude to not consider
905 installing systemd-sysv as part of any installation and upgrade
906 solution when resolving dependencies, and thus tell it to avoid
907 systemd as a default boot system. The end result should be that the
908 upgraded system keep using sysvinit.
</p
>
910 <p
>If you are installing Jessie for the first time, there is no way to
911 get sysvinit installed by default (debootstrap used by
912 debian-installer have no option for this), but one can tell the
913 installer to switch to sysvinit before the first boot. Either by
914 using a kernel argument to the installer, or by adding a line to the
915 preseed file used. First, the kernel command line argument:
917 <p
><blockquote
><pre
>
918 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
919 </pre
></blockquote
><p
>
921 <p
>Next, the line to use in a preseed file:
</p
>
923 <p
><blockquote
><pre
>
924 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
925 </pre
></blockquote
><p
>
927 <p
>One can of course also do this after the first boot by installing
928 the sysvinit-core package.
</p
>
930 <p
>I recommend only using sysvinit if you really need it, as the
931 sysvinit boot sequence in Debian have several hardware specific bugs
932 on Linux caused by the fact that it is unpredictable when hardware
933 devices show up during boot. But on the other hand, the new default
934 boot system still have a few rough edges I hope will be fixed before
935 Jessie is released.
</p
>
937 <p
>Update
2014-
11-
26: Inspired by
938 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
939 blog post by Torsten Glaser
</a
>, added --purge to the preseed
945 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
946 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
948 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
949 <description><p
>The right to communicate with your friends and family in private,
950 without anyone snooping, is a right every citicen have in a liberal
951 democracy. But this right is under serious attack these days.
</p
>
953 <p
>A while back it occurred to me that one way to make the dragnet
954 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
955 the whisleblower Snowden) more expensive for Internet email,
956 is to deliver all email using SMTP via Tor. Such SMTP option would be
957 a nice addition to the FreedomBox project if we could send email
958 between FreedomBox machines without leaking metadata about the emails
959 to the people peeking on the wire. I
960 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
961 this on the FreedomBox project mailing list in October
</a
> and got a
962 lot of useful feedback and suggestions. It also became obvious to me
963 that this was not a novel idea, as the same idea was tested and
964 documented by Johannes Berg as early as
2006, and both
965 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
966 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
967 propose a similar method / protocol to pass emails between users.
</p
>
969 <p
>To implement such system one need to set up a Tor hidden service
970 providing the SMTP protocol on port
25, and use email addresses
971 looking like username@hidden-service-name.onion. With such addresses
972 the connections to port
25 on hidden-service-name.onion using Tor will
973 go to the correct SMTP server. To do this, one need to configure the
974 Tor daemon to provide the hidden service and the mail server to accept
975 emails for this .onion domain. To learn more about Exim configuration
976 in Debian and test the design provided by Johannes Berg in his FAQ, I
977 set out yesterday to create a Debian package for making it trivial to
978 set up such SMTP over Tor service based on Debian. Getting it to work
979 were fairly easy, and
980 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
981 source code for the Debian package
</a
> is available from github. I
982 plan to move it into Debian if further testing prove this to be a
983 useful approach.
</p
>
985 <p
>If you want to test this, set up a blank Debian machine without any
986 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
987 get rid of exim4). Install tor, clone the git repository mentioned
988 above, build the deb and install it on the machine. Next, run
989 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
990 the instructions to get the service up and running. Restart tor and
991 exim when it is done, and test mail delivery using swaks like
994 <p
><blockquote
><pre
>
995 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
996 --to fbx@dutlqrrmjhtfa3vp.onion
997 </pre
></blockquote
></p
>
999 <p
>This will test the SMTP delivery using tor. Replace the email
1000 address with your own address to test your server. :)
</p
>
1002 <p
>The setup procedure is still to complex, and I hope it can be made
1003 easier and more automatic. Especially the tor setup need more work.
1004 Also, the package include a tor-smtp tool written in C, but its task
1005 should probably be rewritten in some script language to make the deb
1006 architecture independent. It would probably also make the code easier
1007 to review. The tor-smtp tool currently need to listen on a socket for
1008 exim to talk to it and is started using xinetd. It would be better if
1009 no daemon and no socket is needed. I suspect it is possible to get
1010 exim to run a command line tool for delivery instead of talking to a
1011 socket, and hope to figure out how in a future version of this
1014 <p
>Until I wipe my test machine, I can be reached using the
1015 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1016 SMTorP. :)
</p
>
1021 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1022 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1023 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1024 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1025 <description><p
>If you ever had to moderate a mailman list, like the ones on
1026 alioth.debian.org, you know the web interface is fairly slow to
1027 operate. First you visit one web page, enter the moderation password
1028 and get a new page shown with a list of all the messages to moderate
1029 and various options for each email address. This take a while for
1030 every list you moderate, and you need to do it regularly to do a good
1031 job as a list moderator. But there is a quick alternative,
1032 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1033 listadmin program
</a
>. It allow you to check lists for new messages
1034 to moderate in a fraction of a second. Here is a test run on two
1035 lists I recently took over:
</p
>
1037 <p
><blockquote
><pre
>
1038 % time listadmin xiph
1039 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1040 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1046 </pre
></blockquote
></p
>
1048 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1049 there are no message in the moderation queue. Every morning I
1050 currently moderate
68 mailman lists, and it normally take around two
1051 minutes. When I took over the two pkg-xiph lists above a few days
1052 ago, there were
400 emails waiting in the moderator queue. It took me
1053 less than
15 minutes to process them all using the listadmin
1056 <p
>If you install
1057 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1058 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1059 with content like this, the moderation task is a breeze:
</p
>
1061 <p
><blockquote
><pre
>
1062 username username@example.org
1065 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1068 adminurl https://{domain}/mailman/admindb/{list}
1069 mailman-list@lists.example.com
1072 other-list@otherserver.example.org
1073 </pre
></blockquote
></p
>
1075 <p
>There are other options to set as well. Check the manual page to
1076 learn the details.
</p
>
1078 <p
>If you are forced to moderate lists on a mailman installation where
1079 the SSL certificate is self signed or not properly signed by a
1080 generally accepted signing authority, you can set a environment
1081 variable when calling listadmin to disable SSL verification:
</p
>
1083 <p
><blockquote
><pre
>
1084 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1085 </pre
></blockquote
></p
>
1087 <p
>If you want to moderate a subset of the lists you take care of, you
1088 can provide an argument to the listadmin script like I do in the
1089 initial screen dump (the xiph argument). Using an argument, only
1090 lists matching the argument string will be processed. This make it
1091 quick to accept messages if you notice the moderation request in your
1094 <p
>Without the listadmin program, I would never be the moderator of
68
1095 mailing lists, as I simply do not have time to spend on that if the
1096 process was any slower. The listadmin program have saved me hours of
1097 time I could spend elsewhere over the years. It truly is nice free
1100 <p
>As usual, if you use Bitcoin and want to show your support of my
1101 activities, please send Bitcoin donations to my address
1102 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1104 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1105 configuration example. Also, I
've been told that the
1106 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1112 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1113 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1114 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1115 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1116 <description><p
>When PXE installing laptops with Debian, I often run into the
1117 problem that the WiFi card require some firmware to work properly.
1118 And it has been a pain to fix this using preseeding in Debian.
1119 Normally something more is needed. But thanks to
1120 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1121 package
</a
> and its recent tasksel extension, it has now become easy
1122 to do this using simple preseeding.
</p
>
1124 <p
>The isenkram-cli package provide tasksel tasks which will install
1125 firmware for the hardware found in the machine (actually, requested by
1126 the kernel modules for the hardware). (It can also install user space
1127 programs supporting the hardware detected, but that is not the focus
1128 of this story.)
</p
>
1130 <p
>To get this working in the default installation, two preeseding
1131 values are needed. First, the isenkram-cli package must be installed
1132 into the target chroot (aka the hard drive) before tasksel is executed
1133 in the pkgsel step of the debian-installer system. This is done by
1134 preseeding the base-installer/includes debconf value to include the
1135 isenkram-cli package. The package name is next passed to debootstrap
1136 for installation. With the isenkram-cli package in place, tasksel
1137 will automatically use the isenkram tasks to detect hardware specific
1138 packages for the machine being installed and install them, because
1139 isenkram-cli contain tasksel tasks.
</p
>
1141 <p
>Second, one need to enable the non-free APT repository, because
1142 most firmware unfortunately is non-free. This is done by preseeding
1143 the apt-mirror-setup step. This is unfortunate, but for a lot of
1144 hardware it is the only option in Debian.
</p
>
1146 <p
>The end result is two lines needed in your preseeding file to get
1147 firmware installed automatically by the installer:
</p
>
1149 <p
><blockquote
><pre
>
1150 base-installer base-installer/includes string isenkram-cli
1151 apt-mirror-setup apt-setup/non-free boolean true
1152 </pre
></blockquote
></p
>
1154 <p
>The current version of isenkram-cli in testing/jessie will install
1155 both firmware and user space packages when using this method. It also
1156 do not work well, so use version
0.15 or later. Installing both
1157 firmware and user space packages might give you a bit more than you
1158 want, so I decided to split the tasksel task in two, one for firmware
1159 and one for user space programs. The firmware task is enabled by
1160 default, while the one for user space programs is not. This split is
1161 implemented in the package currently in unstable.
</p
>
1163 <p
>If you decide to give this a go, please let me know (via email) how
1164 this recipe work for you. :)
</p
>
1166 <p
>So, I bet you are wondering, how can this work. First and
1167 foremost, it work because tasksel is modular, and driven by whatever
1168 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1169 isenkram-cli package place two files for tasksel to find. First there
1170 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1172 <p
><blockquote
><pre
>
1173 Task: isenkram-packages
1175 Description: Hardware specific packages (autodetected by isenkram)
1176 Based on the detected hardware various hardware specific packages are
1178 Test-new-install: show show
1180 Packages: for-current-hardware
1182 Task: isenkram-firmware
1184 Description: Hardware specific firmware packages (autodetected by isenkram)
1185 Based on the detected hardware various hardware specific firmware
1186 packages are proposed.
1187 Test-new-install: mark show
1189 Packages: for-current-hardware-firmware
1190 </pre
></blockquote
></p
>
1192 <p
>The key parts are Test-new-install which indicate how the task
1193 should be handled and the Packages line referencing to a script in
1194 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1195 list of packages to install. The for-current-hardware-firmware script
1196 look like this to list relevant firmware for the machine:
1198 <p
><blockquote
><pre
>
1201 PATH=/usr/sbin:$PATH
1203 isenkram-autoinstall-firmware -l
1204 </pre
></blockquote
></p
>
1206 <p
>With those two pieces in place, the firmware is installed by
1207 tasksel during the normal d-i run. :)
</p
>
1209 <p
>If you want to test what tasksel will install when isenkram-cli is
1210 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1211 --new-install
</tt
> to get the list of packages that tasksel would
1214 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1215 pilots in testing this feature, as isenkram is used there now to
1216 install firmware, replacing the earlier scripts.
</p
>
1221 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1222 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1224 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1225 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1226 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1227 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1228 on a screen normally showing the bread types and prizes:
</p
>
1230 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1232 <p
>If it had booted as it was supposed to, I would never had known
1233 about this hidden Linux installation. It is interesting what
1234 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1239 <title>New lsdvd release version
0.17 is ready
</title>
1240 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1242 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1243 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1244 got a new set of developers a few weeks ago, after the original
1245 developer decided to step down and pass the project to fresh blood.
1246 This project is now maintained by Petter Reinholdtsen and Steve
1249 <p
>I just wrapped up
1250 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1251 new lsdvd release
</a
>, available in git or from
1252 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1253 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1258 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1259 <li
>Check for garbage in the program chains, which indicate that a track is
1260 non-existant, to work around additional copy protection
</li
>
1261 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
1262 <li
>Fix pallete display of first entry
</li
>
1263 <li
>Fix include orders
</li
>
1264 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
1265 <li
>Fix the chapter count
</li
>
1266 <li
>Make sure the array size and the array limit used when initialising
1267 the palette size is the same.
</li
>
1268 <li
>Fix array printing.
</li
>
1269 <li
>Correct subsecond calculations.
</li
>
1270 <li
>Add sector information to the output format.
</li
>
1271 <li
>Clean up code to be closer to ANSI C and compile without warnings
1272 with more GCC compiler warnings.
</li
>
1276 <p
>This change bring together patches for lsdvd in use in various
1277 Linux and Unix distributions, as well as patches submitted to the
1278 project the last nine years. Please check it out. :)
</p
>
1283 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
1284 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
1285 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
1286 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
1287 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1288 project
</a
> provide a Linux solution for schools, including a
1289 powerful desktop with education software, a central server providing
1290 web pages, user database, user home directories, central login and PXE
1291 boot of both clients without disk and the installation to install Debian
1292 Edu on machines with disk (and a few other services perhaps to small
1293 to mention here). We in the Debian Edu team are currently working on
1294 the Jessie based version, trying to get everything in shape before the
1295 freeze, to avoid having to maintain our own package repository in the
1297 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
1298 status
</a
> can be seen on the Debian wiki, and there is still heaps of
1299 work left. Some fatal problems block testing, breaking the installer,
1300 but it is possible to work around these to get anyway. Here is a
1301 recipe on how to get the installation limping along.
</p
>
1303 <p
>First, download the test ISO via
1304 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
1305 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
1307 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
1308 The ISO build was broken on Tuesday, so we do not get a new ISO every
1309 12 hours or so, but thankfully the ISO we already got we are able to
1310 install with some tweaking.
</p
>
1312 <p
>When you get to the Debian Edu profile question, go to tty2
1313 (use Alt-Ctrl-F2), run
</p
>
1315 <p
><blockquote
><pre
>
1316 nano /usr/bin/edu-eatmydata-install
1317 </pre
></blockquote
></p
>
1319 <p
>and add
'exit
0' as the second line, disabling the eatmydata
1320 optimization. Return to the installation, select the profile you want
1321 and continue. Without this change, exim4-config will fail to install
1322 due to a known bug in eatmydata.
</p
>
1324 <p
>When you get the grub question at the end, answer /dev/sda (or if
1325 this do not work, figure out what your correct value would be. All my
1326 test machines need /dev/sda, so I have no advice if it do not fit
1327 your need.
</p
>
1329 <p
>If you installed a profile including a graphical desktop, log in as
1330 root after the initial boot from hard drive, and install the
1331 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1332 or mate. If you want several desktop options, install more than one
1333 metapackage. Once this is done, reboot and you should have a working
1334 graphical login screen. This workaround should no longer be needed
1335 once the education-tasks package version
1.801 enter testing in two
1338 <p
>I believe the ISO build will start working on two days when the new
1339 tasksel package enter testing and Steve McIntyre get a chance to
1340 update the debian-cd git repository. The eatmydata, grub and desktop
1341 issues are already fixed in unstable and testing, and should show up
1342 on the ISO as soon as the ISO build start working again. Well the
1343 eatmydata optimization is really just disabled. The proper fix
1344 require an upload by the eatmydata maintainer applying the patch
1345 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
1346 The rest have proper fixes in unstable.
</p
>
1348 <p
>I hope this get you going with the installation testing, as we are
1349 quickly running out of time trying to get our Jessie based
1350 installation ready before the distribution freeze in a month.
</p
>
1355 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
1356 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
1357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
1358 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
1359 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
1360 to handle my fairly large DVD collection. It is a nice command line
1361 tool to get details about a DVD, like title, tracks, track length,
1362 etc, in XML, Perl or human readable format. But lsdvd have not seen
1363 any new development since
2006 and had a few irritating bugs affecting
1364 its use with some DVDs. Upstream seemed to be dead, and in January I
1365 sent a small probe asking for a version control repository for the
1366 project, without any reply. But I use it regularly and would like to
1367 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
1368 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
1369 the project admin, and after getting a reply from him explaining that
1370 he was no longer interested in the project, I asked if I could take
1371 over. And yesterday, I became project admin.
</p
>
1373 <p
>I
've been in touch with a Gentoo developer and the Debian
1374 maintainer interested in joining forces to maintain the upstream
1375 project, and I hope we can get a new release out fairly quickly,
1376 collecting the patches spread around on the internet into on place.
1377 I
've added the relevant Debian patches to the freshly created git
1378 repository, and expect the Gentoo patches to make it too. If you got
1379 a DVD collection and care about command line tools, check out
1380 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
1381 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1382 list
</a
>. :)
</p
>
1387 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1388 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1390 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1391 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1392 a lot quicker. When we install more than
2000 packages in
1393 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1394 tasksel in the installer, unpacking the binary packages take forever.
1395 A part of the slow I/O issue was discussed in
1396 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1397 much file system sync-ing done by dpkg, which is the package
1398 responsible for unpacking the binary packages. Other parts (like code
1399 executed by postinst scripts) might also sync to disk during
1400 installation. All this sync-ing to disk do not really make sense to
1401 me. If the machine crash half-way through, I start over, I do not try
1402 to salvage the half installed system. So the failure sync-ing is
1403 supposed to protect against, hardware or system crash, is not really
1404 relevant while the installer is running.
</p
>
1406 <p
>A few days ago, I thought of a way to get rid of all the file
1407 system sync()-ing in a fairly non-intrusive way, without the need to
1408 change the code in several packages. The idea is not new, but I have
1409 not heard anyone propose the approach using dpkg-divert before. It
1410 depend on the small and clever package
1411 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1412 uses LD_PRELOAD to replace the system functions for syncing data to
1413 disk with functions doing nothing, thus allowing programs to live
1414 dangerous while speeding up disk I/O significantly. Instead of
1415 modifying the implementation of dpkg, apt and tasksel (which are the
1416 packages responsible for selecting, fetching and installing packages),
1417 it occurred to me that we could just divert the programs away, replace
1418 them with a simple shell wrapper calling
1419 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1420 Two days ago I decided to test the idea, and wrapped up a simple
1421 implementation for the Debian Edu udeb.
</p
>
1423 <p
>The effect was stunning. In my first test it reduced the running
1424 time of the pkgsel step (installing tasks) from
64 to less than
44
1425 minutes (
20 minutes shaved off the installation) on an old Dell
1426 Latitude D505 machine. I am not quite sure what the optimised time
1427 would have been, as I messed up the testing a bit, causing the debconf
1428 priority to get low enough for two questions to pop up during
1429 installation. As soon as I saw the questions I moved the installation
1430 along, but do not know how long the question were holding up the
1431 installation. I did some more measurements using Debian Edu Jessie,
1432 and got these results. The time measured is the time stamp in
1433 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1434 "pkgsel: finishing up
" lines, if you want to do the same measurement
1435 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1436 timing thus do not depend on how quickly the user handle the tasksel
1439 <p
><table
>
1442 <th
>Machine/setup
</th
>
1443 <th
>Original tasksel
</th
>
1444 <th
>Optimised tasksel
</th
>
1445 <th
>Reduction
</th
>
1449 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1450 <td
>64 min (
07:
46-
08:
50)
</td
>
1451 <td
><44 min (
11:
27-
12:
11)
</td
>
1452 <td
>>20 min
18%
</td
>
1456 <td
>Latitude D505 Roaming LXDE
</td
>
1457 <td
>57 min (
08:
48-
09:
45)
</td
>
1458 <td
>34 min (
07:
43-
08:
17)
</td
>
1459 <td
>23 min
40%
</td
>
1463 <td
>Latitude D505 Minimal
</td
>
1464 <td
>22 min (
10:
37-
10:
59)
</td
>
1465 <td
>11 min (
11:
16-
11:
27)
</td
>
1466 <td
>11 min
50%
</td
>
1470 <td
>Thinkpad X200 Minimal
</td
>
1471 <td
>6 min (
08:
19-
08:
25)
</td
>
1472 <td
>4 min (
08:
04-
08:
08)
</td
>
1473 <td
>2 min
33%
</td
>
1477 <td
>Thinkpad X200 Roaming KDE
</td
>
1478 <td
>19 min (
09:
21-
09:
40)
</td
>
1479 <td
>15 min (
10:
25-
10:
40)
</td
>
1480 <td
>4 min
21%
</td
>
1483 </table
></p
>
1485 <p
>The test is done using a netinst ISO on a USB stick, so some of the
1486 time is spent downloading packages. The connection to the Internet
1487 was
100Mbit/s during testing, so downloading should not be a
1488 significant factor in the measurement. Download typically took a few
1489 seconds to a few minutes, depending on the amount of packages being
1490 installed.
</p
>
1492 <p
>The speedup is implemented by using two hooks in
1493 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
1494 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
1495 finish-install.d hook to remove the divert at the end of the
1496 installation. I picked the pre-pkgsel.d hook instead of the
1497 post-base-installer.d hook because I test using an ISO without the
1498 eatmydata package included, and the post-base-installer.d hook in
1499 Debian Edu can only operate on packages included in the ISO. The
1500 negative effect of this is that I am unable to activate this
1501 optimization for the kernel installation step in d-i. If the code is
1502 moved to the post-base-installer.d hook, the speedup would be larger
1503 for the entire installation.
</p
>
1505 <p
>I
've implemented this in the
1506 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
1507 git repository, and plan to provide the optimization as part of the
1508 Debian Edu installation. If you want to test this yourself, you can
1509 create two files in the installer (or in an udeb). One shell script
1510 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
1512 <p
><blockquote
><pre
>
1515 . /usr/share/debconf/confmodule
1517 logger -t my-pkgsel
"info: $*
"
1520 logger -t my-pkgsel
"error: $*
"
1522 override_install() {
1523 apt-install eatmydata || true
1524 if [ -x /target/usr/bin/eatmydata ] ; then
1525 for bin in dpkg apt-get aptitude tasksel ; do
1527 # Test that the file exist and have not been diverted already.
1528 if [ -f /target$file ] ; then
1529 info
"diverting $file using eatmydata
"
1530 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
1531 > /target$file.edu
1532 chmod
755 /target$file.edu
1533 in-target dpkg-divert --package debian-edu-config \
1534 --rename --quiet --add $file
1535 ln -sf ./$bin.edu /target$file
1537 error
"unable to divert $file, as it is missing.
"
1541 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
1546 </pre
></blockquote
></p
>
1548 <p
>To clean up, another shell script should go into
1549 /usr/lib/finish-install.d/ with code like this:
1551 <p
><blockquote
><pre
>
1553 . /usr/share/debconf/confmodule
1555 logger -t my-finish-install
"error: $@
"
1557 remove_install_override() {
1558 for bin in dpkg apt-get aptitude tasksel ; do
1560 if [ -x /target$file.edu ] ; then
1562 in-target dpkg-divert --package debian-edu-config \
1563 --rename --quiet --remove $file
1566 error
"Missing divert for $file.
"
1569 sync # Flush file buffers before continuing
1572 remove_install_override
1573 </pre
></blockquote
></p
>
1575 <p
>In Debian Edu, I placed both code fragments in a separate script
1576 edu-eatmydata-install and call it from the pre-pkgsel.d and
1577 finish-install.d scripts.
</p
>
1579 <p
>By now you might ask if this change should get into the normal
1580 Debian installer too? I suspect it should, but am not sure the
1581 current debian-installer coordinators find it useful enough. It also
1582 depend on the side effects of the change. I
'm not aware of any, but I
1583 guess we will see if the change is safe after some more testing.
1584 Perhaps there is some package in Debian depending on sync() and
1585 fsync() having effect? Perhaps it should go into its own udeb, to
1586 allow those of us wanting to enable it to do so without affecting
1589 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
1590 will break installation of all programs using gnutls because of
1591 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
1592 eatmydata package in Debian will solve it.
</p
>
1594 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
1595 the optimization work again. And I have discovered that the
1596 dpkg-divert trick is not really needed and implemented a slightly
1597 simpler approach as part of the debian-edu-install package. See
1598 tools/edu-eatmydata-install in the source package.
</p
>
1600 <p
>Update
2014-
11-
11: Unfortunately, a new
1601 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
1602 triggering on i386 made it into testing, and broke this installation
1603 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
1604 request
768893</a
> is accepted, it should be working again.
</p
>
1609 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
1610 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
1611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
1612 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
1613 <description><p
>Yesterday, I had the pleasure of attending a talk with the
1614 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
1615 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
1616 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
1617 learn that there is a large set of publicly available key servers to
1618 use when looking for peoples public key. So far I have used
1619 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1620 were misbehaving, but those days are ended. The servers I have used
1621 up until yesterday have been slow and some times unavailable. I hope
1622 those problems are gone now.
</p
>
1624 <p
>Behind the round robin DNS entry of the
1625 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
1626 there is a pool of more than
100 keyservers which are checked every
1627 day to ensure they are well connected and up to date. It must be
1628 better than what I have used so far. :)
</p
>
1630 <p
>Yesterdays speaker told me that the service is the default
1631 keyserver provided by the default configuration in GnuPG, but this do
1632 not seem to be used in Debian. Perhaps it should?
</p
>
1634 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
1637 <p
><blockquote
><pre
>
1638 keyserver pool.sks-keyservers.net
1639 </pre
></blockquote
></p
>
1641 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
1642 entries in DNS. Just for fun, I did just that at work, so now every
1643 user of GnuPG at the University of Oslo should find a OpenGPG
1644 keyserver automatically should their need it:
</p
>
1646 <p
><blockquote
><pre
>
1647 % host -t srv _pgpkey-http._tcp.uio.no
1648 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
1650 </pre
></blockquote
></p
>
1652 <p
>Now if only
1653 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
1654 HKP lookup protocol
</a
> supported finding signature paths, I would be
1655 very happy. It can look up a given key or search for a user ID, but I
1656 normally do not want that, but to find a trust path from my key to
1657 another key. Given a user ID or key ID, I would like to find (and
1658 download) the keys representing a signature path from my key to the
1659 key in question, to be able to get a trust path between the two keys.
1660 This is as far as I can tell not possible today. Perhaps something
1661 for a future version of the protocol?
</p
>
1666 <title>From English wiki to translated PDF and epub via Docbook
</title>
1667 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
1668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
1669 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
1670 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1671 project
</a
> provide an instruction manual for teachers, system
1672 administrators and other users that contain useful tips for setting up
1673 and maintaining a Debian Edu installation. This text is about how the
1674 text processing of this manual is handled in the project.
</p
>
1676 <p
>One goal of the project is to provide information in the native
1677 language of its users, and for this we need to handle translations.
1678 But we also want to make sure each language contain the same
1679 information, so for this we need a good way to keep the translations
1680 in sync. And we want it to be easy for our users to improve the
1681 documentation, avoiding the need to learn special formats or tools to
1682 contribute, and the obvious way to do this is to make it possible to
1683 edit the documentation using a web browser. We also want it to be
1684 easy for translators to keep the translation up to date, and give them
1685 help in figuring out what need to be translated. Here is the list of
1686 tools and the process we have found trying to reach all these
1689 <p
>We maintain the authoritative source of our manual in the
1690 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
1691 wiki
</a
>, as several wiki pages written in English. It consist of one
1692 front page with references to the different chapters, several pages
1693 for each chapter, and finally one
"collection page
" gluing all the
1694 chapters together into one large web page (aka
1695 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
1696 AllInOne page
</a
>). The AllInOne page is the one used for further
1697 processing and translations. Thanks to the fact that the
1698 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
1699 wiki.debian.org support exporting pages in
1700 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
1701 the list of pages to export using the raw version of the AllInOne
1702 page, loop over each of them to generate a Docbook XML version of the
1703 manual. This process also download images and transform image
1704 references to use the locally downloaded images. The generated
1705 Docbook XML files are slightly broken, so some post-processing is done
1706 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
1707 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1708 a handfull of images. The XML file can now be used to generate PDF, HTML
1709 and epub versions of the English manual. This is the basic step of
1710 our process, making PDF (using dblatex), HTML (using xsltproc) and
1711 epub (using dbtoepub) version from Docbook XML, and the resulting files
1712 are placed in the debian-edu-doc-en binary package.
</p
>
1714 <p
>But English documentation is not enough for us. We want translated
1715 documentation too, and we want to make it easy for translators to
1716 track the English original. For this we use the
1717 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
1718 which allow us to transform the English Docbook XML file into a
1719 translation file (a .pot file), usable with the normal gettext based
1720 translation tools used by those translating free software. The pot
1721 file is used to create and maintain translation files (several .po
1722 files), which the translations update with the native language
1723 translations of all titles, paragraphs and blocks of text in the
1724 original. The next step is combining the original English Docbook XML
1725 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1726 create a translated Docbook XML file (in this case
1727 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1728 translated, if the translation is not complete) Docbook XML file can
1729 then be used like the original to create a PDF, HTML and epub version
1730 of the documentation.
</p
>
1732 <p
>The translators use different tools to edit the .po files. We
1734 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
1735 while some use emacs and vi, others can use web based editors like
1736 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
1737 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
1738 is where the .po file end up, in our git repository. Updated
1739 translations can either be committed directly to git, or submitted as
1740 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
1741 against the debian-edu-doc package
</a
>.
</p
>
1743 <p
>One challenge is images, which both might need to be translated (if
1744 they show translated user applications), and are needed in different
1745 formats when creating PDF and HTML versions (epub is a HTML version in
1746 this regard). For this we transform the original PNG images to the
1747 needed density and format during build, and have a way to provide
1748 translated images by storing translated versions in
1749 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1750 package maintainers know more.
</p
>
1752 <p
>If you wonder what the result look like, we provide
1753 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
1754 of the documentation packages on the web
</a
>. See for example the
1755 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
1756 PDF version
</a
> or the
1757 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
1758 HTML version
</a
>. We do not yet build the epub version by default,
1759 but perhaps it will be done in the future.
</p
>
1761 <p
>To learn more, check out
1762 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
1763 debian-edu-doc package
</a
>,
1764 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
1765 manual on the wiki
</a
> and
1766 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
1767 translation instructions
</a
> in the manual.
</p
>
1772 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
1773 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
1774 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
1775 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
1776 <description><p
>It would be nice if it was easier in Debian to get all the hardware
1777 related packages relevant for the computer installed automatically.
1778 So I implemented one, using
1779 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
1780 package
</a
>. To use it, install the tasksel and isenkram packages and
1781 run tasksel as user root. You should be presented with a new option,
1782 "Hardware specific packages (autodetected by isenkram)
". When you
1783 select it, tasksel will install the packages isenkram claim is fit for
1784 the current hardware, hot pluggable or not.
<p
>
1786 <p
>The implementation is in two files, one is the tasksel menu entry
1787 description, and the other is the script used to extract the list of
1788 packages to install. The first part is in
1789 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
1792 <p
><blockquote
><pre
>
1795 Description: Hardware specific packages (autodetected by isenkram)
1796 Based on the detected hardware various hardware specific packages are
1798 Test-new-install: mark show
1800 Packages: for-current-hardware
1801 </pre
></blockquote
></p
>
1803 <p
>The second part is in
1804 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
1807 <p
><blockquote
><pre
>
1812 isenkram-autoinstall-firmware -l
1814 </pre
></blockquote
></p
>
1816 <p
>All in all, a very short and simple implementation making it
1817 trivial to install the hardware dependent package we all may want to
1818 have installed on our machines. I
've not been able to find a way to
1819 get tasksel to tell you exactly which packages it plan to install
1820 before doing the installation. So if you are curious or careful,
1821 check the output from the isenkram-* command line tools first.
</p
>
1823 <p
>The information about which packages are handling which hardware is
1824 fetched either from the isenkram package itself in
1825 /usr/share/isenkram/, from git.debian.org or from the APT package
1826 database (using the Modaliases header). The APT package database
1827 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1828 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
1829 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
1830 the python-apt code (bug
1831 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
1832 workaround I was able to get rid of the file descriptor leak and
1833 reduce the memory leak from ~
30 MiB per hardware detection down to
1834 around
2 MiB per hardware detection. It should make the desktop
1835 daemon a lot more useful. The fix is in version
0.7 uploaded to
1836 unstable today.
</p
>
1838 <p
>I believe the current way of mapping hardware to packages in
1839 Isenkram is is a good draft, but in the future I expect isenkram to
1840 use the AppStream data source for this. A proposal for getting proper
1841 AppStream support into Debian is floating around as
1842 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
1843 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
1844 project
</a
> will take place this summer to improve the situation. I
1845 look forward to seeing the result, and welcome patches for isenkram to
1846 start using the information when it is ready.
</p
>
1848 <p
>If you want your package to map to some specific hardware, either
1849 add a
"Xb-Modaliases
" header to your control file like I did in
1850 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
1851 package
</a
> or submit a bug report with the details to the isenkram
1853 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
1854 blog posts tagged isenkram
</a
> for details on the notation. I expect
1855 the information will be migrated to AppStream eventually, but for the
1856 moment I got no better place to store it.
</p
>
1861 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
1862 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
1863 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
1864 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
1865 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1866 project
</a
> is working on providing the software and hardware to make
1867 it easy for non-technical people to host their data and communication
1868 at home, and being able to communicate with their friends and family
1869 encrypted and away from prying eyes. It is still going strong, and
1870 today a major mile stone was reached.
</p
>
1872 <p
>Today, the last of the packages currently used by the project to
1873 created the system images were accepted into Debian Unstable. It was
1874 the freedombox-setup package, which is used to configure the images
1875 during build and on the first boot. Now all one need to get going is
1876 the build code from the freedom-maker git repository and packages from
1877 Debian. And once the freedombox-setup package enter testing, we can
1878 build everything directly from Debian. :)
</p
>
1880 <p
>Some key packages used by Freedombox are
1881 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
1882 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
1883 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
1884 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
1885 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
1886 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
1887 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
1888 are plans to integrate more packages into the setup. User
1889 documentation is maintained on the Debian wiki. Please
1890 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
1891 the manual
</a
> and help us improve it.
</p
>
1893 <p
>To test for yourself and create boot images with the FreedomBox
1894 setup, run this on a Debian machine using a user with sudo rights to
1895 become root:
</p
>
1897 <p
><pre
>
1898 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1899 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1901 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1903 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1904 </pre
></p
>
1906 <p
>Root access is needed to run debootstrap and mount loopback
1907 devices. See the README in the freedom-maker git repo for more
1908 details on the build. If you do not want all three images, trim the
1909 make line. Note that the virtualbox-image target is not really
1910 virtualbox specific. It create a x86 image usable in kvm, qemu,
1911 vmware and any other x86 virtual machine environment. You might need
1912 the version of vmdebootstrap in Jessie to get the build working, as it
1913 include fixes for a race condition with kpartx.
</p
>
1915 <p
>If you instead want to install using a Debian CD and the preseed
1916 method, boot a Debian Wheezy ISO and use this boot argument to load
1917 the preseed values:
</p
>
1919 <p
><pre
>
1920 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1921 </pre
></p
>
1923 <p
>I have not tested it myself the last few weeks, so I do not know if
1924 it still work.
</p
>
1926 <p
>If you wonder how to help, one task you could look at is using
1927 systemd as the boot system. It will become the default for Linux in
1928 Jessie, so we need to make sure it is usable on the Freedombox. I did
1929 a simple test a few weeks ago, and noticed dnsmasq failed to start
1930 during boot when using systemd. I suspect there are other problems
1931 too. :) To detect problems, there is a test suite included, which can
1932 be run from the plinth web interface.
</p
>
1934 <p
>Give it a go and let us know how it goes on the mailing list, and help
1935 us get the new release published. :) Please join us on
1936 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1937 irc.debian.org)
</a
> and
1938 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1939 mailing list
</a
> if you want to help make this vision come true.
</p
>
1944 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
1945 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
1946 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
1947 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
1948 <description><p
>For a while now, I have been looking for a sensible offsite backup
1949 solution for use at home. My requirements are simple, it must be
1950 cheap and locally encrypted (in other words, I keep the encryption
1951 keys, the storage provider do not have access to my private files).
1952 One idea me and my friends had many years ago, before the cloud
1953 storage providers showed up, was to use Google mail as storage,
1954 writing a Linux block device storing blocks as emails in the mail
1955 service provided by Google, and thus get heaps of free space. On top
1956 of this one can add encryption, RAID and volume management to have
1957 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1958 I never found time to implement such system. But the last few weeks I
1959 have looked at a system called
1960 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
1961 mounted network backed file system with the features I need.
</p
>
1963 <p
>S3QL is a fuse file system with a local cache and cloud storage,
1964 handling several different storage providers, any with Amazon S3,
1965 Google Drive or OpenStack API. There are heaps of such storage
1966 providers. S3QL can also use a local directory as storage, which
1967 combined with sshfs allow for file storage on any ssh server. S3QL
1968 include support for encryption, compression, de-duplication, snapshots
1969 and immutable file systems, allowing me to mount the remote storage as
1970 a local mount point, look at and use the files as if they were local,
1971 while the content is stored in the cloud as well. This allow me to
1972 have a backup that should survive fire. The file system can not be
1973 shared between several machines at the same time, as only one can
1974 mount it at the time, but any machine with the encryption key and
1975 access to the storage service can mount it if it is unmounted.
</p
>
1977 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
1978 package is included already. So to get started, run
<tt
>apt-get
1979 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
1980 Greenqloud, after reading their nice recipe on
1981 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
1982 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
1983 in Iceland more than those in USA when it come to keeping my personal
1984 data safe and private, and thus would rather spend money on a company
1985 in Iceland. Another nice recipe is available from the article
1986 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
1987 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
1988 Admin magazine. When the provider is picked, figure out how to get
1989 the API key needed to connect to the storage API. With Greencloud,
1990 the key did not show up until I had added payment details to my
1993 <p
>Armed with the API access details, it is time to create the file
1994 system. First, create a new bucket in the cloud. This bucket is the
1995 file system storage area. I picked a bucket name reflecting the
1996 machine that was going to store data there, but any name will do.
1997 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
1998 the API login and password, and a locally created password. Store it
1999 all in ~root/.s3ql/authinfo2 like this:
2001 <p
><blockquote
><pre
>
2003 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2004 backend-login: API-login
2005 backend-password: API-password
2006 fs-passphrase: local-password
2007 </pre
></blockquote
></p
>
2009 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2010 but any sensible way to create a fairly random password should do it.
2011 Armed with these details, it is now time to run mkfs, entering the API
2012 details and password to create it:
</p
>
2014 <p
><blockquote
><pre
>
2015 # mkdir -m
700 /var/lib/s3ql-cache
2016 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2017 --ssl s3c://s.greenqloud.com:
443/bucket-name
2018 Enter backend login:
2019 Enter backend password:
2020 Before using S3QL, make sure to read the user
's guide, especially
2021 the
'Important Rules to Avoid Loosing Data
' section.
2022 Enter encryption password:
2023 Confirm encryption password:
2024 Generating random encryption key...
2025 Creating metadata tables...
2035 Compressing and uploading metadata...
2036 Wrote
0.00 MB of compressed metadata.
2037 #
</pre
></blockquote
></p
>
2039 <p
>The next step is mounting the file system to make the storage available.
2041 <p
><blockquote
><pre
>
2042 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2043 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2044 Using
4 upload threads.
2045 Downloading and decompressing metadata...
2055 Mounting filesystem...
2057 Filesystem Size Used Avail Use% Mounted on
2058 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2060 </pre
></blockquote
></p
>
2062 <p
>The file system is now ready for use. I use rsync to store my
2063 backups in it, and as the metadata used by rsync is downloaded at
2064 mount time, no network traffic (and storage cost) is triggered by
2065 running rsync. To unmount, one should not use the normal umount
2066 command, as this will not flush the cache to the cloud storage, but
2067 instead running the umount.s3ql command like this:
2069 <p
><blockquote
><pre
>
2072 </pre
></blockquote
></p
>
2074 <p
>There is a fsck command available to check the file system and
2075 correct any problems detected. This can be used if the local server
2076 crashes while the file system is mounted, to reset the
"already
2077 mounted
" flag. This is what it look like when processing a working
2078 file system:
</p
>
2080 <p
><blockquote
><pre
>
2081 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2082 Using cached metadata.
2083 File system seems clean, checking anyway.
2084 Checking DB integrity...
2085 Creating temporary extra indices...
2086 Checking lost+found...
2087 Checking cached objects...
2088 Checking names (refcounts)...
2089 Checking contents (names)...
2090 Checking contents (inodes)...
2091 Checking contents (parent inodes)...
2092 Checking objects (reference counts)...
2093 Checking objects (backend)...
2094 ..processed
5000 objects so far..
2095 ..processed
10000 objects so far..
2096 ..processed
15000 objects so far..
2097 Checking objects (sizes)...
2098 Checking blocks (referenced objects)...
2099 Checking blocks (refcounts)...
2100 Checking inode-block mapping (blocks)...
2101 Checking inode-block mapping (inodes)...
2102 Checking inodes (refcounts)...
2103 Checking inodes (sizes)...
2104 Checking extended attributes (names)...
2105 Checking extended attributes (inodes)...
2106 Checking symlinks (inodes)...
2107 Checking directory reachability...
2108 Checking unix conventions...
2109 Checking referential integrity...
2110 Dropping temporary indices...
2111 Backing up old metadata...
2121 Compressing and uploading metadata...
2122 Wrote
0.89 MB of compressed metadata.
2124 </pre
></blockquote
></p
>
2126 <p
>Thanks to the cache, working on files that fit in the cache is very
2127 quick, about the same speed as local file access. Uploading large
2128 amount of data is to me limited by the bandwidth out of and into my
2129 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2130 which is very close to my upload speed, and downloading the same
2131 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2132 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2133 network, not the file system code. I do not know what a good cache
2134 size would be, but suspect that the cache should e larger than your
2135 working set.
</p
>
2137 <p
>I mentioned that only one machine can mount the file system at the
2138 time. If another machine try, it is told that the file system is
2141 <p
><blockquote
><pre
>
2142 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2143 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2144 Using
8 upload threads.
2145 Backend reports that fs is still mounted elsewhere, aborting.
2147 </pre
></blockquote
></p
>
2149 <p
>The file content is uploaded when the cache is full, while the
2150 metadata is uploaded once every
24 hour by default. To ensure the
2151 file system content is flushed to the cloud, one can either umount the
2152 file system, or ask S3QL to flush the cache and metadata using
2155 <p
><blockquote
><pre
>
2156 # s3qlctrl upload-meta /s3ql
2157 # s3qlctrl flushcache /s3ql
2159 </pre
></blockquote
></p
>
2161 <p
>If you are curious about how much space your data uses in the
2162 cloud, and how much compression and deduplication cut down on the
2163 storage usage, you can use s3qlstat on the mounted file system to get
2166 <p
><blockquote
><pre
>
2168 Directory entries:
9141
2171 Total data size:
22049.38 MB
2172 After de-duplication:
21955.46 MB (
99.57% of total)
2173 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2174 Database size:
2.39 MB (uncompressed)
2175 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2177 </pre
></blockquote
></p
>
2179 <p
>I mentioned earlier that there are several possible suppliers of
2180 storage. I did not try to locate them all, but am aware of at least
2181 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2182 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2183 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2184 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2185 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2186 accept payment in Bitcoin. Pick one that suit your need. Some of
2187 them provide several GiB of free storage, but the prize models are
2188 quite different and you will have to figure out what suits you
2191 <p
>While researching this blog post, I had a look at research papers
2192 and posters discussing the S3QL file system. There are several, which
2193 told me that the file system is getting a critical check by the
2194 science community and increased my confidence in using it. One nice
2196 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2197 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2198 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2199 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2200 and Pamela Smith. Please have a look.
</p
>
2202 <p
>Given my problems with different file systems earlier, I decided to
2203 check out the mounted S3QL file system to see if it would be usable as
2204 a home directory (in other word, that it provided POSIX semantics when
2205 it come to locking and umask handling etc). Running
2206 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2207 test code to check file system semantics
</a
>, I was happy to discover that
2208 no error was found. So the file system can be used for home
2209 directories, if one chooses to do so.
</p
>
2211 <p
>If you do not want a locally file system, and want something that
2212 work without the Linux fuse file system, I would like to mention the
2213 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2214 provide locally encrypted backup using a command line client. It have
2215 a nicer access control system, where one can split out read and write
2216 access, allowing some systems to write to the backup and others to
2217 only read from it.
</p
>
2219 <p
>As usual, if you use Bitcoin and want to show your support of my
2220 activities, please send Bitcoin donations to my address
2221 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2226 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2227 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2229 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2230 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2231 project
</a
> is working on providing the software and hardware for
2232 making it easy for non-technical people to host their data and
2233 communication at home, and being able to communicate with their
2234 friends and family encrypted and away from prying eyes. It has been
2235 going on for a while, and is slowly progressing towards a new test
2236 release (
0.2).
</p
>
2238 <p
>And what day could be better than the Pi day to announce that the
2239 new version will provide
"hard drive
" / SD card / USB stick images for
2240 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2241 system), and can also be installed using a Debian installer preseed
2242 file. The Debian based Freedombox is now based on Debian Jessie,
2243 where most of the needed packages used are already present. Only one,
2244 the freedombox-setup package, is missing. To try to build your own
2245 boot image to test the current status, fetch the freedom-maker scripts
2247 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2248 with a user with sudo access to become root:
2251 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2253 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2254 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2256 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2259 <p
>Root access is needed to run debootstrap and mount loopback
2260 devices. See the README for more details on the build. If you do not
2261 want all three images, trim the make line. But note that thanks to
<a
2262 href=
"https://bugs.debian.org/
741407">a race condition in
2263 vmdebootstrap
</a
>, the build might fail without the patch to the
2264 kpartx call.
</p
>
2266 <p
>If you instead want to install using a Debian CD and the preseed
2267 method, boot a Debian Wheezy ISO and use this boot argument to load
2268 the preseed values:
</p
>
2271 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2274 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
2275 recently introduced bug in apt in Jessie
</a
>, the installer will
2276 currently hang while setting up APT sources. Killing the
2277 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
2278 installation will get the installation going. This affect all
2279 installations in Jessie, and I expect it will be fixed soon.
</p
>
2281 <p
>Give it a go and let us know how it goes on the mailing list, and help
2282 us get the new release published. :) Please join us on
2283 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2284 irc.debian.org)
</a
> and
2285 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2286 mailing list
</a
> if you want to help make this vision come true.
</p
>
2291 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
2292 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
2293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
2294 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
2295 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
2296 innetgr tools, because I needed them in
2297 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
2298 ng-utils, and it has served me well. I placed the project under the
2299 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
2300 repository. But many years ago, the CVS repository was dropped (lost,
2301 not migrated to new hardware, not sure), and the project have lacked a
2302 proper home since then.
</p
>
2304 <p
>Last summer, I had a look at the package and made a new release
2305 fixing a irritating crash bug, but was unable to store the changes in
2306 a proper source control system. I applied for a project on
2307 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
2308 to follow up on it. Until today. :)
</p
>
2310 <p
>After many hours of cleaning and migration, the ng-utils project
2311 now have a new home, and a git repository with the highlight of the
2312 history of the project. I published all release tarballs and imported
2313 them into the git repository. As the project is really stable and not
2314 expected to gain new features any time soon, I decided to make a new
2315 release and call it
1.0. Visit the new project home on
2316 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
2317 if you want to check it out. The new version is also uploaded into
2318 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
2323 <title>Testing sysvinit from experimental in Debian Hurd
</title>
2324 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
2325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
2326 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
2327 <description><p
>A few days ago I decided to try to help the Hurd people to get
2328 their changes into sysvinit, to allow them to use the normal sysvinit
2329 boot system instead of their old one. This follow up on the
2330 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
2331 Google Summer of Code work
</a
> done last summer by Justus Winter to
2332 get Debian on Hurd working more like Debian on Linux. To get started,
2333 I downloaded a prebuilt hard disk image from
2334 <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
>,
2335 and started it using virt-manager.
</p
>
2337 <p
>The first think I had to do after logging in (root without any
2338 password) was to get the network operational. I followed
2339 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
2340 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
2341 commands as root to get the machine to accept a IP address from the
2342 kvm internal DHCP server:
</p
>
2344 <p
><blockquote
><pre
>
2345 settrans -fgap /dev/netdde /hurd/netdde
2346 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
2347 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
2349 </pre
></blockquote
></p
>
2351 <p
>After this, the machine had internet connectivity, and I could
2352 upgrade it and install the sysvinit packages from experimental and
2353 enable it as the default boot system in Hurd.
</p
>
2355 <p
>But before I did that, I set a password on the root user, as ssh is
2356 running on the machine it for ssh login to work a password need to be
2357 set. Also, note that a bug somewhere in openssh on Hurd block
2358 compression from working. Remember to turn that off on the client
2361 <p
>Run these commands as root to upgrade and test the new sysvinit
2364 <p
><blockquote
><pre
>
2365 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
2366 deb http://http.debian.net/debian/ experimental main
2369 apt-get dist-upgrade
2370 apt-get install -t experimental initscripts sysv-rc sysvinit \
2371 sysvinit-core sysvinit-utils
2372 update-alternatives --config runsystem
2373 </pre
></blockquote
></p
>
2375 <p
>To reboot after switching boot system, you have to use
2376 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
2377 yet a sysvinit process able to receive the signals from the normal
2378 'reboot
' command. After switching to sysvinit as the boot system,
2379 upgrading every package and rebooting, the network come up with DHCP
2380 after boot as it should, and the settrans/pkill hack mentioned at the
2381 start is no longer needed. But for some strange reason, there are no
2382 longer any login prompt in the virtual console, so I logged in using
2385 <p
>Note that there are some race conditions in Hurd making the boot
2386 fail some times. No idea what the cause is, but hope the Hurd porters
2387 figure it out. At least Justus said on IRC (#debian-hurd on
2388 irc.debian.org) that they are aware of the problem. A way to reduce
2389 the impact is to upgrade to the Hurd packages built by Justus by
2390 adding this repository to the machine:
</p
>
2392 <p
><blockquote
><pre
>
2393 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2394 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2396 </pre
></blockquote
></p
>
2398 <p
>At the moment the prebuilt virtual machine get some packages from
2399 http://ftp.debian-ports.org/debian, because some of the packages in
2400 unstable do not yet include the required patches that are lingering in
2401 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2403 <p
><blockquote
><pre
>
2404 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2405 i emacs - GNU Emacs editor (metapackage)
2406 i gdb - GNU Debugger
2407 i hurd-recommended - Miscellaneous translators
2408 i isc-dhcp-client - ISC DHCP client
2409 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2410 i libc-bin - Embedded GNU C Library: Binaries
2411 i libc-dev-bin - Embedded GNU C Library: Development binaries
2412 i libc0.3 - Embedded GNU C Library: Shared libraries
2413 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2414 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2415 i multiarch-support - Transitional package to ensure multiarch compatibilit
2416 i A x11-common - X Window System (X.Org) infrastructure
2417 i xorg - X.Org X Window System
2418 i A xserver-xorg - X.Org X server
2419 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2421 </pre
></blockquote
></p
>
2423 <p
>All in all, testing hurd has been an interesting experience. :)
2424 X.org did not work out of the box and I never took the time to follow
2425 the porters instructions to fix it. This time I was interested in the
2426 command line stuff.
<p
>
2431 <title>New chrpath release
0.16</title>
2432 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2434 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2435 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2436 find problems in C, C++ and Java code using static source code
2437 analysis. It can detect a lot of different problems, and is very
2438 useful to find memory and locking bugs in the error handling part of
2439 the source. The company behind it provide
2440 <a href=
"https://scan.coverity.com/
">check of free software projects as
2441 a community service
</a
>, and many hundred free software projects are
2442 already checked. A few days ago I decided to have a closer look at
2443 the Coverity system, and discovered that the
2444 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2445 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2446 projects I am involved with was already registered. But these are
2447 fairly big, and I would also like to have a small and easy project to
2448 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2449 checking of the chrpath project
</a
>. It was
2450 added to the checker and discovered seven potential defects. Six of
2451 these were real, mostly resource
"leak
" when the program detected an
2452 error. Nothing serious, as the resources would be released a fraction
2453 of a second later when the program exited because of the error, but it
2454 is nice to do it right in case the source of the program some time in
2455 the future end up in a library. Having fixed all defects and added
2456 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
2457 mailing list for the chrpath developers
</a
>, I decided it was time to
2458 publish a new release. These are the release notes:
</p
>
2460 <p
>New in
0.16 released
2014-
01-
14:
</p
>
2464 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
2465 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
2466 <li
>Mention new project mailing list in the documentation.
</li
>
2471 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2472 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
2473 project if something is wrong with the new release. The test suite
2474 did not discover any old errors, so if you find a new one, please also
2475 include a test suite check.
</p
>
2480 <title>New chrpath release
0.15</title>
2481 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
2482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
2483 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
2484 <description><p
>After many years break from the package and a vain hope that
2485 development would be continued by someone else, I finally pulled my
2486 acts together this morning and wrapped up a new release of chrpath,
2487 the command line tool to modify the rpath and runpath of already
2488 compiled ELF programs. The update was triggered by the persistence of
2489 Isha Vishnoi at IBM, which needed a new config.guess file to get
2490 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
2491 is working on. I checked the
2492 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
2493 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
2494 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
2495 packages for interesting patches (failed to find the source from
2496 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2497 These are the release notes:
</p
>
2499 <p
>New in
0.15 released
2013-
11-
24:
</p
>
2503 <li
>Updated config.sub and config.guess from the GNU project to work
2504 with newer architectures. Thanks to isha vishnoi for the heads
2507 <li
>Updated README with current URLs.
</li
>
2509 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2510 Matthias Klose.
</li
>
2512 <li
>Added missing help for -k|--keepgoing option, using patch by
2513 Petr Machata found in Fedora.
</li
>
2515 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
2516 .dynamic is a NULL terminated string. Based on patch found in
2517 Fedora credited Axel Thimm and Christian Krause.
</li
>
2522 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2523 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
2524 project if something is wrong with the new release. The test suite
2525 did not discover any old errors, so if you find a new one, please also
2526 include a testsuite check.
</p
>
2531 <title>Debian init.d boot script example for rsyslog
</title>
2532 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
2533 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
2534 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
2535 <description><p
>If one of the points of switching to a new init system in Debian is
2536 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
2537 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
2538 init.d scripts at all. Here is an example init.d script, ie a rewrite
2539 of /etc/init.d/rsyslog:
</p
>
2541 <p
><pre
>
2542 #!/lib/init/init-d-script
2545 # Required-Start: $remote_fs $time
2546 # Required-Stop: umountnfs $time
2547 # X-Stop-After: sendsigs
2548 # Default-Start:
2 3 4 5
2549 # Default-Stop:
0 1 6
2550 # Short-Description: enhanced syslogd
2551 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2552 # It is quite compatible to stock sysklogd and can be
2553 # used as a drop-in replacement.
2555 DESC=
"enhanced syslogd
"
2556 DAEMON=/usr/sbin/rsyslogd
2557 </pre
></p
>
2559 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
2560 script was
137 lines, and the above is just
15 lines, most of it meta
2561 info/comments.
</p
>
2563 <p
>How to do this, you ask? Well, one create a new script
2564 /lib/init/init-d-script looking something like this:
2566 <p
><pre
>
2569 # Define LSB log_* functions.
2570 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
2571 # and status_of_proc is working.
2572 . /lib/lsb/init-functions
2575 # Function that starts the daemon/service
2581 #
0 if daemon has been started
2582 #
1 if daemon was already running
2583 #
2 if daemon could not be started
2584 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
2586 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2589 # Add code here, if necessary, that waits for the process to be ready
2590 # to handle requests from services started subsequently which depend
2591 # on this one. As a last resort, sleep for some time.
2595 # Function that stops the daemon/service
2600 #
0 if daemon has been stopped
2601 #
1 if daemon was already stopped
2602 #
2 if daemon could not be stopped
2603 # other if a failure occurred
2604 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
2605 RETVAL=
"$?
"
2606 [
"$RETVAL
" =
2 ]
&& return
2
2607 # Wait for children to finish too if this is a daemon that forks
2608 # and if the daemon is only ever run from this initscript.
2609 # If the above conditions are not satisfied then add some other code
2610 # that waits for the process to drop all resources that could be
2611 # needed by services started subsequently. A last resort is to
2612 # sleep for some time.
2613 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
2614 [
"$?
" =
2 ]
&& return
2
2615 # Many daemons don
't delete their pidfiles when they exit.
2617 return
"$RETVAL
"
2621 # Function that sends a SIGHUP to the daemon/service
2625 # If the daemon can reload its configuration without
2626 # restarting (for example, when it is sent a SIGHUP),
2627 # then implement that here.
2629 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
2634 scriptbasename=
"$(basename $
1)
"
2635 echo
"SN: $scriptbasename
"
2636 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
2637 script=
"$
1"
2644 NAME=$(basename $DAEMON)
2645 PIDFILE=/var/run/$NAME.pid
2647 # Exit if the package is not installed
2648 #[ -x
"$DAEMON
" ] || exit
0
2650 # Read configuration variable file if it is present
2651 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
2653 # Load the VERBOSE setting and other rcS variables
2656 case
"$
1" in
2658 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
2660 case
"$?
" in
2661 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2662 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2666 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
2668 case
"$?
" in
2669 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2670 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2674 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
2676 #reload|force-reload)
2678 # If do_reload() is not implemented then leave this commented out
2679 # and leave
'force-reload
' as an alias for
'restart
'.
2681 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
2685 restart|force-reload)
2687 # If the
"reload
" option is implemented then remove the
2688 #
'force-reload
' alias
2690 log_daemon_msg
"Restarting $DESC
" "$NAME
"
2692 case
"$?
" in
2695 case
"$?
" in
2697 1) log_end_msg
1 ;; # Old process is still running
2698 *) log_end_msg
1 ;; # Failed to start
2708 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
2714 </pre
></p
>
2716 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
2717 lot. I did not really polish the approach, so it might not always
2718 work out of the box, but you get the idea. I did not try very hard to
2719 optimize it nor make it more robust either.
</p
>
2721 <p
>A better argument for switching init system in Debian than reducing
2722 the size of init scripts (which is a good thing to do anyway), is to
2723 get boot system that is able to handle the kernel events sensibly and
2724 robustly, and do not depend on the boot to run sequentially. The boot
2725 and the kernel have not behaved sequentially in years.
</p
>
2730 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
2731 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
2732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
2733 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
2734 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
2735 remote display access is the preferred solution with oVirt and RedHat
2736 Enterprise Virtualization, and I was sad to discover the other day
2737 that the browser plugin needed to use these systems seamlessly was
2738 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
2739 for a package
</a
> was from
2012-
04-
10 with no progress since
2740 2013-
04-
01, so I decided to wrap up a package based on the great work
2741 from Cajus Pollmeier and put it in a collab-maint maintained git
2742 repository to get a package I could use. I would very much like
2743 others to help me maintain the package (or just take over, I do not
2744 mind), but as no-one had volunteered so far, I just uploaded it to
2745 NEW. I hope it will be available in Debian in a few days.
</p
>
2747 <p
>The source is now available from
2748 <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
>
2753 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
2754 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
2755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
2756 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
2757 <description><p
>The
2758 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
2759 program is a a very nice system to create virtual machine images. It
2760 create a image file, add a partition table, mount it and run
2761 debootstrap in the mounted directory to create a Debian system on a
2762 stick. Yesterday, I decided to try to teach it how to make images for
2763 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
2764 of a plan to simplify the build system for
2765 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
2766 project
</a
>. The FreedomBox project already uses vmdebootstrap for
2767 the virtualbox images, but its current build system made multistrap
2768 based system for Dreamplug images, and it is lacking support for
2769 Raspberry Pi.
</p
>
2771 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
2772 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2773 code and adjusted it to be able to build armel images on my amd64
2774 Debian laptop. I ended up giving vmdebootstrap five new options,
2775 allowing me to replicate the image creation process I use to make
2776 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
2777 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
2778 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
2779 call debootstrap with --foreign and to copy the handler into the
2780 generated chroot before running the second stage. This allow
2781 vmdebootstrap to create armel images on an amd64 host. Next I added
2782 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
2783 fstype
</tt
> to teach it to create a separate /boot/ partition with the
2784 given file system type, allowing me to create an image with a vfat
2785 partition for the /boot/ stuff. I also added a
<tt
>--variant
2786 variant
</tt
> option to allow me to create smaller images without the
2787 Debian base system packages installed. Finally, I added an option
2788 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
2789 as a boot loader. It is not needed on the Raspberry Pi and probably
2790 most other non-x86 architectures. The changes were accepted by the
2791 upstream author of vmdebootstrap yesterday and today, and is now
2793 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
2794 upstream project page
</a
>.
</p
>
2796 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
2797 create a small script (the customize script) to add the non-free
2798 binary blob needed to boot the Raspberry Pi and the APT source
2801 <p
><pre
>
2803 set -e # Exit on first error
2804 rootdir=
"$
1"
2805 cd
"$rootdir
"
2806 cat
&lt;
&lt;EOF
> etc/apt/sources.list
2807 deb http://http.debian.net/debian/ jessie main contrib non-free
2809 # Install non-free binary blob needed to boot Raspberry Pi. This
2810 # install a kernel somewhere too.
2811 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2812 -O $rootdir/usr/bin/rpi-update
2813 chmod a+x $rootdir/usr/bin/rpi-update
2814 mkdir -p $rootdir/lib/modules
2815 touch $rootdir/boot/start.elf
2816 chroot $rootdir rpi-update
2817 </pre
></p
>
2819 <p
>Next, fetch the latest vmdebootstrap script and call it like this
2820 to build the image:
</p
>
2823 sudo ./vmdebootstrap \
2826 --distribution jessie \
2827 --mirror http://http.debian.net/debian \
2836 --root-password raspberry \
2837 --hostname raspberrypi \
2838 --foreign /usr/bin/qemu-arm-static \
2839 --customize `pwd`/customize \
2841 --package git-core \
2842 --package binutils \
2843 --package ca-certificates \
2846 </pre
></p
>
2848 <p
>The list of packages being installed are the ones needed by
2849 rpi-update to make the image bootable on the Raspberry Pi, with the
2850 exception of netbase, which is needed by debootstrap to find
2851 /etc/hosts with the minbase variant. I really wish there was a way to
2852 set up an Raspberry Pi using only packages in the Debian archive, but
2853 that is not possible as far as I know, because it boots from the GPU
2854 using a non-free binary blob.
</p
>
2856 <p
>The build host need debootstrap, kpartx and qemu-user-static and
2857 probably a few others installed. I have not checked the complete
2858 build dependency list.
</p
>
2860 <p
>The resulting image will not use the hardware floating point unit
2861 on the Raspberry PI, because the armel architecture in Debian is not
2862 optimized for that use. So the images created will be a bit slower
2863 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
2868 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
2869 <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>
2870 <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>
2871 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
2872 <description><p
>The last few days I came across a few good causes that should get
2873 wider attention. I recommend signing and donating to each one of
2876 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
2877 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
2878 Women program which is a Google Summer of Code like initiative to get
2879 more women involved in free software. One debian sponsor has offered
2880 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
2881 earmarked
</a
> for this initiative. I donated a few minutes ago, and
2882 hope you will to. :)
</p
>
2884 <p
>And the Electronic Frontier Foundation just announced plans to
2885 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
2886 documentaries about the excessive spying
</a
> on every Internet user that
2887 take place these days, and their need to fund the work. I
've already
2888 donated. Are you next?
</p
>
2890 <p
>For my Norwegian audience, the organisation Studentenes og
2891 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2892 statement under the heading
2893 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
2894 Access
</a
> for those of us asking for more focus on open access in the
2895 Norwegian government. So far
499 signatures. I hope you will sign it
2901 <title>Videos about the Freedombox project - for inspiration and learning
</title>
2902 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
2903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
2904 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
2905 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
2906 project
</a
> have been going on for a while, and have presented the
2907 vision, ideas and solution several places. Here is a little
2908 collection of videos of talks and presentation of the project.
</p
>
2912 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
2913 2,
5 minute marketing film
</a
> (Youtube)
</li
>
2915 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
2916 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
2918 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
2919 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2920 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
2921 (Youtube)
</li
>
2923 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
2924 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
2926 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
2927 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
2929 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
2930 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2931 York City in
2012</a
> (Youtube)
</li
>
2933 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
2934 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
2935 (Youtube)
</li
>
2937 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
2938 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
2940 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
2941 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
2943 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
2944 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2945 2013</a
> (Youtube)
</li
>
2949 <p
>A larger list is available from
2950 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
2951 Freedombox Wiki
</a
>.
</p
>
2953 <p
>On other news, I am happy to report that Freedombox based on Debian
2954 Jessie is coming along quite well, and soon both Owncloud and using
2955 Tor should be available for testers of the Freedombox solution. :) In
2956 a few weeks I hope everything needed to test it is included in Debian.
2957 The withsqlite package is already in Debian, and the plinth package is
2958 pending in NEW. The third and vital part of that puzzle is the
2959 metapackage/setup framework, which is still pending an upload. Join
2960 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
2961 (#freedombox on irc.debian.org)
</a
> and
2962 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2963 mailing list
</a
> if you want to help make this vision come true.
</p
>
2968 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
2969 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
2970 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
2971 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
2972 <description><p
>I was introduced to the
2973 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
2974 in
2010, when Eben Moglen presented his vision about serving the need
2975 of non-technical people to keep their personal information private and
2976 within the legal protection of their own homes. The idea is to give
2977 people back the power over their network and machines, and return
2978 Internet back to its intended peer-to-peer architecture. Instead of
2979 depending on a central service, the Freedombox will give everyone
2980 control over their own basic infrastructure.
</p
>
2982 <p
>I
've intended to join the effort since then, but other tasks have
2983 taken priority. But this summers nasty news about the misuse of trust
2984 and privilege exercised by the
"western
" intelligence gathering
2985 communities increased my eagerness to contribute to a point where I
2986 actually started working on the project a while back.
</p
>
2988 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
2989 Debian initiative
</a
> based on the vision from Eben Moglen, is to
2990 create a simple and cheap Debian based appliance that anyone can hook
2991 up in their home and get access to secure and private services and
2992 communication. The initial deployment platform have been the
2993 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
2994 which is a piece of hardware I do not own. So to be able to test what
2995 the current Freedombox setup look like, I had to come up with a way to install
2996 it on some hardware I do have access to. I have rewritten the
2997 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
2998 image build framework to use .deb packages instead of only copying
2999 setup into the boot images, and thanks to this rewrite I am able to
3000 set up any machine supported by Debian Wheezy as a Freedombox, using
3001 the previously mentioned deb (and a few support debs for packages
3002 missing in Debian).
</p
>
3004 <p
>The current Freedombox setup consist of a set of bootstrapping
3006 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3007 and a administrative web interface
3008 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3009 withsqlite), as well as a privacy enhancing proxy based on
3010 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3011 (freedombox-privoxy). There is also a web/javascript based XMPP
3012 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3013 trying (unsuccessfully so far) to talk to the XMPP server
3014 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3015 web interface is pluggable, and the goal is to use it to enable OpenID
3016 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3017 this is really working yet, see
3018 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3019 project TODO
</a
> for links to GIT repositories. Most of the code is
3020 on github at the moment. The HTTP proxy is operational out of the
3021 box, and the admin web interface can be used to add/remove plinth
3022 users. I
've not been able to do anything else with it so far, but
3023 know there are several branches spread around github and other places
3024 with lots of half baked features.
</p
>
3026 <p
>Anyway, if you want to have a look at the current state, the
3027 following recipes should work to give you a test machine to poke
3030 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3034 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3035 <li
>Boot from it, either as CD or USB stick.
</li
>
3036 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3037 to the Debian installer:
<p
>
3038 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3040 <li
>Answer the few language/region/password questions and pick disk to
3041 install on.
</li
>
3043 <li
>When the installation is finished and the machine have rebooted a
3044 few times, your Freedombox is ready for testing.
</li
>
3048 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3052 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3053 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3054 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3056 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3057 </pre
></li
>
3058 <li
><p
>Run this as root:
</p
>
3060 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3063 apt-get install freedombox-setup
3064 /usr/lib/freedombox/setup
3065 </pre
></li
>
3066 <li
>Reboot into your freshly created Freedombox.
</li
>
3070 <p
>You can test it on other architectures too, but because the
3071 freedombox-privoxy package is binary, it will only work as intended on
3072 the architectures where I have had time to build the binary and put it
3073 in my APT repository. But do not let this stop you. It is only a
3074 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3076 <p
>Note that by default Freedombox is a DHCP server on the
3077 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3078 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3079 disable
</tt
>" as root.
</p
>
3081 <p
>Please let me know if this works for you, or if you have any
3082 problems. We gather on the IRC channel
3083 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3084 irc.debian.org and the
3085 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3086 mailing list
</a
>.
</p
>
3088 <p
>Once you get your freedombox operational, you can visit
3089 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3090 welcome screen (dead end - do not be surprised if you are unable to
3091 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3092 to look at the rest of plinth. The default user is
'admin
' and the
3093 default password is
'secret
'.
</p
>
3098 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3099 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3101 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3102 <description><p
>Earlier, I reported about
3103 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3104 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3105 told by IBM that the original disk should be thrown away. And as
3106 there no longer was a problem if I bricked the firmware, I decided
3107 today to try to install Intel firmware to replace the Lenovo firmware
3108 currently on the disk.
</p
>
3110 <p
>I searched the Intel site for firmware, and found
3111 <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
>
3112 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3113 according to the site should contain the latest firmware for SSD
3114 disks. I inserted the broken disk in one of my spare laptops and
3115 booted the ISO from a USB stick. The disk was recognized, but the
3116 program claimed the newest firmware already were installed and refused
3117 to insert any Intel firmware. So no change, and the disk is still
3118 unable to handle write load. :( I guess the only way to get them
3119 working would be if Lenovo releases new firmware. No idea how likely
3120 that is. Anyway, just blogging about this test for completeness. I
3121 got a working Samsung disk, and see no point in spending more time on
3122 the broken disks.
</p
>
3127 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3128 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3130 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3131 <description><p
>Today I switched to
3132 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3133 new laptop
</a
>. I
've previously written about the problems I had with
3134 my new Thinkpad X230, which was delivered with an
3135 <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
3136 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3137 sustained writes. My hardware supplier have been very forthcoming in
3138 trying to find a solution, and after first trying with another
3139 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3140 disk instead to fix it once and for all. The Samsung disk survived
3141 the installation of Debian with encrypted disks (filling the disk with
3142 random data during installation killed the first two), and I thus
3143 decided to trust it with my data. I have installed it as a Debian Edu
3144 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3145 server at home using Kerberos and LDAP, and will use it as my work
3146 station from now on.
</p
>
3148 <p
>As this is a solid state disk with no moving parts, I believe the
3149 Debian Wheezy default installation need to be tuned a bit to increase
3150 performance and increase life time of the disk. The Linux kernel and
3151 user space applications do not yet adjust automatically to such
3152 environment. To make it easier for my self, I created a draft Debian
3153 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3154 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3155 for the ssd-setup package
</a
> is available from collab-maint, and it
3156 is set up to adjust the setup of the machine by just installing the
3157 package. If there is any non-SSD disk in the machine, the package
3158 will refuse to install, as I did not try to write any logic to sort
3159 file systems in SSD and non-SSD file systems.
</p
>
3161 <p
>I consider the package a draft, as I am a bit unsure how to best
3162 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3163 where I set up the machine with one large encrypted partition (in
3164 addition to /boot), put LVM on top of this and set up partitions on
3165 top of this again. See the README file in the package source for the
3166 references I used to pick the settings. At the moment these
3167 parameters are tuned:
</p
>
3171 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3172 (adding discard to /etc/crypttab)
</li
>
3174 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3175 this case a cryptsetup partition) by changing issue_discards from
3176 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3178 <li
>Set relatime as a file system option for ext3 and ext4 file
3181 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3182 /etc/fstab.
</li
>
3184 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3186 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3187 cron.daily).
</li
>
3189 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3190 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3194 <p
>During installation, I cancelled the part where the installer fill
3195 the disk with random data, as this would kill the SSD performance for
3196 little gain. My goal with the encrypted file system is to ensure
3197 those stealing my laptop end up with a brick and not a working
3198 computer. I have no hope in keeping the really resourceful people
3199 from getting the data on the disk (see
3200 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3201 Thus I concluded that adding the discard option to crypttab is the
3202 right thing to do.
</p
>
3204 <p
>I considered using the noop I/O scheduler, as several recommended
3205 it for SSD, but others recommended deadline and a benchmark I found
3206 indicated that deadline might be better for interactive use.
</p
>
3208 <p
>I also considered using the
'discard
' file system option for ext3
3209 and ext4, but read that it would give a performance hit ever time a
3210 file is removed, and thought it best to that that slowdown once a day
3211 instead of during my work.
</p
>
3213 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3214 this is already done by Debian Edu.
</p
>
3216 <p
>I have not yet started on the user space tuning. I expect
3217 iceweasel need some tuning, and perhaps other applications too, but
3218 have not yet had time to investigate those parts.
</p
>
3220 <p
>The package should work on Ubuntu too, but I have not yet tested it
3223 <p
>As for the answer to the question in the title of this blog post,
3224 as far as I know, the only solution I know about is to replace the
3225 disk. It might be possible to flash it with Intel firmware instead of
3226 the Lenovo firmware. But I have not tried and did not want to do so
3227 without approval from Lenovo as I wanted to keep the warranty on the
3228 disk until a solution was found and they wanted the broken disks
3234 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3235 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3236 <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>
3237 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3238 <description><p
>A few days ago, I wrote about
3239 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3240 problems I experienced with my new X230 and its SSD disk
</a
>, which
3241 was dying during installation because it is unable to cope with
3242 sustained write. My supplier is in contact with
3243 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3244 replacement disk to try to fix the problem. They decided to send an
3245 identical model, so my hopes for a permanent fix was slim.
</p
>
3247 <p
>Anyway, today I got the replacement disk and tried to install
3248 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3249 same firmware version as the original. This time my hope raised
3250 slightly as the installation progressed, as the original disk used to
3251 die after
4-
7% of the disk was written to, while this time it kept
3252 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3253 died again and I was back on square one. I still do not have a new
3254 laptop with a disk I can trust. I can not live with a disk that might
3255 lock up when I download a new
3256 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3257 other large files. I look forward to hearing from my supplier with
3258 the next proposal from Lenovo.
</p
>
3260 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3261 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3262 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3263 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
3264 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3265 P/N
45N8295, P0C38732.
</p
>
3267 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
3268 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
3269 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3270 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
3271 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3272 P/N
45N8295, P0C38732.
</p
>
3274 <p
>The only difference is in the first number (serial number?), ISN,
3275 SA, date and WNPP values. Mentioning all the details here in case
3276 someone is able to use the information to find a way to identify the
3277 failing disk among working ones (if any such working disk actually
3283 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
3284 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
3285 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
3286 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
3287 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
3288 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3289 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
3290 member assosiation NUUG
</a
> and
3291 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
3292 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
3293 Bitraf
</a
>.
</p
>
3295 <p
>It starts
10:
00 and continue until late evening. Everyone is
3296 welcome, and there is no fee to participate. There is on the other
3297 hand limited space, and only room for
30 people. Please put your name
3298 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
3299 wiki page
</a
> if you plan to join us.
</p
>
3304 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
3305 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
3306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
3307 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
3308 <description><p
>Half a year ago, I reported that I had to find a
3309 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
3310 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
3311 time to spend on it, and it took a while to find a model I believe
3312 will do the job, but two days ago the replacement finally arrived. I
3314 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
3315 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3316 a roaming workstation, and it seemed to work flawlessly. But my
3317 second installation with encrypted disk was not as successful. More
3318 on that below.
</p
>
3320 <p
>I had a hard time trying to track down a good laptop, as my most
3321 important requirements (robust and with a good keyboard) are never
3322 listed in the feature list. But I did get good help from the search
3323 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3324 allowed me to limit the list of interesting laptops based on my other
3325 requirements. A bit surprising that SSD disk are not disks according
3326 to that search interface, so I had to drop specifying the number of
3327 disks from my search parameters. I also asked around among friends to
3328 get their impression on keyboards and robustness.
</p
>
3330 <p
>So the new laptop arrived, and it is quite a lot wider than the
3331 X41. I am not quite convinced about the keyboard, as it is
3332 significantly wider than my old keyboard, and I have to stretch my
3333 hand a lot more to reach the edges. But the key response is fairly
3334 good and the individual key shape is fairly easy to handle, so I hope
3335 I will get used to it. My old X40 was starting to fail, and I really
3336 needed a new laptop now. :)
</p
>
3338 <p
>Turning off the touch pad was simple. All it took was a quick
3339 visit to the BIOS during boot it disable it.
</p
>
3341 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
3342 lock up during load. And this happen when installing Debian Wheezy
3343 with encrypted disk, while the disk is being filled with random data.
3344 I also tested to install Ubuntu Raring, and it happen there too if I
3345 reenable the code to fill the disk with random data (it is disabled by
3346 default in Ubuntu). And the bug with is already known. It was
3347 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
3348 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
3349 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3350 kernel developers as
3351 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
3352 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
3353 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3354 Lenovo forums, both for
3355 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
3356 2012-
11-
10</a
> and for
3357 <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
3358 03-
20-
2013</a
>. The problem do not only affect installation. The
3359 reports state that the disk lock up during use if many writes are done
3360 on the disk, so it is much no use to work around the installation
3361 problem and end up with a computer that can lock up at any moment.
3363 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
3364 available
</a
> that will lock up the hard drive after running a few
3365 minutes by writing to a file.
</p
>
3367 <p
>I
've contacted my supplier and asked how to handle this, and after
3368 contacting PCHELP Norway (request
01D1FDP) which handle support
3369 requests for Lenovo, his first suggestion was to upgrade the disk
3370 firmware. Unfortunately there is no newer firmware available from
3371 Lenovo, as my disk already have the most recent one (version LF1i). I
3372 hope to hear more from him today and hope the problem can be
3378 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
3379 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
3380 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
3381 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3382 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3383 trusty old Thinkpad X41. Unfortunately I did not have much time to
3384 spend on it, but today the replacement finally arrived. I ended up
3385 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3386 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3387 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3388 this, it is installing what I hope will be a more final installation,
3389 with a encrypted hard drive to ensure any dope head stealing it end up
3390 with an expencive door stop.
</p
>
3392 <p
>I had a hard time trying to track down a good laptop, as my most
3393 important requirements (robust and with a good keyboard) are never
3394 listed in the feature list. But I did get good help from the search
3395 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3396 allowed me to limit the list of interesting laptops based on my other
3397 requirements. A bit surprising that SSD disk are not disks, so I had
3398 to drop number of disks from my search parameters.
</p
>
3400 <p
>I am not quite convinced about the keyboard, as it is significantly
3401 wider than my old keyboard, and I have to stretch my hand a lot more
3402 to reach the edges. But the key response is fairly good and the
3403 individual key shape is fairly easy to handle, so I hope I will get
3404 used to it. My old X40 was starting to fail, and I really needed a
3405 new laptop now. :)
</p
>
3407 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3412 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3413 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3414 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3415 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3416 <description><p
>It annoys me when the computer fail to do automatically what it is
3417 perfectly capable of, and I have to do it manually to get things
3418 working. One such task is to find out what firmware packages are
3419 needed to get the hardware on my computer working. Most often this
3420 affect the wifi card, but some times it even affect the RAID
3421 controller or the ethernet card. Today I pushed version
0.4 of the
3422 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3423 including a new script isenkram-autoinstall-firmware handling the
3424 process of asking all the loaded kernel modules what firmware files
3425 they want, find debian packages providing these files and install the
3426 debian packages. Here is a test run on my laptop:
</p
>
3428 <p
><pre
>
3429 # isenkram-autoinstall-firmware
3430 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3431 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3432 info: locating packages with the requested firmware files
3433 info: Updating APT sources after adding non-free APT source
3434 info: trying to install firmware-ipw2x00
3437 Preconfiguring packages ...
3438 Selecting previously deselected package firmware-ipw2x00.
3439 (Reading database ...
259727 files and directories currently installed.)
3440 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3441 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3443 </pre
></p
>
3445 <p
>When all the requested firmware is present, a simple message is
3446 printed instead:
</p
>
3448 <p
><pre
>
3449 # isenkram-autoinstall-firmware
3450 info: did not find any firmware files requested by loaded kernel modules. exiting
3452 </pre
></p
>
3454 <p
>It could use some polish, but it is already working well and saving
3455 me some time when setting up new machines. :)
</p
>
3457 <p
>So, how does it work? It look at the set of currently loaded
3458 kernel modules, and look up each one of them using modinfo, to find
3459 the firmware files listed in the module meta-information. Next, it
3460 download the Contents file from a nearby APT mirror, and search for
3461 the firmware files in this file to locate the package with the
3462 requested firmware file. If the package is in the non-free section, a
3463 non-free APT source is added and the package is installed using
3464 <tt
>apt-get install
</tt
>. The end result is a slightly better working
3467 <p
>I hope someone find time to implement a more polished version of
3468 this script as part of the hw-detect debian-installer module, to
3469 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
3470 #
655507</a
>. There really is no need to insert USB sticks with
3471 firmware during a PXE install when the packages already are available
3472 from the nearby Debian mirror.
</p
>
3477 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
3478 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
3479 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
3480 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
3481 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3482 the screen just turn black when Linux boot, either during installation
3483 or on first boot from the hard disk. I
've seen it once in a while the
3484 last few years, but only recently understood the cause. I
've seen it
3485 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3486 The reason seem to be in the wiring of some laptops. The system to
3487 control the screen background light is inverted, so when Linux try to
3488 turn the brightness fully on, it end up turning it off instead. I do
3489 not know which Linux drivers are affected, but this post is about the
3490 i915 driver used by the
3491 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3492 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
3494 <p
>The problem can be worked around two ways. Either by adding
3495 i915.invert_brightness=
1 as a kernel option, or by adding a file in
3496 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
3497 option when it load the i915 kernel module. On Debian and Ubuntu, it
3498 can be done by running these commands as root:
</p
>
3501 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
3502 update-initramfs -u -k all
3505 <p
>Since March
2012 there is
3506 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
3507 mechanism in the Linux kernel
</a
> to tell the i915 driver which
3508 hardware have this problem, and get the driver to invert the
3509 brightness setting automatically. To use it, one need to add a row in
3510 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
3511 intel_quirks array
</a
> in the driver source
3512 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
3513 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
3514 number (vendor number
8086 is assumed) and subdevice vendor and device
3517 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
3518 -vvnn
</tt
> for the video card in question:
</p
>
3520 <p
><pre
>
3521 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
3522 3rd Gen Core processor Graphics Controller [
8086:
0156] \
3523 (rev
09) (prog-if
00 [VGA controller])
3524 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
3525 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3526 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3527 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
3528 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
3530 Interrupt: pin A routed to IRQ
42
3531 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
3532 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
3533 Region
4: I/O ports at
4000 [size=
64]
3534 Expansion ROM at
<unassigned
> [disabled]
3535 Capabilities:
<access denied
>
3536 Kernel driver in use: i915
3537 </pre
></p
>
3539 <p
>The resulting intel_quirks entry would then look like this:
</p
>
3541 <p
><pre
>
3542 struct intel_quirk intel_quirks[] = {
3544 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3545 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
3548 </pre
></p
>
3550 <p
>According to the kernel module instructions (as seen using
3551 <tt
>modinfo i915
</tt
>), information about hardware needing the
3552 invert_brightness flag should be sent to the
3553 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
3554 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
3555 developers. But my email about the laptop sent
2013-
06-
03 have not
3557 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
3558 web archive for the mailing list
</a
>, so I suspect they do not accept
3559 emails from non-subscribers. Because of this, I sent my patch also to
3560 the Debian bug tracking system instead as
3561 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
3562 sure the patch is not lost.
</p
>
3564 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
3565 with this problem working properly with Linux. If you use Gnome, your
3566 worries should be over at this point. But if you use KDE, there is
3567 something in KDE ignoring the invert_brightness setting and turning on
3568 the screen during login. I
've reported it to Debian as
3569 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
3570 have no idea yet how to figure out exactly what subsystem is doing
3571 this. Perhaps you can help? Perhaps you know what the Gnome
3572 developers did to handle this, and this can give a clue to the KDE
3573 developers? Or you know where in KDE the screen brightness is changed
3574 during login? If so, please update the BTS report (or get in touch if
3575 you do not know how to update BTS).
</p
>
3577 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
3578 acpi_backlight=vendor, to disable ACPI backlight support completely,
3579 as the ACPI information on the machine is trash and it is better to
3580 leave it to the intel video driver to control the screen
3581 backlight.
</p
>
3586 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
3587 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
3588 <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>
3589 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
3590 <description><p
>Two days ago, I asked
3591 <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
3592 I could install Linux on a Packard Bell EasyNote LV computer
3593 preinstalled with Windows
8</a
>. I found a solution, but am horrified
3594 with the obstacles put in the way of Linux users on a laptop with UEFI
3595 and Windows
8.
</p
>
3597 <p
>I never found out if the cause of my problems were the use of UEFI
3598 secure booting or fast boot. I suspect fast boot was the problem,
3599 causing the firmware to boot directly from HD without considering any
3600 key presses and alternative devices, but do not know UEFI settings
3601 enough to tell.
</p
>
3603 <p
>There is no way to install Linux on the machine in question without
3604 opening the box and disconnecting the hard drive! This is as far as I
3605 can tell, the only way to get access to the firmware setup menu
3606 without accepting the Windows
8 license agreement. I am told (and
3607 found description on how to) that it is possible to configure the
3608 firmware setup once booted into Windows
8. But as I believe the terms
3609 of that agreement are completely unacceptable, accepting the license
3610 was never an alternative. I do not enter agreements I do not intend
3611 to follow.
</p
>
3613 <p
>I feared I had to return the laptops and ask for a refund, and
3614 waste many hours on this, but luckily there was a way to get it to
3615 work. But I would not recommend it to anyone planning to run Linux on
3616 it, and I have become sceptical to Windows
8 certified laptops. Is
3617 this the way Linux will be forced out of the market place, by making
3618 it close to impossible for
"normal
" users to install Linux without
3619 accepting the Microsoft Windows license terms? Or at least not
3620 without risking to loose the warranty?
</p
>
3622 <p
>I
've updated the
3623 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
3624 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
3625 do not have to struggle as much as I did to get Linux into the
3628 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3629 Michael Tokarev and others for feedback and ideas.
</p
>
3634 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
3635 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
3636 <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>
3637 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
3638 <description><p
>I
've run into quite a problem the last few days. I bought three
3639 new laptops for my parents and a few others. I bought Packard Bell
3640 Easynote LV to run Kubuntu on and use as their home computer. But I
3641 am completely unable to figure out how to install Linux on it. The
3642 computer is preinstalled with Windows
8, and I suspect it uses UEFI
3643 instead of a BIOS to boot.
</p
>
3645 <p
>The problem is that I am unable to get it to PXE boot, and unable
3646 to get it to boot the Linux installer from my USB stick. I have yet
3647 to try the DVD install, and still hope it will work. when I turn on
3648 the computer, there is no information on what buttons to press to get
3649 the normal boot menu. I expect to get some boot menu to select PXE or
3650 USB stick booting. When booting, it first ask for the language to
3651 use, then for some regional settings, and finally if I will accept the
3652 Windows
8 terms of use. As these terms are completely unacceptable to
3653 me, I have no other choice but to turn off the computer and try again
3654 to get it to boot the Linux installer.
</p
>
3656 <p
>I have gathered my findings so far on a Linlap page about the
3657 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3658 EasyNote LV
</a
> model. If you have any idea how to get Linux
3659 installed on this machine, please get in touch or update that wiki
3660 page. If I can
't find a way to install Linux, I will have to return
3661 the laptop to the seller and find another machine for my parents.
</p
>
3663 <p
>I wonder, is this the way Linux will be forced out of the market
3664 using UEFI and
"secure boot
" by making it impossible to install Linux
3665 on new Laptops?
</p
>
3670 <title>How to transform a Debian based system to a Debian Edu installation
</title>
3671 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
3672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
3673 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
3674 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
3675 an operating system based on Debian intended for use in schools. It
3676 contain a turn-key solution for the computer network provided to
3677 pupils in the primary schools. It provide both the central server,
3678 network boot servers and desktop environments with heaps of
3679 educational software. The project was founded almost
12 years ago,
3680 2001-
07-
02. If you want to support the project, which is in need for
3681 cash to fund developer gatherings and other project related activity,
3682 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
3683 donate some money
</a
>.
3685 <p
>A topic that come up again and again on the Debian Edu mailing
3686 lists and elsewhere, is the question on how to transform a Debian or
3687 Ubuntu installation into a Debian Edu installation. It isn
't very
3688 hard, and last week I wrote a script to replicate the steps done by
3689 the Debian Edu installer.
</p
>
3691 <p
>The script,
3692 <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/
>
3693 in the debian-edu-config package, will go through these six steps and
3694 transform an existing Debian Wheezy or Ubuntu (untested) installation
3695 into a Debian Edu Workstation:
</p
>
3699 <li
>Add skolelinux related APT sources.
</li
>
3700 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
3701 <li
>Install debian-edu-install to load preseeding values and pull in
3702 our configuration.
</li
>
3703 <li
>Preseed debconf database with profile setup in
3704 /etc/debian-edu/config, and run tasksel to install packages
3705 according to the profile specified in the config above,
3706 overriding some of the Debian automation machinery.
</li
>
3707 <li
>Run debian-edu-cfengine-D installation to configure everything
3708 that could not be done using preseeding.
</li
>
3709 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
3713 <p
>There are some steps in the Debian Edu installation that can not be
3714 replicated like this. Disk partitioning and LVM setup, for example.
3715 So this script just assume there is enough disk space to install all
3716 the needed packages.
</p
>
3718 <p
>The script was created to help a Debian Edu student working on
3719 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
3720 Debian Edu client, and using it he can take the existing
3721 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
3722 transform it into a fully functioning Debian Edu Workstation (or
3723 Roaming Workstation, or whatever :).
</p
>
3725 <p
>The default setting in the script is to create a KDE Workstation.
3726 If a LXDE based Roaming workstation is wanted instead, modify the
3727 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
3729 <p
><pre
>
3730 PROFILE=
"Roaming-Workstation
"
3731 DESKTOP=
"lxde
"
3732 </pre
></p
>
3734 <p
>The script could even become useful to set up Debian Edu servers in
3735 the cloud, by starting with a virtual Debian installation at some
3736 virtual hosting service and setting up all the services on first
3742 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
3743 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
3744 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
3745 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
3746 <description><P
>In January,
3747 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
3748 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
3749 channel #debian-lego
</a
>, for those of us in the Debian and Linux
3750 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
3751 marvellous construction system from Denmark. We also created
3752 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
3753 a place to take notes and write down our plans and hopes. And several
3754 people showed up to help. I was very happy to see the effect of my
3755 call. Since the small start, we have a debtags tag
3756 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
3757 tag for LEGO related packages, and now count
10 packages related to
3758 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
3760 <p
><table
>
3761 <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
>
3762 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
3763 <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
>
3764 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
3765 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
3766 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
3767 <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
>
3768 <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
>
3769 <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
>
3770 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
3771 </table
></p
>
3773 <p
>Some of these are available in Wheezy, and all but one are
3774 currently available in Jessie/testing. leocad is so far only
3775 available in experimental.
</p
>
3777 <p
>If you care about LEGO in Debian, please join us on IRC and help
3778 adding the rest of the great free software tools available on Linux
3779 for LEGO designers.
</p
>
3784 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
3785 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
3786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
3787 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
3788 <description><p
>When I woke up this morning, I was very happy to see that the
3789 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
3790 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
3791 Debian release, and I expect to move my machines at home over to it fairly
3794 <p
>The new debian release contain heaps of new stuff, and one program
3795 in particular make me very happy to see included. The
3796 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
3797 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
3798 included for the first time. Alongside similar programs like
3799 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
3800 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
3801 it allow for visual programming where syntax errors can not happen,
3802 and a friendly programming environment for learning to control the
3803 computer. Scratch will also be included in the next release of Debian
3806 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
3807 Edu/Skolelinux release too. The
3808 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
3809 alpha release
</a
> went out last week, and the next should soon
3815 <title>Isenkram
0.2 finally in the Debian archive
</title>
3816 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
3817 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
3818 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
3819 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
3820 package
</a
> finally made it into the archive, after lingering in NEW
3821 for many months. I uploaded it to the Debian experimental suite
3822 2013-
01-
27, and today it was accepted into the archive.
</p
>
3824 <p
>Isenkram is a system for suggesting to users what packages to
3825 install to work with a pluggable hardware device. The suggestion pop
3826 up when the device is plugged in. For example if a Lego Mindstorm NXT
3827 is inserted, it will suggest to install the program needed to program
3828 the NXT controller. Give it a go, and report bugs and suggestions to
3834 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
3835 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
3836 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
3837 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
3838 <description><p
>My
3839 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
3840 bitcoin related blog post
</a
> mentioned that the new
3841 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
3842 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3843 2013-
01-
19, and have been available in unstable since then. It was
3844 automatically copied to Ubuntu, and is available in their Raring
3845 version too.
</p
>
3847 <p
>But there is a strange problem with the build that block this new
3848 version from being available on the i386 and kfreebsd-i386
3849 architectures. For some strange reason, the autobuilders in Debian
3850 for these architectures fail to run the test suite on these
3851 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
3852 We are so far unable to reproduce it when building it manually, and
3853 no-one have been able to propose a fix. If you got an idea what is
3854 failing, please let us know via the BTS.
</p
>
3856 <p
>One feature that is annoying me with of the bitcoin client, because
3857 I often run low on disk space, is the fact that the client will exit
3858 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
3859 #
696715</a
>). So make sure you have enough disk space when you run
3862 <p
>As usual, if you use bitcoin and want to show your support of my
3863 activities, please send Bitcoin donations to my address
3864 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3869 <title>Welcome to the world, Isenkram!
</title>
3870 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
3871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
3872 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
3873 <description><p
>Yesterday, I
3874 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
3875 for testers
</a
> for my prototype for making Debian better at handling
3876 pluggable hardware devices, which I
3877 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
3878 out to create
</a
> earlier this month. Several valuable testers showed
3879 up, and caused me to really want to to open up the development to more
3880 people. But before I did this, I want to come up with a sensible name
3881 for this project. Today I finally decided on a new name, and I have
3882 renamed the project from hw-support-handler to this new name. In the
3883 process, I moved the source to git and made it available as a
3884 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
3885 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
3886 To fetch and build the latest version of the source, use
</p
>
3889 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3890 cd isenkram
&& git-buildpackage -us -uc
3893 <p
>I have not yet adjusted all files to use the new name yet. If you
3894 want to hack on the source or improve the package, please go ahead.
3895 But please talk to me first on IRC or via email before you do major
3896 changes, to make sure we do not step on each others toes. :)
</p
>
3898 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
3899 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3900 stuff, in other words. I
've been told it is the Norwegian variant of
3901 the German word eisenkram, for those that are familiar with that
3904 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
3905 instructions, to avoid confusing people with an error from the signing
3908 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
3909 clone argument to avoid the need for authentication.
</p
>
3914 <title>First prototype ready making hardware easier to use in Debian
</title>
3915 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
3916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
3917 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
3918 <description><p
>Early this month I set out to try to
3919 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
3920 the Debian support for pluggable hardware devices
</a
>. Now my
3921 prototype is working, and it is ready for a larger audience. To test
3923 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
3924 from the Debian Edu subversion repository
</a
>, build and install the
3925 package. You might have to log out and in again activate the
3926 autostart script.
</p
>
3928 <p
>The design is simple:
</p
>
3932 <li
>Add desktop entry in /usr/share/autostart/ causing a program
3933 hw-support-handlerd to start when the user log in.
</li
>
3935 <li
>This program listen for kernel events about new hardware (directly
3936 from the kernel like udev does), not using HAL dbus events as I
3937 initially did.
</li
>
3939 <li
>When new hardware is inserted, look up the hardware modalias in
3940 the APT database, a database
3941 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
3942 via HTTP
</a
> and a database available as part of the package.
</li
>
3944 <li
>If a package is mapped to the hardware in question, the package
3945 isn
't installed yet and this is the first time the hardware was
3946 plugged in, show a desktop notification suggesting to install the
3947 package or packages.
</li
>
3949 <li
>If the user click on the
'install package now
' button, ask
3950 aptdaemon via the PackageKit API to install the requrired package.
</li
>
3952 <li
>aptdaemon ask for root password or sudo password, and install the
3953 package while showing progress information in a window.
</li
>
3957 <p
>I still need to come up with a better name for the system. Here
3958 are some screen shots showing the prototype in action. First the
3959 notification, then the password request, and finally the request to
3960 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
3962 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
3963 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
3964 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
3965 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
3966 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
3968 <p
>The prototype still need to be improved with longer timeouts, but
3969 is already useful. The database of hardware to package mappings also
3970 need more work. It is currently compatible with the Ubuntu way of
3971 storing such information in the package control file, but could be
3972 changed to use other formats instead or in addition to the current
3973 method. I
've dropped the use of discover for this mapping, as the
3974 modalias approach is more flexible and easier to use on Linux as long
3975 as the Linux kernel expose its modalias strings directly.
</p
>
3977 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
3978 here is the command required to check out and build the source: Use
3979 '<tt
>svn checkout
3980 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3981 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
3982 devscripts package.
</p
>
3984 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
3985 renamed to Isenkram and the source moved from the Debian Edu
3986 subversion repository to a Debian collab-maint git repository. See
3987 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
3988 instructions
</a
> for details.
</p
>
3993 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
3994 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
3995 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
3996 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
3997 <description><p
>This Christmas my trusty old laptop died. It died quietly and
3998 suddenly in bed. With a quiet whimper, it went completely quiet and
3999 black. The power button was no longer able to turn it on. It was a
4000 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4001 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4002 Compaq I had before that. Now I need to find a replacement. To keep
4003 going during Christmas, I moved the one year old SSD disk to my old
4004 X40 where it fitted (only one I had left that could use it), but it is
4005 not a durable solution.
4007 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4008 got a new one more than
10 years ago. It still holds true.:)
</p
>
4012 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4013 than A4).
</li
>
4014 <li
>Robust, it will be in my backpack every day.
</li
>
4015 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4016 <li
>Long battery life time. Preferable a week.
</li
>
4017 <li
>Internal WIFI network card.
</li
>
4018 <li
>Internal Twisted Pair network card.
</li
>
4019 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4020 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4021 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4023 <li
>Hardware supported by Debian Stable, ie the default kernel and
4024 X.org packages.
</li
>
4025 <li
>Quiet, preferably fan free (or at least not using the fan most of
4030 <p
>You will notice that there are no RAM and CPU requirements in the
4031 list. The reason is simply that the specifications on laptops the
4032 last
10-
15 years have been sufficient for my needs, and I have to look
4033 at other features to choose my laptop. But are there still made as
4034 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4035 robust, and Thinkpads seem to be heading in the wrong direction since
4036 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4037 still be useful.
</p
>
4039 <p
>Perhaps I should rethink my needs, and look for a pad with an
4040 external keyboard? I
'll have to check the
4041 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4042 well-supported laptops, or perhaps just buy one preinstalled from one
4043 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4044 Pre-loaded site
</a
>.
</p
>
4049 <title>How to find a browser plugin supporting a given MIME type
</title>
4050 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4051 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4052 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4053 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4054 install to get support for a given MIME type. Thanks to
4055 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4056 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4057 Unfortunately, not very many packages provide the needed meta
4058 information, Anyway, here is a small script to look up all browser
4059 plugin packages announcing ther MIME support using this specification:
</p
>
4065 def pkgs_handling_mimetype(mimetype):
4070 version = pkg.candidate
4072 version = pkg.installed
4075 record = version.record
4076 if not record.has_key(
'Npp-MimeType
'):
4078 mime_types = record[
'Npp-MimeType
'].split(
',
')
4079 for t in mime_types:
4080 t = t.rstrip().strip()
4082 thepkgs.append(pkg.name)
4084 mimetype =
"audio/ogg
"
4085 if
1 < len(sys.argv):
4086 mimetype = sys.argv[
1]
4087 print
"Browser plugin packages supporting %s:
" % mimetype
4088 for pkg in pkgs_handling_mimetype(mimetype):
4089 print
" %s
" %pkg
4092 <p
>It can be used like this to look up a given MIME type:
</p
>
4095 % ./apt-find-browserplug-for-mimetype
4096 Browser plugin packages supporting audio/ogg:
4098 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4099 Browser plugin packages supporting application/x-shockwave-flash:
4100 browser-plugin-gnash
4104 <p
>In Ubuntu this mechanism is combined with support in the browser
4105 itself to query for plugins and propose to install the needed
4106 packages. It would be great if Debian supported such feature too. Is
4107 anyone working on adding it?
</p
>
4109 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4110 request for icweasel support for this feature is
4111 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4112 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4113 of manpower and wish for a different design is the reason thus feature
4114 is not yet in iceweasel from Debian.
</p
>
4119 <title>What is the most supported MIME type in Debian?
</title>
4120 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4122 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4123 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4124 proposal to add AppStream information to the Debian archive
</a
>, is a
4125 proposal to make it possible for a Desktop application to propose to
4126 the user some package to install to gain support for a given MIME
4127 type, font, library etc. that is currently missing. With such
4128 mechanism in place, it would be possible for the desktop to
4129 automatically propose and install leocad if some LDraw file is
4130 downloaded by the browser.
</p
>
4132 <p
>To get some idea about the current content of the archive, I decided
4133 to write a simple program to extract all .desktop files from the
4134 Debian archive and look up the claimed MIME support there. The result
4136 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4137 site
</a
>. Using the collected information, it become possible to
4138 answer the question in the title. Here are the
20 most supported MIME
4139 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4140 The complete list is available from the link above.
</p
>
4142 <p
><strong
>Debian Stable:
</strong
></p
>
4146 ----- -----------------------
4162 18 application/x-ogg
4169 <p
><strong
>Debian Testing:
</strong
></p
>
4173 ----- -----------------------
4189 18 application/x-ogg
4196 <p
><strong
>Debian Unstable:
</strong
></p
>
4200 ----- -----------------------
4217 18 application/x-ogg
4223 <p
>I am told that PackageKit can provide an API to access the kind of
4224 information mentioned in DEP-
11. I have not yet had time to look at
4225 it, but hope the PackageKit people in Debian are on top of these
4228 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4229 discovering a typo in my script.
</p
>
4234 <title>Using modalias info to find packages handling my hardware
</title>
4235 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4237 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4238 <description><p
>Yesterday, I wrote about the
4239 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4240 values provided by the Linux kernel
</a
> following my hope for
4241 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4242 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4243 modalias values attached to package names can be used to map packages
4244 to hardware. This allow the system to look up and suggest relevant
4245 packages when I plug in some new hardware into my machine, and replace
4246 discover and discover-data as the database used to map hardware to
4249 <p
>I create a modaliases file with entries like the following,
4250 containing package name, kernel module name (if relevant, otherwise
4251 the package name) and globs matching the relevant hardware
4254 <p
><blockquote
>
4255 Package: package-name
4256 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4257 </blockquote
></p
>
4259 <p
>It is fairly trivial to write code to find the relevant packages
4260 for a given modalias value using this file.
</p
>
4262 <p
>An entry like this would suggest the video and picture application
4263 cheese for many USB web cameras (interface bus class
0E01):
</p
>
4265 <p
><blockquote
>
4267 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
4268 </blockquote
></p
>
4270 <p
>An entry like this would suggest the pcmciautils package when a
4271 CardBus bridge (bus class
0607) PCI device is present:
</p
>
4273 <p
><blockquote
>
4274 Package: pcmciautils
4275 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4276 </blockquote
></p
>
4278 <p
>An entry like this would suggest the package colorhug-client when
4279 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
4281 <p
><blockquote
>
4282 Package: colorhug-client
4283 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
4284 </blockquote
></p
>
4286 <p
>I believe the format is compatible with the format of the Packages
4287 file in the Debian archive. Ubuntu already uses their Packages file
4288 to store their mappings from packages to hardware.
</p
>
4290 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
4291 announce the hardware it support in a way my prototype understand.
4292 This allow those publishing packages in an APT source outside the
4293 Debian archive as well as those backporting packages to make sure the
4294 hardware mapping are included in the package meta information. I
've
4295 tested such header in the pymissile package, and its modalias mapping
4296 is working as it should with my prototype. It even made it to Ubuntu
4299 <p
>To test if it was possible to look up supported hardware using only
4300 the shell tools available in the Debian installer, I wrote a shell
4301 implementation of the lookup code. The idea is to create files for
4302 each modalias and let the shell do the matching. Please check out and
4304 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
4305 shell script. It run without any extra dependencies and fetch the
4306 hardware mappings from the Debian archive and the subversion
4307 repository where I currently work on my prototype.
</p
>
4309 <p
>When I use it on a machine with a yubikey inserted, it suggest to
4310 install yubikey-personalization:
</p
>
4312 <p
><blockquote
>
4313 % ./hw-support-lookup
4314 <br
>yubikey-personalization
4316 </blockquote
></p
>
4318 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4319 propose to install the pcmciautils package:
</p
>
4321 <p
><blockquote
>
4322 % ./hw-support-lookup
4323 <br
>pcmciautils
4325 </blockquote
></p
>
4327 <p
>If you know of any hardware-package mapping that should be added to
4328 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
4329 database
</a
>, please tell me about it.
</p
>
4331 <p
>It could be possible to generate several of the mappings between
4332 packages and hardware. One source would be to look at packages with
4333 kernel modules, ie packages with *.ko files in /lib/modules/, and
4334 extract their modalias information. Another would be to look at
4335 packages with udev rules, ie packages with files in
4336 /lib/udev/rules.d/, and extract their vendor/model information to
4337 generate a modalias matching rule. I have not tested any of these to
4338 see if it work.
</p
>
4340 <p
>If you want to help implementing a system to let us propose what
4341 packages to install when new hardware is plugged into a Debian
4342 machine, please send me an email or talk to me on
4343 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4348 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
4349 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
4350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
4351 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
4352 <description><p
>While looking into how to look up Debian packages based on hardware
4353 information, to find the packages that support a given piece of
4354 hardware, I refreshed my memory regarding modalias values, and decided
4355 to document the details. Here are my findings so far, also available
4357 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4358 Debian Edu subversion repository
</a
>:
4360 <p
><strong
>Modalias decoded
</strong
></p
>
4362 <p
>This document try to explain what the different types of modalias
4363 values stands for. It is in part based on information from
4364 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
4365 &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;,
4366 &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
4367 &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;.
4369 <p
>The modalias entries for a given Linux machine can be found using
4370 this shell script:
</p
>
4373 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
4376 <p
>The supported modalias globs for a given kernel module can be found
4377 using modinfo:
</p
>
4380 % /sbin/modinfo psmouse | grep alias:
4381 alias: serio:ty05pr*id*ex*
4382 alias: serio:ty01pr*id*ex*
4386 <p
><strong
>PCI subtype
</strong
></p
>
4388 <p
>A typical PCI entry can look like this. This is an Intel Host
4389 Bridge memory controller:
</p
>
4391 <p
><blockquote
>
4392 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4393 </blockquote
></p
>
4395 <p
>This represent these values:
</p
>
4400 sv
00001028 (subvendor)
4401 sd
000001AD (subdevice)
4403 sc
00 (bus subclass)
4407 <p
>The vendor/device values are the same values outputted from
'lspci
4408 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4409 0600. The
0600 class is a host bridge. Other useful bus values are
4410 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4412 <p
>Not sure how to figure out the interface value, nor what it
4415 <p
><strong
>USB subtype
</strong
></p
>
4417 <p
>Some typical USB entries can look like this. This is an internal
4418 USB hub in a laptop:
</p
>
4420 <p
><blockquote
>
4421 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4422 </blockquote
></p
>
4424 <p
>Here is the values included in this alias:
</p
>
4427 v
1D6B (device vendor)
4428 p
0001 (device product)
4430 dc
09 (device class)
4431 dsc
00 (device subclass)
4432 dp
00 (device protocol)
4433 ic
09 (interface class)
4434 isc
00 (interface subclass)
4435 ip
00 (interface protocol)
4438 <p
>The
0900 device class/subclass means hub. Some times the relevant
4439 class is in the interface class section. For a simple USB web camera,
4440 these alias entries show up:
</p
>
4442 <p
><blockquote
>
4443 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4444 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4445 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4446 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4447 </blockquote
></p
>
4449 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4450 camera),
0101 is audio control device and
0102 is audio streaming (aka
4451 microphone). Thus this is a camera with microphone included.
</p
>
4453 <p
><strong
>ACPI subtype
</strong
></p
>
4455 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
4456 receiver in a Thinkpad X40:
</p
>
4458 <p
><blockquote
>
4459 acpi:IBM0071:PNP0511:
4460 </blockquote
></p
>
4462 <p
>The values between the colons are IDs.
</p
>
4464 <p
><strong
>DMI subtype
</strong
></p
>
4466 <p
>The DMI table contain lots of information about the computer case
4467 and model. This is an entry for a IBM Thinkpad X40, fetched from
4468 /sys/devices/virtual/dmi/id/modalias:
</p
>
4470 <p
><blockquote
>
4471 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4472 </blockquote
></p
>
4474 <p
>The values present are
</p
>
4477 bvn IBM (BIOS vendor)
4478 bvr
1UETB
6WW(
1.66) (BIOS version)
4479 bd
06/
15/
2005 (BIOS date)
4480 svn IBM (system vendor)
4481 pn
2371H4G (product name)
4482 pvr ThinkPadX40 (product version)
4483 rvn IBM (board vendor)
4484 rn
2371H4G (board name)
4485 rvr NotAvailable (board version)
4486 cvn IBM (chassis vendor)
4487 ct
10 (chassis type)
4488 cvr NotAvailable (chassis version)
4491 <p
>The chassis type
10 is Notebook. Other interesting values can be
4492 found in the dmidecode source:
</p
>
4496 4 Low Profile Desktop
4509 17 Main Server Chassis
4510 18 Expansion Chassis
4512 20 Bus Expansion Chassis
4513 21 Peripheral Chassis
4515 23 Rack Mount Chassis
4524 <p
>The chassis type values are not always accurately set in the DMI
4525 table. For example my home server is a tower, but the DMI modalias
4526 claim it is a desktop.
</p
>
4528 <p
><strong
>SerIO subtype
</strong
></p
>
4530 <p
>This type is used for PS/
2 mouse plugs. One example is from my
4531 test machine:
</p
>
4533 <p
><blockquote
>
4534 serio:ty01pr00id00ex00
4535 </blockquote
></p
>
4537 <p
>The values present are
</p
>
4546 <p
>This type is supported by the psmouse driver. I am not sure what
4547 the valid values are.
</p
>
4549 <p
><strong
>Other subtypes
</strong
></p
>
4551 <p
>There are heaps of other modalias subtypes according to
4552 file2alias.c. There is the rest of the list from that source: amba,
4553 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4554 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4555 vmbus, x86cpu and zorro. I did not spend time documenting all of
4556 these, as they do not seem relevant for my intended use with mapping
4557 hardware to packages when new stuff is inserted during run time.
</p
>
4559 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
4561 <p
>To check which kernel modules provide support for a given modalias,
4562 one can use the following shell script:
</p
>
4565 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
4566 echo
"$id
" ; \
4567 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
4571 <p
>The output can look like this (only the first few entries as the
4572 list is very long on my test machine):
</p
>
4576 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
4578 FATAL: Module acpi:device: not found.
4580 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
4581 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
4582 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
4583 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4584 acpi:IBM0071:PNP0511:
4585 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
4586 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
4587 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
4591 <p
>If you want to help implementing a system to let us propose what
4592 packages to install when new hardware is plugged into a Debian
4593 machine, please send me an email or talk to me on
4594 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4596 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
4597 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
4598 in /sys/ with space in them.
</p
>
4603 <title>Moved the pymissile Debian packaging to collab-maint
</title>
4604 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
4605 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
4606 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
4607 <description><p
>As part of my investigation on how to improve the support in Debian
4608 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4609 Launcher and updated the Debian package
4610 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
4611 sure udev will fix the device permissions when it is plugged in. I
4612 also added a
"Modaliases
" header to test it in the Debian archive and
4613 hopefully make the package be proposed by jockey in Ubuntu when a user
4614 plug in his rocket launcher. In the process I moved the source to a
4615 git repository under collab-maint, to make it easier for any DD to
4616 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
4617 is not very active, but the software still work for me even after five
4618 years of relative silence. The new git repository is not listed in
4619 the uploaded package yet, because I want to test the other changes a
4620 bit more before I upload the new version. If you want to check out
4621 the new version with a .desktop file included, visit the
4622 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
4623 view
</a
> or use
"<tt
>git clone
4624 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
4629 <title>Lets make hardware dongles easier to use in Debian
</title>
4630 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
4631 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
4632 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
4633 <description><p
>One thing that annoys me with Debian and Linux distributions in
4634 general, is that there is a great package management system with the
4635 ability to automatically install software packages by downloading them
4636 from the distribution mirrors, but no way to get it to automatically
4637 install the packages I need to use the hardware I plug into my
4638 machine. Even if the package to use it is easily available from the
4639 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4640 suggest to automatically install the python-nxt, nbc and t2n packages
4641 I need to talk to it. When I plug in a Yubikey, it could propose the
4642 yubikey-personalization package. The information required to do this
4643 is available, but no-one have pulled all the pieces together.
</p
>
4645 <p
>Some years ago, I proposed to
4646 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
4647 the discover subsystem to implement this
</a
>. The idea is fairly
4652 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
4653 starting when a user log in.
</li
>
4655 <li
>Set this program up to listen for kernel events emitted when new
4656 hardware is inserted into the computer.
</li
>
4658 <li
>When new hardware is inserted, look up the hardware ID in a
4659 database mapping to packages, and take note of any non-installed
4660 packages.
</li
>
4662 <li
>Show a message to the user proposing to install the discovered
4663 package, and make it easy to install it.
</li
>
4667 <p
>I am not sure what the best way to implement this is, but my
4668 initial idea was to use dbus events to discover new hardware, the
4669 discover database to find packages and
4670 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
4673 <p
>Yesterday, I found time to try to implement this idea, and the
4674 draft package is now checked into
4675 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4676 Debian Edu subversion repository
</a
>. In the process, I updated the
4677 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
4678 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4679 the relevant packages in Debian, and uploaded a new version
4680 2.2013.01.09 to unstable. I also discovered that the current
4681 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
4682 package in Debian no longer discovered any USB devices, because
4683 /proc/bus/usb/devices is no longer present. I ported it to use
4684 libusb as a fall back option to get it working. The fixed package
4685 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
4686 because of the freeze).
</p
>
4688 <p
>With this prototype in place, I can insert my Yubikey, and get this
4689 desktop notification to show up (only once, the first time it is
4690 inserted):
</p
>
4692 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
4694 <p
>For this prototype to be really useful, some way to automatically
4695 install the proposed packages by pressing the
"Please install
4696 program(s)
" button should to be implemented.
</p
>
4698 <p
>If this idea seem useful to you, and you want to help make it
4699 happen, please help me update the discover-data database with mappings
4700 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
4701 list the package you would like to have installed when a given
4702 hardware device is inserted into your computer, and report bugs using
4703 reportbug if it isn
't. Or, if you know of a better way to provide
4704 such mapping, please let me know.
</p
>
4706 <p
>This prototype need more work, and there are several questions that
4707 should be considered before it is ready for production use. Is dbus
4708 the correct way to detect new hardware? At the moment I look for HAL
4709 dbus events on the system bus, because that is the events I could see
4710 on my Debian Squeeze KDE desktop. Are there better events to use?
4711 How should the user be notified? Is the desktop notification
4712 mechanism the best option, or should the background daemon raise a
4713 popup instead? How should packages be installed? When should they
4714 not be installed?
</p
>
4716 <p
>If you want to help getting such feature implemented in Debian,
4717 please send me an email. :)
</p
>
4722 <title>New IRC channel for LEGO designers using Debian
</title>
4723 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
4724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
4725 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
4726 <description><p
>During Christmas, I have worked a bit on the Debian support for
4727 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
4728 NXT
</a
>. My son and I have played a bit with my NXT set, and I
4729 discovered I had to build all the tools myself because none were
4730 already in Debian Squeeze. If Debian support for LEGO is something
4731 you care about, please join me on the IRC channel
4732 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
4733 irc.debian.org). There is a lot that could be done to improve the
4734 Debian support for LEGO designers. For example both CAD software
4735 and Mindstorm compilers are missing. :)
</p
>
4737 <p
>Update
2012-
01-
03: A
4738 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
4739 including links to Lego related packages is now available.
</p
>
4744 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
4745 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
4746 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
4747 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
4748 <description><p
>Let me start by wishing you all marry Christmas and a happy new
4749 year! I hope next year will prove to be a good year.
</p
>
4751 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
4752 decentralised
"currency
" that allow people to transfer bitcoins
4753 between each other with minimal overhead, is a very interesting
4754 experiment. And as I wrote a few days ago, the bitcoin situation in
4755 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
4756 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
4757 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
4758 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
4759 for one of the ftpmasters to approve the new bitcoin-qt package
4762 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
4763 team in Debian, you can easily test the package in Debian Squeeze
4764 using the following steps to get a set of working packages:
</p
>
4766 <blockquote
><pre
>
4767 git clone git://git.debian.org/git/collab-maint/bitcoin
4769 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4770 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4771 </pre
></blockquote
>
4773 <p
>You might have to install some build dependencies as well. The
4774 list of commands should give you two packages, bitcoind and
4775 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4776 client will download the complete set of bitcoin
"blocks
", which need
4777 around
5.6 GiB of data on my machine at the moment. Make sure your
4778 ~/.bitcoin/ directory have lots of spare room if you want to download
4779 all the blocks. The client will warn if the disk is getting full, so
4780 there is not really a problem if you got too little room, but you will
4781 not be able to get all the features out of the client.
</p
>
4783 <p
>As usual, if you use bitcoin and want to show your support of my
4784 activities, please send Bitcoin donations to my address
4785 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4790 <title>A word on bitcoin support in Debian
</title>
4791 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
4792 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
4793 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
4794 <description><p
>It has been a while since I wrote about
4795 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
4796 peer-to-peer based crypto-currency, and the reason is simply that I
4797 have been busy elsewhere. But two days ago, I started looking at the
4798 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
4799 Debian
</a
> again to try to recover my old bitcoin wallet. The package
4800 is now maintained by a
4801 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
4802 people
</a
>, and the grunt work had already been done by this team. We
4803 owe a huge thank you to all these team members. :)
4804 But I was sad to discover that the bitcoin client is missing in
4805 Wheezy. It is only available in Sid (and an outdated client from
4806 backports). The client had several RC bugs registered in BTS blocking
4807 it from entering testing. To try to help the team and improve the
4808 situation, I spent some time providing patches and triaging the bug
4809 reports. I also had a look at the bitcoin package available from Matt
4811 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
4812 Ubuntu
</a
>, and moved the useful pieces from that version into the
4813 Debian package.
</p
>
4815 <p
>After checking with the main package maintainer Jonas Smedegaard on
4816 IRC, I pushed several patches into the collab-maint git repository to
4817 improve the package. It now contains fixes for the RC issues (not from
4818 me, but fixed by Scott Howard), build rules for a Qt GUI client
4819 package, konqueror support for the bitcoin: URI and bash completion
4820 setup. As I work on Debian Squeeze, I also created
4821 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
4822 patch to backport
</a
> the latest version. Jonas is going to look at
4823 it and try to integrate it into the git repository before uploading a
4824 new version to unstable.
4826 <p
>I would very much like bitcoin to succeed, to get rid of the
4827 centralized control currently exercised in the monetary system. I
4828 find it completely unacceptable that the USA government is collecting
4829 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4830 that the major credit card companies can block legal money
4831 transactions to Wikileaks. But for bitcoin to succeed, more people
4832 need to use bitcoins, and more people need to accept bitcoins when
4833 they sell products and services. Improving the bitcoin support in
4834 Debian is a small step in the right direction, but not enough.
4835 Unfortunately the user experience when browsing the web and wanting to
4836 pay with bitcoin is still not very good. The bitcoin: URI is a step
4837 in the right direction, but need to work in most or every browser in
4838 use. Also the bitcoin-qt client is too heavy to fire up to do a
4839 quick transaction. I believe there are other clients available, but
4840 have not tested them.
</p
>
4843 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
4844 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
4845 I received
20.15 BTC so far on the address I provided in my blog two
4846 years ago, as can be
4847 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
4848 on the blockexplorer service
</a
>. Thank you everyone for your
4849 donation. The blockexplorer service demonstrates quite well that
4850 bitcoin is not quite anonymous and untracked. :) I wonder if the
4851 number of users have gone up since then. If you use bitcoin and want
4852 to show your support of my activity, please send Bitcoin donations to
4853 the same address as last time,
4854 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4859 <title>Git repository for song book for Computer Scientists
</title>
4860 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
4861 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
4862 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
4863 <description><p
>As I
4864 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
4865 this summer
</a
>, I have created a Computer Science song book a few
4866 years ago, and today I finally found time to create a public
4867 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
4868 repository for the project
</a
>.
</p
>
4870 <p
>If you want to help out, please clone the source and submit patches
4871 to the HTML version. To generate the PDF and PostScript version,
4872 please use prince XML, or let me know about a useful free software
4873 processor capable of creating a good looking PDF from the HTML.
</p
>
4875 <p
>Want to sing? You can still find the song book in HTML, PDF and
4876 PostScript formats at
4877 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
4878 Science Songbook
</a
>.
</p
>
4883 <title>Gratulerer med
19-årsdagen, Debian!
</title>
4884 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
4885 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
4886 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
4887 <description><p
>I dag fyller
4888 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
4889 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
4890 si gratulerer med dagen, Debian!
</p
>
4895 <title>Song book for Computer Scientists
</title>
4896 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
4897 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
4898 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
4899 <description><p
>Many years ago, while studying Computer Science at the
4900 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
4901 collecting computer related songs for use at parties. The original
4902 version was written in LaTeX, but a few years ago I got help from
4903 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4904 while keeping the ability to create a nice book in PDF format. I have
4905 not had time to maintain the book for a while now, and guess I should
4906 put it up on some public version control repository where others can
4907 help me extend and update the book. If anyone is volunteering to help
4908 me with this, send me an email. Also let me know if there are songs
4909 missing in my book.
</p
>
4911 <p
>I have not mentioned the book on my blog so far, and it occured to
4912 me today that I really should let all my readers share the joys of
4913 singing out load about programming, computers and computer networks.
4914 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
4915 12</a
> is about to start (and I am not going). Want to sing? Check
4916 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
4917 Computer Science Songbook
</a
>.
4922 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
4923 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
4924 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
4925 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
4926 <description><p
>At work we have heaps of servers. I believe the total count is
4927 around
1000 at the moment. To be able to get help from the vendors
4928 when something go wrong, we want to keep the firmware on the servers
4929 up to date. If the firmware isn
't the latest and greatest, the
4930 vendors typically refuse to start debugging any problems until the
4931 firmware is upgraded. So before every reboot, we want to upgrade the
4932 firmware, and we would really like everyone handling servers at the
4933 university to do this themselves when they plan to reboot a machine.
4934 For that to happen we at the unix server admin group need to provide
4935 the tools to do so.
</p
>
4937 <p
>To make firmware upgrading easier, I am working on a script to
4938 fetch and install the latest firmware for the servers we got. Most of
4939 our hardware are from Dell and HP, so I have focused on these servers
4940 so far. This blog post is about the Dell part.
</P
>
4942 <p
>On the Dell FTP site I was lucky enough to find
4943 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
4944 with firmware information for all
11th generation servers, listing
4945 which firmware should be used on a given model and where on the FTP
4946 site I can find it. Using a simple perl XML parser I can then
4947 download the shell scripts Dell provides to do firmware upgrades from
4948 within Linux and reboot when all the firmware is primed and ready to
4949 be activated on the first reboot.
</p
>
4951 <p
>This is the Dell related fragment of the perl code I am working on.
4952 Are there anyone working on similar tools for firmware upgrading all
4953 servers at a site? Please get in touch and lets share resources.
</p
>
4955 <p
><pre
>
4959 use File::Temp qw(tempdir);
4961 # Install needed RHEL packages if missing
4963 'XML::Simple
' =
> 'perl-XML-Simple
',
4965 for my $module (keys %rhelmodules) {
4966 eval
"use $module;
";
4968 my $pkg = $rhelmodules{$module};
4969 system(
"yum install -y $pkg
");
4970 eval
"use $module;
";
4974 my $errorsto =
'pere@hungry.com
';
4980 sub run_firmware_script {
4981 my ($opts, $script) = @_;
4983 print STDERR
"fail: missing script name\n
";
4986 print STDERR
"Running $script\n\n
";
4988 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
4989 print STDERR
"success: firmware script ran succcessfully\n
";
4991 print STDERR
"fail: firmware script returned error\n
";
4995 sub run_firmware_scripts {
4996 my ($opts, @dirs) = @_;
4997 # Run firmware packages
4998 for my $dir (@dirs) {
4999 print STDERR
"info: Running scripts in $dir\n
";
5000 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5001 while (my $s = readdir $dh) {
5002 next if $s =~ m/^\.\.?/;
5003 run_firmware_script($opts,
"$dir/$s
");
5011 print STDERR
"info: Downloading $url\n
";
5012 system(
"wget --quiet \
"$url\
"");
5017 my $product = `dmidecode -s system-product-name`;
5020 if ($product =~ m/PowerEdge/) {
5022 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5023 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5025 my $tmpdir = tempdir(
5029 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5030 system(
'gunzip Catalog.xml.gz
');
5031 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5032 # -q is quiet, disabling interactivity and reducing console output
5033 my $fwopts =
"-q
";
5035 for my $url (@paths) {
5036 fetch_dell_fw($url);
5038 run_firmware_scripts($fwopts, $tmpdir);
5040 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5041 print STDERR
"error: Please report to $errorsto.\n
";
5045 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5046 print STDERR
"error: Please report to $errorsto.\n
";
5052 my $url =
"ftp://ftp.us.dell.com/$path
";
5056 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5057 # firmware packages to download from Dell. Only work for Linux
5058 # machines and
11th generation Dell servers.
5059 sub fetch_dell_fw_list {
5060 my $filename = shift;
5062 my $product = `dmidecode -s system-product-name`;
5064 my ($mybrand, $mymodel) = split(/\s+/, $product);
5066 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5068 my $xml = XMLin($filename);
5070 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5071 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5072 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5074 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5075 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5077 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5079 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5081 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5084 for my $component (@{$xml-
>{SoftwareComponent}}) {
5085 my $componenttype = $component-
>{ComponentType}-
>{value};
5087 # Drop application packages, only firmware and BIOS
5088 next if
'APAC
' eq $componenttype;
5090 my $cpath = $component-
>{path};
5091 for my $path (@paths) {
5092 if ($cpath =~ m%/$path$%) {
5093 push(@paths, $cpath);
5101 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5102 it could work on other platforms with some tweaking. Anyone know a
5103 index like Catalog.xml is available from HP for HP servers? At the
5104 moment I maintain a similar list manually and it is quickly getting
5110 <title>How is booting into runlevel
1 different from single user boots?
</title>
5111 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5113 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5114 <description><p
>Wouter Verhelst have some
5115 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5116 comments and opinions
</a
> on my blog post on
5117 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5118 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5119 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5120 default KDE desktop in Debian
</a
>. I only have time to address one
5121 small piece of his comment now, and though it best to address the
5122 misunderstanding he bring forward:
</p
>
5124 <p
><blockquote
>
5125 Currently, a system admin has four options: [...] boot to a
5126 single-user system (by adding
'single
' to the kernel command line;
5127 this runs rcS and rc1 scripts)
5128 </blockquote
></p
>
5130 <p
>This make me believe Wouter believe booting into single user mode
5131 and booting into runlevel
1 is the same. I am not surprised he
5132 believe this, because it would make sense and is a quite sensible
5133 thing to believe. But because the boot in Debian is slightly broken,
5134 runlevel
1 do not work properly and it isn
't the same as single user
5135 mode. I
'll try to explain what is actually happing, but it is a bit
5136 hard to explain.
</p
>
5138 <p
>Single user mode is defined like this in /etc/inittab:
5139 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5140 executed in single user mode is sulogin. Single user mode is a boot
5141 state
"between
" the runlevels, and when booting into single user mode,
5142 only the scripts in /etc/rcS.d/ are executed before the init process
5143 enters the single user state. When switching to runlevel
1, the state
5144 is in fact not ending in runlevel
1, but it passes through runlevel
1
5145 and end up in the single user mode (see /etc/rc1.d/S03single, which
5146 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5147 1. It is confusing that the
'S
' (single user) init mode is not the
5148 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5151 <p
>This summary might make it clearer. When booting for the first
5152 time into single user mode, the following commands are executed:
5153 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5154 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5155 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5156 trying to continue after visiting single user mode. Not all services
5157 are started again as they should, causing the machine to end up in an
5158 unpredicatble state. This is why Debian admins recommend rebooting
5159 after visiting single user mode.
</p
>
5161 <p
>A similar problem with runlevel
1 is caused by the amount of
5162 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5163 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5164 stopped when passing through the scripts in /etc/rc1.d/, and not
5165 started again when switching away from runlevel
1 to the runlevels
5166 2-
5. I believe the problem is best fixed by moving all the scripts
5167 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5168 functioning single user mode during boot.
</p
>
5170 <p
>I have spent several years investigating the Debian boot system,
5171 and discovered this problem a few years ago. I suspect it originates
5172 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5177 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5178 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5179 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5180 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5181 <description><p
>In the Debian boot system, several packages include scripts that
5182 are started from /etc/rcS.d/. In fact, there is a bite more of them
5183 than make sense, and this causes a few problems. What kind of
5184 problems, you might ask. There are at least two problems. The first
5185 is that it is not possible to recover a machine after switching to
5186 runlevel
1. One need to actually reboot to get the machine back to
5187 the expected state. The other is that single user boot will sometimes
5188 run into problems because some of the subsystems are activated before
5189 the root login is presented, causing problems when trying to recover a
5190 machine from a problem in that subsystem. A minor additional point is
5191 that moving more scripts out of rcS.d/ and into the other rc#.d/
5192 directories will increase the amount of scripts that can run in
5193 parallel during boot, and thus decrease the boot time.
</p
>
5195 <p
>So, which scripts should start from rcS.d/. In short, only the
5196 scripts that _have_ to execute before the root login prompt is
5197 presented during a single user boot should go there. Everything else
5198 should go into the numeric runlevels. This means things like
5199 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5200 the numeric runlevels. Today in Debian, there are around
115 init.d
5201 scripts that are started from rcS.d/, and most of them should be moved
5202 out. Do your package have one of them? Please help us make single
5203 user and runlevel
1 better by moving it.
</p
>
5205 <p
>Scripts setting up the screen, keyboard, system partitions
5206 etc. should still be started from rcS.d/, but there is for example no
5207 need to have the network enabled before the single user login prompt
5208 is presented.
</p
>
5210 <p
>As always, things are not so easy to fix as they sound. To keep
5211 Debian systems working while scripts migrate and during upgrades, the
5212 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5213 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5214 and the next ones can only be moved when their dependencies have been
5215 moved first. This migration must be done sequentially while we ensure
5216 that the package system upgrade packages in the right order to keep
5217 the system state correct. This will require some coordination when it
5218 comes to network related packages, but most of the packages with
5219 scripts that should migrate do not have anything in rcS.d/ depending
5220 on them. Some packages have already been updated, like the sudo
5221 package, while others are still left to do. I wish I had time to work
5222 on this myself, but real live constrains make it unlikely that I will
5223 find time to push this forward.
</p
>
5228 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5229 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5231 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5232 <description><p
>While at Debconf11, I have several times during discussions
5233 mentioned the issues I believe should be improved in Debian for its
5234 desktop to be useful for more people. The use case for this is my
5235 parents, which are currently running Kubuntu which solve the
5238 <p
>I suspect these four missing features are not very hard to
5239 implement. After all, they are present in Ubuntu, so if we wanted to
5240 do this in Debian we would have a source.
</p
>
5244 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5245 are new packages available for upgrades, a icon in the KDE status bar
5246 indicate this, and clicking on it will activate the simple upgrade
5247 tool to handle it. I have no problem guiding both of my parents
5248 through the process over the phone. If a kernel reboot is required,
5249 this too is indicated by the status bars and the upgrade tool. Last
5250 time I checked, nothing with the same features was working in KDE in
5253 <li
><strong
>Simple handling of missing Firefox browser
5254 plugins.
</strong
> When the browser encounter a MIME type it do not
5255 currently have a handler for, it will ask the user if the system
5256 should search for a package that would add support for this MIME type,
5257 and if the user say yes, the APT sources will be searched for packages
5258 advertising the MIME type in their control file (visible in the
5259 Packages file in the APT archive). If one or more packages are found,
5260 it is a simple click of the mouse to add support for the missing mime
5261 type. If the package require the user to accept some non-free
5262 license, this is explained to the user. The entire process make it
5263 more clear to the user why something do not work in the browser, and
5264 make the chances higher for the user to blame the web page authors and
5265 not the browser for any missing features.
</li
>
5267 <li
><strong
>Simple handling of missing multimedia codec/format
5268 handlers.
</strong
> When the media players encounter a format or codec
5269 it is not supporting, a dialog pop up asking the user if the system
5270 should search for a package that would add support for it. This
5271 happen with things like MP3, Windows Media or H
.264. The selection
5272 and installation procedure is very similar to the Firefox browser
5273 plugin handling. This is as far as I know implemented using a
5274 gstreamer hook. The end result is that the user easily get access to
5275 the codecs that are present from the APT archives available, while
5276 explaining more on why a given format is unsupported by Ubuntu.
</li
>
5278 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
5279 displaying a text/plain file in my Debian browser, it will propose to
5280 start emacs to show it. If I remember correctly, when doing the same
5281 in Kunbutu it show the file as a text file in the browser. At least I
5282 know Opera will show text files within the browser. I much prefer the
5283 latter behaviour.
</li
>
5287 <p
>There are other nice features as well, like the simplified suite
5288 upgrader, but given that I am the one mostly doing the dist-upgrade,
5289 it do not matter much.
</p
>
5291 <p
>I really hope we could get these features in place for the next
5292 Debian release. It would require the coordinated effort of several
5293 maintainers, but would make the end user experience a lot better.
</p
>
5298 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
5299 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
5300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
5301 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
5302 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
5303 site is build on Debian/Squeeze, and this platform was chosen because
5304 I am most familiar with Debian (being a Debian Developer for around
10
5305 years) because it is the latest stable Debian release which should get
5306 security support for a few years.
</p
>
5308 <p
>The web service is written in Perl, and depend on some perl modules
5309 that are missing in Debian at the moment. It would be great if these
5310 modules were added to the Debian archive, allowing anyone to set up
5311 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
5312 in their own country using only Debian packages. The list of modules
5313 missing in Debian/Squeeze isn
't very long, and I hope the perl group
5314 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
5315 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5316 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5317 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5318 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5319 easier in the future.
</p
>
5321 <p
>Thanks to the great tools in Debian, getting the missing modules
5322 installed on my server was a simple call to
'cpan2deb Module::Name
'
5323 and
'dpkg -i
' to install the resulting package. But this leave me
5324 with the responsibility of tracking security problems, which I really
5325 do not have time for.
</p
>
5330 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
5331 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
5332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
5333 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
5334 <description><p
>Here is a small update for my English readers. Most of my blog
5335 posts have been in Norwegian the last few weeks, so here is a short
5336 update in English.
</p
>
5338 <p
>The kids still keep me too busy to get much free software work
5339 done, but I did manage to organise a project to get a Norwegian port
5340 of the British service
5341 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
5342 and it has been running for a month now. The entire project has been
5343 organised by me and two others. Around Christmas we gathered sponsors
5344 to fund the development work. In January I drafted a contract with
5345 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
5346 and in February the development took place. Most of it involved
5347 converting the source to use GPS coordinates instead of British
5348 easting/northing, and the resulting code should be a lot easier to get
5349 running in any country by now. The Norwegian
5350 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
5351 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
5352 source and the source for administrative borders in Norway, and
5353 support for this had to be added/fixed.
</p
>
5355 <p
>The Norwegian version went live March
3th, and we spent the weekend
5356 polishing the system before we announced it March
7th. The system is
5357 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
5358 problem reports in a few weeks. Soon we hope to announce the Android
5359 and iPhone versions making it even easier to report problems with the
5360 public infrastructure.
</p
>
5362 <p
>Perhaps something to consider for those of you in countries without
5363 such service?
</p
>
5368 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
5369 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
5370 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
5371 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
5372 <description><p
>The last few days I have looked at ways to track open security
5373 issues here at my work with the University of Oslo. My idea is that
5374 it should be possible to use the information about security issues
5375 available on the Internet, and check our locally
5376 maintained/distributed software against this information. It should
5377 allow us to verify that no known security issues are forgotten. The
5378 CVE database listing vulnerabilities seem like a great central point,
5379 and by using the package lists from Debian mapped to CVEs provided by
5380 the testing security team, I believed it should be possible to figure
5381 out which security holes were present in our free software
5382 collection.
</p
>
5384 <p
>After reading up on the topic, it became obvious that the first
5385 building block is to be able to name software packages in a unique and
5386 consistent way across data sources. I considered several ways to do
5387 this, for example coming up with my own naming scheme like using URLs
5388 to project home pages or URLs to the Freshmeat entries, or using some
5389 existing naming scheme. And it seem like I am not the first one to
5390 come across this problem, as MITRE already proposed and implemented a
5391 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5392 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5393 software, hardware and other platform components. The CPE ids are
5394 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5395 Vulnerability Database
</a
>, allowing me to look up know security
5396 issues for any CPE name. With this in place, all I need to do is to
5397 locate the CPE id for the software packages we use at the university.
5398 This is fairly trivial (I google for
'cve cpe $package
' and check the
5399 NVD entry if a CVE for the package exist).
</p
>
5401 <p
>To give you an example. The GNU gzip source package have the CPE
5402 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5403 check out, one could look up
5404 <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
5405 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5406 The most recent one is
5407 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5408 and at the bottom of the NVD page for this vulnerability the complete
5409 list of affected versions is provided.
</p
>
5411 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5412 for offline processing of issues. Using this dump, I
've written a
5413 small script taking a list of CPEs as input and list all CVEs
5414 affecting the packages represented by these CPEs. One give it CPEs
5415 with version numbers as specified above and get a list of open
5416 security issues out.
</p
>
5418 <p
>Of course for this approach to be useful, the quality of the NVD
5419 information need to be high. For that to happen, I believe as many as
5420 possible need to use and contribute to the NVD database. I notice
5422 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5423 map from CVE to CPE
</a
>, indicating that they are using the CPE
5424 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5426 <p
>To get an idea about the quality for free software, I spent some
5427 time making it possible to compare the CVE database from Debian with
5428 the CVE database in NVD. The result look fairly good, but there are
5429 some inconsistencies in NVD (same software package having several
5430 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5431 Debian believe are affected by a CVE). Hope to find time to improve
5432 the quality of NVD, but that require being able to get in touch with
5433 someone maintaining it. So far my three emails with questions and
5434 corrections have not seen any reply, but I hope contact can be
5435 established soon.
</p
>
5437 <p
>An interesting application for CPEs is cross platform package
5438 mapping. It would be useful to know which packages in for example
5439 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5440 this would be trivial if all linux distributions provided CPE entries
5441 for their packages.
</p
>
5446 <title>Which module is loaded for a given PCI and USB device?
</title>
5447 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5449 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5450 <description><p
>In the
5451 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5452 package in Debian, there is a script to report useful information
5453 about the running hardware for use when people report missing
5454 information. One part of this script that I find very useful when
5455 debugging hardware problems, is the part mapping loaded kernel module
5456 to the PCI device it claims. It allow me to quickly see if the kernel
5457 module I expect is driving the hardware I am struggling with. To see
5458 the output, make sure discover-data is installed and run
5459 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
5460 one of my machines like this:
</p
>
5464 10de:
03eb i2c_nforce2
5467 10de:
03f0 snd_hda_intel
5476 <p
>The code in question look like this, slightly modified for
5477 readability and to drop the output to file descriptor
3:
</p
>
5480 if [ -d /sys/bus/pci/devices/ ] ; then
5481 echo loaded pci modules:
5483 cd /sys/bus/pci/devices/
5484 for address in * ; do
5485 if [ -d
"$address/driver/module
" ] ; then
5486 module=`cd $address/driver/module ; pwd -P | xargs basename`
5487 if grep -q
"^$module
" /proc/modules ; then
5488 address=$(echo $address |sed s/
0000://)
5489 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
5490 echo
"$id $module
"
5499 <p
>Similar code could be used to extract USB device module
5503 if [ -d /sys/bus/usb/devices/ ] ; then
5504 echo loaded usb modules:
5506 cd /sys/bus/usb/devices/
5507 for address in * ; do
5508 if [ -d
"$address/driver/module
" ] ; then
5509 module=`cd $address/driver/module ; pwd -P | xargs basename`
5510 if grep -q
"^$module
" /proc/modules ; then
5511 address=$(echo $address |sed s/
0000://)
5512 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
5513 if [
"$id
" ] ; then
5514 echo
"$id $module
"
5524 <p
>This might perhaps be something to include in other tools as
5530 <title>How to test if a laptop is working with Linux
</title>
5531 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
5532 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
5533 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
5534 <description><p
>The last few days I have spent at work here at the
<a
5535 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
5536 batch of computers will work with Linux. Every year for the last few
5537 years the university have organised shared bid of a few thousand
5538 computers, and this year HP won the bid. Two different desktops and
5539 five different laptops are on the list this year. We in the UNIX
5540 group want to know which one of these computers work well with RHEL
5541 and Ubuntu, the two Linux distributions we currently handle at the
5542 university.
</p
>
5544 <p
>My test method is simple, and I share it here to get feedback and
5545 perhaps inspire others to test hardware as well. To test, I PXE
5546 install the OS version of choice, and log in as my normal user and run
5547 a few applications and plug in selected pieces of hardware. When
5548 something fail, I make a note about this in the test matrix and move
5549 on. If I have some spare time I try to report the bug to the OS
5550 vendor, but as I only have the machines for a short time, I rarely
5551 have the time to do this for all the problems I find.
</p
>
5553 <p
>Anyway, to get to the point of this post. Here is the simple tests
5554 I perform on a new model.
</p
>
5558 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
5559 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5560 RHEL5 and Debian Edu/Squeeze.
</li
>
5562 <li
>Is X.org working? If the graphical login screen show up after
5563 installation, X.org is working.
</li
>
5565 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
5566 package mesa-utils on Ubuntu) and writing down the frames per second
5567 reported by the program.
</li
>
5569 <li
>Is sound working? With Gnome and KDE, a sound is played when
5570 logging in, and if I can hear this the test is successful. If there
5571 are several audio exits on the machine, I try them all and check if
5572 the Gnome/KDE audio mixer can control where to send the sound. I
5573 normally test this by playing
5574 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
5575 video
</a
> in Firefox/Iceweasel.
</li
>
5577 <li
>Is the USB subsystem working? I test this by plugging in a USB
5578 memory stick and see if Gnome/KDE notices this.
</li
>
5580 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
5581 I have lying around, and see if Gnome/KDE notices this.
</li
>
5583 <li
>Is any built in camera working? Test using cheese, and see if a
5584 picture from the v4l device show up.
</li
>
5586 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5587 any bluetooth devices are discovered. In my office, I normally see a
5590 <li
>For laptops, is the SD or Compaq Flash reader working. I have
5591 memory modules lying around, and stick them in and see if Gnome/KDE
5592 notice this.
</li
>
5594 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
5595 special button work, and if the laptop continue to work after
5598 <li
>For laptops, is the extra buttons working, like audio level,
5599 adjusting background light, switching on/off external video output,
5600 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5601 laptop to laptop, so I just write down which are working and which are
5604 <li
>Some laptops have smart card readers, finger print readers,
5605 acceleration sensors etc. I rarely test these, as I do not know how
5606 to quickly test if they are working or not, so I only document their
5607 existence.
</li
>
5611 <p
>By now I suspect you are really curious what the test results are
5612 for the HP machines I am testing. I
'm not done yet, so I will report
5613 the test results later. For now I can report that HP
8100 Elite work
5614 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
5615 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
5616 can see, I have most machines left to test. One interesting
5617 observation is that Ubuntu Lucid has almost twice the frame rate than
5618 RHEL6 with glxgears. No idea why.
</p
>
5623 <title>Some thoughts on BitCoins
</title>
5624 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
5625 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
5626 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
5627 <description><p
>As I continue to explore
5628 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
5629 what properties the system have, and how it will be affected by laws
5630 and regulations here in Norway. Here are some random notes.
</p
>
5632 <p
>One interesting thing to note is that since the transactions are
5633 verified using a peer to peer network, all details about a transaction
5634 is known to everyone. This means that if a BitCoin address has been
5635 published like I did with mine in my initial post about BitCoin, it is
5636 possible for everyone to see how many BitCoins have been transfered to
5637 that address. There is even a web service to look at the details for
5638 all transactions. There I can see that my address
5639 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
5640 have received
16.06 Bitcoin, the
5641 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
5642 address of Simon Phipps have received
181.97 BitCoin and the address
5643 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
5644 of EFF have received
2447.38 BitCoins so far. Thank you to each and
5645 every one of you that donated bitcoins to support my activity. The
5646 fact that anyone can see how much money was transfered to a given
5647 address make it more obvious why the BitCoin community recommend to
5648 generate and hand out a new address for each transaction. I
'm told
5649 there is no way to track which addresses belong to a given person or
5650 organisation without the person or organisation revealing it
5651 themselves, as Simon, EFF and I have done.
</p
>
5653 <p
>In Norway, and in most other countries, there are laws and
5654 regulations limiting how much money one can transfer across the border
5655 without declaring it. There are money laundering, tax and accounting
5656 laws and regulations I would expect to apply to the use of BitCoin.
5657 If the Skolelinux foundation
5658 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
5659 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
5660 normal bank transfers like EFF is doing, how should this be accounted?
5661 Given that it is impossible to know if money can cross the border or
5662 not, should everything or nothing be declared? What exchange rate
5663 should be used when calculating taxes? Would receivers have to pay
5664 income tax if the foundation were to pay Skolelinux contributors in
5665 BitCoin? I have no idea, but it would be interesting to know.
</p
>
5667 <p
>For a currency to be useful and successful, it must be trusted and
5668 accepted by a lot of users. It must be possible to get easy access to
5669 the currency (as a wage or using currency exchanges), and it must be
5670 easy to spend it. At the moment BitCoin seem fairly easy to get
5671 access to, but there are very few places to spend it. I am not really
5672 a regular user of any of the vendor types currently accepting BitCoin,
5673 so I wonder when my kind of shop would start accepting BitCoins. I
5674 would like to buy electronics, travels and subway tickets, not herbs
5675 and books. :) The currency is young, and this will improve over time
5676 if it become popular, but I suspect regular banks will start to lobby
5677 to get BitCoin declared illegal if it become popular. I
'm sure they
5678 will claim it is helping fund terrorism and money laundering (which
5679 probably would be true, as is any currency in existence), but I
5680 believe the problems should be solved elsewhere and not by blaming
5681 currencies.
</p
>
5683 <p
>The process of creating new BitCoins is called mining, and it is
5684 CPU intensive process that depend on a bit of luck as well (as one is
5685 competing against all the other miners currently spending CPU cycles
5686 to see which one get the next lump of cash). The
"winner
" get
50
5687 BitCoin when this happen. Yesterday I came across the obvious way to
5688 join forces to increase ones changes of getting at least some coins,
5689 by coordinating the work on mining BitCoins across several machines
5690 and people, and sharing the result if one is lucky and get the
50
5692 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
5693 if this sounds interesting. I have not had time to try to set up a
5694 machine to participate there yet, but have seen that running on ones
5695 own for a few days have not yield any BitCoins througth mining
5698 <p
>Update
2010-
12-
15: Found an
<a
5699 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
5700 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
5701 it was interesting to read. The arguments presented seem to be
5702 equally valid for gold, which was used as a currency for many years.
</p
>
5707 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
5708 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
5709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
5710 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
5711 <description><p
>With this weeks lawless
5712 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
5713 attacks
</a
> on Wikileak and
5714 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
5715 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
5716 not be trusted to handle money transactions.
5718 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
5719 Phipps on bitcoin
</a
> reminded me about a project that a friend of
5720 mine mentioned earlier. I decided to follow Simon
's example, and get
5721 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
5722 some help from my friend to get it all running, and he even handed me
5723 some bitcoins to get started. I even donated a few bitcoins to Simon
5724 for helping me remember BitCoin.
</p
>
5726 <p
>So, what is bitcoins, you probably wonder? It is a digital
5727 crypto-currency, decentralised and handled using peer-to-peer
5728 networks. It allows anonymous transactions and prohibits central
5729 control over the transactions, making it impossible for governments
5730 and companies alike to block donations and other transactions. The
5731 source is free software, and while the key dependency wxWidgets
2.9
5732 for the graphical user interface is missing in Debian, the command
5733 line client builds just fine. Hopefully Jonas
5734 <a href=
"http://bugs.debian.org/
578157">will get the package into
5735 Debian
</a
> soon.
</p
>
5737 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
5738 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
5739 bitcoins
</a
> when selling services and goods, and there are even
5740 currency
"stock
" markets where the exchange rate is decided. There
5741 are not many users so far, but the concept seems promising. If you
5742 want to get started and lack a friend with any bitcoins to spare,
5744 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
5745 bitcoin at the time of writing). Use
5746 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
5747 on the current exchange rates.
</p
>
5749 <p
>As an experiment, I have decided to set up bitcoind on one of my
5750 machines. If you want to support my activity, please send Bitcoin
5751 donations to the address
5752 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
5757 <title>Why isn
't Debian Edu using VLC?
</title>
5758 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
5759 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
5760 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
5761 <description><p
>In the latest issue of Linux Journal, the readers choices were
5762 presented, and the winner among the multimedia player were VLC.
5763 Personally, I like VLC, and it is my player of choice when I first try
5764 to play a video file or stream. Only if VLC fail will I drag out
5765 gmplayer to see if it can do better. The reason is mostly the failure
5766 model and trust. When VLC fail, it normally pop up a error message
5767 reporting the problem. When mplayer fail, it normally segfault or
5768 just hangs. The latter failure mode drain my trust in the program.
<p
>
5770 <p
>But even if VLC is my player of choice, we have choosen to use
5771 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
5772 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
5773 plugin to play web videos seamlessly, and the VLC browser plugin is
5774 not very good. For example, it lack in-line control buttons, so there
5775 is no way for the user to pause the video. Also, when I
5776 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
5777 tested the browser plugins
</a
> available in Debian, the VLC plugin
5778 failed on several video pages where mplayer based plugins worked. If
5779 the browser plugin for VLC was as good as the gecko-mediaplayer
5780 package (which uses mplayer), we would switch.
</P
>
5782 <p
>While VLC is a good player, its user interface is slightly
5783 annoying. The most annoying feature is its inconsistent use of
5784 keyboard shortcuts. When the player is in full screen mode, its
5785 shortcuts are different from when it is playing the video in a window.
5786 For example, space only work as pause when in full screen mode. I
5787 wish it had consisten shortcuts and that space also would work when in
5788 window mode. Another nice shortcut in gmplayer is [enter] to restart
5789 the current video. It is very nice when playing short videos from the
5790 web and want to restart it when new people arrive to have a look at
5791 what is going on.
</p
>
5796 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
5797 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
5798 <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>
5799 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
5800 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
5801 upgrade testing of the
5802 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5803 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
5804 This seem like a very good idea, so I adjusted by test scripts and
5805 can now present the updated result from today:
</p
>
5807 <p
>This is for Gnome:
</p
>
5809 <p
>Installed using apt-get, missing with aptitude
</p
>
5811 <blockquote
><p
>
5816 browser-plugin-gnash
5823 freedesktop-sound-theme
5825 gconf-defaults-service
5840 gnome-desktop-environment
5844 gnome-session-canberra
5849 gstreamer0.10-fluendo-mp3
5855 libapache2-mod-dnssd
5858 libaprutil1-dbd-sqlite3
5861 libboost-date-time1.42
.0
5862 libboost-python1.42
.0
5863 libboost-thread1.42
.0
5865 libchamplain-gtk-
0.4-
0
5867 libclutter-gtk-
0.10-
0
5874 libfreerdp-plugins-standard
5889 libgnomepanel2.24-cil
5894 libgtksourceview2.0-common
5895 libmono-addins-gui0.2-cil
5896 libmono-addins0.2-cil
5897 libmono-cairo2.0-cil
5898 libmono-corlib2.0-cil
5899 libmono-i18n-west2.0-cil
5900 libmono-posix2.0-cil
5901 libmono-security2.0-cil
5902 libmono-sharpzip2.84-cil
5903 libmono-system2.0-cil
5906 libndesk-dbus-glib1.0-cil
5907 libndesk-dbus1.0-cil
5917 libtelepathy-farsight0
5926 nautilus-sendto-empathy
5930 python-aptdaemon-gtk
5932 python-beautifulsoup
5947 python-gtksourceview2
5958 python-pkg-resources
5965 python-twisted-conch
5971 python-zope.interface
5976 rhythmbox-plugin-cdrecorder
5983 system-config-printer-udev
5985 telepathy-mission-control-
5
5996 </p
></blockquote
>
5998 <p
>Installed using apt-get, removed with aptitude
</p
>
6000 <blockquote
><p
>
6006 fast-user-switch-applet
6025 libgtksourceview2.0-
0
6027 libsdl1.2debian-alsa
6033 system-config-printer
6038 </p
></blockquote
>
6040 <p
>Installed using aptitude, missing with apt-get
</p
>
6042 <blockquote
><p
>
6043 gstreamer0.10-gnomevfs
6044 </p
></blockquote
>
6046 <p
>Installed using aptitude, removed with apt-get
</p
>
6048 <blockquote
><p
>
6050 </p
></blockquote
>
6052 <p
>This is for KDE:
</p
>
6054 <p
>Installed using apt-get, missing with aptitude
</p
>
6056 <blockquote
><p
>
6058 </p
></blockquote
>
6060 <p
>Installed using apt-get, removed with aptitude
</p
>
6062 <blockquote
><p
>
6065 </p
></blockquote
>
6067 <p
>Installed using aptitude, missing with apt-get
</p
>
6069 <blockquote
><p
>
6083 kdeartwork-emoticons
6085 kdeartwork-theme-icon
6089 kdebase-workspace-bin
6090 kdebase-workspace-data
6104 kscreensaver-xsavers
6119 plasma-dataengines-workspace
6121 plasma-desktopthemes-artwork
6122 plasma-runners-addons
6123 plasma-scriptengine-googlegadgets
6124 plasma-scriptengine-python
6125 plasma-scriptengine-qedje
6126 plasma-scriptengine-ruby
6127 plasma-scriptengine-webkit
6128 plasma-scriptengines
6129 plasma-wallpapers-addons
6130 plasma-widget-folderview
6131 plasma-widget-networkmanagement
6135 xscreensaver-data-extra
6137 xscreensaver-gl-extra
6138 xscreensaver-screensaver-bsod
6139 </p
></blockquote
>
6141 <p
>Installed using aptitude, removed with apt-get
</p
>
6143 <blockquote
><p
>
6145 google-gadgets-common
6163 libggadget-qt-
1.0-
0b
6168 libkonqsidebarplugin4a
6177 libplasma-geolocation-interface4
6179 libplasmagenericshell4
6193 libsmokeknewstuff2-
3
6194 libsmokeknewstuff3-
3
6196 libsmokektexteditor3
6204 libsmokeqtnetwork4-
3
6210 libsmokeqtuitools4-
3
6222 plasma-dataengines-addons
6223 plasma-scriptengine-superkaramba
6224 plasma-widget-lancelot
6225 plasma-widgets-addons
6226 plasma-widgets-workspace
6230 update-notifier-common
6231 </p
></blockquote
>
6233 <p
>Running apt-get autoremove made the results using apt-get and
6234 aptitude a bit more similar, but there are still quite a lott of
6235 differences. I have no idea what packages should be installed after
6236 the upgrade, but hope those that do can have a look.
</p
>
6241 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6242 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6244 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6245 <description><p
>Most of the computers in use by the
6246 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6247 are virtual machines. And they have been Xen machines running on a
6248 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6249 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6250 bit harder that it could have been, because we set up the Xen virtual
6251 machines to get the virtual partitions from LVM, which as far as I
6252 know is not supported by KVM. So to migrate, we had to convert
6253 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6256 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6257 nice recipe
</a
> to do this, and wrote the following script to do the
6258 migration. It uses qemu-img from the qemu package to make the disk
6259 image, parted to partition it, losetup and kpartx to present the disk
6260 image partions as devices, and dd to copy the data. I NFS mounted the
6261 new servers storage area on the old server to do the migration.
</p
>
6267 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6272 if [ -z
"$
1" ] ; then
6273 echo
"Usage: $
0 &lt;hostname
&gt;
"
6279 if [ ! -e /dev/vg_data/$host-disk ] ; then
6280 echo
"error: unable to find LVM volume for $host
"
6284 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6285 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6286 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6287 totalsize=$(( ( $disksize + $swapsize ) ))
6290 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
6291 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6293 parted $img mklabel msdos
6294 parted $img mkpart primary linux-swap
0 $disksize
6295 parted $img mkpart primary ext2 $disksize $totalsize
6296 parted $img set
1 boot on
6299 losetup /dev/loop0 $img
6300 kpartx -a /dev/loop0
6302 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
6303 fsck.ext3 -f /dev/mapper/loop0p1 || true
6304 mkswap /dev/mapper/loop0p2
6306 kpartx -d /dev/loop0
6307 losetup -d /dev/loop0
6310 <p
>The script is perhaps so simple that it is not copyrightable, but
6311 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
6313 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
6314 the new disk image attached, installed grub-pc and linux-image-
686 and
6315 set up grub to boot from the disk image. After this, the KVM machines
6316 seem to work just fine.
</p
>
6321 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
6322 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
6323 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
6324 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
6325 <description><p
>I
'm still running upgrade testing of the
6326 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6327 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
6328 status. Here is a short update based on a test I ran
20101118.
</p
>
6330 <p
>I still do not know what a correct migration should look like, so I
6331 report any differences between apt and aptitude and hope someone else
6332 can see if anything should be changed.
</p
>
6334 <p
>This is for Gnome:
</p
>
6336 <p
>Installed using apt-get, missing with aptitude
</p
>
6338 <blockquote
><p
>
6339 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6340 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
6341 dmz-cursor-theme empathy empathy-common finger
6342 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6343 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6344 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6345 gnome-cards-data gnome-codec-install gnome-core
6346 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6347 gnome-search-tool gnome-session-canberra gnome-spell
6348 gnome-system-log gnome-themes-extras gnome-themes-more
6349 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6350 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6351 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6352 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6353 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
6354 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
6355 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
6356 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
6357 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
6358 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6359 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
6360 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6361 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6362 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6363 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6364 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6365 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6366 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6367 libmono-security2.0-cil libmono-sharpzip2.84-cil
6368 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
6369 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
6370 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
6371 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
6372 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
6373 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
6374 libxalan2-java libxerces2-java media-player-info mesa-utils
6375 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
6376 nautilus-sendto-empathy openoffice.org-writer2latex
6377 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
6378 python-aptdaemon python-aptdaemon-gtk python-axiom
6379 python-beautifulsoup python-bugbuddy python-clientform
6380 python-coherence python-configobj python-crypto python-cupshelpers
6381 python-cupsutils python-eggtrayicon python-elementtree
6382 python-epsilon python-evolution python-feedparser python-gdata
6383 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6384 python-gtksourceview2 python-httplib2 python-louie python-mako
6385 python-markupsafe python-mechanize python-nevow python-notify
6386 python-opengl python-openssl python-pam python-pkg-resources
6387 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6388 python-tagpy python-twisted-bin python-twisted-conch
6389 python-twisted-core python-twisted-web python-utidylib python-webkit
6390 python-xdg python-zope.interface remmina remmina-plugin-data
6391 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6392 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6393 software-center svgalibg1 system-config-printer-udev
6394 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6395 totem totem-coherence totem-mozilla totem-plugins
6396 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6398 </p
></blockquote
>
6400 Installed using apt-get, removed with aptitude
6402 <blockquote
><p
>
6403 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6404 epiphany-extensions epiphany-gecko evolution-exchange
6405 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6406 gedit-common gnome-app-install gnome-games gnome-games-data
6407 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6408 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6409 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6410 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6411 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6412 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6413 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6414 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6415 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6416 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6417 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6418 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6419 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6420 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6421 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6422 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6423 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6424 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6425 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6426 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6427 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6428 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6429 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6430 sound-juicer swfdec-gnome system-config-printer totem-common
6431 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6432 </p
></blockquote
>
6434 <p
>Installed using aptitude, missing with apt-get
</p
>
6436 <blockquote
><p
>
6437 gstreamer0.10-gnomevfs
6438 </p
></blockquote
>
6440 <p
>Installed using aptitude, removed with apt-get
</p
>
6442 <blockquote
><p
>
6444 </p
></blockquote
>
6446 <p
>This is for KDE:
</p
>
6448 <p
>Installed using apt-get, missing with aptitude
</p
>
6450 <blockquote
><p
>
6451 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6452 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6453 ghostscript-x git gnome-audio gnugo granatier gs-common
6454 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6455 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6456 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6457 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6458 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6459 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6460 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6461 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6462 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6463 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6464 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6465 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
6466 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6467 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6468 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6469 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6470 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6471 libkrossui4 libmailtools-perl libmime-tools-perl
6472 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6473 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6474 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6475 lirc luatex marble networkstatus noatun-plugins
6476 openoffice.org-writer2latex palapeli palapeli-data parley
6477 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6478 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6479 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6481 </p
></blockquote
>
6483 <p
>Installed using apt-get, removed with aptitude
</p
>
6485 <blockquote
><p
>
6486 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6487 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6488 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6489 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6490 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6491 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6492 kitchensync kiten kjumpingcube klatin klettres klickety klines
6493 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6494 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6495 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6496 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6497 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6498 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6499 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6500 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6501 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6502 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
6503 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
6504 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6505 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
6506 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
6507 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6508 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6509 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6510 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6511 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6512 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6513 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
6514 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
6515 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6516 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6517 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6518 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6519 </p
></blockquote
>
6521 <p
>Installed using aptitude, missing with apt-get
</p
>
6523 <blockquote
><p
>
6524 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6525 kdeartwork kdebase kdebase-apps kdebase-workspace
6526 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6527 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6528 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6529 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6530 xscreensaver-screensaver-bsod
6531 </p
></blockquote
>
6533 <p
>Installed using aptitude, removed with apt-get
</p
>
6535 <blockquote
><p
>
6536 kdebase-bin konq-plugins konqueror
6537 </p
></blockquote
>
6542 <title>Gnash buildbot slave and Debian kfreebsd
</title>
6543 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
6544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
6545 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
6546 <description><p
>Answering
6547 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
6548 call from the Gnash project
</a
> for
6549 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
6550 current source, I have set up a virtual KVM machine on the Debian
6551 Edu/Skolelinux virtualization host to test the git source on
6552 Debian/Squeeze. I hope this can help the developers in getting new
6553 releases out more often.
</p
>
6555 <p
>As the developers want less main-stream build platforms tested to,
6556 I have considered setting up a
<a
6557 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
6558 machine as well. I have also considered using the kfreebsd
6559 architecture in Debian as a file server in NUUG to get access to the
5
6560 TB zfs volume we currently use to store DV video. Because of this, I
6561 finally got around to do a test installation of Debian/Squeeze with
6562 kfreebsd. Installation went fairly smooth, thought I noticed some
6563 visual glitches in the cdebconf dialogs (black cursor left on the
6564 screen at random locations). Have not gotten very far with the
6565 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6566 fatal problem. Have to spend some more time on it to see if it is
6567 useful as a file server for NUUG. Will try to find time to set up a
6568 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
6573 <title>Debian in
3D
</title>
6574 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
6575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
6576 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
6577 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
6579 <p
>3D printing is just great. I just came across this Debian logo in
6581 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
6582 thingiverse blog
</a
>.
</p
>
6587 <title>Software updates
2010-
10-
24</title>
6588 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
6589 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
6590 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
6591 <description><p
>Some updates.
</p
>
6593 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
6594 raise money for the project is going well. The lower limit of
10
6595 signers was reached in
24 hours, and so far
13 people have signed it.
6596 More signers and more funding is most welcome, and I am really curious
6597 how far we can get before the time limit of December
24 is reached.
6600 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
6601 about what appear to be a great code coverage tool capable of
6602 generating code coverage stats without any changes to the source code.
6604 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
6605 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
6606 It is missing in Debian, but the git source built just fine in Squeeze
6607 after I installed libelf-dev, libdwarf-dev, pkg-config and
6608 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6609 solvable. I hope kcov make it into Debian soon.
</p
>
6611 <p
>Finally found time to wrap up the release notes for
<a
6612 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
6613 new alpha release of Debian Edu
</a
>, and just published the second
6614 alpha test release of the Squeeze based Debian Edu /
6615 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
6616 release. Give it a try if you need a complete linux solution for your
6617 school, including central infrastructure server, workstations, thin
6618 client servers and diskless workstations. A nice touch added
6619 yesterday is RDP support on the thin client servers, for windows
6620 clients to get a Linux desktop on request.
</p
>
6625 <title>Some notes on Flash in Debian and Debian Edu
</title>
6626 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
6627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
6628 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
6629 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
6630 popularity-contest numbers
</a
>, the adobe-flashplugin package the
6631 second most popular used package that is missing in Debian. The sixth
6632 most popular is flashplayer-mozilla. This is a clear indication that
6633 working flash is important for Debian users. Around
10 percent of the
6634 users submitting data to popcon.debian.org have this package
6635 installed.
</p
>
6637 <p
>In the report written by Lars Risan in August
2008
6638 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
6639 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6640 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
6641 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
6642 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
6643 web sites require Flash to work, and lacking working Flash support in
6644 the web browser and the problems with installing it was perceived as a
6645 good reason to stay with Windows.
</p
>
6647 <p
>I once saw a funny and sad comment in a web forum, where Linux was
6648 said to be the retarded cousin that did not really understand
6649 everything you told him but could work fairly well. This was a
6650 comment regarding the problems Linux have with proprietary formats and
6651 non-standard web pages, and is sad because it exposes a fairly common
6652 understanding of whose fault it is if web pages that only work in for
6653 example Internet Explorer
6 fail to work on Firefox, and funny because
6654 it explain very well how annoying it is for users when Linux
6655 distributions do not work with the documents they receive or the web
6656 pages they want to visit.
</p
>
6658 <p
>This is part of the reason why I believe it is important for Debian
6659 and Debian Edu to have a well working Flash implementation in the
6660 distribution, to get at least popular sites as Youtube and Google
6661 Video to working out of the box. For Squeeze, Debian have the chance
6662 to include the latest version of Gnash that will make this happen, as
6663 the new release
0.8.8 was published a few weeks ago and is resting in
6664 unstable. The new version work with more sites that version
0.8.7.
6665 The Gnash maintainers have asked for a freeze exception, but the
6666 release team have not had time to reply to it yet. I hope they agree
6667 with me that Flash is important for the Debian desktop users, and thus
6668 accept the new package into Squeeze.
</p
>
6673 <title>Circular package dependencies harms apt recovery
</title>
6674 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
6675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
6676 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
6677 <description><p
>I discovered this while doing
6678 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
6679 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
6680 in Debian still got circular dependencies, and it is often claimed
6681 that apt and aptitude should be able to handle this just fine, but
6682 some times these dependency loops causes apt to fail.
</p
>
6684 <p
>An example is from todays
6685 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
6686 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
6687 causes perl-modules to fail to upgrade. The cause is simple. If a
6688 package fail to unpack, then only part of packages with the circular
6689 dependency might end up being unpacked when unpacking aborts, and the
6690 ones already unpacked will fail to configure in the recovery phase
6691 because its dependencies are unavailable.
</p
>
6693 <p
>In this log, the problem manifest itself with this error:
</p
>
6695 <blockquote
><pre
>
6696 dpkg: dependency problems prevent configuration of perl-modules:
6697 perl-modules depends on perl (
>=
5.10.1-
1); however:
6698 Version of perl on system is
5.10.0-
19lenny
2.
6699 dpkg: error processing perl-modules (--configure):
6700 dependency problems - leaving unconfigured
6701 </pre
></blockquote
>
6703 <p
>The perl/perl-modules circular dependency is already
6704 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
6705 hopefully be solved as soon as possible, but it is not the only one,
6706 and each one of these loops in the dependency tree can cause similar
6707 failures. Of course, they only occur when there are bugs in other
6708 packages causing the unpacking to fail, but it is rather nasty when
6709 the failure of one package causes the problem to become worse because
6710 of dependency loops.
</p
>
6713 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
6714 tireless effort by Bill Allombert
</a
>, the number of circular
6716 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
6717 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
6719 <p
>Todays testing also exposed a bug in
6720 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
6721 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
6722 apt-get and aptitude, the latter possibly caused by some circular
6723 dependency. Reported both to BTS to try to get someone to look at
6729 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
6730 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
6731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
6732 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
6733 <description><p
>This is a
6734 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
6736 <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
6738 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
6739 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
6741 <p
>As a step to try to see if it possible to merge the DNS and DHCP
6742 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6743 and dhcp3-server-ldap in Debian use the LDAP server. The two
6744 implementations are quite different in how they use LDAP.
</p
>
6746 To get this information, I started slapd with debugging enabled and
6747 dumped the debug output to a file to get the LDAP searches performed
6748 on a Debian Edu main-server. Here is a summary.
6750 <p
><strong
>powerdns
</strong
></p
>
6752 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
6753 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
6756 <p
>PowerDNS have two modes of operation using LDAP as its backend.
6757 One
"strict
" mode where the forward and reverse DNS lookups are done
6758 using the same LDAP objects, and a
"tree
" mode where the forward and
6759 reverse entries are in two different subtrees in LDAP with a structure
6760 based on the DNS names, as in tjener.intern and
6761 2.2.0.10.in-addr.arpa.
</p
>
6763 <p
>In tree mode, the server is set up to use a LDAP subtree as its
6764 base, and uses a
"base
" scoped search for the DNS name by adding
6765 "dc=tjener,dc=intern,
" to the base with a filter for
6766 "(associateddomain=tjener.intern)
" for the forward entry and
6767 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
6768 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
6769 forward entries, it is looking for attributes named dnsttl, arecord,
6770 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6771 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6772 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6773 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6774 spfrecord and modifytimestamp. For reverse entries it is looking for
6775 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6776 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6777 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6778 ldapsearch commands could look like this:
</p
>
6780 <blockquote
><pre
>
6781 ldapsearch -h ldap \
6782 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6783 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6784 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6785 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6786 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6787 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6789 ldapsearch -h ldap \
6790 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6791 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
6792 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6793 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6794 srvrecord naptrrecord modifytimestamp
6795 </pre
></blockquote
>
6797 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
6798 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6799 example LDAP objects used there. In addition to these objects, the
6800 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6801 also exist.
</p
>
6803 <blockquote
><pre
>
6804 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6806 objectclass: dnsdomain
6807 objectclass: domainrelatedobject
6810 associateddomain: tjener.intern
6812 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6814 objectclass: dnsdomain2
6815 objectclass: domainrelatedobject
6817 ptrrecord: tjener.intern
6818 associateddomain:
2.2.0.10.in-addr.arpa
6819 </pre
></blockquote
>
6821 <p
>In strict mode, the server behaves differently. When looking for
6822 forward DNS entries, it is doing a
"subtree
" scoped search with the
6823 same base as in the tree mode for a object with filter
6824 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
6825 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6826 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6827 naptrrecord and modifytimestamp. For reverse entires it also do a
6828 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
6829 and the requested attributes are associateddomain, dnsttl and
6830 modifytimestamp. In short, in strict mode the objects with ptrrecord
6831 go away, and the arecord attribute in the forward object is used
6834 <p
>The forward and reverse searches can be simulated using ldapsearch
6835 like this:
</p
>
6837 <blockquote
><pre
>
6838 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6839 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6840 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6841 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6842 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6843 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6845 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6846 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
6847 </pre
></blockquote
>
6849 <p
>In addition to the forward and reverse searches , there is also a
6850 search for SOA records, which behave similar to the forward and
6851 reverse lookups.
</p
>
6853 <p
>A thing to note with the PowerDNS behaviour is that it do not
6854 specify any objectclass names, and instead look for the attributes it
6855 need to generate a DNS reply. This make it able to work with any
6856 objectclass that provide the needed attributes.
</p
>
6858 <p
>The attributes are normally provided in the cosine (RFC
1274) and
6859 dnsdomain2 schemas. The latter is used for reverse entries like
6860 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
6862 <p
>In Debian Edu, we have created DNS objects using the object classes
6863 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6864 attributes) and domainrelatedobject (for associatedDomain). The use
6865 of structural object classes make it impossible to combine these
6866 classes with the object classes used by DHCP.
</p
>
6868 <p
>There are other schemas that could be used too, for example the
6869 dnszone structural object class used by Gosa and bind-sdb for the DNS
6870 attributes combined with the domainrelatedobject object class, but in
6871 this case some unused attributes would have to be included as well
6872 (zonename and relativedomainname).
</p
>
6874 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
6875 mode and not use any of the existing objectclasses (dnsdomain,
6876 dnsdomain2 and dnszone) when one want to combine the DNS information
6877 with DHCP information, and instead create a auxiliary object class
6878 defined something like this (using the attributes defined for
6879 dnsdomain and dnsdomain2 or dnszone):
</p
>
6881 <blockquote
><pre
>
6882 objectclass ( some-oid NAME
'dnsDomainAux
'
6885 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6886 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6887 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6888 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6889 A6Record $ DNAMERecord
6891 </pre
></blockquote
>
6893 <p
>This will allow any object to become a DNS entry when combined with
6894 the domainrelatedobject object class, and allow any entity to include
6895 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
6896 developers asking for their view on this schema and if they are
6897 interested in providing such schema with PowerDNS, and I hope my
6898 message will be accepted into their mailing list soon.
</p
>
6900 <p
><strong
>ISC dhcp
</strong
></p
>
6902 <p
>The DHCP server searches for specific objectclass and requests all
6903 the object attributes, and then uses the attributes it want. This
6904 make it harder to figure out exactly what attributes are used, but
6905 thanks to the working example in Debian Edu I can at least get an idea
6906 what is needed without having to read the source code.
</p
>
6908 <p
>In the DHCP server configuration, the LDAP base to use and the
6909 search filter to use to locate the correct dhcpServer entity is
6910 stored. These are the relevant entries from
6911 /etc/dhcp3/dhcpd.conf:
</p
>
6913 <blockquote
><pre
>
6914 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
6915 ldap-dhcp-server-cn
"dhcp
";
6916 </pre
></blockquote
>
6918 <p
>The DHCP server uses this information to nest all the DHCP
6919 configuration it need. The cn
"dhcp
" is located using the given LDAP
6920 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
6921 search result is this entry:
</p
>
6923 <blockquote
><pre
>
6924 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6927 objectClass: dhcpServer
6928 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6929 </pre
></blockquote
>
6931 <p
>The content of the dhcpServiceDN attribute is next used to locate the
6932 subtree with DHCP configuration. The DHCP configuration subtree base
6933 is located using a base scope search with base
"cn=DHCP
6934 Config,dc=skole,dc=skolelinux,dc=no
" and filter
6935 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
6936 The search result is this entry:
</p
>
6938 <blockquote
><pre
>
6939 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6942 objectClass: dhcpService
6943 objectClass: dhcpOptions
6944 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6945 dhcpStatements: ddns-update-style none
6946 dhcpStatements: authoritative
6947 dhcpOption: smtp-server code
69 = array of ip-address
6948 dhcpOption: www-server code
72 = array of ip-address
6949 dhcpOption: wpad-url code
252 = text
6950 </pre
></blockquote
>
6952 <p
>Next, the entire subtree is processed, one level at the time. When
6953 all the DHCP configuration is loaded, it is ready to receive requests.
6954 The subtree in Debian Edu contain objects with object classes
6955 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6956 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6957 and information about netmasks, dynamic range etc. Leaving out the
6958 details here because it is not relevant for the focus of my
6959 investigation, which is to see if it is possible to merge dns and dhcp
6960 related computer objects.
</p
>
6962 <p
>When a DHCP request come in, LDAP is searched for the MAC address
6963 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
6964 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
6965 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6966 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
6969 <blockquote
><pre
>
6970 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6973 objectClass: dhcpHost
6974 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6975 dhcpStatements: fixed-address hostname
6976 </pre
></blockquote
>
6978 <p
>There is less flexiblity in the way LDAP searches are done here.
6979 The object classes need to have fixed names, and the configuration
6980 need to be stored in a fairly specific LDAP structure. On the
6981 positive side, the invidiual dhcpHost entires can be anywhere without
6982 the DN pointed to by the dhcpServer entries. The latter should make
6983 it possible to group all host entries in a subtree next to the
6984 configuration entries, and this subtree can also be shared with the
6985 DNS server if the schema proposed above is combined with the dhcpHost
6986 structural object class.
6988 <p
><strong
>Conclusion
</strong
></p
>
6990 <p
>The PowerDNS implementation seem to be very flexible when it come
6991 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
6992 come to the the LDAP structure, the
"strict
" mode is very flexible,
6993 allowing DNS objects to be stored anywhere under the base cn specified
6994 in the configuration.
</p
>
6996 <p
>The DHCP implementation on the other hand is very inflexible, both
6997 regarding which LDAP schemas to use and which LDAP structure to use.
6998 I guess one could implement ones own schema, as long as the
6999 objectclasses and attributes have the names used, but this do not
7000 really help when the DHCP subtree need to have a fairly fixed
7001 structure.
</p
>
7003 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7004 this might work for Debian Edu:
</p
>
7006 <blockquote
><pre
>
7008 cn=machine-info (dhcpService) - dhcpServiceDN points here
7009 cn=dhcp (dhcpServer)
7010 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7011 cn=
10.0.2.0 (dhcpSubnet)
7012 cn=group1 (dhcpGroup/dhcpOptions)
7013 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7014 cn=
192.168.0.0 (dhcpSubnet)
7015 cn=group1 (dhcpGroup/dhcpOptions)
7016 ou=machines - PowerDNS base points here
7017 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7018 </pre
></blockquote
>
7020 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7021 entries to be in the dhcpGroup subtrees, the entries can be stored
7022 there instead of a common machines subtree, and the PowerDNS base
7023 would have to be moved one level up to the machine-info subtree.
</p
>
7025 <p
>The combined object under the machines subtree would look something
7026 like this:
</p
>
7028 <blockquote
><pre
>
7029 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7032 objectClass: dhcpHost
7033 objectclass: domainrelatedobject
7034 objectclass: dnsDomainAux
7035 associateddomain: hostname.intern
7036 arecord:
10.11.12.13
7037 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7038 dhcpStatements: fixed-address hostname.intern
7039 </pre
></blockquote
>
7041 </p
>One could even add the LTSP configuration associated with a given
7042 machine, as long as the required attributes are available in a
7043 auxiliary object class.
</p
>
7048 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7049 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7051 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7052 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7053 DHCP services in Debian Edu to use the same LDAP objects for a given
7054 computer, to avoid the possibility of having a inconsistent state for
7055 a computer in LDAP (as in DHCP but no DNS entry or the other way
7056 around) and make it easier to add computers to LDAP.
</p
>
7058 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7059 information finally found a solution that seem to work.
</p
>
7061 <p
>The old setup required three LDAP objects for a given computer.
7062 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7063 we switch powerdns to use its strict LDAP method (ldap-method=strict
7064 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7065 merged into one while making it impossible to transfer the reverse map
7066 to a slave DNS server.
</p
>
7068 <p
>If we also replace the object class used to get the DNS related
7069 attributes to one allowing these attributes to be combined with the
7070 dhcphost object class, we can merge the DNS and DHCP entries into one.
7071 I
've written such object class in the dnsdomainaux.schema file (need
7072 proper OIDs, but that is a minor issue), and tested the setup. It
7073 seem to work.
</p
>
7075 <p
>With this test setup in place, we can get away with one LDAP object
7076 for both DNS and DHCP, and even the LTSP configuration I suggested in
7077 an earlier email. The combined LDAP object will look something like
7080 <blockquote
><pre
>
7081 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7083 objectClass: dhcphost
7084 objectclass: domainrelatedobject
7085 objectclass: dnsdomainaux
7086 associateddomain: hostname.intern
7087 arecord:
10.11.12.13
7088 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7089 dhcpstatements: fixed-address hostname
7091 </pre
></blockquote
>
7093 <p
>The DNS server uses the associateddomain and arecord entries, while
7094 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7095 before asking DNS to resolve the fixed-adddress. LTSP will use
7096 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7098 <p
>I am not yet sure if I can get the DHCP server to look for its
7099 dhcphost in a different location, to allow us to put the objects
7100 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7101 that. If I can
't figure out a way to do that, we can still get rid of
7102 the hosts subtree and move all its content into the DHCP Config tree
7103 (which probably should be renamed to be more related to the new
7104 content. I suspect cn=dnsdhcp,ou=services or something like that
7105 might be a good place to put it.
</p
>
7107 <p
>If you want to help out with implementing this for Debian Edu,
7108 please contact us on debian-edu@lists.debian.org.
</p
>
7113 <title>Idea for storing LTSP configuration in LDAP
</title>
7114 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7115 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7116 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7117 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7118 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7119 clients, and that this can be used to fetch configuration from LDAP if
7120 Debian Edu choose to store configuration there.
</p
>
7122 <p
>Armed with this information, I got inspired and wrote a test module
7123 to get configuration from LDAP. The idea is to look up the MAC
7124 address of the client in LDAP, and look for attributes on the form
7125 ltspconfigsetting=value, and use this to export SETTING=value to the
7126 LTSP clients.
</p
>
7128 <p
>The goal is to be able to store the LTSP configuration attributes
7129 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7130 allowing us to store all information about a computer in one place.
</p
>
7132 <p
>This is a untested draft implementation, and I welcome feedback on
7133 this approach. A real LDAP schema for the ltspClientAux objectclass
7134 need to be written. Comments, suggestions, etc?
</p
>
7136 <blockquote
><pre
>
7137 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7139 # Fetch LTSP client settings from LDAP based on MAC address
7141 # Uses ethernet address as stored in the dhcpHost objectclass using
7142 # the dhcpHWAddress attribute or ethernet address stored in the
7143 # ieee802Device objectclass with the macAddress attribute.
7145 # This module is written to be schema agnostic, and only depend on the
7146 # existence of attribute names.
7148 # The LTSP configuration variables are saved directly using a
7149 # ltspConfig prefix and uppercasing the rest of the attribute name.
7150 # To set the SERVER variable, set the ltspConfigServer attribute.
7152 # Some LDAP schema should be created with all the relevant
7153 # configuration settings. Something like this should work:
7155 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7158 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7160 LDAPSERVER=$(debian-edu-ldapserver)
7161 if [
"$LDAPSERVER
" ] ; then
7162 LDAPBASE=$(debian-edu-ldapserver -b)
7163 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7164 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7165 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7166 grep
'^ltspConfig
' | while read attr value ; do
7167 # Remove prefix and convert to upper case
7168 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7169 # bass value on to clients
7170 eval
"$attr=$value; export $attr
"
7174 </pre
></blockquote
>
7176 <p
>I
'm not sure this shell construction will work, because I suspect
7177 the while block might end up in a subshell causing the variables set
7178 there to not show up in ltsp-config, but if that is the case I am sure
7179 the code can be restructured to make sure the variables are passed on.
7180 I expect that can be solved with some testing. :)
</p
>
7182 <p
>If you want to help out with implementing this for Debian Edu,
7183 please contact us on debian-edu@lists.debian.org.
</p
>
7185 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7186 configuration in LDAP that was created around year
2000 by
7187 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7188 Xperience, Inc.,
2000</a
>. I found its
7189 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7190 personal home page over at redhat.com.
</p
>
7195 <title>jXplorer, a very nice LDAP GUI
</title>
7196 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7198 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7199 <description><p
>Since
7200 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7201 last post
</a
> about available LDAP tools in Debian, I was told about a
7202 LDAP GUI that is even better than luma. The java application
7203 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7204 moving LDAP objects and subtrees using drag-and-drop, and can
7205 authenticate using Kerberos. I have only tested the Kerberos
7206 authentication, but do not have a LDAP setup allowing me to rewrite
7207 LDAP with my test user yet. It is
7208 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7209 Debian
</a
> testing and unstable at the moment. The only problem I
7210 have with it is how it handle errors. If something go wrong, its
7211 non-intuitive behaviour require me to go through some query work list
7212 and remove the failing query. Nothing big, but very annoying.
</p
>
7217 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7218 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7220 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7221 <description><p
>Here is a short update on my
<a
7222 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7223 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7224 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7225 not reporting the status for KDE, because the upgrade crashes when
7226 aptitude try because of missing conflicts
7227 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7228 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7230 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7231 complete list of the installed packages. Based on this I see these
7232 differences when I did a test run today. As usual, I do not really
7233 know what the correct set of packages would be, but thought it best to
7234 publish the difference.
</p
>
7236 <p
>Installed using apt-get, missing with aptitude
</p
>
7238 <blockquote
><p
>
7239 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7240 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7241 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7242 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7243 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7244 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7245 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7246 python-gtkmozembed svgalibg1 xserver-xephyr zip
7247 </p
></blockquote
>
7249 <p
>Installed using apt-get, removed with aptitude
</p
>
7251 <blockquote
><p
>
7252 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7253 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7254 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7255 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7256 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7257 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7258 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7259 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7260 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7261 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
7262 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
7263 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
7264 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7265 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
7266 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7267 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
7268 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
7269 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7270 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7271 mysql-common swfdec-gnome totem-gstreamer wodim
7272 </p
></blockquote
>
7274 <p
>Installed using aptitude, missing with apt-get
</p
>
7276 <blockquote
><p
>
7277 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7278 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7279 xserver-xorg-input-all xserver-xorg-input-evdev
7280 xserver-xorg-input-kbd xserver-xorg-input-mouse
7281 xserver-xorg-input-synaptics xserver-xorg-video-all
7282 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7283 xserver-xorg-video-chips xserver-xorg-video-cirrus
7284 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7285 xserver-xorg-video-glint xserver-xorg-video-i128
7286 xserver-xorg-video-i740 xserver-xorg-video-mach64
7287 xserver-xorg-video-mga xserver-xorg-video-neomagic
7288 xserver-xorg-video-nouveau xserver-xorg-video-nv
7289 xserver-xorg-video-r128 xserver-xorg-video-radeon
7290 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7291 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7292 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7293 xserver-xorg-video-sis xserver-xorg-video-sisusb
7294 xserver-xorg-video-tdfx xserver-xorg-video-tga
7295 xserver-xorg-video-trident xserver-xorg-video-tseng
7296 xserver-xorg-video-vesa xserver-xorg-video-vmware
7297 xserver-xorg-video-voodoo
7298 </p
></blockquote
>
7300 <p
>Installed using aptitude, removed with apt-get
</p
>
7302 <blockquote
><p
>
7303 deskbar-applet xserver-xorg xserver-xorg-core
7304 xserver-xorg-input-wacom xserver-xorg-video-intel
7305 xserver-xorg-video-openchrome
7306 </p
></blockquote
>
7308 <p
>I was told on IRC that the xorg-xserver package was
7309 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
7310 in git
</a
> today to try to get apt-get to not remove xorg completely.
7311 No idea when it hits Squeeze, but when it does I hope it will reduce
7312 the difference somewhat.
7317 <title>LUMA, a very nice LDAP GUI
</title>
7318 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
7319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
7320 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
7321 <description><p
>The last few days I have been looking into the status of the LDAP
7322 directory in Debian Edu, and in the process I started to miss a GUI
7323 tool to browse the LDAP tree. The only one I was able to find in
7324 Debian/Squeeze and Lenny is
7325 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
7326 be a great tool to get a overview of the current LDAP directory
7327 populated by default in Skolelinux. Thanks to it, I have been able to
7328 find empty and obsolete subtrees, misplaced objects and duplicate
7329 objects. It will be installed by default in Debian/Squeeze. If you
7330 are working with LDAP, give it a go. :)
</p
>
7332 <p
>I did notice one problem with it I have not had time to report to
7333 the BTS yet. There is no .desktop file in the package, so the tool do
7334 not show up in the Gnome and KDE menus, but only deep down in in the
7335 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7338 <p
>I have not yet been able to get it to modify the tree yet. I would
7339 like to move objects and remove subtrees directly in the GUI, but have
7340 not found a way to do that with LUMA yet. So in the mean time, I use
7341 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
7343 <p
>If you have tips on other GUI tools for LDAP that might be useful
7344 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
7346 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
7347 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
7348 useful GUI alternative. It seem like a good tool, but is unmaintained
7349 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7350 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
7355 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
7356 <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>
7357 <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>
7358 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
7359 <description><p
>A while back, I
7360 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
7361 about the fact
</a
> that it is not possible with the provided schemas
7362 for storing DNS and DHCP information in LDAP to combine the two sets
7363 of information into one LDAP object representing a computer.
</p
>
7365 <p
>In the mean time, I discovered that a simple fix would be to make
7366 the dhcpHost object class auxiliary, to allow it to be combined with
7367 the dNSDomain object class, and thus forming one object for one
7368 computer when storing both DHCP and DNS information in LDAP.
</p
>
7370 <p
>If I understand this correctly, it is not safe to do this change
7371 without also changing the assigned number for the object class, and I
7372 do not know enough about LDAP schema design to do that properly for
7373 Debian Edu.
</p
>
7375 <p
>Anyway, for future reference, this is how I believe we could change
7377 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
7378 schema
</a
> to solve at least part of the problem with the LDAP schemas
7379 available today from IETF.
</p
>
7382 --- dhcp.schema (revision
65192)
7383 +++ dhcp.schema (working copy)
7385 objectclass (
2.16.840.1.113719.1.203.6.6
7386 NAME
'dhcpHost
'
7387 DESC
'This represents information about a particular client
'
7391 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7392 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7395 <p
>I very much welcome clues on how to do this properly for Debian
7396 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7397 package, and should thus be free to rewrite it as we see fit.
</p
>
7399 <p
>If you want to help out with implementing this for Debian Edu,
7400 please contact us on debian-edu@lists.debian.org.
</p
>
7405 <title>Calling tasksel like the installer, while still getting useful output
</title>
7406 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7408 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7409 <description><p
>A few times I have had the need to simulate the way tasksel
7410 installs packages during the normal debian-installer run. Until now,
7411 I have ended up letting tasksel do the work, with the annoying problem
7412 of not getting any feedback at all when something fails (like a
7413 conffile question from dpkg or a download that fails), using code like
7416 <blockquote
><pre
>
7417 export DEBIAN_FRONTEND=noninteractive
7418 tasksel --new-install
7419 </pre
></blockquote
>
7421 This would invoke tasksel, let its automatic task selection pick the
7422 tasks to install, and continue to install the requested tasks without
7423 any output what so ever.
7425 Recently I revisited this problem while working on the automatic
7426 package upgrade testing, because tasksel would some times hang without
7427 any useful feedback, and I want to see what is going on when it
7428 happen. Then it occured to me, I can parse the output from tasksel
7429 when asked to run in test mode, and use that aptitude command line
7430 printed by tasksel then to simulate the tasksel run. I ended up using
7433 <blockquote
><pre
>
7434 export DEBIAN_FRONTEND=noninteractive
7435 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7437 </pre
></blockquote
>
7439 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7440 --without-recommends -o APT::Install-Recommends=no -y install
7441 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7442 ~pimportant
</tt
>", which will install the gnome desktop task, the
7443 laptop task and all packages with priority standard , required and
7444 important, just like tasksel would have done it during
7445 installation.
</p
>
7447 <p
>A better approach is probably to extend tasksel to be able to
7448 install packages without using debconf-apt-progress, for use cases
7449 like this.
</p
>
7454 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
7455 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
7456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
7457 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
7458 <description><p
>My
7459 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
7460 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
7461 finally made the upgrade logs available from
7462 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
7463 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7464 apt and aptitude, and found their differences interesting. This time
7465 I will only focus on their removal plans.
</p
>
7467 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
7468 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
7469 surprising part is that it want to remove xorg and all
7470 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7471 sure why. When asking aptitude to do the same, it want to remove
129
7472 packages, but most of them are library packages I suspect are no
7473 longer needed. Both of them want to remove bluetooth packages, which
7474 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
7476 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
7477 which seem like a bad idea and xorg the same way as with Gnome. Asking
7478 aptitude for the same, it wants to remove
192 packages, none which are
7479 too surprising.
</p
>
7481 <p
>I guess the removal of xorg during upgrades should be investigated
7482 and avoided, and perhaps others as well. Here are the complete list
7483 of planned removals. The complete logs is available from the URL
7484 above. Note if you want to repeat these tests, that the upgrade test
7485 for kde+apt-get hung in the tasksel setup because of dpkg asking
7486 conffile questions. No idea why. I worked around it by using
7487 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
7490 <p
><b
>apt-get gnome
72</b
>
7491 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
7492 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7493 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
7494 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7495 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7496 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7497 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7498 xserver-xorg-input-kbd xserver-xorg-input-mouse
7499 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7500 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7501 xserver-xorg-video-ati xserver-xorg-video-chips
7502 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7503 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7504 xserver-xorg-video-glint xserver-xorg-video-i128
7505 xserver-xorg-video-i740 xserver-xorg-video-imstt
7506 xserver-xorg-video-intel xserver-xorg-video-mach64
7507 xserver-xorg-video-mga xserver-xorg-video-neomagic
7508 xserver-xorg-video-nsc xserver-xorg-video-nv
7509 xserver-xorg-video-openchrome xserver-xorg-video-r128
7510 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7511 xserver-xorg-video-rendition xserver-xorg-video-s3
7512 xserver-xorg-video-s3virge xserver-xorg-video-savage
7513 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7514 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7515 xserver-xorg-video-tga xserver-xorg-video-trident
7516 xserver-xorg-video-tseng xserver-xorg-video-v4l
7517 xserver-xorg-video-vesa xserver-xorg-video-vga
7518 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
7519 xulrunner-
1.9-gnome-support
</p
>
7521 <p
><b
>aptitude gnome
129</b
>
7523 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
7524 djvulibre-desktop finger gnome-app-install gnome-mount
7525 gnome-network-admin gnome-spell gnome-vfs-obexftp
7526 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7527 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7528 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7529 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
7530 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
7531 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
7532 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
7533 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
7534 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
7535 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
7536 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
7537 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
7538 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7539 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
7540 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
7541 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
7542 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
7543 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
7544 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7545 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7546 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7547 openoffice.org-writer2latex openssl-blacklist p7zip
7548 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
7549 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7550 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7551 swfdec-mozilla totem-gstreamer update-manager wodim
7552 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7553 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7556 <p
><b
>apt-get kde
82</b
>
7558 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7559 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7560 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7561 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7562 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7563 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7564 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7565 xserver-xorg-input-kbd xserver-xorg-input-mouse
7566 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7567 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7568 xserver-xorg-video-ati xserver-xorg-video-chips
7569 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7570 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7571 xserver-xorg-video-glint xserver-xorg-video-i128
7572 xserver-xorg-video-i740 xserver-xorg-video-imstt
7573 xserver-xorg-video-intel xserver-xorg-video-mach64
7574 xserver-xorg-video-mga xserver-xorg-video-neomagic
7575 xserver-xorg-video-nsc xserver-xorg-video-nv
7576 xserver-xorg-video-openchrome xserver-xorg-video-r128
7577 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7578 xserver-xorg-video-rendition xserver-xorg-video-s3
7579 xserver-xorg-video-s3virge xserver-xorg-video-savage
7580 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7581 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7582 xserver-xorg-video-tga xserver-xorg-video-trident
7583 xserver-xorg-video-tseng xserver-xorg-video-v4l
7584 xserver-xorg-video-vesa xserver-xorg-video-vga
7585 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
7587 <p
><b
>aptitude kde
192</b
>
7588 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
7589 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7590 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7591 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7592 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7593 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7594 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7595 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7596 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7597 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7598 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7599 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7600 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7601 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7602 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7603 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7604 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7605 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7606 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
7607 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7608 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7609 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
7610 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7611 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7612 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7613 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7614 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7615 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
7616 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
7617 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7618 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7619 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7620 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7621 texlive-common texlive-doc-base texlive-fonts-recommended
7622 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7623 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7624 xulrunner-
1.9</p
>
7630 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
7631 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
7632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
7633 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
7634 <description><p
>The last few days I have done some upgrade testing in Debian, to
7635 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7636 have been discovered and reported in the process
7637 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
7638 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
7639 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
7640 kdebase-workspace-data), and to get a more regular testing going on, I
7641 am working on a script to automate the test.
</p
>
7643 <p
>The idea is to create a Lenny chroot and use tasksel to install a
7644 Gnome or KDE desktop installation inside the chroot before upgrading
7645 it. To ensure no services are started in the chroot, a policy-rc.d
7646 script is inserted. To make sure tasksel believe it is to install a
7647 desktop on a laptop, the tasksel tests are replaced in the chroot
7648 (only acceptable because this is a throw-away chroot).
</p
>
7650 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7651 currently always fail because udev refuses to upgrade with the kernel
7652 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7653 is created. The bug report
7654 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
7655 this problem do not trigger in a chroot, but I touch the file anyway
7656 to make sure the upgrade go well. Testing on virtual and real
7657 hardware have failed me because of udev so far, and creating this file
7658 do the trick in such settings anyway. This is a
7659 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
7660 issue
</a
> and the current udev behaviour is intended by the udev
7661 maintainer because he lack the resources to rewrite udev to keep
7662 working with old kernels or something like that. I really wish the
7663 udev upstream would keep udev backwards compatible, to avoid such
7664 upgrade problem, but given that they fail to do so, I guess
7665 documenting the way out of this mess is the best option we got for
7666 Debian Squeeze.
</p
>
7668 <p
>Anyway, back to the task at hand, testing upgrades. This test
7669 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
7672 <blockquote
><pre
>
7676 if [
"$
1" ] ; then
7685 exec
&lt; /dev/null
7687 mirror=http://ftp.skolelinux.org/debian
7688 tmpdir=chroot-$from-upgrade-$to-$desktop
7690 debootstrap $from $tmpdir $mirror
7691 chroot $tmpdir aptitude update
7692 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
7696 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7700 mount -t proc proc $tmpdir/proc
7701 # Make sure proc is unmounted also on failure
7702 trap exit_cleanup EXIT INT
7704 chroot $tmpdir aptitude -y install debconf-utils
7706 # Make sure tasksel autoselection trigger. It need the test scripts
7707 # to return the correct answers.
7708 echo tasksel tasksel/desktop multiselect $desktop | \
7709 chroot $tmpdir debconf-set-selections
7711 # Include the desktop and laptop task
7712 for test in desktop laptop ; do
7713 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
7717 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7720 DEBIAN_FRONTEND=noninteractive
7721 DEBIAN_PRIORITY=critical
7722 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7723 chroot $tmpdir tasksel --new-install
7725 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
7726 chroot $tmpdir aptitude update
7727 touch $tmpdir/etc/udev/kernel-upgrade
7728 chroot $tmpdir aptitude -y dist-upgrade
7730 </pre
></blockquote
>
7732 <p
>I suspect it would be useful to test upgrades with both apt-get and
7733 with aptitude, but I have not had time to look at how they behave
7734 differently so far. I hope to get a cron job running to do the test
7735 regularly and post the result on the web. The Gnome upgrade currently
7736 work, while the KDE upgrade fail because of the bug in
7737 kdebase-workspace-data
</p
>
7739 <p
>I am not quite sure what kind of extract from the huge upgrade logs
7740 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
7741 post, so I will refrain from trying. I can report that for Gnome,
7742 aptitude report
760 packages upgraded,
448 newly installed,
129 to
7743 remove and
1 not upgraded and
1024MB need to be downloaded while for
7744 KDE the same numbers are
702 packages upgraded,
507 newly installed,
7745 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
7747 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
7748 is able to migrate to dependency based boot sequencing and parallel
7749 booting without a hitch. Was unsure if there were still bugs with
7750 packages failing to clean up their obsolete init.d script during
7751 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7757 <title>Upstart or sysvinit - as init.d scripts see it
</title>
7758 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
7759 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
7760 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
7761 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
7762 scripts to migrate (some of) their operations to upstart job while
7763 keeping the init.d for hurd and kfreebsd. The packages with such
7764 needs will need a way to get their init.d scripts to behave
7765 differently when used with sysvinit and with upstart. Because of
7766 this, I had a look at the environment variables set when a init.d
7767 script is running under upstart, and when it is not.
</p
>
7769 <p
>With upstart, I notice these environment variables are set when a
7770 script is started from rcS.d/ (ignoring some irrelevant ones like
7773 <blockquote
><pre
>
7779 UPSTART_EVENTS=startup
7781 UPSTART_JOB=rc-sysinit
7782 </pre
></blockquote
>
7784 <p
>With sysvinit, these environment variables are set for the same
7787 <blockquote
><pre
>
7788 INIT_VERSION=sysvinit-
2.88
7793 </pre
></blockquote
>
7795 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
7796 sysvinit are not set by upstart. Not sure if it is intentional or not
7797 to not be compatible with sysvinit in this regard.
</p
>
7799 <p
>For scripts needing to behave differently when upstart is used,
7800 looking for the UPSTART_JOB environment variable seem to be a good
7806 <title>A manual for standards wars...
</title>
7807 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
7808 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
7809 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
7810 <description><p
>Via the
7811 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
7812 of Rob Weir
</a
> I came across the very interesting essay named
7813 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
7814 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
7815 following the standards wars of today.
</p
>
7820 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
7821 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
7822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
7823 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
7824 <description><p
>When using sitesummary at a site to track machines, it is possible
7825 to get a list of the machine types in use thanks to the DMI
7826 information extracted from each machine. The script to do so is
7827 included in the sitesummary package, and here is example output from
7828 the Skolelinux build servers:
</p
>
7830 <blockquote
><pre
>
7831 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7833 Dell Computer Corporation
1
7836 eserver xSeries
345 -[
8670M1X]-
1
7840 </pre
></blockquote
>
7842 <p
>The quality of the report depend on the quality of the DMI tables
7843 provided in each machine. Here there are Intel machines without model
7844 information listed with Intel as vendor and no model, and virtual Xen
7845 machines listed as [no-dmi-info]. One can add -l as a command line
7846 option to list the individual machines.
</p
>
7848 <p
>A larger list is
7849 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
7850 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
7851 provide the basic sitesummary report publicly. In their report there
7852 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
7853 their machines, and as sitesummary is available in both distributions,
7854 it is trivial to get all of them to report to the same central
7855 collector.
</p
>
7860 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
7861 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
7862 <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>
7863 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
7864 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
7865 start at boot when an NVidia video card is used is handled. The
7866 problem seem to be that the nvidia X.org driver uses a long time to
7867 initialize, and this duration is longer than kdm is configured to
7870 <p
>I came across two bugs related to this issue,
7871 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
7872 against initscripts and passed on to nvidia-glx when it became obvious
7873 that the nvidia drivers were involved, and
7874 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
7875 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
7877 <p
>To me, it seem that no-one is interested in actually solving the
7878 problem nvidia video card owners experience and make sure the Debian
7879 distribution work out of the box for these users. The nvidia driver
7880 maintainers expect kdm to be set up to wait longer, while kdm expect
7881 the nvidia driver maintainers to fix the driver to start faster, and
7882 while they wait for each other I guess the users end up switching to a
7883 distribution that work for them. I have no idea what the solution is,
7884 but I am pretty sure that waiting for each other is not it.
</p
>
7886 <p
>I wonder why we end up handling bugs this way.
</p
>
7891 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
7892 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
7893 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
7894 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
7895 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
7896 The feature seem to hold up pretty well, but three fairly serious
7897 issues are known and should be solved:
7901 <li
>The wicd package seen to
7902 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
7903 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
7904 parallel booting is enabled. No idea why, but the wicd maintainer
7905 seem to be on the case.
</li
>
7907 <li
>The nvidia X driver seem to
7908 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
7909 triggered more easily when parallel booting is in effect. The
7910 maintainer is on the case.
</li
>
7912 <li
>The sysv-rc package fail to properly enable dependency based boot
7913 sequencing (the shutdown is broken) when old file-rc users
7914 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
7915 sysv-rc. One way to solve it would be for file-rc to create
7916 /etc/init.d/.legacy-bootordering, and another is to try to make
7917 sysv-rc more robust. Will investigate some more and probably upload a
7918 workaround in sysv-rc to help those trying to move from file-rc to
7919 sysv-rc get a working shutdown.
</li
>
7921 </ul
></p
>
7923 <p
>All in all not many surprising issues, and all of them seem
7924 solvable before Squeeze is released. In addition to these there are
7925 some packages with bugs in their dependencies and run level settings,
7926 which I expect will be fixed in a reasonable time span.
</p
>
7928 <p
>If you report any problems with dependencies in init.d scripts to
7929 the BTS, please usertag the report to get it to show up at
7930 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7931 list of usertagged bugs related to this
</a
>.
</p
>
7933 <p
>Update: Correct bug number to file-rc issue.
</p
>
7938 <title>More flexible firmware handling in debian-installer
</title>
7939 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
7940 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
7941 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
7942 <description><p
>After a long break from debian-installer development, I finally
7943 found time today to return to the project. Having to spend less time
7944 working dependency based boot in debian, as it is almost complete now,
7945 definitely helped freeing some time.
</p
>
7947 <p
>A while back, I ran into a problem while working on Debian Edu. We
7948 include some firmware packages on the Debian Edu CDs, those needed to
7949 get disk and network controllers working. Without having these
7950 firmware packages available during installation, it is impossible to
7951 install Debian Edu on the given machine, and because our target group
7952 are non-technical people, asking them to provide firmware packages on
7953 an external medium is a support pain. Initially, I expected it to be
7954 enough to include the firmware packages on the CD to get
7955 debian-installer to find and use them. This proved to be wrong.
7956 Next, I hoped it was enough to symlink the relevant firmware packages
7957 to some useful location on the CD (tried /cdrom/ and
7958 /cdrom/firmware/). This also proved to not work, and at this point I
7959 found time to look at the debian-installer code to figure out what was
7960 going to work.
</p
>
7962 <p
>The firmware loading code is in the hw-detect package, and a closer
7963 look revealed that it would only look for firmware packages outside
7964 the installation media, so the CD was never checked for firmware
7965 packages. It would only check USB sticks, floppies and other
7966 "external
" media devices. Today I changed it to also look in the
7967 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7968 solve the problem I ran into with Debian edu. I also changed it to
7969 look in /firmware/, to make sure the installer also find firmware
7970 provided in the initrd when booting the installer via PXE, to allow us
7971 to provide the same feature in the PXE setup included in Debian
7974 <p
>To make sure firmware deb packages with a license questions are not
7975 activated without asking if the license is accepted, I extended
7976 hw-detect to look for preinst scripts in the firmware packages, and
7977 run these before activating the firmware during installation. The
7978 license question is asked using debconf in the preinst, so this should
7979 solve the issue for the firmware packages I have looked at so far.
</p
>
7981 <p
>If you want to discuss the details of these features, please
7982 contact us on debian-boot@lists.debian.org.
</p
>
7987 <title>Parallellized boot is now the default in Debian/unstable
</title>
7988 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
7989 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
7990 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
7991 <description><p
>Since this evening, parallel booting is the default in
7992 Debian/unstable for machines using dependency based boot sequencing.
7993 Apparently the testing of concurrent booting has been wider than
7994 expected, if I am to believe the
7995 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7996 on debian-devel@
</a
>, and I concluded a few days ago to move forward
7997 with the feature this weekend, to give us some time to detect any
7998 remaining problems before Squeeze is frozen. If serious problems are
7999 detected, it is simple to change the default back to sequential boot.
8000 The upload of the new sysvinit package also activate a new upstream
8003 More information about
8004 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8005 based boot sequencing
</a
> is available from the Debian wiki. It is
8006 currently possible to disable parallel booting when one run into
8007 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8009 <blockquote
><pre
>
8011 </pre
></blockquote
>
8013 <p
>If you report any problems with dependencies in init.d scripts to
8014 the BTS, please usertag the report to get it to show up at
8015 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8016 list of usertagged bugs related to this
</a
>.
</p
>
8021 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8022 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8023 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8024 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8025 <description><p
>In the recent Debian Edu versions, the
8026 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8027 system
</a
> is used to keep track of the machines in the school
8028 network. Each machine will automatically report its status to the
8029 central server after boot and once per night. The network setup is
8030 also reported, and using this information it is possible to get the
8031 MAC address of all network interfaces in the machines. This is useful
8032 to update the DHCP configuration.
</p
>
8034 <p
>To give some idea how to use sitesummary, here is a one-liner to
8035 ist all MAC addresses of all machines reporting to sitesummary. Run
8036 this on the collector host:
</p
>
8038 <blockquote
><pre
>
8039 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8040 </pre
></blockquote
>
8042 <p
>This will list all MAC addresses assosiated with all machine, one
8043 line per machine and with space between the MAC addresses.
</p
>
8045 <p
>To allow system administrators easier job at adding static DHCP
8046 addresses for hosts, it would be possible to extend this to fetch
8047 machine information from sitesummary and update the DHCP and DNS
8048 tables in LDAP using this information. Such tool is unfortunately not
8049 written yet.
</p
>
8054 <title>systemd, an interesting alternative to upstart
</title>
8055 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8056 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8057 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8058 <description><p
>The last few days a new boot system called
8059 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8061 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8063 to the free software world. I have not yet had time to play around
8064 with it, but it seem to be a very interesting alternative to
8065 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8066 a good alternative for Debian when we are able to switch to an event
8067 based boot system. Tollef is
8068 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8069 systemd into Debian, and I look forward to seeing how well it work. I
8070 like the fact that systemd handles init.d scripts with dependency
8071 information natively, allowing them to run in parallel where upstart
8072 at the moment do not.
</p
>
8074 <p
>Unfortunately do systemd have the same problem as upstart regarding
8075 platform support. It only work on recent Linux kernels, and also need
8076 some new kernel features enabled to function properly. This means
8077 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8078 system. Not sure how that will be handled if systemd proves to be the
8079 way forward.
</p
>
8081 <p
>In the mean time, based on the
8082 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8083 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8084 decided to enable full parallel booting as the default in Debian as
8085 soon as possible (probably this weekend or early next week), to see if
8086 there are any remaining serious bugs in the init.d dependencies. A
8087 new version of the sysvinit package implementing this change is
8088 already in experimental. If all go well, Squeeze will be released
8089 with parallel booting enabled by default.
</p
>
8094 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8095 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8097 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8098 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8099 complete, so complete that it is actually possible to run all the
8100 init.d scripts in parallell based on these dependencies. If you want
8101 to test your Squeeze system, make sure
8102 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8103 based boot sequencing
</a
> is enabled, and add this line to
8104 /etc/default/rcS:
</p
>
8106 <blockquote
><pre
>
8107 CONCURRENCY=makefile
8108 </pre
></blockquote
>
8110 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8111 scripts in parallel using the dependency information stored in
8112 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8113 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8114 to try to start the kdm and gdm scripts as early as possible, and will
8115 start the facilities required by kdm or gdm as early as possible to
8116 make this happen.
</p
>
8118 <p
>Give it a try, and see if you like the result. If some services
8119 fail to start properly, it is most likely because they have incomplete
8120 init.d script dependencies in their startup script (or some of their
8121 dependent scripts have incomplete dependencies). Report bugs and get
8122 the package maintainers to fix it. :)
</p
>
8124 <p
>Running scripts in parallel could be the default in Debian when we
8125 manage to get the init.d script dependencies complete and correct. I
8126 expect we will get there in Squeeze+
1, if we get manage to test and
8127 fix the remaining issues.
</p
>
8129 <p
>If you report any problems with dependencies in init.d scripts to
8130 the BTS, please usertag the report to get it to show up at
8131 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8132 list of usertagged bugs related to this
</a
>.
</p
>
8137 <title>Debian has switched to dependency based boot sequencing
</title>
8138 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8140 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8141 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8142 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8143 have been migrated to using dependency based boot sequencing. This
8144 conclude work me and others have been doing for the last three days.
8145 It feels great to see this finally part of the default Debian
8146 installation. Now we just need to weed out the last few problems that
8147 are bound to show up, to get everything ready for Squeeze.
</p
>
8149 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8150 fixing the more fundamental problem of handing the event based
8151 non-predictable kernel in the early boot.
</p
>
8156 <title>Taking over sysvinit development
</title>
8157 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8159 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8160 <description><p
>After several years of frustration with the lack of activity from
8161 the existing sysvinit upstream developer, I decided a few weeks ago to
8162 take over the package and become the new upstream. The number of
8163 patches to track for the Debian package was becoming a burden, and the
8164 lack of synchronization between the distribution made it hard to keep
8165 the package up to date.
</p
>
8167 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8168 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8169 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8170 and Fedora), based on the patches currently in use in these
8171 distributions. We Debian maintainers plan to move to this tarball as
8172 the new upstream as soon as we find time to do the merge. Since the
8173 new tarball was created, we agreed with Werner at SuSe to make a new
8174 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8175 development there. The project is registered and currently waiting
8176 for approval by the Savannah administrators, and as soon as it is
8177 approved, we will import the old versions from svn and continue
8178 working on the future release.
</p
>
8180 <p
>It is a bit ironic that this is done now, when some of the involved
8181 distributions are moving to upstart as a syvinit replacement.
</p
>
8186 <title>Debian boots quicker and quicker
</title>
8187 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8189 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8190 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8191 people involved in the boot system on Debian and Ubuntu, to see if we
8192 could find more ways to speed up the boot system. This was an Ubuntu
8194 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8195 gathering
</a
>. It was quite productive. We also discussed the future
8196 of boot systems, and ways to handle the increasing number of boot
8197 issues introduced by the Linux kernel becoming more and more
8198 asynchronous and event base. The Ubuntu approach using udev and
8199 upstart might be a good way forward. Time will show.
</p
>
8201 <p
>Anyway, there are a few ways at the moment to speed up the boot
8202 process in Debian. All of these should be applied to get a quick
8207 <li
>Use dash as /bin/sh.
</li
>
8209 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8210 clock is in UTC.
</li
>
8212 <li
>Install and activate the insserv package to enable
8213 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8214 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8218 These points are based on the Google summer of code work done by
8219 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8222 <p
>Support for makefile-style concurrency during boot was uploaded to
8223 unstable yesterday. When we tested it, we were able to cut
6 seconds
8224 from the boot sequence. It depend on very correct dependency
8225 declaration in all init.d scripts, so I expect us to find edge cases
8226 where the dependences in some scripts are slightly wrong when we start
8227 using this.
</p
>
8229 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8230 introduced by Raphael Geissert today, one that could affect the
8231 startup speed as well. Instead of starting some scripts concurrently
8232 from rcS.d/ and another set of scripts from rc2.d/, it would be
8233 possible to run a of them in the same process. A quick way to test
8234 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8235 insserv
'. Will need to test if that work. :)
</p
>
8240 <title>BSAs påstander om piratkopiering møter motstand
</title>
8241 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8242 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8243 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8244 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8245 programvareselskapene som Microsoft og Apple, publisert en rapport der
8246 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8247 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8249 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8250 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8251 dagene. Et spesielt interessant kommentar fra Sverige,
8252 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8253 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8256 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8257 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8258 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8259 exakta
", säger BSAs Sverigechef John Hugosson.
8262 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
8263 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
8264 piracy figures need a shot of reality
</a
> og
<a
8265 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
8266 Copyright Treaty Work?
</a
></p
>
8268 <p
>Fant lenkene via
<a
8269 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
8270 på Slashdot
</a
>.
</p
>
8275 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
8276 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
8277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
8278 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
8279 <description><p
>Kom over
8280 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
8281 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8282 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8283 jobber til daglig. En rask opptelling forteller meg at vi har
490
8284 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
8285 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
8286 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
8291 <title>Kryptert harddisk - naturligvis
</title>
8292 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
8293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
8294 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
8295 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
8296 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
8297 når en tar tap av arbeidstid, fortrolige dokumenter,
8298 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8299 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8300 til at jeg har kryptert harddisken på både kontormaskinen og min
8301 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8302 komme på avveie, den første informasjon relatert til jobben min ved
8303 Universitetet i Oslo, og den andre relatert til blant annet
8304 foreningsarbeide. Kryptering av diskene gjør at det er lite
8305 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8306 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8307 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8308 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8309 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8310 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8311 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8312 det er gjort slik jeg gjør det er minimale, og gevinstene er
8313 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8314 maskinen reinstalleres og alt er tapt.
</p
>
8316 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8317 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8318 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8319 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8320 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8321 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8322 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8323 betydelige.
</p
>
8328 <title>Two projects that have improved the quality of free software a lot
</title>
8329 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
8330 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
8331 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
8332 <description><p
>There are two software projects that have had huge influence on the
8333 quality of free software, and I wanted to mention both in case someone
8334 do not yet know them.
</p
>
8336 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
8337 tool to detect and expose errors in the memory handling of programs.
8338 It is easy to use, all one need to do is to run
'valgrind program
',
8339 and it will report any problems on stdout. It is even better if the
8340 program include debug information. With debug information, it is able
8341 to report the source file name and line number where the problem
8342 occurs. It can report things like
'reading past memory block in file
8343 X line N, the memory block was allocated in file Y, line M
', and
8344 'using uninitialised value in control logic
'. This tool has made it
8345 trivial to investigate reproducible crash bugs in programs, and have
8346 reduced the number of this kind of bugs in free software a lot.
8348 <p
>The second one is
8349 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
8350 a source code checker. It is able to process the source of a program
8351 and find problems in the logic without running the program. It
8352 started out as the Stanford Checker and became well known when it was
8353 used to find bugs in the Linux kernel. It is now a commercial tool
8354 and the company behind it is running
8355 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
8356 free software community, where a lot of free software projects get
8357 their source checked for free. Several thousand defects have been
8358 found and fixed so far. It can find errors like
'lock L taken in file
8359 X line N is never released if exiting in line M
', or
'the code in file
8360 Y lines O to P can never be executed
'. The projects included in the
8361 community service project have managed to get rid of a lot of
8362 reliability problems thanks to Coverity.
</p
>
8364 <p
>I believe tools like this, that are able to automatically find
8365 errors in the source, are vital to improve the quality of software and
8366 make sure we can get rid of the crashing and failing software we are
8367 surrounded by today.
</p
>
8372 <title>No patch is not better than a useless patch
</title>
8373 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
8374 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
8375 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
8376 <description><p
>Julien Blache
8377 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
8378 patch is better than a useless patch
</a
>. I completely disagree, as a
8379 patch allow one to discuss a concrete and proposed solution, and also
8380 prove that the issue at hand is important enough for someone to spent
8381 time on fixing it. No patch do not provide any of these positive
8382 properties.
</p
>
8387 <title>Standardize on protocols and formats, not vendors and applications
</title>
8388 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8390 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8391 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8392 very good one to form a long lived computer infrastructure. It is the
8393 simple one, lost by many in todays computer industry: Standardize on
8394 open network protocols and open exchange/storage formats, not applications.
8395 Applications come and go, while protocols and files tend to stay, and
8396 thus one want to make it easy to change application and vendor, while
8397 avoiding conversion costs and locking users to a specific platform or
8398 application.
</p
>
8400 <p
>This approach make it possible to replace the client applications
8401 independently of the server applications. One can even allow users to
8402 use several different applications as long as they handle the selected
8403 protocol and format. In the normal case, only one client application
8404 is recommended and users only get help if they choose to use this
8405 application, but those that want to deviate from the easy path are not
8406 blocked from doing so.
</p
>
8408 <p
>It also allow us to replace the server side without forcing the
8409 users to replace their applications, and thus allow us to select the
8410 best server implementation at any moment, when scale and resouce
8411 requirements change.
</p
>
8413 <p
>I strongly recommend standardizing - on open network protocols and
8414 open formats, but I would never recommend standardizing on a single
8415 application that do not use open network protocol or open formats.
</p
>
8420 <title>Returning from Skolelinux developer gathering
</title>
8421 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8422 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8423 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8424 <description><p
>I
'm sitting on the train going home from this weekends Debian
8425 Edu/Skolelinux development gathering. I got a bit done tuning the
8426 desktop, and looked into the dynamic service location protocol
8427 implementation avahi. It look like it could be useful for us. Almost
8428 30 people participated, and I believe it was a great environment to
8429 get to know the Skolelinux system. Walter Bender, involved in the
8430 development of the Sugar educational platform, presented his stuff and
8431 also helped me improve my OLPC installation. He also showed me that
8432 his Turtle Art application can be used in standalone mode, and we
8433 agreed that I would help getting it packaged for Debian. As a
8434 standalone application it would be great for Debian Edu. We also
8435 tried to get the video conferencing working with two OLPCs, but that
8436 proved to be too hard for us. The application seem to need more work
8437 before it is ready for me. I look forward to getting home and relax
8443 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8444 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8445 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8446 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8447 <description><p
>The state of standardized LDAP schemas on Linux is far from
8448 optimal. There is RFC
2307 documenting one way to store NIS maps in
8449 LDAP, and a modified version of this normally called RFC
2307bis, with
8450 some modifications to be compatible with Active Directory. The RFC
8451 specification handle the content of a lot of system databases, but do
8452 not handle DNS zones and DHCP configuration.
</p
>
8454 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
8455 we would like to store information about users, SMB clients/hosts,
8456 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8457 and LTSP configuration in LDAP. These objects have a lot in common,
8458 but with the current LDAP schemas it is not possible to have one
8459 object per entity. For example, one need to have at least three LDAP
8460 objects for a given computer, one with the SMB related stuff, one with
8461 DNS information and another with DHCP information. The schemas
8462 provided for DNS and DHCP are impossible to combine into one LDAP
8463 object. In addition, it is impossible to implement quick queries for
8464 netgroup membership, because of the way NIS triples are implemented.
8465 It just do not scale. I believe it is time for a few RFC
8466 specifications to cleam up this mess.
</p
>
8468 <p
>I would like to have one LDAP object representing each computer in
8469 the network, and this object can then keep the SMB (ie host key), DHCP
8470 (mac address/name) and DNS (name/IP address) settings in one place.
8471 It need to be efficently stored to make sure it scale well.
</p
>
8473 <p
>I would also like to have a quick way to map from a user or
8474 computer and to the net group this user or computer is a member.
</p
>
8476 <p
>Active Directory have done a better job than unix heads like myself
8477 in this regard, and the unix side need to catch up. Time to start a
8478 new IETF work group?
</p
>
8483 <title>Endelig er Debian Lenny gitt ut
</title>
8484 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
8485 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
8486 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
8487 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
8488 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
8489 Et langt steg videre for Debian-prosjektet, og en rekke nye
8490 programpakker blir nå tilgjengelig for de av oss som bruker den
8491 stabile utgaven av Debian. Neste steg er nå å få
8492 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
8493 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
8494 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8495 slippes løs på skolene. Takk til alle debian-utviklerne som har
8496 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8497 bootsekvens tilgjengelig i stabil utgave, vha pakken
8498 <tt
>insserv
</tt
>.
</p
>
8503 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
8504 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
8505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
8506 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
8507 <description><p
>This weekend we had a small developer gathering for Debian Edu in
8508 Oslo. Most of Saturday was used for the general assemly for the
8509 member organization, but the rest of the weekend I used to tune the
8510 LTSP installation. LTSP now work out of the box on the
10-network.
8511 Acer Aspire One proved to be a very nice thin client, with both
8512 screen, mouse and keybard in a small box. Was working on getting the
8513 diskless workstation setup configured out of the box, but did not
8514 finish it before the weekend was up.
</p
>
8516 <p
>Did not find time to look at the
4 VGA cards in one box we got from
8517 the Brazilian group, so that will have to wait for the next
8518 development gathering. Would love to have the Debian Edu installer
8519 automatically detect and configure a multiseat setup when it find one
8520 of these cards.
</p
>
8525 <title>The sorry state of multimedia browser plugins in Debian
</title>
8526 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
8527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
8528 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
8529 <description><p
>Recently I have spent some time evaluating the multimedia browser
8530 plugins available in Debian Lenny, to see which one we should use by
8531 default in Debian Edu. We need an embedded video playing plugin with
8532 control buttons to pause or stop the video, and capable of streaming
8533 all the multimedia content available on the web. The test results and
8534 notes are available on
8535 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
8536 Debian wiki
</a
>. I was surprised how few of the plugins are able to
8537 fill this need. My personal video player favorite, VLC, has a really
8538 bad plugin which fail on a lot of the test pages. A lot of the MIME
8539 types I would expect to work with any free software player (like
8540 video/ogg), just do not work. And simple formats like the
8541 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
8542 totem and vlc plugins. I hope the situation will improve soon. No
8543 wonder sites use the proprietary Adobe flash to play video.
</p
>
8545 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
8546 be the only one fitting our needs. :/
</p
>