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>Creepy, visualise geotagged social media information - nice free software
</title>
11 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
13 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
14 <description><p
>Most people seem not to realise that every time they walk around
15 with the computerised radio beacon known as a mobile phone their
16 position is tracked by the phone company and often stored for a long
17 time (like every time a SMS is received or sent). And if their
18 computerised radio beacon is capable of running programs (often called
19 mobile apps) downloaded from the Internet, these programs are often
20 also capable of tracking their location (if the app requested access
21 during installation). And when these programs send out information to
22 central collection points, the location is often included, unless
23 extra care is taken to not send the location. The provided
24 information is used by several entities, for good and bad (what is
25 good and bad, depend on your point of view). What is certain, is that
26 the private sphere and the right to free movement is challenged and
27 perhaps even eradicated for those announcing their location this way,
28 when they share their whereabouts with private and public
31 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
33 <p
>The phone company logs provide a register of locations to check out
34 when one want to figure out what the tracked person was doing. It is
35 unavailable for most of us, but provided to selected government
36 officials, company staff, those illegally buying information from
37 unfaithful servants and crackers stealing the information. But the
38 public information can be collected and analysed, and a free software
39 tool to do so is called
40 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
41 discovered it when I read
42 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
43 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
44 November
2014, and decided to check if it was available in Debian.
45 The python program was in Debian, but
46 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
47 Debian
</a
> was completely broken and practically unmaintained. I
48 uploaded a new version which did not work quite right, but did not
49 have time to fix it then. This Christmas I decided to finally try to
50 get Creepy operational in Debian. Now a fixed version is available in
51 Debian unstable and testing, and almost all Debian specific patches
53 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
55 <p
>The Creepy program visualises geolocation information fetched from
56 Twitter, Instagram, Flickr and Google+, and allow one to get a
57 complete picture of every social media message posted recently in a
58 given area, or track the movement of a given individual across all
59 these services. Earlier it was possible to use the search API of at
60 least some of these services without identifying oneself, but these
61 days it is impossible. This mean that to use Creepy, you need to
62 configure it to log in as yourself on these services, and provide
63 information to them about your search interests. This should be taken
64 into account when using Creepy, as it will also share information
65 about yourself with the services.
</p
>
67 <p
>The picture above show the twitter messages sent from (or at least
68 geotagged with a position from) the city centre of Oslo, the capital
69 of Norway. One useful way to use Creepy is to first look at
70 information tagged with an area of interest, and next look at all the
71 information provided by one or more individuals who was in the area.
72 I tested it by checking out which celebrity provide their location in
73 twitter messages by checkout out who sent twitter messages near a
74 Norwegian TV station, and next could track their position over time,
75 making it possible to locate their home and work place, among other
76 things. A similar technique have been
77 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
78 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
79 tool to discover lying governments, and a useful tool to help people
80 understand the value of the private information they provide to the
83 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
84 it depend on several python modules currently missing in Jessie (at
85 least python-instagram, python-flickrapi and
86 python-requests-toolbelt).
</p
>
88 <p
>(I have uploaded
89 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
90 screenshots.debian.net
</a
> and licensed it under the same terms as the
91 Creepy program in Debian.)
</p
>
96 <title>Always download Debian packages using Tor - the simple recipe
</title>
97 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
98 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
99 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
100 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
101 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
102 that those listening on the Internet lines would have good reason to
103 believe a computer have a given security hole
</a
> if it download a
104 security fix from a Debian mirror. This is a good reason to always
105 use encrypted connections to the Debian mirror, to make sure those
106 listening do not know which IP address to attack. In August, Richard
107 Hartmann observed that encryption was not enough, when it was possible
108 to interfere download size to security patches or the fact that
109 download took place shortly after a security fix was released, and
110 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
111 to always use Tor to download packages from the Debian mirror
</a
>. He
112 was not the first to propose this, as the
113 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
114 package by Tim Retout already existed to make it easy to convince apt
115 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
116 aware of that package when I read the blog post from Richard.
</p
>
118 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
119 sysadmins, and he set up a Tor hidden service on one of the central
120 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
121 it possible to download packages directly between two tor nodes,
122 making sure the network traffic always were encrypted.
</p
>
124 <p
>Here is a short recipe for enabling this on your machine, by
125 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
126 urls with tor+http and tor+https, and using the hidden service instead
127 of the official Debian mirror site. I recommend installing
128 <tt
>etckeeper
</tt
> before you start to have a history of the changes
129 done in /etc/.
</p
>
131 <blockquote
><pre
>
132 apt install apt-transport-tor
133 sed -i
's% http://ftp.debian.org/%tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
134 sed -i
's% http% tor+http%
' /etc/apt/sources.list
135 </pre
></blockquote
>
137 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
138 the sed commands for these too. The sed command is assuming your are
139 using the ftp.debian.org Debian mirror. Adjust the command (or just
140 edit the file manually) to match your mirror.
</p
>
142 <p
>This work in Debian Jessie and later. Note that tools like
143 <tt
>apt-file
</tt
> only recently started using the apt transport
144 system, and do not work with these tor+http URLs. For
145 <tt
>apt-file
</tt
> you need the version currently in experimental,
146 which need a recent apt version currently only in unstable. So if you
147 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
149 <p
>Another advantage from this change is that your machine will start
150 using Tor regularly and at fairly random intervals (every time you
151 update the package lists or upgrade or install a new package), thus
152 masking other Tor traffic done from the same machine. Using Tor will
153 become normal for the machine in question.
</p
>
155 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
156 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
157 enabled. It would be great if it was the default on any Debian
163 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
164 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
165 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
166 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
167 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
168 call the car license plate numbers in those days. I would write the
169 numbers down in my little book and compare notes with the other kids
170 to see how many region codes we had seen and if we had seen some
171 exotic or special region codes and numbers. It was a fun game to pass
172 time, as we kids have plenty of it.
</p
>
174 <p
>A few days I came across
175 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
176 project
</a
>, a free software project to automatically discover and
177 report license plates in images and video streams, and provide the
178 "car numbers
" in a machine readable format. I
've been looking for
179 such system for a while now, because I believe it is a bad idea that the
180 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
181 number plate recognition
</a
> tool only is available in the hands of
182 the powerful, and want it to be available also for the powerless to
183 even the score when it comes to surveillance and sousveillance. I
184 discovered the developer
185 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
186 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
187 help him get it into shape to get the package uploaded into the Debian
190 <p
>Today we finally managed to get the package into shape and uploaded
191 it into Debian, where it currently
192 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
193 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
195 <p
>I guess you are wondering why on earth such tool would be useful
196 for the common folks, ie those not running a large government
197 surveillance system? Well, I plan to put it in a computer on my bike
198 and in my car, tracking the cars nearby and allowing me to be notified
199 when number plates on my watch list are discovered. Another use case
200 was suggested by a friend of mine, who wanted to set it up at his home
201 to open the car port automatically when it discovered the plate on his
202 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
203 capable of placing his license plate number of a piece of cardboard to
204 open his car port, men replied that it was always unlocked anyway. I
205 guess for such use case it make sense. I am sure there are other use
206 cases too, for those with imagination and a vision.
</p
>
208 <p
>If you want to build your own version of the Debian package, check
209 out the upstream git source and symlink ./distros/debian to ./debian/
210 before running
"debuild
" to build the source. Or wait a bit until the
211 package show up in unstable.
</p
>
216 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
217 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
218 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
219 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
220 <description><p
>Around three years ago, I created
221 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
222 system
</a
> to get a more practical solution in Debian for handing
223 hardware related packages. A GUI system in the isenkram package will
224 present a pop-up dialog when some hardware dongle supported by
225 relevant packages in Debian is inserted into the machine. The same
226 lookup mechanism to detect packages is available as command line
227 tools in the isenkram-cli package. In addition to mapping hardware,
228 it will also map kernel firmware files to packages and make it easy to
229 install needed firmware packages automatically. The key for this
230 system to work is a good way to map hardware to packages, in other
231 words, allow packages to announce what hardware they will work
234 <p
>I started by providing data files in the isenkram source, and
235 adding code to download the latest version of these data files at run
236 time, to ensure every user had the most up to date mapping available.
237 I also added support for storing the mapping in the Packages file in
238 the apt repositories, but did not push this approach because while I
239 was trying to figure out how to best store hardware/package mappings,
240 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
241 appstream system
</a
> was announced. I got in touch and suggested to
242 add the hardware mapping into that data set to be able to use
243 appstream as a data source, and this was accepted at least for the
244 Debian version of appstream.
</p
>
246 <p
>A few days ago using appstream in Debian for this became possible,
247 and today I uploaded a new version
0.20 of isenkram adding support for
248 appstream as a data source for mapping hardware to packages. The only
249 package so far using appstream to announce its hardware support is my
250 pymissile package. I got help from Matthias Klumpp with figuring out
251 how do add the required
252 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
253 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
254 this content:
</p
>
256 <blockquote
><pre
>
257 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
258 &lt;component
&gt;
259 &lt;id
&gt;pymissile
&lt;/id
&gt;
260 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
261 &lt;name
&gt;pymissile
&lt;/name
&gt;
262 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
263 &lt;description
&gt;
265 Pymissile provides a curses interface to control an original
266 Marks and Spencer / Striker USB Missile Launcher, as well as a
267 motion control script to allow a webcamera to control the
270 &lt;/description
&gt;
271 &lt;provides
&gt;
272 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
273 &lt;/provides
&gt;
274 &lt;/component
&gt;
275 </pre
></blockquote
>
277 <p
>The key for isenkram is the component/provides/modalias value,
278 which is a glob style match rule for hardware specific strings
279 (modalias strings) provided by the Linux kernel. In this case, it
280 will map to all USB devices with vendor code
1130 and product code
283 <p
>Note, it is important that the license of all the metadata files
284 are compatible to have permissions to aggregate them into archive wide
285 appstream files. Matthias suggested to use MIT or BSD licenses for
286 these files. A challenge is figuring out a good id for the data, as
287 it is supposed to be globally unique and shared across distributions
288 (in other words, best to coordinate with upstream what to use). But
289 it can be changed later or, so we went with the package name as
290 upstream for this project is dormant.
</p
>
292 <p
>To get the metadata file installed in the correct location for the
293 mirror update scripts to pick it up and include its content the
294 appstream data source, the file must be installed in the binary
295 package under /usr/share/appdata/. I did this by adding the following
296 line to debian/pymissile.install:
</p
>
298 <blockquote
><pre
>
299 debian/pymissile.metainfo.xml usr/share/appdata
300 </pre
></blockquote
>
302 <p
>With that in place, the command line tool isenkram-lookup will list
303 all packages useful on the current computer automatically, and the GUI
304 pop-up handler will propose to install the package not already
305 installed if a hardware dongle is inserted into the machine in
308 <p
>Details of the modalias field in appstream is available from the
309 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
311 <p
>To locate the modalias values of all hardware present in a machine,
312 try running this command on the command line:
</p
>
314 <blockquote
><pre
>
315 cat $(find /sys/devices/|grep modalias)
316 </pre
></blockquote
>
318 <p
>To learn more about the isenkram system, please check out
319 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
320 blog posts tagged isenkram
</a
>.
</p
>
325 <title>The GNU General Public License is not magic pixie dust
</title>
326 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
328 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
329 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
330 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
331 GPL is not magic pixie dust
</a
>" explain the importance of making sure
332 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
333 I quote the blog post from Paul in full here with his permission:
<p
>
337 <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
>
340 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
342 The first step is to choose a
343 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
346 The next step is, when someone fails to follow that copyleft license,
347 <b
>it must be enforced
</b
><br/
>
349 and its a simple fact of our modern society that such type of
352 is incredibly expensive to do and incredibly difficult to do.
355 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
356 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
357 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
358 0x57</a
></small
></p
>
360 <p
>As the Debian Website
361 <a href=
"https://bugs.debian.org/
794116">used
</a
>
362 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
363 imply, public domain and permissively licensed software can lead to
364 the production of more proprietary software as people discover useful
365 software, extend it and or incorporate it into their hardware or
366 software products. Copyleft licenses such as the GNU GPL were created
367 to close off this avenue to the production of proprietary software but
368 such licenses are not enough. With the ongoing adoption of Free
369 Software by individuals and groups, inevitably the community
's
370 expectations of license compliance are violated, usually out of
371 ignorance of the way Free Software works, but not always. As Karen
372 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
373 Freedom
">FaiF
</a
>
374 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
375 copyleft is nothing if no-one is willing and able to stand up in court
376 to protect it. The reality of today
's world is that legal
377 representation is expensive, difficult and time consuming. With
378 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
379 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
380 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
381 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
382 of the Linux project, Debian and other groups against GPL violations.
383 In March the SFC supported a
384 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
385 by Christoph Hellwig
</a
> against VMware for refusing to
386 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
387 with the GPL
</a
> in relation to their use of parts of the Linux
388 kernel. Since then two of their sponsors pulled corporate funding and
390 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
391 or cancelled their talks
</a
>. As a result they have decided to rely
392 less on corporate funding and more on the broad community of
393 individuals who support Free Software and copyleft. So the SFC has
394 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
395 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
396 a community of folks who stand up for copyleft and the GPL by
397 supporting their work on promoting and supporting copyleft and Free
400 <p
>If you support Free Software,
401 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
402 what the SFC do, agree with their
403 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
404 principles
</a
>, are happy about their
405 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
406 work on a project that is an SFC
407 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
408 just want to stand up for copyleft, please join
409 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
410 Allan Webber
</a
>,
411 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
413 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
414 Bacon
</a
>, myself and
415 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
417 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
418 next week your donation will be
419 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
420 by an anonymous donor. Please also consider asking your employer to
421 match your donation or become a sponsor of SFC. Don
't forget to
422 spread the word about your support for SFC via email, your blog and or
423 social media accounts.
</p
>
427 <p
>I agree with Paul on this topic and just signed up as a Supporter
428 of Software Freedom Conservancy myself. Perhaps you should be a
429 supporter too?
</p
>
434 <title>PGP key transition statement for key EE4E02F9
</title>
435 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
436 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
437 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
438 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
439 set it up properly. I wanted to generate it offline and have it
440 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
441 smart card
</a
> for daily use, and learning how to do it and finding
442 time to sit down with an offline machine almost took forever. But
443 finally I
've been able to complete the process, and have now moved
444 from my old GPG key to a new GPG key. See
445 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
446 full transition statement, signed with both my old and new key
</a
> for
447 the details. This is my new key:
</p
>
450 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
451 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
452 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
453 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
454 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
455 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
456 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
459 <p
>The key can be downloaded from the OpenPGP key servers, signed by
460 my old key.
</p
>
462 <p
>If you signed my old key
463 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
464 I
'd very much appreciate a signature on my new key, details and
465 instructions in the transition statement. I m happy to reciprocate if
466 you have a similarly signed transition statement to present.
</p
>
471 <title>The life and death of a laptop battery
</title>
472 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
474 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
475 <description><p
>When I get a new laptop, the battery life time at the start is OK.
476 But this do not last. The last few laptops gave me a feeling that
477 within a year, the life time is just a fraction of what it used to be,
478 and it slowly become painful to use the laptop without power connected
479 all the time. Because of this, when I got a new Thinkpad X230 laptop
480 about two years ago, I decided to monitor its battery state to have
481 more hard facts when the battery started to fail.
</p
>
483 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
485 <p
>First I tried to find a sensible Debian package to record the
486 battery status, assuming that this must be a problem already handled
487 by someone else. I found
488 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
489 which collects statistics from the battery, but it was completely
490 broken. I sent a few suggestions to the maintainer, but decided to
491 write my own collector as a shell script while I waited for feedback
493 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
494 blog post about the battery development on a MacBook Air
</a
> I also
496 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
497 available in Debian.
</p
>
499 <p
>I started my collector
2013-
07-
15, and it has been collecting
500 battery stats ever since. Now my
501 /var/log/hjemmenett-battery-status.log file contain around
115,
000
502 measurements, from the time the battery was working great until now,
503 when it is unable to charge above
7% of original capacity. My
504 collector shell script is quite simple and look like this:
</p
>
509 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
511 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
512 logfile=/var/log/hjemmenett-battery-status.log
514 files=
"manufacturer model_name technology serial_number \
515 energy_full energy_full_design energy_now cycle_count status
"
517 if [ ! -e
"$logfile
" ] ; then
519 printf
"timestamp,
"
521 printf
"%s,
" $f
524 )
> "$logfile
"
528 # Print complete message in one echo call, to avoid race condition
529 # when several log processes run in parallel.
530 msg=$(printf
"%s,
" $(date +%s); \
531 for f in $files; do \
532 printf
"%s,
" $(cat $f); \
534 echo
"$msg
"
537 cd /sys/class/power_supply
540 (cd $bat
&& log_battery
>> "$logfile
")
544 <p
>The script is called when the power management system detect a
545 change in the power status (power plug in or out), and when going into
546 and out of hibernation and suspend. In addition, it collect a value
547 every
10 minutes. This make it possible for me know when the battery
548 is discharging, charging and how the maximum charge change over time.
549 The code for the Debian package
550 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
551 available on github
</a
>.
</p
>
553 <p
>The collected log file look like this:
</p
>
556 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
557 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
559 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
560 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
563 <p
>I wrote a small script to create a graph of the charge development
564 over time. This graph depicted above show the slow death of my laptop
567 <p
>But why is this happening? Why are my laptop batteries always
568 dying in a year or two, while the batteries of space probes and
569 satellites keep working year after year. If we are to believe
570 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
571 University
</a
>, the cause is me charging the battery whenever I have a
572 chance, and the fix is to not charge the Lithium-ion batteries to
100%
573 all the time, but to stay below
90% of full charge most of the time.
574 I
've been told that the Tesla electric cars
575 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
576 the charge of their batteries to
80%
</a
>, with the option to charge to
577 100% when preparing for a longer trip (not that I would want a car
578 like Tesla where rights to privacy is abandoned, but that is another
579 story), which I guess is the option we should have for laptops on
582 <p
>Is there a good and generic way with Linux to tell the battery to
583 stop charging at
80%, unless requested to charge to
100% once in
584 preparation for a longer trip? I found
585 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
586 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
587 80%
</a
>, but could not get it to work (kernel module refused to
590 <p
>I wonder why the battery capacity was reported to be more than
100%
591 at the start. I also wonder why the
"full capacity
" increases some
592 times, and if it is possible to repeat the process to get the battery
593 back to design capacity. And I wonder if the discharge and charge
594 speed change over time, or if this stay the same. I did not yet try
595 to write a tool to calculate the derivative values of the battery
596 level, but suspect some interesting insights might be learned from
599 <p
>Update
2015-
09-
24: I got a tip to install the packages
600 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
601 packages instead of the tp-smapi-dkms package I had tried to use
602 initially, and use
'tlp setcharge
40 80' to change when charging start
603 and stop. I
've done so now, but expect my existing battery is toast
604 and need to be replaced. The proposal is unfortunately Thinkpad
610 <title>New laptop - some more clues and ideas based on feedback
</title>
611 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
612 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
613 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
614 <description><p
>Several people contacted me after my previous blog post about my
615 need for a new laptop, and provided very useful feedback. I wish to
616 thank every one of these. Several pointed me to the possibility of
617 fixing my X230, and I am already in the process of getting Lenovo to
618 do so thanks to the on site, next day support contract covering the
619 machine. But the battery is almost useless (I expect to replace it
620 with a non-official battery) and I do not expect the machine to live
621 for many more years, so it is time to plan its replacement. If I did
622 not have a support contract, it was suggested to find replacement parts
623 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
624 might present a language barrier as I do not understand French.
</p
>
626 <p
>One tip I got was to use the
627 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
628 compare laptop models. It seem to have more models available than
629 prisjakt.no. Another tip I got from someone I know have similar
630 keyboard preferences was that the HP EliteBook
840 keyboard is not
631 very good, and this matches my experience with earlier EliteBook
632 keyboards I tested. Because of this, I will not consider it any further.
634 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
635 newest Thinkpad X model. The keyboard reintroduces mouse buttons
636 (which is missing from the X240), and is working fairly well with
637 Debian Sid/Unstable according to
638 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
639 got on the keyboard quality are not consistent. Some say the keyboard
640 is good, others say it is ok, while others say it is not very good.
641 Those with experience from X41 and and X60 agree that the X250
642 keyboard is not as good as those trusty old laptops, and suggest I
643 keep and fix my X230 instead of upgrading, or get a used X230 to
644 replace it. I
'm also told that the X250 lack leds for caps lock, disk
645 activity and battery status, which is very convenient on my X230. I
'm
646 also told that the CPU fan is running very often, making it a bit
647 noisy. In any case, the X250 do not work out of the box with Debian
648 Stable/Jessie, one of my requirements.
</p
>
650 <p
>I have also gotten a few vendor proposals, one was
651 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
652 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
653 The latter look very attractive to me.
</p
>
655 <p
>Again, thank you all for the very useful feedback. It help a lot
656 as I keep looking for a replacement.
</p
>
658 <p
>Update
2015-
07-
06: I was recommended to check out the
659 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
661 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
662 thinkpad X models
</a
>, and provide one year warranty.
</p
>
667 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
668 <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>
669 <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>
670 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
671 <description><p
>My primary work horse laptop is failing, and will need a
672 replacement soon. The left
5 cm of the screen on my Thinkpad X230
673 started flickering yesterday, and I suspect the cause is a broken
674 cable, as changing the angle of the screen some times get rid of the
675 flickering.
</p
>
677 <p
>My requirements have not really changed since I bought it, and is
679 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
680 described them in
2013</a
>. The last time I bought a laptop, I had
682 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
683 where I could select at least a few of the requirements (mouse pin,
684 wifi, weight) and go through the rest manually. Three button mouse
685 and a good keyboard is not available as an option, and all the three
686 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
687 G2) lack three mouse buttons). It is also unclear to me how good the
688 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
689 the keyboard, even if the quality and robustness in the X series have
690 deteriorated since X41.
</p
>
692 <p
>I wonder how I can find a sensible laptop when none of the options
693 seem sensible to me? Are there better services around to search the
694 set of available laptops for features? Please send me an email if you
695 have suggestions.
</p
>
697 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
698 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
699 of endorsed hardware
</a
>, which is useful background information.
</p
>
704 <title>How to stay with sysvinit in Debian Jessie
</title>
705 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
706 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
707 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
708 <description><p
>By now, it is well known that Debian Jessie will not be using
709 sysvinit as its boot system by default. But how can one keep using
710 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
712 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
713 Schubert
</a
> and
714 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
717 <p
>If you already are using Wheezy and want to upgrade to Jessie and
718 keep sysvinit as your boot system, create a file
719 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
720 you upgrade:
</p
>
722 <p
><blockquote
><pre
>
723 Package: systemd-sysv
724 Pin: release o=Debian
726 </pre
></blockquote
><p
>
728 <p
>This file content will tell apt and aptitude to not consider
729 installing systemd-sysv as part of any installation and upgrade
730 solution when resolving dependencies, and thus tell it to avoid
731 systemd as a default boot system. The end result should be that the
732 upgraded system keep using sysvinit.
</p
>
734 <p
>If you are installing Jessie for the first time, there is no way to
735 get sysvinit installed by default (debootstrap used by
736 debian-installer have no option for this), but one can tell the
737 installer to switch to sysvinit before the first boot. Either by
738 using a kernel argument to the installer, or by adding a line to the
739 preseed file used. First, the kernel command line argument:
741 <p
><blockquote
><pre
>
742 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
743 </pre
></blockquote
><p
>
745 <p
>Next, the line to use in a preseed file:
</p
>
747 <p
><blockquote
><pre
>
748 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
749 </pre
></blockquote
><p
>
751 <p
>One can of course also do this after the first boot by installing
752 the sysvinit-core package.
</p
>
754 <p
>I recommend only using sysvinit if you really need it, as the
755 sysvinit boot sequence in Debian have several hardware specific bugs
756 on Linux caused by the fact that it is unpredictable when hardware
757 devices show up during boot. But on the other hand, the new default
758 boot system still have a few rough edges I hope will be fixed before
759 Jessie is released.
</p
>
761 <p
>Update
2014-
11-
26: Inspired by
762 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
763 blog post by Torsten Glaser
</a
>, added --purge to the preseed
769 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
770 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
772 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
773 <description><p
>The right to communicate with your friends and family in private,
774 without anyone snooping, is a right every citicen have in a liberal
775 democracy. But this right is under serious attack these days.
</p
>
777 <p
>A while back it occurred to me that one way to make the dragnet
778 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
779 the whisleblower Snowden) more expensive for Internet email,
780 is to deliver all email using SMTP via Tor. Such SMTP option would be
781 a nice addition to the FreedomBox project if we could send email
782 between FreedomBox machines without leaking metadata about the emails
783 to the people peeking on the wire. I
784 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
785 this on the FreedomBox project mailing list in October
</a
> and got a
786 lot of useful feedback and suggestions. It also became obvious to me
787 that this was not a novel idea, as the same idea was tested and
788 documented by Johannes Berg as early as
2006, and both
789 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
790 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
791 propose a similar method / protocol to pass emails between users.
</p
>
793 <p
>To implement such system one need to set up a Tor hidden service
794 providing the SMTP protocol on port
25, and use email addresses
795 looking like username@hidden-service-name.onion. With such addresses
796 the connections to port
25 on hidden-service-name.onion using Tor will
797 go to the correct SMTP server. To do this, one need to configure the
798 Tor daemon to provide the hidden service and the mail server to accept
799 emails for this .onion domain. To learn more about Exim configuration
800 in Debian and test the design provided by Johannes Berg in his FAQ, I
801 set out yesterday to create a Debian package for making it trivial to
802 set up such SMTP over Tor service based on Debian. Getting it to work
803 were fairly easy, and
804 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
805 source code for the Debian package
</a
> is available from github. I
806 plan to move it into Debian if further testing prove this to be a
807 useful approach.
</p
>
809 <p
>If you want to test this, set up a blank Debian machine without any
810 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
811 get rid of exim4). Install tor, clone the git repository mentioned
812 above, build the deb and install it on the machine. Next, run
813 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
814 the instructions to get the service up and running. Restart tor and
815 exim when it is done, and test mail delivery using swaks like
818 <p
><blockquote
><pre
>
819 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
820 --to fbx@dutlqrrmjhtfa3vp.onion
821 </pre
></blockquote
></p
>
823 <p
>This will test the SMTP delivery using tor. Replace the email
824 address with your own address to test your server. :)
</p
>
826 <p
>The setup procedure is still to complex, and I hope it can be made
827 easier and more automatic. Especially the tor setup need more work.
828 Also, the package include a tor-smtp tool written in C, but its task
829 should probably be rewritten in some script language to make the deb
830 architecture independent. It would probably also make the code easier
831 to review. The tor-smtp tool currently need to listen on a socket for
832 exim to talk to it and is started using xinetd. It would be better if
833 no daemon and no socket is needed. I suspect it is possible to get
834 exim to run a command line tool for delivery instead of talking to a
835 socket, and hope to figure out how in a future version of this
838 <p
>Until I wipe my test machine, I can be reached using the
839 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
845 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
846 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
848 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
849 <description><p
>If you ever had to moderate a mailman list, like the ones on
850 alioth.debian.org, you know the web interface is fairly slow to
851 operate. First you visit one web page, enter the moderation password
852 and get a new page shown with a list of all the messages to moderate
853 and various options for each email address. This take a while for
854 every list you moderate, and you need to do it regularly to do a good
855 job as a list moderator. But there is a quick alternative,
856 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
857 listadmin program
</a
>. It allow you to check lists for new messages
858 to moderate in a fraction of a second. Here is a test run on two
859 lists I recently took over:
</p
>
861 <p
><blockquote
><pre
>
862 % time listadmin xiph
863 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
864 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
870 </pre
></blockquote
></p
>
872 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
873 there are no message in the moderation queue. Every morning I
874 currently moderate
68 mailman lists, and it normally take around two
875 minutes. When I took over the two pkg-xiph lists above a few days
876 ago, there were
400 emails waiting in the moderator queue. It took me
877 less than
15 minutes to process them all using the listadmin
880 <p
>If you install
881 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
882 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
883 with content like this, the moderation task is a breeze:
</p
>
885 <p
><blockquote
><pre
>
886 username username@example.org
889 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
892 adminurl https://{domain}/mailman/admindb/{list}
893 mailman-list@lists.example.com
896 other-list@otherserver.example.org
897 </pre
></blockquote
></p
>
899 <p
>There are other options to set as well. Check the manual page to
900 learn the details.
</p
>
902 <p
>If you are forced to moderate lists on a mailman installation where
903 the SSL certificate is self signed or not properly signed by a
904 generally accepted signing authority, you can set a environment
905 variable when calling listadmin to disable SSL verification:
</p
>
907 <p
><blockquote
><pre
>
908 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
909 </pre
></blockquote
></p
>
911 <p
>If you want to moderate a subset of the lists you take care of, you
912 can provide an argument to the listadmin script like I do in the
913 initial screen dump (the xiph argument). Using an argument, only
914 lists matching the argument string will be processed. This make it
915 quick to accept messages if you notice the moderation request in your
918 <p
>Without the listadmin program, I would never be the moderator of
68
919 mailing lists, as I simply do not have time to spend on that if the
920 process was any slower. The listadmin program have saved me hours of
921 time I could spend elsewhere over the years. It truly is nice free
924 <p
>As usual, if you use Bitcoin and want to show your support of my
925 activities, please send Bitcoin donations to my address
926 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
928 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
929 configuration example. Also, I
've been told that the
930 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
936 <title>Debian Jessie, PXE and automatic firmware installation
</title>
937 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
938 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
939 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
940 <description><p
>When PXE installing laptops with Debian, I often run into the
941 problem that the WiFi card require some firmware to work properly.
942 And it has been a pain to fix this using preseeding in Debian.
943 Normally something more is needed. But thanks to
944 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
945 package
</a
> and its recent tasksel extension, it has now become easy
946 to do this using simple preseeding.
</p
>
948 <p
>The isenkram-cli package provide tasksel tasks which will install
949 firmware for the hardware found in the machine (actually, requested by
950 the kernel modules for the hardware). (It can also install user space
951 programs supporting the hardware detected, but that is not the focus
952 of this story.)
</p
>
954 <p
>To get this working in the default installation, two preeseding
955 values are needed. First, the isenkram-cli package must be installed
956 into the target chroot (aka the hard drive) before tasksel is executed
957 in the pkgsel step of the debian-installer system. This is done by
958 preseeding the base-installer/includes debconf value to include the
959 isenkram-cli package. The package name is next passed to debootstrap
960 for installation. With the isenkram-cli package in place, tasksel
961 will automatically use the isenkram tasks to detect hardware specific
962 packages for the machine being installed and install them, because
963 isenkram-cli contain tasksel tasks.
</p
>
965 <p
>Second, one need to enable the non-free APT repository, because
966 most firmware unfortunately is non-free. This is done by preseeding
967 the apt-mirror-setup step. This is unfortunate, but for a lot of
968 hardware it is the only option in Debian.
</p
>
970 <p
>The end result is two lines needed in your preseeding file to get
971 firmware installed automatically by the installer:
</p
>
973 <p
><blockquote
><pre
>
974 base-installer base-installer/includes string isenkram-cli
975 apt-mirror-setup apt-setup/non-free boolean true
976 </pre
></blockquote
></p
>
978 <p
>The current version of isenkram-cli in testing/jessie will install
979 both firmware and user space packages when using this method. It also
980 do not work well, so use version
0.15 or later. Installing both
981 firmware and user space packages might give you a bit more than you
982 want, so I decided to split the tasksel task in two, one for firmware
983 and one for user space programs. The firmware task is enabled by
984 default, while the one for user space programs is not. This split is
985 implemented in the package currently in unstable.
</p
>
987 <p
>If you decide to give this a go, please let me know (via email) how
988 this recipe work for you. :)
</p
>
990 <p
>So, I bet you are wondering, how can this work. First and
991 foremost, it work because tasksel is modular, and driven by whatever
992 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
993 isenkram-cli package place two files for tasksel to find. First there
994 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
996 <p
><blockquote
><pre
>
997 Task: isenkram-packages
999 Description: Hardware specific packages (autodetected by isenkram)
1000 Based on the detected hardware various hardware specific packages are
1002 Test-new-install: show show
1004 Packages: for-current-hardware
1006 Task: isenkram-firmware
1008 Description: Hardware specific firmware packages (autodetected by isenkram)
1009 Based on the detected hardware various hardware specific firmware
1010 packages are proposed.
1011 Test-new-install: mark show
1013 Packages: for-current-hardware-firmware
1014 </pre
></blockquote
></p
>
1016 <p
>The key parts are Test-new-install which indicate how the task
1017 should be handled and the Packages line referencing to a script in
1018 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1019 list of packages to install. The for-current-hardware-firmware script
1020 look like this to list relevant firmware for the machine:
1022 <p
><blockquote
><pre
>
1025 PATH=/usr/sbin:$PATH
1027 isenkram-autoinstall-firmware -l
1028 </pre
></blockquote
></p
>
1030 <p
>With those two pieces in place, the firmware is installed by
1031 tasksel during the normal d-i run. :)
</p
>
1033 <p
>If you want to test what tasksel will install when isenkram-cli is
1034 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1035 --new-install
</tt
> to get the list of packages that tasksel would
1038 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1039 pilots in testing this feature, as isenkram is used there now to
1040 install firmware, replacing the earlier scripts.
</p
>
1045 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1046 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1048 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1049 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1050 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1051 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1052 on a screen normally showing the bread types and prizes:
</p
>
1054 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1056 <p
>If it had booted as it was supposed to, I would never had known
1057 about this hidden Linux installation. It is interesting what
1058 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1063 <title>New lsdvd release version
0.17 is ready
</title>
1064 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1065 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1066 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1067 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1068 got a new set of developers a few weeks ago, after the original
1069 developer decided to step down and pass the project to fresh blood.
1070 This project is now maintained by Petter Reinholdtsen and Steve
1073 <p
>I just wrapped up
1074 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1075 new lsdvd release
</a
>, available in git or from
1076 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1077 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1082 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1083 <li
>Check for garbage in the program chains, which indicate that a track is
1084 non-existant, to work around additional copy protection
</li
>
1085 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
1086 <li
>Fix pallete display of first entry
</li
>
1087 <li
>Fix include orders
</li
>
1088 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
1089 <li
>Fix the chapter count
</li
>
1090 <li
>Make sure the array size and the array limit used when initialising
1091 the palette size is the same.
</li
>
1092 <li
>Fix array printing.
</li
>
1093 <li
>Correct subsecond calculations.
</li
>
1094 <li
>Add sector information to the output format.
</li
>
1095 <li
>Clean up code to be closer to ANSI C and compile without warnings
1096 with more GCC compiler warnings.
</li
>
1100 <p
>This change bring together patches for lsdvd in use in various
1101 Linux and Unix distributions, as well as patches submitted to the
1102 project the last nine years. Please check it out. :)
</p
>
1107 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
1108 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
1109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
1110 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
1111 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1112 project
</a
> provide a Linux solution for schools, including a
1113 powerful desktop with education software, a central server providing
1114 web pages, user database, user home directories, central login and PXE
1115 boot of both clients without disk and the installation to install Debian
1116 Edu on machines with disk (and a few other services perhaps to small
1117 to mention here). We in the Debian Edu team are currently working on
1118 the Jessie based version, trying to get everything in shape before the
1119 freeze, to avoid having to maintain our own package repository in the
1121 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
1122 status
</a
> can be seen on the Debian wiki, and there is still heaps of
1123 work left. Some fatal problems block testing, breaking the installer,
1124 but it is possible to work around these to get anyway. Here is a
1125 recipe on how to get the installation limping along.
</p
>
1127 <p
>First, download the test ISO via
1128 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
1129 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
1131 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
1132 The ISO build was broken on Tuesday, so we do not get a new ISO every
1133 12 hours or so, but thankfully the ISO we already got we are able to
1134 install with some tweaking.
</p
>
1136 <p
>When you get to the Debian Edu profile question, go to tty2
1137 (use Alt-Ctrl-F2), run
</p
>
1139 <p
><blockquote
><pre
>
1140 nano /usr/bin/edu-eatmydata-install
1141 </pre
></blockquote
></p
>
1143 <p
>and add
'exit
0' as the second line, disabling the eatmydata
1144 optimization. Return to the installation, select the profile you want
1145 and continue. Without this change, exim4-config will fail to install
1146 due to a known bug in eatmydata.
</p
>
1148 <p
>When you get the grub question at the end, answer /dev/sda (or if
1149 this do not work, figure out what your correct value would be. All my
1150 test machines need /dev/sda, so I have no advice if it do not fit
1151 your need.
</p
>
1153 <p
>If you installed a profile including a graphical desktop, log in as
1154 root after the initial boot from hard drive, and install the
1155 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1156 or mate. If you want several desktop options, install more than one
1157 metapackage. Once this is done, reboot and you should have a working
1158 graphical login screen. This workaround should no longer be needed
1159 once the education-tasks package version
1.801 enter testing in two
1162 <p
>I believe the ISO build will start working on two days when the new
1163 tasksel package enter testing and Steve McIntyre get a chance to
1164 update the debian-cd git repository. The eatmydata, grub and desktop
1165 issues are already fixed in unstable and testing, and should show up
1166 on the ISO as soon as the ISO build start working again. Well the
1167 eatmydata optimization is really just disabled. The proper fix
1168 require an upload by the eatmydata maintainer applying the patch
1169 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
1170 The rest have proper fixes in unstable.
</p
>
1172 <p
>I hope this get you going with the installation testing, as we are
1173 quickly running out of time trying to get our Jessie based
1174 installation ready before the distribution freeze in a month.
</p
>
1179 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
1180 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
1181 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
1182 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
1183 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
1184 to handle my fairly large DVD collection. It is a nice command line
1185 tool to get details about a DVD, like title, tracks, track length,
1186 etc, in XML, Perl or human readable format. But lsdvd have not seen
1187 any new development since
2006 and had a few irritating bugs affecting
1188 its use with some DVDs. Upstream seemed to be dead, and in January I
1189 sent a small probe asking for a version control repository for the
1190 project, without any reply. But I use it regularly and would like to
1191 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
1192 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
1193 the project admin, and after getting a reply from him explaining that
1194 he was no longer interested in the project, I asked if I could take
1195 over. And yesterday, I became project admin.
</p
>
1197 <p
>I
've been in touch with a Gentoo developer and the Debian
1198 maintainer interested in joining forces to maintain the upstream
1199 project, and I hope we can get a new release out fairly quickly,
1200 collecting the patches spread around on the internet into on place.
1201 I
've added the relevant Debian patches to the freshly created git
1202 repository, and expect the Gentoo patches to make it too. If you got
1203 a DVD collection and care about command line tools, check out
1204 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
1205 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1206 list
</a
>. :)
</p
>
1211 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1212 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1214 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1215 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1216 a lot quicker. When we install more than
2000 packages in
1217 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1218 tasksel in the installer, unpacking the binary packages take forever.
1219 A part of the slow I/O issue was discussed in
1220 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1221 much file system sync-ing done by dpkg, which is the package
1222 responsible for unpacking the binary packages. Other parts (like code
1223 executed by postinst scripts) might also sync to disk during
1224 installation. All this sync-ing to disk do not really make sense to
1225 me. If the machine crash half-way through, I start over, I do not try
1226 to salvage the half installed system. So the failure sync-ing is
1227 supposed to protect against, hardware or system crash, is not really
1228 relevant while the installer is running.
</p
>
1230 <p
>A few days ago, I thought of a way to get rid of all the file
1231 system sync()-ing in a fairly non-intrusive way, without the need to
1232 change the code in several packages. The idea is not new, but I have
1233 not heard anyone propose the approach using dpkg-divert before. It
1234 depend on the small and clever package
1235 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1236 uses LD_PRELOAD to replace the system functions for syncing data to
1237 disk with functions doing nothing, thus allowing programs to live
1238 dangerous while speeding up disk I/O significantly. Instead of
1239 modifying the implementation of dpkg, apt and tasksel (which are the
1240 packages responsible for selecting, fetching and installing packages),
1241 it occurred to me that we could just divert the programs away, replace
1242 them with a simple shell wrapper calling
1243 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1244 Two days ago I decided to test the idea, and wrapped up a simple
1245 implementation for the Debian Edu udeb.
</p
>
1247 <p
>The effect was stunning. In my first test it reduced the running
1248 time of the pkgsel step (installing tasks) from
64 to less than
44
1249 minutes (
20 minutes shaved off the installation) on an old Dell
1250 Latitude D505 machine. I am not quite sure what the optimised time
1251 would have been, as I messed up the testing a bit, causing the debconf
1252 priority to get low enough for two questions to pop up during
1253 installation. As soon as I saw the questions I moved the installation
1254 along, but do not know how long the question were holding up the
1255 installation. I did some more measurements using Debian Edu Jessie,
1256 and got these results. The time measured is the time stamp in
1257 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1258 "pkgsel: finishing up
" lines, if you want to do the same measurement
1259 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1260 timing thus do not depend on how quickly the user handle the tasksel
1263 <p
><table
>
1266 <th
>Machine/setup
</th
>
1267 <th
>Original tasksel
</th
>
1268 <th
>Optimised tasksel
</th
>
1269 <th
>Reduction
</th
>
1273 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1274 <td
>64 min (
07:
46-
08:
50)
</td
>
1275 <td
><44 min (
11:
27-
12:
11)
</td
>
1276 <td
>>20 min
18%
</td
>
1280 <td
>Latitude D505 Roaming LXDE
</td
>
1281 <td
>57 min (
08:
48-
09:
45)
</td
>
1282 <td
>34 min (
07:
43-
08:
17)
</td
>
1283 <td
>23 min
40%
</td
>
1287 <td
>Latitude D505 Minimal
</td
>
1288 <td
>22 min (
10:
37-
10:
59)
</td
>
1289 <td
>11 min (
11:
16-
11:
27)
</td
>
1290 <td
>11 min
50%
</td
>
1294 <td
>Thinkpad X200 Minimal
</td
>
1295 <td
>6 min (
08:
19-
08:
25)
</td
>
1296 <td
>4 min (
08:
04-
08:
08)
</td
>
1297 <td
>2 min
33%
</td
>
1301 <td
>Thinkpad X200 Roaming KDE
</td
>
1302 <td
>19 min (
09:
21-
09:
40)
</td
>
1303 <td
>15 min (
10:
25-
10:
40)
</td
>
1304 <td
>4 min
21%
</td
>
1307 </table
></p
>
1309 <p
>The test is done using a netinst ISO on a USB stick, so some of the
1310 time is spent downloading packages. The connection to the Internet
1311 was
100Mbit/s during testing, so downloading should not be a
1312 significant factor in the measurement. Download typically took a few
1313 seconds to a few minutes, depending on the amount of packages being
1314 installed.
</p
>
1316 <p
>The speedup is implemented by using two hooks in
1317 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
1318 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
1319 finish-install.d hook to remove the divert at the end of the
1320 installation. I picked the pre-pkgsel.d hook instead of the
1321 post-base-installer.d hook because I test using an ISO without the
1322 eatmydata package included, and the post-base-installer.d hook in
1323 Debian Edu can only operate on packages included in the ISO. The
1324 negative effect of this is that I am unable to activate this
1325 optimization for the kernel installation step in d-i. If the code is
1326 moved to the post-base-installer.d hook, the speedup would be larger
1327 for the entire installation.
</p
>
1329 <p
>I
've implemented this in the
1330 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
1331 git repository, and plan to provide the optimization as part of the
1332 Debian Edu installation. If you want to test this yourself, you can
1333 create two files in the installer (or in an udeb). One shell script
1334 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
1336 <p
><blockquote
><pre
>
1339 . /usr/share/debconf/confmodule
1341 logger -t my-pkgsel
"info: $*
"
1344 logger -t my-pkgsel
"error: $*
"
1346 override_install() {
1347 apt-install eatmydata || true
1348 if [ -x /target/usr/bin/eatmydata ] ; then
1349 for bin in dpkg apt-get aptitude tasksel ; do
1351 # Test that the file exist and have not been diverted already.
1352 if [ -f /target$file ] ; then
1353 info
"diverting $file using eatmydata
"
1354 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
1355 > /target$file.edu
1356 chmod
755 /target$file.edu
1357 in-target dpkg-divert --package debian-edu-config \
1358 --rename --quiet --add $file
1359 ln -sf ./$bin.edu /target$file
1361 error
"unable to divert $file, as it is missing.
"
1365 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
1370 </pre
></blockquote
></p
>
1372 <p
>To clean up, another shell script should go into
1373 /usr/lib/finish-install.d/ with code like this:
1375 <p
><blockquote
><pre
>
1377 . /usr/share/debconf/confmodule
1379 logger -t my-finish-install
"error: $@
"
1381 remove_install_override() {
1382 for bin in dpkg apt-get aptitude tasksel ; do
1384 if [ -x /target$file.edu ] ; then
1386 in-target dpkg-divert --package debian-edu-config \
1387 --rename --quiet --remove $file
1390 error
"Missing divert for $file.
"
1393 sync # Flush file buffers before continuing
1396 remove_install_override
1397 </pre
></blockquote
></p
>
1399 <p
>In Debian Edu, I placed both code fragments in a separate script
1400 edu-eatmydata-install and call it from the pre-pkgsel.d and
1401 finish-install.d scripts.
</p
>
1403 <p
>By now you might ask if this change should get into the normal
1404 Debian installer too? I suspect it should, but am not sure the
1405 current debian-installer coordinators find it useful enough. It also
1406 depend on the side effects of the change. I
'm not aware of any, but I
1407 guess we will see if the change is safe after some more testing.
1408 Perhaps there is some package in Debian depending on sync() and
1409 fsync() having effect? Perhaps it should go into its own udeb, to
1410 allow those of us wanting to enable it to do so without affecting
1413 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
1414 will break installation of all programs using gnutls because of
1415 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
1416 eatmydata package in Debian will solve it.
</p
>
1418 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
1419 the optimization work again. And I have discovered that the
1420 dpkg-divert trick is not really needed and implemented a slightly
1421 simpler approach as part of the debian-edu-install package. See
1422 tools/edu-eatmydata-install in the source package.
</p
>
1424 <p
>Update
2014-
11-
11: Unfortunately, a new
1425 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
1426 triggering on i386 made it into testing, and broke this installation
1427 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
1428 request
768893</a
> is accepted, it should be working again.
</p
>
1433 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
1434 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
1435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
1436 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
1437 <description><p
>Yesterday, I had the pleasure of attending a talk with the
1438 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
1439 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
1440 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
1441 learn that there is a large set of publicly available key servers to
1442 use when looking for peoples public key. So far I have used
1443 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1444 were misbehaving, but those days are ended. The servers I have used
1445 up until yesterday have been slow and some times unavailable. I hope
1446 those problems are gone now.
</p
>
1448 <p
>Behind the round robin DNS entry of the
1449 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
1450 there is a pool of more than
100 keyservers which are checked every
1451 day to ensure they are well connected and up to date. It must be
1452 better than what I have used so far. :)
</p
>
1454 <p
>Yesterdays speaker told me that the service is the default
1455 keyserver provided by the default configuration in GnuPG, but this do
1456 not seem to be used in Debian. Perhaps it should?
</p
>
1458 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
1461 <p
><blockquote
><pre
>
1462 keyserver pool.sks-keyservers.net
1463 </pre
></blockquote
></p
>
1465 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
1466 entries in DNS. Just for fun, I did just that at work, so now every
1467 user of GnuPG at the University of Oslo should find a OpenGPG
1468 keyserver automatically should their need it:
</p
>
1470 <p
><blockquote
><pre
>
1471 % host -t srv _pgpkey-http._tcp.uio.no
1472 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
1474 </pre
></blockquote
></p
>
1476 <p
>Now if only
1477 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
1478 HKP lookup protocol
</a
> supported finding signature paths, I would be
1479 very happy. It can look up a given key or search for a user ID, but I
1480 normally do not want that, but to find a trust path from my key to
1481 another key. Given a user ID or key ID, I would like to find (and
1482 download) the keys representing a signature path from my key to the
1483 key in question, to be able to get a trust path between the two keys.
1484 This is as far as I can tell not possible today. Perhaps something
1485 for a future version of the protocol?
</p
>
1490 <title>From English wiki to translated PDF and epub via Docbook
</title>
1491 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
1492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
1493 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
1494 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1495 project
</a
> provide an instruction manual for teachers, system
1496 administrators and other users that contain useful tips for setting up
1497 and maintaining a Debian Edu installation. This text is about how the
1498 text processing of this manual is handled in the project.
</p
>
1500 <p
>One goal of the project is to provide information in the native
1501 language of its users, and for this we need to handle translations.
1502 But we also want to make sure each language contain the same
1503 information, so for this we need a good way to keep the translations
1504 in sync. And we want it to be easy for our users to improve the
1505 documentation, avoiding the need to learn special formats or tools to
1506 contribute, and the obvious way to do this is to make it possible to
1507 edit the documentation using a web browser. We also want it to be
1508 easy for translators to keep the translation up to date, and give them
1509 help in figuring out what need to be translated. Here is the list of
1510 tools and the process we have found trying to reach all these
1513 <p
>We maintain the authoritative source of our manual in the
1514 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
1515 wiki
</a
>, as several wiki pages written in English. It consist of one
1516 front page with references to the different chapters, several pages
1517 for each chapter, and finally one
"collection page
" gluing all the
1518 chapters together into one large web page (aka
1519 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
1520 AllInOne page
</a
>). The AllInOne page is the one used for further
1521 processing and translations. Thanks to the fact that the
1522 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
1523 wiki.debian.org support exporting pages in
1524 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
1525 the list of pages to export using the raw version of the AllInOne
1526 page, loop over each of them to generate a Docbook XML version of the
1527 manual. This process also download images and transform image
1528 references to use the locally downloaded images. The generated
1529 Docbook XML files are slightly broken, so some post-processing is done
1530 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
1531 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1532 a handfull of images. The XML file can now be used to generate PDF, HTML
1533 and epub versions of the English manual. This is the basic step of
1534 our process, making PDF (using dblatex), HTML (using xsltproc) and
1535 epub (using dbtoepub) version from Docbook XML, and the resulting files
1536 are placed in the debian-edu-doc-en binary package.
</p
>
1538 <p
>But English documentation is not enough for us. We want translated
1539 documentation too, and we want to make it easy for translators to
1540 track the English original. For this we use the
1541 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
1542 which allow us to transform the English Docbook XML file into a
1543 translation file (a .pot file), usable with the normal gettext based
1544 translation tools used by those translating free software. The pot
1545 file is used to create and maintain translation files (several .po
1546 files), which the translations update with the native language
1547 translations of all titles, paragraphs and blocks of text in the
1548 original. The next step is combining the original English Docbook XML
1549 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1550 create a translated Docbook XML file (in this case
1551 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1552 translated, if the translation is not complete) Docbook XML file can
1553 then be used like the original to create a PDF, HTML and epub version
1554 of the documentation.
</p
>
1556 <p
>The translators use different tools to edit the .po files. We
1558 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
1559 while some use emacs and vi, others can use web based editors like
1560 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
1561 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
1562 is where the .po file end up, in our git repository. Updated
1563 translations can either be committed directly to git, or submitted as
1564 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
1565 against the debian-edu-doc package
</a
>.
</p
>
1567 <p
>One challenge is images, which both might need to be translated (if
1568 they show translated user applications), and are needed in different
1569 formats when creating PDF and HTML versions (epub is a HTML version in
1570 this regard). For this we transform the original PNG images to the
1571 needed density and format during build, and have a way to provide
1572 translated images by storing translated versions in
1573 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1574 package maintainers know more.
</p
>
1576 <p
>If you wonder what the result look like, we provide
1577 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
1578 of the documentation packages on the web
</a
>. See for example the
1579 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
1580 PDF version
</a
> or the
1581 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
1582 HTML version
</a
>. We do not yet build the epub version by default,
1583 but perhaps it will be done in the future.
</p
>
1585 <p
>To learn more, check out
1586 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
1587 debian-edu-doc package
</a
>,
1588 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
1589 manual on the wiki
</a
> and
1590 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
1591 translation instructions
</a
> in the manual.
</p
>
1596 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
1597 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
1598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
1599 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
1600 <description><p
>It would be nice if it was easier in Debian to get all the hardware
1601 related packages relevant for the computer installed automatically.
1602 So I implemented one, using
1603 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
1604 package
</a
>. To use it, install the tasksel and isenkram packages and
1605 run tasksel as user root. You should be presented with a new option,
1606 "Hardware specific packages (autodetected by isenkram)
". When you
1607 select it, tasksel will install the packages isenkram claim is fit for
1608 the current hardware, hot pluggable or not.
<p
>
1610 <p
>The implementation is in two files, one is the tasksel menu entry
1611 description, and the other is the script used to extract the list of
1612 packages to install. The first part is in
1613 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
1616 <p
><blockquote
><pre
>
1619 Description: Hardware specific packages (autodetected by isenkram)
1620 Based on the detected hardware various hardware specific packages are
1622 Test-new-install: mark show
1624 Packages: for-current-hardware
1625 </pre
></blockquote
></p
>
1627 <p
>The second part is in
1628 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
1631 <p
><blockquote
><pre
>
1636 isenkram-autoinstall-firmware -l
1638 </pre
></blockquote
></p
>
1640 <p
>All in all, a very short and simple implementation making it
1641 trivial to install the hardware dependent package we all may want to
1642 have installed on our machines. I
've not been able to find a way to
1643 get tasksel to tell you exactly which packages it plan to install
1644 before doing the installation. So if you are curious or careful,
1645 check the output from the isenkram-* command line tools first.
</p
>
1647 <p
>The information about which packages are handling which hardware is
1648 fetched either from the isenkram package itself in
1649 /usr/share/isenkram/, from git.debian.org or from the APT package
1650 database (using the Modaliases header). The APT package database
1651 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1652 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
1653 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
1654 the python-apt code (bug
1655 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
1656 workaround I was able to get rid of the file descriptor leak and
1657 reduce the memory leak from ~
30 MiB per hardware detection down to
1658 around
2 MiB per hardware detection. It should make the desktop
1659 daemon a lot more useful. The fix is in version
0.7 uploaded to
1660 unstable today.
</p
>
1662 <p
>I believe the current way of mapping hardware to packages in
1663 Isenkram is is a good draft, but in the future I expect isenkram to
1664 use the AppStream data source for this. A proposal for getting proper
1665 AppStream support into Debian is floating around as
1666 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
1667 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
1668 project
</a
> will take place this summer to improve the situation. I
1669 look forward to seeing the result, and welcome patches for isenkram to
1670 start using the information when it is ready.
</p
>
1672 <p
>If you want your package to map to some specific hardware, either
1673 add a
"Xb-Modaliases
" header to your control file like I did in
1674 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
1675 package
</a
> or submit a bug report with the details to the isenkram
1677 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
1678 blog posts tagged isenkram
</a
> for details on the notation. I expect
1679 the information will be migrated to AppStream eventually, but for the
1680 moment I got no better place to store it.
</p
>
1685 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
1686 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
1687 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
1688 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
1689 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1690 project
</a
> is working on providing the software and hardware to make
1691 it easy for non-technical people to host their data and communication
1692 at home, and being able to communicate with their friends and family
1693 encrypted and away from prying eyes. It is still going strong, and
1694 today a major mile stone was reached.
</p
>
1696 <p
>Today, the last of the packages currently used by the project to
1697 created the system images were accepted into Debian Unstable. It was
1698 the freedombox-setup package, which is used to configure the images
1699 during build and on the first boot. Now all one need to get going is
1700 the build code from the freedom-maker git repository and packages from
1701 Debian. And once the freedombox-setup package enter testing, we can
1702 build everything directly from Debian. :)
</p
>
1704 <p
>Some key packages used by Freedombox are
1705 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
1706 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
1707 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
1708 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
1709 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
1710 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
1711 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
1712 are plans to integrate more packages into the setup. User
1713 documentation is maintained on the Debian wiki. Please
1714 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
1715 the manual
</a
> and help us improve it.
</p
>
1717 <p
>To test for yourself and create boot images with the FreedomBox
1718 setup, run this on a Debian machine using a user with sudo rights to
1719 become root:
</p
>
1721 <p
><pre
>
1722 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1723 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1725 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1727 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1728 </pre
></p
>
1730 <p
>Root access is needed to run debootstrap and mount loopback
1731 devices. See the README in the freedom-maker git repo for more
1732 details on the build. If you do not want all three images, trim the
1733 make line. Note that the virtualbox-image target is not really
1734 virtualbox specific. It create a x86 image usable in kvm, qemu,
1735 vmware and any other x86 virtual machine environment. You might need
1736 the version of vmdebootstrap in Jessie to get the build working, as it
1737 include fixes for a race condition with kpartx.
</p
>
1739 <p
>If you instead want to install using a Debian CD and the preseed
1740 method, boot a Debian Wheezy ISO and use this boot argument to load
1741 the preseed values:
</p
>
1743 <p
><pre
>
1744 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1745 </pre
></p
>
1747 <p
>I have not tested it myself the last few weeks, so I do not know if
1748 it still work.
</p
>
1750 <p
>If you wonder how to help, one task you could look at is using
1751 systemd as the boot system. It will become the default for Linux in
1752 Jessie, so we need to make sure it is usable on the Freedombox. I did
1753 a simple test a few weeks ago, and noticed dnsmasq failed to start
1754 during boot when using systemd. I suspect there are other problems
1755 too. :) To detect problems, there is a test suite included, which can
1756 be run from the plinth web interface.
</p
>
1758 <p
>Give it a go and let us know how it goes on the mailing list, and help
1759 us get the new release published. :) Please join us on
1760 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1761 irc.debian.org)
</a
> and
1762 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1763 mailing list
</a
> if you want to help make this vision come true.
</p
>
1768 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
1769 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
1770 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
1771 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
1772 <description><p
>For a while now, I have been looking for a sensible offsite backup
1773 solution for use at home. My requirements are simple, it must be
1774 cheap and locally encrypted (in other words, I keep the encryption
1775 keys, the storage provider do not have access to my private files).
1776 One idea me and my friends had many years ago, before the cloud
1777 storage providers showed up, was to use Google mail as storage,
1778 writing a Linux block device storing blocks as emails in the mail
1779 service provided by Google, and thus get heaps of free space. On top
1780 of this one can add encryption, RAID and volume management to have
1781 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1782 I never found time to implement such system. But the last few weeks I
1783 have looked at a system called
1784 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
1785 mounted network backed file system with the features I need.
</p
>
1787 <p
>S3QL is a fuse file system with a local cache and cloud storage,
1788 handling several different storage providers, any with Amazon S3,
1789 Google Drive or OpenStack API. There are heaps of such storage
1790 providers. S3QL can also use a local directory as storage, which
1791 combined with sshfs allow for file storage on any ssh server. S3QL
1792 include support for encryption, compression, de-duplication, snapshots
1793 and immutable file systems, allowing me to mount the remote storage as
1794 a local mount point, look at and use the files as if they were local,
1795 while the content is stored in the cloud as well. This allow me to
1796 have a backup that should survive fire. The file system can not be
1797 shared between several machines at the same time, as only one can
1798 mount it at the time, but any machine with the encryption key and
1799 access to the storage service can mount it if it is unmounted.
</p
>
1801 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
1802 package is included already. So to get started, run
<tt
>apt-get
1803 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
1804 Greenqloud, after reading their nice recipe on
1805 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
1806 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
1807 in Iceland more than those in USA when it come to keeping my personal
1808 data safe and private, and thus would rather spend money on a company
1809 in Iceland. Another nice recipe is available from the article
1810 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
1811 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
1812 Admin magazine. When the provider is picked, figure out how to get
1813 the API key needed to connect to the storage API. With Greencloud,
1814 the key did not show up until I had added payment details to my
1817 <p
>Armed with the API access details, it is time to create the file
1818 system. First, create a new bucket in the cloud. This bucket is the
1819 file system storage area. I picked a bucket name reflecting the
1820 machine that was going to store data there, but any name will do.
1821 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
1822 the API login and password, and a locally created password. Store it
1823 all in ~root/.s3ql/authinfo2 like this:
1825 <p
><blockquote
><pre
>
1827 storage-url: s3c://s.greenqloud.com:
443/bucket-name
1828 backend-login: API-login
1829 backend-password: API-password
1830 fs-passphrase: local-password
1831 </pre
></blockquote
></p
>
1833 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
1834 but any sensible way to create a fairly random password should do it.
1835 Armed with these details, it is now time to run mkfs, entering the API
1836 details and password to create it:
</p
>
1838 <p
><blockquote
><pre
>
1839 # mkdir -m
700 /var/lib/s3ql-cache
1840 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1841 --ssl s3c://s.greenqloud.com:
443/bucket-name
1842 Enter backend login:
1843 Enter backend password:
1844 Before using S3QL, make sure to read the user
's guide, especially
1845 the
'Important Rules to Avoid Loosing Data
' section.
1846 Enter encryption password:
1847 Confirm encryption password:
1848 Generating random encryption key...
1849 Creating metadata tables...
1859 Compressing and uploading metadata...
1860 Wrote
0.00 MB of compressed metadata.
1861 #
</pre
></blockquote
></p
>
1863 <p
>The next step is mounting the file system to make the storage available.
1865 <p
><blockquote
><pre
>
1866 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1867 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1868 Using
4 upload threads.
1869 Downloading and decompressing metadata...
1879 Mounting filesystem...
1881 Filesystem Size Used Avail Use% Mounted on
1882 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
1884 </pre
></blockquote
></p
>
1886 <p
>The file system is now ready for use. I use rsync to store my
1887 backups in it, and as the metadata used by rsync is downloaded at
1888 mount time, no network traffic (and storage cost) is triggered by
1889 running rsync. To unmount, one should not use the normal umount
1890 command, as this will not flush the cache to the cloud storage, but
1891 instead running the umount.s3ql command like this:
1893 <p
><blockquote
><pre
>
1896 </pre
></blockquote
></p
>
1898 <p
>There is a fsck command available to check the file system and
1899 correct any problems detected. This can be used if the local server
1900 crashes while the file system is mounted, to reset the
"already
1901 mounted
" flag. This is what it look like when processing a working
1902 file system:
</p
>
1904 <p
><blockquote
><pre
>
1905 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
1906 Using cached metadata.
1907 File system seems clean, checking anyway.
1908 Checking DB integrity...
1909 Creating temporary extra indices...
1910 Checking lost+found...
1911 Checking cached objects...
1912 Checking names (refcounts)...
1913 Checking contents (names)...
1914 Checking contents (inodes)...
1915 Checking contents (parent inodes)...
1916 Checking objects (reference counts)...
1917 Checking objects (backend)...
1918 ..processed
5000 objects so far..
1919 ..processed
10000 objects so far..
1920 ..processed
15000 objects so far..
1921 Checking objects (sizes)...
1922 Checking blocks (referenced objects)...
1923 Checking blocks (refcounts)...
1924 Checking inode-block mapping (blocks)...
1925 Checking inode-block mapping (inodes)...
1926 Checking inodes (refcounts)...
1927 Checking inodes (sizes)...
1928 Checking extended attributes (names)...
1929 Checking extended attributes (inodes)...
1930 Checking symlinks (inodes)...
1931 Checking directory reachability...
1932 Checking unix conventions...
1933 Checking referential integrity...
1934 Dropping temporary indices...
1935 Backing up old metadata...
1945 Compressing and uploading metadata...
1946 Wrote
0.89 MB of compressed metadata.
1948 </pre
></blockquote
></p
>
1950 <p
>Thanks to the cache, working on files that fit in the cache is very
1951 quick, about the same speed as local file access. Uploading large
1952 amount of data is to me limited by the bandwidth out of and into my
1953 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
1954 which is very close to my upload speed, and downloading the same
1955 Debian installation ISO gave me
610 kiB/s, close to my download speed.
1956 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
1957 network, not the file system code. I do not know what a good cache
1958 size would be, but suspect that the cache should e larger than your
1959 working set.
</p
>
1961 <p
>I mentioned that only one machine can mount the file system at the
1962 time. If another machine try, it is told that the file system is
1965 <p
><blockquote
><pre
>
1966 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1967 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1968 Using
8 upload threads.
1969 Backend reports that fs is still mounted elsewhere, aborting.
1971 </pre
></blockquote
></p
>
1973 <p
>The file content is uploaded when the cache is full, while the
1974 metadata is uploaded once every
24 hour by default. To ensure the
1975 file system content is flushed to the cloud, one can either umount the
1976 file system, or ask S3QL to flush the cache and metadata using
1979 <p
><blockquote
><pre
>
1980 # s3qlctrl upload-meta /s3ql
1981 # s3qlctrl flushcache /s3ql
1983 </pre
></blockquote
></p
>
1985 <p
>If you are curious about how much space your data uses in the
1986 cloud, and how much compression and deduplication cut down on the
1987 storage usage, you can use s3qlstat on the mounted file system to get
1990 <p
><blockquote
><pre
>
1992 Directory entries:
9141
1995 Total data size:
22049.38 MB
1996 After de-duplication:
21955.46 MB (
99.57% of total)
1997 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
1998 Database size:
2.39 MB (uncompressed)
1999 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2001 </pre
></blockquote
></p
>
2003 <p
>I mentioned earlier that there are several possible suppliers of
2004 storage. I did not try to locate them all, but am aware of at least
2005 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2006 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2007 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2008 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2009 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2010 accept payment in Bitcoin. Pick one that suit your need. Some of
2011 them provide several GiB of free storage, but the prize models are
2012 quite different and you will have to figure out what suits you
2015 <p
>While researching this blog post, I had a look at research papers
2016 and posters discussing the S3QL file system. There are several, which
2017 told me that the file system is getting a critical check by the
2018 science community and increased my confidence in using it. One nice
2020 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2021 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2022 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2023 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2024 and Pamela Smith. Please have a look.
</p
>
2026 <p
>Given my problems with different file systems earlier, I decided to
2027 check out the mounted S3QL file system to see if it would be usable as
2028 a home directory (in other word, that it provided POSIX semantics when
2029 it come to locking and umask handling etc). Running
2030 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2031 test code to check file system semantics
</a
>, I was happy to discover that
2032 no error was found. So the file system can be used for home
2033 directories, if one chooses to do so.
</p
>
2035 <p
>If you do not want a locally file system, and want something that
2036 work without the Linux fuse file system, I would like to mention the
2037 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2038 provide locally encrypted backup using a command line client. It have
2039 a nicer access control system, where one can split out read and write
2040 access, allowing some systems to write to the backup and others to
2041 only read from it.
</p
>
2043 <p
>As usual, if you use Bitcoin and want to show your support of my
2044 activities, please send Bitcoin donations to my address
2045 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2050 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2051 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2052 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2053 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2054 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2055 project
</a
> is working on providing the software and hardware for
2056 making it easy for non-technical people to host their data and
2057 communication at home, and being able to communicate with their
2058 friends and family encrypted and away from prying eyes. It has been
2059 going on for a while, and is slowly progressing towards a new test
2060 release (
0.2).
</p
>
2062 <p
>And what day could be better than the Pi day to announce that the
2063 new version will provide
"hard drive
" / SD card / USB stick images for
2064 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2065 system), and can also be installed using a Debian installer preseed
2066 file. The Debian based Freedombox is now based on Debian Jessie,
2067 where most of the needed packages used are already present. Only one,
2068 the freedombox-setup package, is missing. To try to build your own
2069 boot image to test the current status, fetch the freedom-maker scripts
2071 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2072 with a user with sudo access to become root:
2075 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2077 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2078 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2080 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2083 <p
>Root access is needed to run debootstrap and mount loopback
2084 devices. See the README for more details on the build. If you do not
2085 want all three images, trim the make line. But note that thanks to
<a
2086 href=
"https://bugs.debian.org/
741407">a race condition in
2087 vmdebootstrap
</a
>, the build might fail without the patch to the
2088 kpartx call.
</p
>
2090 <p
>If you instead want to install using a Debian CD and the preseed
2091 method, boot a Debian Wheezy ISO and use this boot argument to load
2092 the preseed values:
</p
>
2095 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2098 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
2099 recently introduced bug in apt in Jessie
</a
>, the installer will
2100 currently hang while setting up APT sources. Killing the
2101 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
2102 installation will get the installation going. This affect all
2103 installations in Jessie, and I expect it will be fixed soon.
</p
>
2105 <p
>Give it a go and let us know how it goes on the mailing list, and help
2106 us get the new release published. :) Please join us on
2107 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2108 irc.debian.org)
</a
> and
2109 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2110 mailing list
</a
> if you want to help make this vision come true.
</p
>
2115 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
2116 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
2117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
2118 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
2119 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
2120 innetgr tools, because I needed them in
2121 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
2122 ng-utils, and it has served me well. I placed the project under the
2123 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
2124 repository. But many years ago, the CVS repository was dropped (lost,
2125 not migrated to new hardware, not sure), and the project have lacked a
2126 proper home since then.
</p
>
2128 <p
>Last summer, I had a look at the package and made a new release
2129 fixing a irritating crash bug, but was unable to store the changes in
2130 a proper source control system. I applied for a project on
2131 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
2132 to follow up on it. Until today. :)
</p
>
2134 <p
>After many hours of cleaning and migration, the ng-utils project
2135 now have a new home, and a git repository with the highlight of the
2136 history of the project. I published all release tarballs and imported
2137 them into the git repository. As the project is really stable and not
2138 expected to gain new features any time soon, I decided to make a new
2139 release and call it
1.0. Visit the new project home on
2140 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
2141 if you want to check it out. The new version is also uploaded into
2142 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
2147 <title>Testing sysvinit from experimental in Debian Hurd
</title>
2148 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
2149 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
2150 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
2151 <description><p
>A few days ago I decided to try to help the Hurd people to get
2152 their changes into sysvinit, to allow them to use the normal sysvinit
2153 boot system instead of their old one. This follow up on the
2154 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
2155 Google Summer of Code work
</a
> done last summer by Justus Winter to
2156 get Debian on Hurd working more like Debian on Linux. To get started,
2157 I downloaded a prebuilt hard disk image from
2158 <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
>,
2159 and started it using virt-manager.
</p
>
2161 <p
>The first think I had to do after logging in (root without any
2162 password) was to get the network operational. I followed
2163 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
2164 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
2165 commands as root to get the machine to accept a IP address from the
2166 kvm internal DHCP server:
</p
>
2168 <p
><blockquote
><pre
>
2169 settrans -fgap /dev/netdde /hurd/netdde
2170 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
2171 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
2173 </pre
></blockquote
></p
>
2175 <p
>After this, the machine had internet connectivity, and I could
2176 upgrade it and install the sysvinit packages from experimental and
2177 enable it as the default boot system in Hurd.
</p
>
2179 <p
>But before I did that, I set a password on the root user, as ssh is
2180 running on the machine it for ssh login to work a password need to be
2181 set. Also, note that a bug somewhere in openssh on Hurd block
2182 compression from working. Remember to turn that off on the client
2185 <p
>Run these commands as root to upgrade and test the new sysvinit
2188 <p
><blockquote
><pre
>
2189 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
2190 deb http://http.debian.net/debian/ experimental main
2193 apt-get dist-upgrade
2194 apt-get install -t experimental initscripts sysv-rc sysvinit \
2195 sysvinit-core sysvinit-utils
2196 update-alternatives --config runsystem
2197 </pre
></blockquote
></p
>
2199 <p
>To reboot after switching boot system, you have to use
2200 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
2201 yet a sysvinit process able to receive the signals from the normal
2202 'reboot
' command. After switching to sysvinit as the boot system,
2203 upgrading every package and rebooting, the network come up with DHCP
2204 after boot as it should, and the settrans/pkill hack mentioned at the
2205 start is no longer needed. But for some strange reason, there are no
2206 longer any login prompt in the virtual console, so I logged in using
2209 <p
>Note that there are some race conditions in Hurd making the boot
2210 fail some times. No idea what the cause is, but hope the Hurd porters
2211 figure it out. At least Justus said on IRC (#debian-hurd on
2212 irc.debian.org) that they are aware of the problem. A way to reduce
2213 the impact is to upgrade to the Hurd packages built by Justus by
2214 adding this repository to the machine:
</p
>
2216 <p
><blockquote
><pre
>
2217 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2218 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2220 </pre
></blockquote
></p
>
2222 <p
>At the moment the prebuilt virtual machine get some packages from
2223 http://ftp.debian-ports.org/debian, because some of the packages in
2224 unstable do not yet include the required patches that are lingering in
2225 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2227 <p
><blockquote
><pre
>
2228 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2229 i emacs - GNU Emacs editor (metapackage)
2230 i gdb - GNU Debugger
2231 i hurd-recommended - Miscellaneous translators
2232 i isc-dhcp-client - ISC DHCP client
2233 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2234 i libc-bin - Embedded GNU C Library: Binaries
2235 i libc-dev-bin - Embedded GNU C Library: Development binaries
2236 i libc0.3 - Embedded GNU C Library: Shared libraries
2237 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2238 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2239 i multiarch-support - Transitional package to ensure multiarch compatibilit
2240 i A x11-common - X Window System (X.Org) infrastructure
2241 i xorg - X.Org X Window System
2242 i A xserver-xorg - X.Org X server
2243 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2245 </pre
></blockquote
></p
>
2247 <p
>All in all, testing hurd has been an interesting experience. :)
2248 X.org did not work out of the box and I never took the time to follow
2249 the porters instructions to fix it. This time I was interested in the
2250 command line stuff.
<p
>
2255 <title>New chrpath release
0.16</title>
2256 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2257 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2258 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2259 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2260 find problems in C, C++ and Java code using static source code
2261 analysis. It can detect a lot of different problems, and is very
2262 useful to find memory and locking bugs in the error handling part of
2263 the source. The company behind it provide
2264 <a href=
"https://scan.coverity.com/
">check of free software projects as
2265 a community service
</a
>, and many hundred free software projects are
2266 already checked. A few days ago I decided to have a closer look at
2267 the Coverity system, and discovered that the
2268 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2269 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2270 projects I am involved with was already registered. But these are
2271 fairly big, and I would also like to have a small and easy project to
2272 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2273 checking of the chrpath project
</a
>. It was
2274 added to the checker and discovered seven potential defects. Six of
2275 these were real, mostly resource
"leak
" when the program detected an
2276 error. Nothing serious, as the resources would be released a fraction
2277 of a second later when the program exited because of the error, but it
2278 is nice to do it right in case the source of the program some time in
2279 the future end up in a library. Having fixed all defects and added
2280 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
2281 mailing list for the chrpath developers
</a
>, I decided it was time to
2282 publish a new release. These are the release notes:
</p
>
2284 <p
>New in
0.16 released
2014-
01-
14:
</p
>
2288 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
2289 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
2290 <li
>Mention new project mailing list in the documentation.
</li
>
2295 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2296 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
2297 project if something is wrong with the new release. The test suite
2298 did not discover any old errors, so if you find a new one, please also
2299 include a test suite check.
</p
>
2304 <title>New chrpath release
0.15</title>
2305 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
2306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
2307 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
2308 <description><p
>After many years break from the package and a vain hope that
2309 development would be continued by someone else, I finally pulled my
2310 acts together this morning and wrapped up a new release of chrpath,
2311 the command line tool to modify the rpath and runpath of already
2312 compiled ELF programs. The update was triggered by the persistence of
2313 Isha Vishnoi at IBM, which needed a new config.guess file to get
2314 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
2315 is working on. I checked the
2316 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
2317 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
2318 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
2319 packages for interesting patches (failed to find the source from
2320 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2321 These are the release notes:
</p
>
2323 <p
>New in
0.15 released
2013-
11-
24:
</p
>
2327 <li
>Updated config.sub and config.guess from the GNU project to work
2328 with newer architectures. Thanks to isha vishnoi for the heads
2331 <li
>Updated README with current URLs.
</li
>
2333 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2334 Matthias Klose.
</li
>
2336 <li
>Added missing help for -k|--keepgoing option, using patch by
2337 Petr Machata found in Fedora.
</li
>
2339 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
2340 .dynamic is a NULL terminated string. Based on patch found in
2341 Fedora credited Axel Thimm and Christian Krause.
</li
>
2346 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2347 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
2348 project if something is wrong with the new release. The test suite
2349 did not discover any old errors, so if you find a new one, please also
2350 include a testsuite check.
</p
>
2355 <title>Debian init.d boot script example for rsyslog
</title>
2356 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
2357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
2358 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
2359 <description><p
>If one of the points of switching to a new init system in Debian is
2360 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
2361 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
2362 init.d scripts at all. Here is an example init.d script, ie a rewrite
2363 of /etc/init.d/rsyslog:
</p
>
2365 <p
><pre
>
2366 #!/lib/init/init-d-script
2369 # Required-Start: $remote_fs $time
2370 # Required-Stop: umountnfs $time
2371 # X-Stop-After: sendsigs
2372 # Default-Start:
2 3 4 5
2373 # Default-Stop:
0 1 6
2374 # Short-Description: enhanced syslogd
2375 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2376 # It is quite compatible to stock sysklogd and can be
2377 # used as a drop-in replacement.
2379 DESC=
"enhanced syslogd
"
2380 DAEMON=/usr/sbin/rsyslogd
2381 </pre
></p
>
2383 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
2384 script was
137 lines, and the above is just
15 lines, most of it meta
2385 info/comments.
</p
>
2387 <p
>How to do this, you ask? Well, one create a new script
2388 /lib/init/init-d-script looking something like this:
2390 <p
><pre
>
2393 # Define LSB log_* functions.
2394 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
2395 # and status_of_proc is working.
2396 . /lib/lsb/init-functions
2399 # Function that starts the daemon/service
2405 #
0 if daemon has been started
2406 #
1 if daemon was already running
2407 #
2 if daemon could not be started
2408 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
2410 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2413 # Add code here, if necessary, that waits for the process to be ready
2414 # to handle requests from services started subsequently which depend
2415 # on this one. As a last resort, sleep for some time.
2419 # Function that stops the daemon/service
2424 #
0 if daemon has been stopped
2425 #
1 if daemon was already stopped
2426 #
2 if daemon could not be stopped
2427 # other if a failure occurred
2428 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
2429 RETVAL=
"$?
"
2430 [
"$RETVAL
" =
2 ]
&& return
2
2431 # Wait for children to finish too if this is a daemon that forks
2432 # and if the daemon is only ever run from this initscript.
2433 # If the above conditions are not satisfied then add some other code
2434 # that waits for the process to drop all resources that could be
2435 # needed by services started subsequently. A last resort is to
2436 # sleep for some time.
2437 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
2438 [
"$?
" =
2 ]
&& return
2
2439 # Many daemons don
't delete their pidfiles when they exit.
2441 return
"$RETVAL
"
2445 # Function that sends a SIGHUP to the daemon/service
2449 # If the daemon can reload its configuration without
2450 # restarting (for example, when it is sent a SIGHUP),
2451 # then implement that here.
2453 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
2458 scriptbasename=
"$(basename $
1)
"
2459 echo
"SN: $scriptbasename
"
2460 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
2461 script=
"$
1"
2468 NAME=$(basename $DAEMON)
2469 PIDFILE=/var/run/$NAME.pid
2471 # Exit if the package is not installed
2472 #[ -x
"$DAEMON
" ] || exit
0
2474 # Read configuration variable file if it is present
2475 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
2477 # Load the VERBOSE setting and other rcS variables
2480 case
"$
1" in
2482 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
2484 case
"$?
" in
2485 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2486 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2490 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
2492 case
"$?
" in
2493 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2494 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2498 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
2500 #reload|force-reload)
2502 # If do_reload() is not implemented then leave this commented out
2503 # and leave
'force-reload
' as an alias for
'restart
'.
2505 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
2509 restart|force-reload)
2511 # If the
"reload
" option is implemented then remove the
2512 #
'force-reload
' alias
2514 log_daemon_msg
"Restarting $DESC
" "$NAME
"
2516 case
"$?
" in
2519 case
"$?
" in
2521 1) log_end_msg
1 ;; # Old process is still running
2522 *) log_end_msg
1 ;; # Failed to start
2532 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
2538 </pre
></p
>
2540 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
2541 lot. I did not really polish the approach, so it might not always
2542 work out of the box, but you get the idea. I did not try very hard to
2543 optimize it nor make it more robust either.
</p
>
2545 <p
>A better argument for switching init system in Debian than reducing
2546 the size of init scripts (which is a good thing to do anyway), is to
2547 get boot system that is able to handle the kernel events sensibly and
2548 robustly, and do not depend on the boot to run sequentially. The boot
2549 and the kernel have not behaved sequentially in years.
</p
>
2554 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
2555 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
2556 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
2557 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
2558 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
2559 remote display access is the preferred solution with oVirt and RedHat
2560 Enterprise Virtualization, and I was sad to discover the other day
2561 that the browser plugin needed to use these systems seamlessly was
2562 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
2563 for a package
</a
> was from
2012-
04-
10 with no progress since
2564 2013-
04-
01, so I decided to wrap up a package based on the great work
2565 from Cajus Pollmeier and put it in a collab-maint maintained git
2566 repository to get a package I could use. I would very much like
2567 others to help me maintain the package (or just take over, I do not
2568 mind), but as no-one had volunteered so far, I just uploaded it to
2569 NEW. I hope it will be available in Debian in a few days.
</p
>
2571 <p
>The source is now available from
2572 <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
>
2577 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
2578 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
2579 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
2580 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
2581 <description><p
>The
2582 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
2583 program is a a very nice system to create virtual machine images. It
2584 create a image file, add a partition table, mount it and run
2585 debootstrap in the mounted directory to create a Debian system on a
2586 stick. Yesterday, I decided to try to teach it how to make images for
2587 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
2588 of a plan to simplify the build system for
2589 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
2590 project
</a
>. The FreedomBox project already uses vmdebootstrap for
2591 the virtualbox images, but its current build system made multistrap
2592 based system for Dreamplug images, and it is lacking support for
2593 Raspberry Pi.
</p
>
2595 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
2596 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2597 code and adjusted it to be able to build armel images on my amd64
2598 Debian laptop. I ended up giving vmdebootstrap five new options,
2599 allowing me to replicate the image creation process I use to make
2600 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
2601 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
2602 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
2603 call debootstrap with --foreign and to copy the handler into the
2604 generated chroot before running the second stage. This allow
2605 vmdebootstrap to create armel images on an amd64 host. Next I added
2606 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
2607 fstype
</tt
> to teach it to create a separate /boot/ partition with the
2608 given file system type, allowing me to create an image with a vfat
2609 partition for the /boot/ stuff. I also added a
<tt
>--variant
2610 variant
</tt
> option to allow me to create smaller images without the
2611 Debian base system packages installed. Finally, I added an option
2612 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
2613 as a boot loader. It is not needed on the Raspberry Pi and probably
2614 most other non-x86 architectures. The changes were accepted by the
2615 upstream author of vmdebootstrap yesterday and today, and is now
2617 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
2618 upstream project page
</a
>.
</p
>
2620 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
2621 create a small script (the customize script) to add the non-free
2622 binary blob needed to boot the Raspberry Pi and the APT source
2625 <p
><pre
>
2627 set -e # Exit on first error
2628 rootdir=
"$
1"
2629 cd
"$rootdir
"
2630 cat
&lt;
&lt;EOF
> etc/apt/sources.list
2631 deb http://http.debian.net/debian/ jessie main contrib non-free
2633 # Install non-free binary blob needed to boot Raspberry Pi. This
2634 # install a kernel somewhere too.
2635 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2636 -O $rootdir/usr/bin/rpi-update
2637 chmod a+x $rootdir/usr/bin/rpi-update
2638 mkdir -p $rootdir/lib/modules
2639 touch $rootdir/boot/start.elf
2640 chroot $rootdir rpi-update
2641 </pre
></p
>
2643 <p
>Next, fetch the latest vmdebootstrap script and call it like this
2644 to build the image:
</p
>
2647 sudo ./vmdebootstrap \
2650 --distribution jessie \
2651 --mirror http://http.debian.net/debian \
2660 --root-password raspberry \
2661 --hostname raspberrypi \
2662 --foreign /usr/bin/qemu-arm-static \
2663 --customize `pwd`/customize \
2665 --package git-core \
2666 --package binutils \
2667 --package ca-certificates \
2670 </pre
></p
>
2672 <p
>The list of packages being installed are the ones needed by
2673 rpi-update to make the image bootable on the Raspberry Pi, with the
2674 exception of netbase, which is needed by debootstrap to find
2675 /etc/hosts with the minbase variant. I really wish there was a way to
2676 set up an Raspberry Pi using only packages in the Debian archive, but
2677 that is not possible as far as I know, because it boots from the GPU
2678 using a non-free binary blob.
</p
>
2680 <p
>The build host need debootstrap, kpartx and qemu-user-static and
2681 probably a few others installed. I have not checked the complete
2682 build dependency list.
</p
>
2684 <p
>The resulting image will not use the hardware floating point unit
2685 on the Raspberry PI, because the armel architecture in Debian is not
2686 optimized for that use. So the images created will be a bit slower
2687 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
2692 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
2693 <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>
2694 <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>
2695 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
2696 <description><p
>The last few days I came across a few good causes that should get
2697 wider attention. I recommend signing and donating to each one of
2700 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
2701 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
2702 Women program which is a Google Summer of Code like initiative to get
2703 more women involved in free software. One debian sponsor has offered
2704 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
2705 earmarked
</a
> for this initiative. I donated a few minutes ago, and
2706 hope you will to. :)
</p
>
2708 <p
>And the Electronic Frontier Foundation just announced plans to
2709 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
2710 documentaries about the excessive spying
</a
> on every Internet user that
2711 take place these days, and their need to fund the work. I
've already
2712 donated. Are you next?
</p
>
2714 <p
>For my Norwegian audience, the organisation Studentenes og
2715 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2716 statement under the heading
2717 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
2718 Access
</a
> for those of us asking for more focus on open access in the
2719 Norwegian government. So far
499 signatures. I hope you will sign it
2725 <title>Videos about the Freedombox project - for inspiration and learning
</title>
2726 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
2727 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
2728 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
2729 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
2730 project
</a
> have been going on for a while, and have presented the
2731 vision, ideas and solution several places. Here is a little
2732 collection of videos of talks and presentation of the project.
</p
>
2736 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
2737 2,
5 minute marketing film
</a
> (Youtube)
</li
>
2739 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
2740 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
2742 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
2743 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2744 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
2745 (Youtube)
</li
>
2747 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
2748 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
2750 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
2751 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
2753 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
2754 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2755 York City in
2012</a
> (Youtube)
</li
>
2757 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
2758 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
2759 (Youtube)
</li
>
2761 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
2762 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
2764 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
2765 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
2767 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
2768 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2769 2013</a
> (Youtube)
</li
>
2773 <p
>A larger list is available from
2774 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
2775 Freedombox Wiki
</a
>.
</p
>
2777 <p
>On other news, I am happy to report that Freedombox based on Debian
2778 Jessie is coming along quite well, and soon both Owncloud and using
2779 Tor should be available for testers of the Freedombox solution. :) In
2780 a few weeks I hope everything needed to test it is included in Debian.
2781 The withsqlite package is already in Debian, and the plinth package is
2782 pending in NEW. The third and vital part of that puzzle is the
2783 metapackage/setup framework, which is still pending an upload. Join
2784 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
2785 (#freedombox on irc.debian.org)
</a
> and
2786 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2787 mailing list
</a
> if you want to help make this vision come true.
</p
>
2792 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
2793 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
2794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
2795 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
2796 <description><p
>I was introduced to the
2797 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
2798 in
2010, when Eben Moglen presented his vision about serving the need
2799 of non-technical people to keep their personal information private and
2800 within the legal protection of their own homes. The idea is to give
2801 people back the power over their network and machines, and return
2802 Internet back to its intended peer-to-peer architecture. Instead of
2803 depending on a central service, the Freedombox will give everyone
2804 control over their own basic infrastructure.
</p
>
2806 <p
>I
've intended to join the effort since then, but other tasks have
2807 taken priority. But this summers nasty news about the misuse of trust
2808 and privilege exercised by the
"western
" intelligence gathering
2809 communities increased my eagerness to contribute to a point where I
2810 actually started working on the project a while back.
</p
>
2812 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
2813 Debian initiative
</a
> based on the vision from Eben Moglen, is to
2814 create a simple and cheap Debian based appliance that anyone can hook
2815 up in their home and get access to secure and private services and
2816 communication. The initial deployment platform have been the
2817 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
2818 which is a piece of hardware I do not own. So to be able to test what
2819 the current Freedombox setup look like, I had to come up with a way to install
2820 it on some hardware I do have access to. I have rewritten the
2821 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
2822 image build framework to use .deb packages instead of only copying
2823 setup into the boot images, and thanks to this rewrite I am able to
2824 set up any machine supported by Debian Wheezy as a Freedombox, using
2825 the previously mentioned deb (and a few support debs for packages
2826 missing in Debian).
</p
>
2828 <p
>The current Freedombox setup consist of a set of bootstrapping
2830 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
2831 and a administrative web interface
2832 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
2833 withsqlite), as well as a privacy enhancing proxy based on
2834 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
2835 (freedombox-privoxy). There is also a web/javascript based XMPP
2836 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
2837 trying (unsuccessfully so far) to talk to the XMPP server
2838 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
2839 web interface is pluggable, and the goal is to use it to enable OpenID
2840 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2841 this is really working yet, see
2842 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
2843 project TODO
</a
> for links to GIT repositories. Most of the code is
2844 on github at the moment. The HTTP proxy is operational out of the
2845 box, and the admin web interface can be used to add/remove plinth
2846 users. I
've not been able to do anything else with it so far, but
2847 know there are several branches spread around github and other places
2848 with lots of half baked features.
</p
>
2850 <p
>Anyway, if you want to have a look at the current state, the
2851 following recipes should work to give you a test machine to poke
2854 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
2858 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
2859 <li
>Boot from it, either as CD or USB stick.
</li
>
2860 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
2861 to the Debian installer:
<p
>
2862 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
2864 <li
>Answer the few language/region/password questions and pick disk to
2865 install on.
</li
>
2867 <li
>When the installation is finished and the machine have rebooted a
2868 few times, your Freedombox is ready for testing.
</li
>
2872 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
2876 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
2877 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
2878 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
2880 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
2881 </pre
></li
>
2882 <li
><p
>Run this as root:
</p
>
2884 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2887 apt-get install freedombox-setup
2888 /usr/lib/freedombox/setup
2889 </pre
></li
>
2890 <li
>Reboot into your freshly created Freedombox.
</li
>
2894 <p
>You can test it on other architectures too, but because the
2895 freedombox-privoxy package is binary, it will only work as intended on
2896 the architectures where I have had time to build the binary and put it
2897 in my APT repository. But do not let this stop you. It is only a
2898 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
2900 <p
>Note that by default Freedombox is a DHCP server on the
2901 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
2902 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
2903 disable
</tt
>" as root.
</p
>
2905 <p
>Please let me know if this works for you, or if you have any
2906 problems. We gather on the IRC channel
2907 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
2908 irc.debian.org and the
2909 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
2910 mailing list
</a
>.
</p
>
2912 <p
>Once you get your freedombox operational, you can visit
2913 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
2914 welcome screen (dead end - do not be surprised if you are unable to
2915 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
2916 to look at the rest of plinth. The default user is
'admin
' and the
2917 default password is
'secret
'.
</p
>
2922 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
2923 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
2924 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
2925 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
2926 <description><p
>Earlier, I reported about
2927 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
2928 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
2929 told by IBM that the original disk should be thrown away. And as
2930 there no longer was a problem if I bricked the firmware, I decided
2931 today to try to install Intel firmware to replace the Lenovo firmware
2932 currently on the disk.
</p
>
2934 <p
>I searched the Intel site for firmware, and found
2935 <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
>
2936 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2937 according to the site should contain the latest firmware for SSD
2938 disks. I inserted the broken disk in one of my spare laptops and
2939 booted the ISO from a USB stick. The disk was recognized, but the
2940 program claimed the newest firmware already were installed and refused
2941 to insert any Intel firmware. So no change, and the disk is still
2942 unable to handle write load. :( I guess the only way to get them
2943 working would be if Lenovo releases new firmware. No idea how likely
2944 that is. Anyway, just blogging about this test for completeness. I
2945 got a working Samsung disk, and see no point in spending more time on
2946 the broken disks.
</p
>
2951 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
2952 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
2953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
2954 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
2955 <description><p
>Today I switched to
2956 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
2957 new laptop
</a
>. I
've previously written about the problems I had with
2958 my new Thinkpad X230, which was delivered with an
2959 <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
2960 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
2961 sustained writes. My hardware supplier have been very forthcoming in
2962 trying to find a solution, and after first trying with another
2963 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
2964 disk instead to fix it once and for all. The Samsung disk survived
2965 the installation of Debian with encrypted disks (filling the disk with
2966 random data during installation killed the first two), and I thus
2967 decided to trust it with my data. I have installed it as a Debian Edu
2968 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2969 server at home using Kerberos and LDAP, and will use it as my work
2970 station from now on.
</p
>
2972 <p
>As this is a solid state disk with no moving parts, I believe the
2973 Debian Wheezy default installation need to be tuned a bit to increase
2974 performance and increase life time of the disk. The Linux kernel and
2975 user space applications do not yet adjust automatically to such
2976 environment. To make it easier for my self, I created a draft Debian
2977 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
2978 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
2979 for the ssd-setup package
</a
> is available from collab-maint, and it
2980 is set up to adjust the setup of the machine by just installing the
2981 package. If there is any non-SSD disk in the machine, the package
2982 will refuse to install, as I did not try to write any logic to sort
2983 file systems in SSD and non-SSD file systems.
</p
>
2985 <p
>I consider the package a draft, as I am a bit unsure how to best
2986 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2987 where I set up the machine with one large encrypted partition (in
2988 addition to /boot), put LVM on top of this and set up partitions on
2989 top of this again. See the README file in the package source for the
2990 references I used to pick the settings. At the moment these
2991 parameters are tuned:
</p
>
2995 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
2996 (adding discard to /etc/crypttab)
</li
>
2998 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
2999 this case a cryptsetup partition) by changing issue_discards from
3000 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3002 <li
>Set relatime as a file system option for ext3 and ext4 file
3005 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3006 /etc/fstab.
</li
>
3008 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3010 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3011 cron.daily).
</li
>
3013 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3014 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3018 <p
>During installation, I cancelled the part where the installer fill
3019 the disk with random data, as this would kill the SSD performance for
3020 little gain. My goal with the encrypted file system is to ensure
3021 those stealing my laptop end up with a brick and not a working
3022 computer. I have no hope in keeping the really resourceful people
3023 from getting the data on the disk (see
3024 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3025 Thus I concluded that adding the discard option to crypttab is the
3026 right thing to do.
</p
>
3028 <p
>I considered using the noop I/O scheduler, as several recommended
3029 it for SSD, but others recommended deadline and a benchmark I found
3030 indicated that deadline might be better for interactive use.
</p
>
3032 <p
>I also considered using the
'discard
' file system option for ext3
3033 and ext4, but read that it would give a performance hit ever time a
3034 file is removed, and thought it best to that that slowdown once a day
3035 instead of during my work.
</p
>
3037 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3038 this is already done by Debian Edu.
</p
>
3040 <p
>I have not yet started on the user space tuning. I expect
3041 iceweasel need some tuning, and perhaps other applications too, but
3042 have not yet had time to investigate those parts.
</p
>
3044 <p
>The package should work on Ubuntu too, but I have not yet tested it
3047 <p
>As for the answer to the question in the title of this blog post,
3048 as far as I know, the only solution I know about is to replace the
3049 disk. It might be possible to flash it with Intel firmware instead of
3050 the Lenovo firmware. But I have not tried and did not want to do so
3051 without approval from Lenovo as I wanted to keep the warranty on the
3052 disk until a solution was found and they wanted the broken disks
3058 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3059 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3060 <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>
3061 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3062 <description><p
>A few days ago, I wrote about
3063 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3064 problems I experienced with my new X230 and its SSD disk
</a
>, which
3065 was dying during installation because it is unable to cope with
3066 sustained write. My supplier is in contact with
3067 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3068 replacement disk to try to fix the problem. They decided to send an
3069 identical model, so my hopes for a permanent fix was slim.
</p
>
3071 <p
>Anyway, today I got the replacement disk and tried to install
3072 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3073 same firmware version as the original. This time my hope raised
3074 slightly as the installation progressed, as the original disk used to
3075 die after
4-
7% of the disk was written to, while this time it kept
3076 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3077 died again and I was back on square one. I still do not have a new
3078 laptop with a disk I can trust. I can not live with a disk that might
3079 lock up when I download a new
3080 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3081 other large files. I look forward to hearing from my supplier with
3082 the next proposal from Lenovo.
</p
>
3084 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3085 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3086 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3087 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
3088 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3089 P/N
45N8295, P0C38732.
</p
>
3091 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
3092 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
3093 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3094 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
3095 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3096 P/N
45N8295, P0C38732.
</p
>
3098 <p
>The only difference is in the first number (serial number?), ISN,
3099 SA, date and WNPP values. Mentioning all the details here in case
3100 someone is able to use the information to find a way to identify the
3101 failing disk among working ones (if any such working disk actually
3107 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
3108 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
3109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
3110 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
3111 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
3112 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3113 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
3114 member assosiation NUUG
</a
> and
3115 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
3116 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
3117 Bitraf
</a
>.
</p
>
3119 <p
>It starts
10:
00 and continue until late evening. Everyone is
3120 welcome, and there is no fee to participate. There is on the other
3121 hand limited space, and only room for
30 people. Please put your name
3122 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
3123 wiki page
</a
> if you plan to join us.
</p
>
3128 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
3129 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
3130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
3131 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
3132 <description><p
>Half a year ago, I reported that I had to find a
3133 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
3134 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
3135 time to spend on it, and it took a while to find a model I believe
3136 will do the job, but two days ago the replacement finally arrived. I
3138 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
3139 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3140 a roaming workstation, and it seemed to work flawlessly. But my
3141 second installation with encrypted disk was not as successful. More
3142 on that below.
</p
>
3144 <p
>I had a hard time trying to track down a good laptop, as my most
3145 important requirements (robust and with a good keyboard) are never
3146 listed in the feature list. But I did get good help from the search
3147 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3148 allowed me to limit the list of interesting laptops based on my other
3149 requirements. A bit surprising that SSD disk are not disks according
3150 to that search interface, so I had to drop specifying the number of
3151 disks from my search parameters. I also asked around among friends to
3152 get their impression on keyboards and robustness.
</p
>
3154 <p
>So the new laptop arrived, and it is quite a lot wider than the
3155 X41. I am not quite convinced about the keyboard, as it is
3156 significantly wider than my old keyboard, and I have to stretch my
3157 hand a lot more to reach the edges. But the key response is fairly
3158 good and the individual key shape is fairly easy to handle, so I hope
3159 I will get used to it. My old X40 was starting to fail, and I really
3160 needed a new laptop now. :)
</p
>
3162 <p
>Turning off the touch pad was simple. All it took was a quick
3163 visit to the BIOS during boot it disable it.
</p
>
3165 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
3166 lock up during load. And this happen when installing Debian Wheezy
3167 with encrypted disk, while the disk is being filled with random data.
3168 I also tested to install Ubuntu Raring, and it happen there too if I
3169 reenable the code to fill the disk with random data (it is disabled by
3170 default in Ubuntu). And the bug with is already known. It was
3171 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
3172 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
3173 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3174 kernel developers as
3175 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
3176 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
3177 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3178 Lenovo forums, both for
3179 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
3180 2012-
11-
10</a
> and for
3181 <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
3182 03-
20-
2013</a
>. The problem do not only affect installation. The
3183 reports state that the disk lock up during use if many writes are done
3184 on the disk, so it is much no use to work around the installation
3185 problem and end up with a computer that can lock up at any moment.
3187 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
3188 available
</a
> that will lock up the hard drive after running a few
3189 minutes by writing to a file.
</p
>
3191 <p
>I
've contacted my supplier and asked how to handle this, and after
3192 contacting PCHELP Norway (request
01D1FDP) which handle support
3193 requests for Lenovo, his first suggestion was to upgrade the disk
3194 firmware. Unfortunately there is no newer firmware available from
3195 Lenovo, as my disk already have the most recent one (version LF1i). I
3196 hope to hear more from him today and hope the problem can be
3202 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
3203 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
3204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
3205 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3206 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3207 trusty old Thinkpad X41. Unfortunately I did not have much time to
3208 spend on it, but today the replacement finally arrived. I ended up
3209 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3210 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3211 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3212 this, it is installing what I hope will be a more final installation,
3213 with a encrypted hard drive to ensure any dope head stealing it end up
3214 with an expencive door stop.
</p
>
3216 <p
>I had a hard time trying to track down a good laptop, as my most
3217 important requirements (robust and with a good keyboard) are never
3218 listed in the feature list. But I did get good help from the search
3219 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3220 allowed me to limit the list of interesting laptops based on my other
3221 requirements. A bit surprising that SSD disk are not disks, so I had
3222 to drop number of disks from my search parameters.
</p
>
3224 <p
>I am not quite convinced about the keyboard, as it is significantly
3225 wider than my old keyboard, and I have to stretch my hand a lot more
3226 to reach the edges. But the key response is fairly good and the
3227 individual key shape is fairly easy to handle, so I hope I will get
3228 used to it. My old X40 was starting to fail, and I really needed a
3229 new laptop now. :)
</p
>
3231 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3236 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3237 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3239 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3240 <description><p
>It annoys me when the computer fail to do automatically what it is
3241 perfectly capable of, and I have to do it manually to get things
3242 working. One such task is to find out what firmware packages are
3243 needed to get the hardware on my computer working. Most often this
3244 affect the wifi card, but some times it even affect the RAID
3245 controller or the ethernet card. Today I pushed version
0.4 of the
3246 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3247 including a new script isenkram-autoinstall-firmware handling the
3248 process of asking all the loaded kernel modules what firmware files
3249 they want, find debian packages providing these files and install the
3250 debian packages. Here is a test run on my laptop:
</p
>
3252 <p
><pre
>
3253 # isenkram-autoinstall-firmware
3254 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3255 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3256 info: locating packages with the requested firmware files
3257 info: Updating APT sources after adding non-free APT source
3258 info: trying to install firmware-ipw2x00
3261 Preconfiguring packages ...
3262 Selecting previously deselected package firmware-ipw2x00.
3263 (Reading database ...
259727 files and directories currently installed.)
3264 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3265 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3267 </pre
></p
>
3269 <p
>When all the requested firmware is present, a simple message is
3270 printed instead:
</p
>
3272 <p
><pre
>
3273 # isenkram-autoinstall-firmware
3274 info: did not find any firmware files requested by loaded kernel modules. exiting
3276 </pre
></p
>
3278 <p
>It could use some polish, but it is already working well and saving
3279 me some time when setting up new machines. :)
</p
>
3281 <p
>So, how does it work? It look at the set of currently loaded
3282 kernel modules, and look up each one of them using modinfo, to find
3283 the firmware files listed in the module meta-information. Next, it
3284 download the Contents file from a nearby APT mirror, and search for
3285 the firmware files in this file to locate the package with the
3286 requested firmware file. If the package is in the non-free section, a
3287 non-free APT source is added and the package is installed using
3288 <tt
>apt-get install
</tt
>. The end result is a slightly better working
3291 <p
>I hope someone find time to implement a more polished version of
3292 this script as part of the hw-detect debian-installer module, to
3293 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
3294 #
655507</a
>. There really is no need to insert USB sticks with
3295 firmware during a PXE install when the packages already are available
3296 from the nearby Debian mirror.
</p
>
3301 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
3302 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
3303 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
3304 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
3305 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3306 the screen just turn black when Linux boot, either during installation
3307 or on first boot from the hard disk. I
've seen it once in a while the
3308 last few years, but only recently understood the cause. I
've seen it
3309 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3310 The reason seem to be in the wiring of some laptops. The system to
3311 control the screen background light is inverted, so when Linux try to
3312 turn the brightness fully on, it end up turning it off instead. I do
3313 not know which Linux drivers are affected, but this post is about the
3314 i915 driver used by the
3315 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3316 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
3318 <p
>The problem can be worked around two ways. Either by adding
3319 i915.invert_brightness=
1 as a kernel option, or by adding a file in
3320 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
3321 option when it load the i915 kernel module. On Debian and Ubuntu, it
3322 can be done by running these commands as root:
</p
>
3325 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
3326 update-initramfs -u -k all
3329 <p
>Since March
2012 there is
3330 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
3331 mechanism in the Linux kernel
</a
> to tell the i915 driver which
3332 hardware have this problem, and get the driver to invert the
3333 brightness setting automatically. To use it, one need to add a row in
3334 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
3335 intel_quirks array
</a
> in the driver source
3336 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
3337 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
3338 number (vendor number
8086 is assumed) and subdevice vendor and device
3341 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
3342 -vvnn
</tt
> for the video card in question:
</p
>
3344 <p
><pre
>
3345 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
3346 3rd Gen Core processor Graphics Controller [
8086:
0156] \
3347 (rev
09) (prog-if
00 [VGA controller])
3348 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
3349 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3350 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3351 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
3352 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
3354 Interrupt: pin A routed to IRQ
42
3355 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
3356 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
3357 Region
4: I/O ports at
4000 [size=
64]
3358 Expansion ROM at
<unassigned
> [disabled]
3359 Capabilities:
<access denied
>
3360 Kernel driver in use: i915
3361 </pre
></p
>
3363 <p
>The resulting intel_quirks entry would then look like this:
</p
>
3365 <p
><pre
>
3366 struct intel_quirk intel_quirks[] = {
3368 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3369 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
3372 </pre
></p
>
3374 <p
>According to the kernel module instructions (as seen using
3375 <tt
>modinfo i915
</tt
>), information about hardware needing the
3376 invert_brightness flag should be sent to the
3377 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
3378 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
3379 developers. But my email about the laptop sent
2013-
06-
03 have not
3381 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
3382 web archive for the mailing list
</a
>, so I suspect they do not accept
3383 emails from non-subscribers. Because of this, I sent my patch also to
3384 the Debian bug tracking system instead as
3385 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
3386 sure the patch is not lost.
</p
>
3388 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
3389 with this problem working properly with Linux. If you use Gnome, your
3390 worries should be over at this point. But if you use KDE, there is
3391 something in KDE ignoring the invert_brightness setting and turning on
3392 the screen during login. I
've reported it to Debian as
3393 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
3394 have no idea yet how to figure out exactly what subsystem is doing
3395 this. Perhaps you can help? Perhaps you know what the Gnome
3396 developers did to handle this, and this can give a clue to the KDE
3397 developers? Or you know where in KDE the screen brightness is changed
3398 during login? If so, please update the BTS report (or get in touch if
3399 you do not know how to update BTS).
</p
>
3401 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
3402 acpi_backlight=vendor, to disable ACPI backlight support completely,
3403 as the ACPI information on the machine is trash and it is better to
3404 leave it to the intel video driver to control the screen
3405 backlight.
</p
>
3410 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
3411 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
3412 <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>
3413 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
3414 <description><p
>Two days ago, I asked
3415 <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
3416 I could install Linux on a Packard Bell EasyNote LV computer
3417 preinstalled with Windows
8</a
>. I found a solution, but am horrified
3418 with the obstacles put in the way of Linux users on a laptop with UEFI
3419 and Windows
8.
</p
>
3421 <p
>I never found out if the cause of my problems were the use of UEFI
3422 secure booting or fast boot. I suspect fast boot was the problem,
3423 causing the firmware to boot directly from HD without considering any
3424 key presses and alternative devices, but do not know UEFI settings
3425 enough to tell.
</p
>
3427 <p
>There is no way to install Linux on the machine in question without
3428 opening the box and disconnecting the hard drive! This is as far as I
3429 can tell, the only way to get access to the firmware setup menu
3430 without accepting the Windows
8 license agreement. I am told (and
3431 found description on how to) that it is possible to configure the
3432 firmware setup once booted into Windows
8. But as I believe the terms
3433 of that agreement are completely unacceptable, accepting the license
3434 was never an alternative. I do not enter agreements I do not intend
3435 to follow.
</p
>
3437 <p
>I feared I had to return the laptops and ask for a refund, and
3438 waste many hours on this, but luckily there was a way to get it to
3439 work. But I would not recommend it to anyone planning to run Linux on
3440 it, and I have become sceptical to Windows
8 certified laptops. Is
3441 this the way Linux will be forced out of the market place, by making
3442 it close to impossible for
"normal
" users to install Linux without
3443 accepting the Microsoft Windows license terms? Or at least not
3444 without risking to loose the warranty?
</p
>
3446 <p
>I
've updated the
3447 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
3448 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
3449 do not have to struggle as much as I did to get Linux into the
3452 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3453 Michael Tokarev and others for feedback and ideas.
</p
>
3458 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
3459 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
3460 <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>
3461 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
3462 <description><p
>I
've run into quite a problem the last few days. I bought three
3463 new laptops for my parents and a few others. I bought Packard Bell
3464 Easynote LV to run Kubuntu on and use as their home computer. But I
3465 am completely unable to figure out how to install Linux on it. The
3466 computer is preinstalled with Windows
8, and I suspect it uses UEFI
3467 instead of a BIOS to boot.
</p
>
3469 <p
>The problem is that I am unable to get it to PXE boot, and unable
3470 to get it to boot the Linux installer from my USB stick. I have yet
3471 to try the DVD install, and still hope it will work. when I turn on
3472 the computer, there is no information on what buttons to press to get
3473 the normal boot menu. I expect to get some boot menu to select PXE or
3474 USB stick booting. When booting, it first ask for the language to
3475 use, then for some regional settings, and finally if I will accept the
3476 Windows
8 terms of use. As these terms are completely unacceptable to
3477 me, I have no other choice but to turn off the computer and try again
3478 to get it to boot the Linux installer.
</p
>
3480 <p
>I have gathered my findings so far on a Linlap page about the
3481 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3482 EasyNote LV
</a
> model. If you have any idea how to get Linux
3483 installed on this machine, please get in touch or update that wiki
3484 page. If I can
't find a way to install Linux, I will have to return
3485 the laptop to the seller and find another machine for my parents.
</p
>
3487 <p
>I wonder, is this the way Linux will be forced out of the market
3488 using UEFI and
"secure boot
" by making it impossible to install Linux
3489 on new Laptops?
</p
>
3494 <title>How to transform a Debian based system to a Debian Edu installation
</title>
3495 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
3496 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
3497 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
3498 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
3499 an operating system based on Debian intended for use in schools. It
3500 contain a turn-key solution for the computer network provided to
3501 pupils in the primary schools. It provide both the central server,
3502 network boot servers and desktop environments with heaps of
3503 educational software. The project was founded almost
12 years ago,
3504 2001-
07-
02. If you want to support the project, which is in need for
3505 cash to fund developer gatherings and other project related activity,
3506 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
3507 donate some money
</a
>.
3509 <p
>A topic that come up again and again on the Debian Edu mailing
3510 lists and elsewhere, is the question on how to transform a Debian or
3511 Ubuntu installation into a Debian Edu installation. It isn
't very
3512 hard, and last week I wrote a script to replicate the steps done by
3513 the Debian Edu installer.
</p
>
3515 <p
>The script,
3516 <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/
>
3517 in the debian-edu-config package, will go through these six steps and
3518 transform an existing Debian Wheezy or Ubuntu (untested) installation
3519 into a Debian Edu Workstation:
</p
>
3523 <li
>Add skolelinux related APT sources.
</li
>
3524 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
3525 <li
>Install debian-edu-install to load preseeding values and pull in
3526 our configuration.
</li
>
3527 <li
>Preseed debconf database with profile setup in
3528 /etc/debian-edu/config, and run tasksel to install packages
3529 according to the profile specified in the config above,
3530 overriding some of the Debian automation machinery.
</li
>
3531 <li
>Run debian-edu-cfengine-D installation to configure everything
3532 that could not be done using preseeding.
</li
>
3533 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
3537 <p
>There are some steps in the Debian Edu installation that can not be
3538 replicated like this. Disk partitioning and LVM setup, for example.
3539 So this script just assume there is enough disk space to install all
3540 the needed packages.
</p
>
3542 <p
>The script was created to help a Debian Edu student working on
3543 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
3544 Debian Edu client, and using it he can take the existing
3545 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
3546 transform it into a fully functioning Debian Edu Workstation (or
3547 Roaming Workstation, or whatever :).
</p
>
3549 <p
>The default setting in the script is to create a KDE Workstation.
3550 If a LXDE based Roaming workstation is wanted instead, modify the
3551 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
3553 <p
><pre
>
3554 PROFILE=
"Roaming-Workstation
"
3555 DESKTOP=
"lxde
"
3556 </pre
></p
>
3558 <p
>The script could even become useful to set up Debian Edu servers in
3559 the cloud, by starting with a virtual Debian installation at some
3560 virtual hosting service and setting up all the services on first
3566 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
3567 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
3568 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
3569 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
3570 <description><P
>In January,
3571 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
3572 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
3573 channel #debian-lego
</a
>, for those of us in the Debian and Linux
3574 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
3575 marvellous construction system from Denmark. We also created
3576 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
3577 a place to take notes and write down our plans and hopes. And several
3578 people showed up to help. I was very happy to see the effect of my
3579 call. Since the small start, we have a debtags tag
3580 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
3581 tag for LEGO related packages, and now count
10 packages related to
3582 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
3584 <p
><table
>
3585 <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
>
3586 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
3587 <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
>
3588 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
3589 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
3590 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
3591 <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
>
3592 <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
>
3593 <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
>
3594 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
3595 </table
></p
>
3597 <p
>Some of these are available in Wheezy, and all but one are
3598 currently available in Jessie/testing. leocad is so far only
3599 available in experimental.
</p
>
3601 <p
>If you care about LEGO in Debian, please join us on IRC and help
3602 adding the rest of the great free software tools available on Linux
3603 for LEGO designers.
</p
>
3608 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
3609 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
3610 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
3611 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
3612 <description><p
>When I woke up this morning, I was very happy to see that the
3613 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
3614 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
3615 Debian release, and I expect to move my machines at home over to it fairly
3618 <p
>The new debian release contain heaps of new stuff, and one program
3619 in particular make me very happy to see included. The
3620 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
3621 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
3622 included for the first time. Alongside similar programs like
3623 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
3624 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
3625 it allow for visual programming where syntax errors can not happen,
3626 and a friendly programming environment for learning to control the
3627 computer. Scratch will also be included in the next release of Debian
3630 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
3631 Edu/Skolelinux release too. The
3632 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
3633 alpha release
</a
> went out last week, and the next should soon
3639 <title>Isenkram
0.2 finally in the Debian archive
</title>
3640 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
3641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
3642 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
3643 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
3644 package
</a
> finally made it into the archive, after lingering in NEW
3645 for many months. I uploaded it to the Debian experimental suite
3646 2013-
01-
27, and today it was accepted into the archive.
</p
>
3648 <p
>Isenkram is a system for suggesting to users what packages to
3649 install to work with a pluggable hardware device. The suggestion pop
3650 up when the device is plugged in. For example if a Lego Mindstorm NXT
3651 is inserted, it will suggest to install the program needed to program
3652 the NXT controller. Give it a go, and report bugs and suggestions to
3658 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
3659 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
3660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
3661 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
3662 <description><p
>My
3663 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
3664 bitcoin related blog post
</a
> mentioned that the new
3665 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
3666 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3667 2013-
01-
19, and have been available in unstable since then. It was
3668 automatically copied to Ubuntu, and is available in their Raring
3669 version too.
</p
>
3671 <p
>But there is a strange problem with the build that block this new
3672 version from being available on the i386 and kfreebsd-i386
3673 architectures. For some strange reason, the autobuilders in Debian
3674 for these architectures fail to run the test suite on these
3675 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
3676 We are so far unable to reproduce it when building it manually, and
3677 no-one have been able to propose a fix. If you got an idea what is
3678 failing, please let us know via the BTS.
</p
>
3680 <p
>One feature that is annoying me with of the bitcoin client, because
3681 I often run low on disk space, is the fact that the client will exit
3682 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
3683 #
696715</a
>). So make sure you have enough disk space when you run
3686 <p
>As usual, if you use bitcoin and want to show your support of my
3687 activities, please send Bitcoin donations to my address
3688 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3693 <title>Welcome to the world, Isenkram!
</title>
3694 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
3695 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
3696 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
3697 <description><p
>Yesterday, I
3698 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
3699 for testers
</a
> for my prototype for making Debian better at handling
3700 pluggable hardware devices, which I
3701 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
3702 out to create
</a
> earlier this month. Several valuable testers showed
3703 up, and caused me to really want to to open up the development to more
3704 people. But before I did this, I want to come up with a sensible name
3705 for this project. Today I finally decided on a new name, and I have
3706 renamed the project from hw-support-handler to this new name. In the
3707 process, I moved the source to git and made it available as a
3708 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
3709 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
3710 To fetch and build the latest version of the source, use
</p
>
3713 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3714 cd isenkram
&& git-buildpackage -us -uc
3717 <p
>I have not yet adjusted all files to use the new name yet. If you
3718 want to hack on the source or improve the package, please go ahead.
3719 But please talk to me first on IRC or via email before you do major
3720 changes, to make sure we do not step on each others toes. :)
</p
>
3722 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
3723 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3724 stuff, in other words. I
've been told it is the Norwegian variant of
3725 the German word eisenkram, for those that are familiar with that
3728 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
3729 instructions, to avoid confusing people with an error from the signing
3732 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
3733 clone argument to avoid the need for authentication.
</p
>
3738 <title>First prototype ready making hardware easier to use in Debian
</title>
3739 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
3740 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
3741 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
3742 <description><p
>Early this month I set out to try to
3743 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
3744 the Debian support for pluggable hardware devices
</a
>. Now my
3745 prototype is working, and it is ready for a larger audience. To test
3747 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
3748 from the Debian Edu subversion repository
</a
>, build and install the
3749 package. You might have to log out and in again activate the
3750 autostart script.
</p
>
3752 <p
>The design is simple:
</p
>
3756 <li
>Add desktop entry in /usr/share/autostart/ causing a program
3757 hw-support-handlerd to start when the user log in.
</li
>
3759 <li
>This program listen for kernel events about new hardware (directly
3760 from the kernel like udev does), not using HAL dbus events as I
3761 initially did.
</li
>
3763 <li
>When new hardware is inserted, look up the hardware modalias in
3764 the APT database, a database
3765 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
3766 via HTTP
</a
> and a database available as part of the package.
</li
>
3768 <li
>If a package is mapped to the hardware in question, the package
3769 isn
't installed yet and this is the first time the hardware was
3770 plugged in, show a desktop notification suggesting to install the
3771 package or packages.
</li
>
3773 <li
>If the user click on the
'install package now
' button, ask
3774 aptdaemon via the PackageKit API to install the requrired package.
</li
>
3776 <li
>aptdaemon ask for root password or sudo password, and install the
3777 package while showing progress information in a window.
</li
>
3781 <p
>I still need to come up with a better name for the system. Here
3782 are some screen shots showing the prototype in action. First the
3783 notification, then the password request, and finally the request to
3784 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
3786 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
3787 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
3788 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
3789 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
3790 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
3792 <p
>The prototype still need to be improved with longer timeouts, but
3793 is already useful. The database of hardware to package mappings also
3794 need more work. It is currently compatible with the Ubuntu way of
3795 storing such information in the package control file, but could be
3796 changed to use other formats instead or in addition to the current
3797 method. I
've dropped the use of discover for this mapping, as the
3798 modalias approach is more flexible and easier to use on Linux as long
3799 as the Linux kernel expose its modalias strings directly.
</p
>
3801 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
3802 here is the command required to check out and build the source: Use
3803 '<tt
>svn checkout
3804 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3805 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
3806 devscripts package.
</p
>
3808 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
3809 renamed to Isenkram and the source moved from the Debian Edu
3810 subversion repository to a Debian collab-maint git repository. See
3811 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
3812 instructions
</a
> for details.
</p
>
3817 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
3818 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
3819 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
3820 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
3821 <description><p
>This Christmas my trusty old laptop died. It died quietly and
3822 suddenly in bed. With a quiet whimper, it went completely quiet and
3823 black. The power button was no longer able to turn it on. It was a
3824 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3825 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3826 Compaq I had before that. Now I need to find a replacement. To keep
3827 going during Christmas, I moved the one year old SSD disk to my old
3828 X40 where it fitted (only one I had left that could use it), but it is
3829 not a durable solution.
3831 <p
>My laptop needs are fairly modest. This is my wishlist from when I
3832 got a new one more than
10 years ago. It still holds true.:)
</p
>
3836 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
3837 than A4).
</li
>
3838 <li
>Robust, it will be in my backpack every day.
</li
>
3839 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
3840 <li
>Long battery life time. Preferable a week.
</li
>
3841 <li
>Internal WIFI network card.
</li
>
3842 <li
>Internal Twisted Pair network card.
</li
>
3843 <li
>Some USB slots (
2-
3 is plenty)
</li
>
3844 <li
>Good keyboard - similar to the Thinkpad.
</li
>
3845 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
3847 <li
>Hardware supported by Debian Stable, ie the default kernel and
3848 X.org packages.
</li
>
3849 <li
>Quiet, preferably fan free (or at least not using the fan most of
3854 <p
>You will notice that there are no RAM and CPU requirements in the
3855 list. The reason is simply that the specifications on laptops the
3856 last
10-
15 years have been sufficient for my needs, and I have to look
3857 at other features to choose my laptop. But are there still made as
3858 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3859 robust, and Thinkpads seem to be heading in the wrong direction since
3860 Lenovo took over. But I
've been told that X220 and X1 Carbon might
3861 still be useful.
</p
>
3863 <p
>Perhaps I should rethink my needs, and look for a pad with an
3864 external keyboard? I
'll have to check the
3865 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
3866 well-supported laptops, or perhaps just buy one preinstalled from one
3867 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
3868 Pre-loaded site
</a
>.
</p
>
3873 <title>How to find a browser plugin supporting a given MIME type
</title>
3874 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
3875 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
3876 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
3877 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
3878 install to get support for a given MIME type. Thanks to
3879 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
3880 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
3881 Unfortunately, not very many packages provide the needed meta
3882 information, Anyway, here is a small script to look up all browser
3883 plugin packages announcing ther MIME support using this specification:
</p
>
3889 def pkgs_handling_mimetype(mimetype):
3894 version = pkg.candidate
3896 version = pkg.installed
3899 record = version.record
3900 if not record.has_key(
'Npp-MimeType
'):
3902 mime_types = record[
'Npp-MimeType
'].split(
',
')
3903 for t in mime_types:
3904 t = t.rstrip().strip()
3906 thepkgs.append(pkg.name)
3908 mimetype =
"audio/ogg
"
3909 if
1 < len(sys.argv):
3910 mimetype = sys.argv[
1]
3911 print
"Browser plugin packages supporting %s:
" % mimetype
3912 for pkg in pkgs_handling_mimetype(mimetype):
3913 print
" %s
" %pkg
3916 <p
>It can be used like this to look up a given MIME type:
</p
>
3919 % ./apt-find-browserplug-for-mimetype
3920 Browser plugin packages supporting audio/ogg:
3922 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3923 Browser plugin packages supporting application/x-shockwave-flash:
3924 browser-plugin-gnash
3928 <p
>In Ubuntu this mechanism is combined with support in the browser
3929 itself to query for plugins and propose to install the needed
3930 packages. It would be great if Debian supported such feature too. Is
3931 anyone working on adding it?
</p
>
3933 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
3934 request for icweasel support for this feature is
3935 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
3936 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
3937 of manpower and wish for a different design is the reason thus feature
3938 is not yet in iceweasel from Debian.
</p
>
3943 <title>What is the most supported MIME type in Debian?
</title>
3944 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
3945 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
3946 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
3947 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
3948 proposal to add AppStream information to the Debian archive
</a
>, is a
3949 proposal to make it possible for a Desktop application to propose to
3950 the user some package to install to gain support for a given MIME
3951 type, font, library etc. that is currently missing. With such
3952 mechanism in place, it would be possible for the desktop to
3953 automatically propose and install leocad if some LDraw file is
3954 downloaded by the browser.
</p
>
3956 <p
>To get some idea about the current content of the archive, I decided
3957 to write a simple program to extract all .desktop files from the
3958 Debian archive and look up the claimed MIME support there. The result
3960 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
3961 site
</a
>. Using the collected information, it become possible to
3962 answer the question in the title. Here are the
20 most supported MIME
3963 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3964 The complete list is available from the link above.
</p
>
3966 <p
><strong
>Debian Stable:
</strong
></p
>
3970 ----- -----------------------
3986 18 application/x-ogg
3993 <p
><strong
>Debian Testing:
</strong
></p
>
3997 ----- -----------------------
4013 18 application/x-ogg
4020 <p
><strong
>Debian Unstable:
</strong
></p
>
4024 ----- -----------------------
4041 18 application/x-ogg
4047 <p
>I am told that PackageKit can provide an API to access the kind of
4048 information mentioned in DEP-
11. I have not yet had time to look at
4049 it, but hope the PackageKit people in Debian are on top of these
4052 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4053 discovering a typo in my script.
</p
>
4058 <title>Using modalias info to find packages handling my hardware
</title>
4059 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4060 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4061 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4062 <description><p
>Yesterday, I wrote about the
4063 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4064 values provided by the Linux kernel
</a
> following my hope for
4065 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4066 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4067 modalias values attached to package names can be used to map packages
4068 to hardware. This allow the system to look up and suggest relevant
4069 packages when I plug in some new hardware into my machine, and replace
4070 discover and discover-data as the database used to map hardware to
4073 <p
>I create a modaliases file with entries like the following,
4074 containing package name, kernel module name (if relevant, otherwise
4075 the package name) and globs matching the relevant hardware
4078 <p
><blockquote
>
4079 Package: package-name
4080 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4081 </blockquote
></p
>
4083 <p
>It is fairly trivial to write code to find the relevant packages
4084 for a given modalias value using this file.
</p
>
4086 <p
>An entry like this would suggest the video and picture application
4087 cheese for many USB web cameras (interface bus class
0E01):
</p
>
4089 <p
><blockquote
>
4091 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
4092 </blockquote
></p
>
4094 <p
>An entry like this would suggest the pcmciautils package when a
4095 CardBus bridge (bus class
0607) PCI device is present:
</p
>
4097 <p
><blockquote
>
4098 Package: pcmciautils
4099 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4100 </blockquote
></p
>
4102 <p
>An entry like this would suggest the package colorhug-client when
4103 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
4105 <p
><blockquote
>
4106 Package: colorhug-client
4107 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
4108 </blockquote
></p
>
4110 <p
>I believe the format is compatible with the format of the Packages
4111 file in the Debian archive. Ubuntu already uses their Packages file
4112 to store their mappings from packages to hardware.
</p
>
4114 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
4115 announce the hardware it support in a way my prototype understand.
4116 This allow those publishing packages in an APT source outside the
4117 Debian archive as well as those backporting packages to make sure the
4118 hardware mapping are included in the package meta information. I
've
4119 tested such header in the pymissile package, and its modalias mapping
4120 is working as it should with my prototype. It even made it to Ubuntu
4123 <p
>To test if it was possible to look up supported hardware using only
4124 the shell tools available in the Debian installer, I wrote a shell
4125 implementation of the lookup code. The idea is to create files for
4126 each modalias and let the shell do the matching. Please check out and
4128 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
4129 shell script. It run without any extra dependencies and fetch the
4130 hardware mappings from the Debian archive and the subversion
4131 repository where I currently work on my prototype.
</p
>
4133 <p
>When I use it on a machine with a yubikey inserted, it suggest to
4134 install yubikey-personalization:
</p
>
4136 <p
><blockquote
>
4137 % ./hw-support-lookup
4138 <br
>yubikey-personalization
4140 </blockquote
></p
>
4142 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4143 propose to install the pcmciautils package:
</p
>
4145 <p
><blockquote
>
4146 % ./hw-support-lookup
4147 <br
>pcmciautils
4149 </blockquote
></p
>
4151 <p
>If you know of any hardware-package mapping that should be added to
4152 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
4153 database
</a
>, please tell me about it.
</p
>
4155 <p
>It could be possible to generate several of the mappings between
4156 packages and hardware. One source would be to look at packages with
4157 kernel modules, ie packages with *.ko files in /lib/modules/, and
4158 extract their modalias information. Another would be to look at
4159 packages with udev rules, ie packages with files in
4160 /lib/udev/rules.d/, and extract their vendor/model information to
4161 generate a modalias matching rule. I have not tested any of these to
4162 see if it work.
</p
>
4164 <p
>If you want to help implementing a system to let us propose what
4165 packages to install when new hardware is plugged into a Debian
4166 machine, please send me an email or talk to me on
4167 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4172 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
4173 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
4174 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
4175 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
4176 <description><p
>While looking into how to look up Debian packages based on hardware
4177 information, to find the packages that support a given piece of
4178 hardware, I refreshed my memory regarding modalias values, and decided
4179 to document the details. Here are my findings so far, also available
4181 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4182 Debian Edu subversion repository
</a
>:
4184 <p
><strong
>Modalias decoded
</strong
></p
>
4186 <p
>This document try to explain what the different types of modalias
4187 values stands for. It is in part based on information from
4188 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
4189 &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;,
4190 &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
4191 &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;.
4193 <p
>The modalias entries for a given Linux machine can be found using
4194 this shell script:
</p
>
4197 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
4200 <p
>The supported modalias globs for a given kernel module can be found
4201 using modinfo:
</p
>
4204 % /sbin/modinfo psmouse | grep alias:
4205 alias: serio:ty05pr*id*ex*
4206 alias: serio:ty01pr*id*ex*
4210 <p
><strong
>PCI subtype
</strong
></p
>
4212 <p
>A typical PCI entry can look like this. This is an Intel Host
4213 Bridge memory controller:
</p
>
4215 <p
><blockquote
>
4216 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4217 </blockquote
></p
>
4219 <p
>This represent these values:
</p
>
4224 sv
00001028 (subvendor)
4225 sd
000001AD (subdevice)
4227 sc
00 (bus subclass)
4231 <p
>The vendor/device values are the same values outputted from
'lspci
4232 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4233 0600. The
0600 class is a host bridge. Other useful bus values are
4234 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4236 <p
>Not sure how to figure out the interface value, nor what it
4239 <p
><strong
>USB subtype
</strong
></p
>
4241 <p
>Some typical USB entries can look like this. This is an internal
4242 USB hub in a laptop:
</p
>
4244 <p
><blockquote
>
4245 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4246 </blockquote
></p
>
4248 <p
>Here is the values included in this alias:
</p
>
4251 v
1D6B (device vendor)
4252 p
0001 (device product)
4254 dc
09 (device class)
4255 dsc
00 (device subclass)
4256 dp
00 (device protocol)
4257 ic
09 (interface class)
4258 isc
00 (interface subclass)
4259 ip
00 (interface protocol)
4262 <p
>The
0900 device class/subclass means hub. Some times the relevant
4263 class is in the interface class section. For a simple USB web camera,
4264 these alias entries show up:
</p
>
4266 <p
><blockquote
>
4267 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4268 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4269 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4270 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4271 </blockquote
></p
>
4273 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4274 camera),
0101 is audio control device and
0102 is audio streaming (aka
4275 microphone). Thus this is a camera with microphone included.
</p
>
4277 <p
><strong
>ACPI subtype
</strong
></p
>
4279 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
4280 receiver in a Thinkpad X40:
</p
>
4282 <p
><blockquote
>
4283 acpi:IBM0071:PNP0511:
4284 </blockquote
></p
>
4286 <p
>The values between the colons are IDs.
</p
>
4288 <p
><strong
>DMI subtype
</strong
></p
>
4290 <p
>The DMI table contain lots of information about the computer case
4291 and model. This is an entry for a IBM Thinkpad X40, fetched from
4292 /sys/devices/virtual/dmi/id/modalias:
</p
>
4294 <p
><blockquote
>
4295 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4296 </blockquote
></p
>
4298 <p
>The values present are
</p
>
4301 bvn IBM (BIOS vendor)
4302 bvr
1UETB
6WW(
1.66) (BIOS version)
4303 bd
06/
15/
2005 (BIOS date)
4304 svn IBM (system vendor)
4305 pn
2371H4G (product name)
4306 pvr ThinkPadX40 (product version)
4307 rvn IBM (board vendor)
4308 rn
2371H4G (board name)
4309 rvr NotAvailable (board version)
4310 cvn IBM (chassis vendor)
4311 ct
10 (chassis type)
4312 cvr NotAvailable (chassis version)
4315 <p
>The chassis type
10 is Notebook. Other interesting values can be
4316 found in the dmidecode source:
</p
>
4320 4 Low Profile Desktop
4333 17 Main Server Chassis
4334 18 Expansion Chassis
4336 20 Bus Expansion Chassis
4337 21 Peripheral Chassis
4339 23 Rack Mount Chassis
4348 <p
>The chassis type values are not always accurately set in the DMI
4349 table. For example my home server is a tower, but the DMI modalias
4350 claim it is a desktop.
</p
>
4352 <p
><strong
>SerIO subtype
</strong
></p
>
4354 <p
>This type is used for PS/
2 mouse plugs. One example is from my
4355 test machine:
</p
>
4357 <p
><blockquote
>
4358 serio:ty01pr00id00ex00
4359 </blockquote
></p
>
4361 <p
>The values present are
</p
>
4370 <p
>This type is supported by the psmouse driver. I am not sure what
4371 the valid values are.
</p
>
4373 <p
><strong
>Other subtypes
</strong
></p
>
4375 <p
>There are heaps of other modalias subtypes according to
4376 file2alias.c. There is the rest of the list from that source: amba,
4377 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4378 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4379 vmbus, x86cpu and zorro. I did not spend time documenting all of
4380 these, as they do not seem relevant for my intended use with mapping
4381 hardware to packages when new stuff is inserted during run time.
</p
>
4383 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
4385 <p
>To check which kernel modules provide support for a given modalias,
4386 one can use the following shell script:
</p
>
4389 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
4390 echo
"$id
" ; \
4391 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
4395 <p
>The output can look like this (only the first few entries as the
4396 list is very long on my test machine):
</p
>
4400 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
4402 FATAL: Module acpi:device: not found.
4404 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
4405 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
4406 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
4407 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4408 acpi:IBM0071:PNP0511:
4409 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
4410 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
4411 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
4415 <p
>If you want to help implementing a system to let us propose what
4416 packages to install when new hardware is plugged into a Debian
4417 machine, please send me an email or talk to me on
4418 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4420 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
4421 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
4422 in /sys/ with space in them.
</p
>
4427 <title>Moved the pymissile Debian packaging to collab-maint
</title>
4428 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
4429 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
4430 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
4431 <description><p
>As part of my investigation on how to improve the support in Debian
4432 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4433 Launcher and updated the Debian package
4434 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
4435 sure udev will fix the device permissions when it is plugged in. I
4436 also added a
"Modaliases
" header to test it in the Debian archive and
4437 hopefully make the package be proposed by jockey in Ubuntu when a user
4438 plug in his rocket launcher. In the process I moved the source to a
4439 git repository under collab-maint, to make it easier for any DD to
4440 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
4441 is not very active, but the software still work for me even after five
4442 years of relative silence. The new git repository is not listed in
4443 the uploaded package yet, because I want to test the other changes a
4444 bit more before I upload the new version. If you want to check out
4445 the new version with a .desktop file included, visit the
4446 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
4447 view
</a
> or use
"<tt
>git clone
4448 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
4453 <title>Lets make hardware dongles easier to use in Debian
</title>
4454 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
4455 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
4456 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
4457 <description><p
>One thing that annoys me with Debian and Linux distributions in
4458 general, is that there is a great package management system with the
4459 ability to automatically install software packages by downloading them
4460 from the distribution mirrors, but no way to get it to automatically
4461 install the packages I need to use the hardware I plug into my
4462 machine. Even if the package to use it is easily available from the
4463 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4464 suggest to automatically install the python-nxt, nbc and t2n packages
4465 I need to talk to it. When I plug in a Yubikey, it could propose the
4466 yubikey-personalization package. The information required to do this
4467 is available, but no-one have pulled all the pieces together.
</p
>
4469 <p
>Some years ago, I proposed to
4470 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
4471 the discover subsystem to implement this
</a
>. The idea is fairly
4476 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
4477 starting when a user log in.
</li
>
4479 <li
>Set this program up to listen for kernel events emitted when new
4480 hardware is inserted into the computer.
</li
>
4482 <li
>When new hardware is inserted, look up the hardware ID in a
4483 database mapping to packages, and take note of any non-installed
4484 packages.
</li
>
4486 <li
>Show a message to the user proposing to install the discovered
4487 package, and make it easy to install it.
</li
>
4491 <p
>I am not sure what the best way to implement this is, but my
4492 initial idea was to use dbus events to discover new hardware, the
4493 discover database to find packages and
4494 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
4497 <p
>Yesterday, I found time to try to implement this idea, and the
4498 draft package is now checked into
4499 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4500 Debian Edu subversion repository
</a
>. In the process, I updated the
4501 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
4502 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4503 the relevant packages in Debian, and uploaded a new version
4504 2.2013.01.09 to unstable. I also discovered that the current
4505 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
4506 package in Debian no longer discovered any USB devices, because
4507 /proc/bus/usb/devices is no longer present. I ported it to use
4508 libusb as a fall back option to get it working. The fixed package
4509 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
4510 because of the freeze).
</p
>
4512 <p
>With this prototype in place, I can insert my Yubikey, and get this
4513 desktop notification to show up (only once, the first time it is
4514 inserted):
</p
>
4516 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
4518 <p
>For this prototype to be really useful, some way to automatically
4519 install the proposed packages by pressing the
"Please install
4520 program(s)
" button should to be implemented.
</p
>
4522 <p
>If this idea seem useful to you, and you want to help make it
4523 happen, please help me update the discover-data database with mappings
4524 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
4525 list the package you would like to have installed when a given
4526 hardware device is inserted into your computer, and report bugs using
4527 reportbug if it isn
't. Or, if you know of a better way to provide
4528 such mapping, please let me know.
</p
>
4530 <p
>This prototype need more work, and there are several questions that
4531 should be considered before it is ready for production use. Is dbus
4532 the correct way to detect new hardware? At the moment I look for HAL
4533 dbus events on the system bus, because that is the events I could see
4534 on my Debian Squeeze KDE desktop. Are there better events to use?
4535 How should the user be notified? Is the desktop notification
4536 mechanism the best option, or should the background daemon raise a
4537 popup instead? How should packages be installed? When should they
4538 not be installed?
</p
>
4540 <p
>If you want to help getting such feature implemented in Debian,
4541 please send me an email. :)
</p
>
4546 <title>New IRC channel for LEGO designers using Debian
</title>
4547 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
4548 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
4549 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
4550 <description><p
>During Christmas, I have worked a bit on the Debian support for
4551 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
4552 NXT
</a
>. My son and I have played a bit with my NXT set, and I
4553 discovered I had to build all the tools myself because none were
4554 already in Debian Squeeze. If Debian support for LEGO is something
4555 you care about, please join me on the IRC channel
4556 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
4557 irc.debian.org). There is a lot that could be done to improve the
4558 Debian support for LEGO designers. For example both CAD software
4559 and Mindstorm compilers are missing. :)
</p
>
4561 <p
>Update
2012-
01-
03: A
4562 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
4563 including links to Lego related packages is now available.
</p
>
4568 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
4569 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
4570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
4571 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
4572 <description><p
>Let me start by wishing you all marry Christmas and a happy new
4573 year! I hope next year will prove to be a good year.
</p
>
4575 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
4576 decentralised
"currency
" that allow people to transfer bitcoins
4577 between each other with minimal overhead, is a very interesting
4578 experiment. And as I wrote a few days ago, the bitcoin situation in
4579 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
4580 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
4581 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
4582 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
4583 for one of the ftpmasters to approve the new bitcoin-qt package
4586 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
4587 team in Debian, you can easily test the package in Debian Squeeze
4588 using the following steps to get a set of working packages:
</p
>
4590 <blockquote
><pre
>
4591 git clone git://git.debian.org/git/collab-maint/bitcoin
4593 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4594 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4595 </pre
></blockquote
>
4597 <p
>You might have to install some build dependencies as well. The
4598 list of commands should give you two packages, bitcoind and
4599 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4600 client will download the complete set of bitcoin
"blocks
", which need
4601 around
5.6 GiB of data on my machine at the moment. Make sure your
4602 ~/.bitcoin/ directory have lots of spare room if you want to download
4603 all the blocks. The client will warn if the disk is getting full, so
4604 there is not really a problem if you got too little room, but you will
4605 not be able to get all the features out of the client.
</p
>
4607 <p
>As usual, if you use bitcoin and want to show your support of my
4608 activities, please send Bitcoin donations to my address
4609 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4614 <title>A word on bitcoin support in Debian
</title>
4615 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
4616 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
4617 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
4618 <description><p
>It has been a while since I wrote about
4619 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
4620 peer-to-peer based crypto-currency, and the reason is simply that I
4621 have been busy elsewhere. But two days ago, I started looking at the
4622 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
4623 Debian
</a
> again to try to recover my old bitcoin wallet. The package
4624 is now maintained by a
4625 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
4626 people
</a
>, and the grunt work had already been done by this team. We
4627 owe a huge thank you to all these team members. :)
4628 But I was sad to discover that the bitcoin client is missing in
4629 Wheezy. It is only available in Sid (and an outdated client from
4630 backports). The client had several RC bugs registered in BTS blocking
4631 it from entering testing. To try to help the team and improve the
4632 situation, I spent some time providing patches and triaging the bug
4633 reports. I also had a look at the bitcoin package available from Matt
4635 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
4636 Ubuntu
</a
>, and moved the useful pieces from that version into the
4637 Debian package.
</p
>
4639 <p
>After checking with the main package maintainer Jonas Smedegaard on
4640 IRC, I pushed several patches into the collab-maint git repository to
4641 improve the package. It now contains fixes for the RC issues (not from
4642 me, but fixed by Scott Howard), build rules for a Qt GUI client
4643 package, konqueror support for the bitcoin: URI and bash completion
4644 setup. As I work on Debian Squeeze, I also created
4645 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
4646 patch to backport
</a
> the latest version. Jonas is going to look at
4647 it and try to integrate it into the git repository before uploading a
4648 new version to unstable.
4650 <p
>I would very much like bitcoin to succeed, to get rid of the
4651 centralized control currently exercised in the monetary system. I
4652 find it completely unacceptable that the USA government is collecting
4653 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4654 that the major credit card companies can block legal money
4655 transactions to Wikileaks. But for bitcoin to succeed, more people
4656 need to use bitcoins, and more people need to accept bitcoins when
4657 they sell products and services. Improving the bitcoin support in
4658 Debian is a small step in the right direction, but not enough.
4659 Unfortunately the user experience when browsing the web and wanting to
4660 pay with bitcoin is still not very good. The bitcoin: URI is a step
4661 in the right direction, but need to work in most or every browser in
4662 use. Also the bitcoin-qt client is too heavy to fire up to do a
4663 quick transaction. I believe there are other clients available, but
4664 have not tested them.
</p
>
4667 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
4668 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
4669 I received
20.15 BTC so far on the address I provided in my blog two
4670 years ago, as can be
4671 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
4672 on the blockexplorer service
</a
>. Thank you everyone for your
4673 donation. The blockexplorer service demonstrates quite well that
4674 bitcoin is not quite anonymous and untracked. :) I wonder if the
4675 number of users have gone up since then. If you use bitcoin and want
4676 to show your support of my activity, please send Bitcoin donations to
4677 the same address as last time,
4678 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4683 <title>Git repository for song book for Computer Scientists
</title>
4684 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
4685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
4686 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
4687 <description><p
>As I
4688 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
4689 this summer
</a
>, I have created a Computer Science song book a few
4690 years ago, and today I finally found time to create a public
4691 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
4692 repository for the project
</a
>.
</p
>
4694 <p
>If you want to help out, please clone the source and submit patches
4695 to the HTML version. To generate the PDF and PostScript version,
4696 please use prince XML, or let me know about a useful free software
4697 processor capable of creating a good looking PDF from the HTML.
</p
>
4699 <p
>Want to sing? You can still find the song book in HTML, PDF and
4700 PostScript formats at
4701 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
4702 Science Songbook
</a
>.
</p
>
4707 <title>Gratulerer med
19-årsdagen, Debian!
</title>
4708 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
4709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
4710 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
4711 <description><p
>I dag fyller
4712 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
4713 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
4714 si gratulerer med dagen, Debian!
</p
>
4719 <title>Song book for Computer Scientists
</title>
4720 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
4721 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
4722 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
4723 <description><p
>Many years ago, while studying Computer Science at the
4724 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
4725 collecting computer related songs for use at parties. The original
4726 version was written in LaTeX, but a few years ago I got help from
4727 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4728 while keeping the ability to create a nice book in PDF format. I have
4729 not had time to maintain the book for a while now, and guess I should
4730 put it up on some public version control repository where others can
4731 help me extend and update the book. If anyone is volunteering to help
4732 me with this, send me an email. Also let me know if there are songs
4733 missing in my book.
</p
>
4735 <p
>I have not mentioned the book on my blog so far, and it occured to
4736 me today that I really should let all my readers share the joys of
4737 singing out load about programming, computers and computer networks.
4738 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
4739 12</a
> is about to start (and I am not going). Want to sing? Check
4740 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
4741 Computer Science Songbook
</a
>.
4746 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
4747 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
4748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
4749 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
4750 <description><p
>At work we have heaps of servers. I believe the total count is
4751 around
1000 at the moment. To be able to get help from the vendors
4752 when something go wrong, we want to keep the firmware on the servers
4753 up to date. If the firmware isn
't the latest and greatest, the
4754 vendors typically refuse to start debugging any problems until the
4755 firmware is upgraded. So before every reboot, we want to upgrade the
4756 firmware, and we would really like everyone handling servers at the
4757 university to do this themselves when they plan to reboot a machine.
4758 For that to happen we at the unix server admin group need to provide
4759 the tools to do so.
</p
>
4761 <p
>To make firmware upgrading easier, I am working on a script to
4762 fetch and install the latest firmware for the servers we got. Most of
4763 our hardware are from Dell and HP, so I have focused on these servers
4764 so far. This blog post is about the Dell part.
</P
>
4766 <p
>On the Dell FTP site I was lucky enough to find
4767 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
4768 with firmware information for all
11th generation servers, listing
4769 which firmware should be used on a given model and where on the FTP
4770 site I can find it. Using a simple perl XML parser I can then
4771 download the shell scripts Dell provides to do firmware upgrades from
4772 within Linux and reboot when all the firmware is primed and ready to
4773 be activated on the first reboot.
</p
>
4775 <p
>This is the Dell related fragment of the perl code I am working on.
4776 Are there anyone working on similar tools for firmware upgrading all
4777 servers at a site? Please get in touch and lets share resources.
</p
>
4779 <p
><pre
>
4783 use File::Temp qw(tempdir);
4785 # Install needed RHEL packages if missing
4787 'XML::Simple
' =
> 'perl-XML-Simple
',
4789 for my $module (keys %rhelmodules) {
4790 eval
"use $module;
";
4792 my $pkg = $rhelmodules{$module};
4793 system(
"yum install -y $pkg
");
4794 eval
"use $module;
";
4798 my $errorsto =
'pere@hungry.com
';
4804 sub run_firmware_script {
4805 my ($opts, $script) = @_;
4807 print STDERR
"fail: missing script name\n
";
4810 print STDERR
"Running $script\n\n
";
4812 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
4813 print STDERR
"success: firmware script ran succcessfully\n
";
4815 print STDERR
"fail: firmware script returned error\n
";
4819 sub run_firmware_scripts {
4820 my ($opts, @dirs) = @_;
4821 # Run firmware packages
4822 for my $dir (@dirs) {
4823 print STDERR
"info: Running scripts in $dir\n
";
4824 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
4825 while (my $s = readdir $dh) {
4826 next if $s =~ m/^\.\.?/;
4827 run_firmware_script($opts,
"$dir/$s
");
4835 print STDERR
"info: Downloading $url\n
";
4836 system(
"wget --quiet \
"$url\
"");
4841 my $product = `dmidecode -s system-product-name`;
4844 if ($product =~ m/PowerEdge/) {
4846 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4847 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
4849 my $tmpdir = tempdir(
4853 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
4854 system(
'gunzip Catalog.xml.gz
');
4855 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
4856 # -q is quiet, disabling interactivity and reducing console output
4857 my $fwopts =
"-q
";
4859 for my $url (@paths) {
4860 fetch_dell_fw($url);
4862 run_firmware_scripts($fwopts, $tmpdir);
4864 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4865 print STDERR
"error: Please report to $errorsto.\n
";
4869 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4870 print STDERR
"error: Please report to $errorsto.\n
";
4876 my $url =
"ftp://ftp.us.dell.com/$path
";
4880 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4881 # firmware packages to download from Dell. Only work for Linux
4882 # machines and
11th generation Dell servers.
4883 sub fetch_dell_fw_list {
4884 my $filename = shift;
4886 my $product = `dmidecode -s system-product-name`;
4888 my ($mybrand, $mymodel) = split(/\s+/, $product);
4890 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
4892 my $xml = XMLin($filename);
4894 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
4895 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
4896 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
4898 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
4899 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
4901 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
4903 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
4905 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
4908 for my $component (@{$xml-
>{SoftwareComponent}}) {
4909 my $componenttype = $component-
>{ComponentType}-
>{value};
4911 # Drop application packages, only firmware and BIOS
4912 next if
'APAC
' eq $componenttype;
4914 my $cpath = $component-
>{path};
4915 for my $path (@paths) {
4916 if ($cpath =~ m%/$path$%) {
4917 push(@paths, $cpath);
4925 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
4926 it could work on other platforms with some tweaking. Anyone know a
4927 index like Catalog.xml is available from HP for HP servers? At the
4928 moment I maintain a similar list manually and it is quickly getting
4934 <title>How is booting into runlevel
1 different from single user boots?
</title>
4935 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
4936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
4937 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
4938 <description><p
>Wouter Verhelst have some
4939 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
4940 comments and opinions
</a
> on my blog post on
4941 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
4942 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
4943 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
4944 default KDE desktop in Debian
</a
>. I only have time to address one
4945 small piece of his comment now, and though it best to address the
4946 misunderstanding he bring forward:
</p
>
4948 <p
><blockquote
>
4949 Currently, a system admin has four options: [...] boot to a
4950 single-user system (by adding
'single
' to the kernel command line;
4951 this runs rcS and rc1 scripts)
4952 </blockquote
></p
>
4954 <p
>This make me believe Wouter believe booting into single user mode
4955 and booting into runlevel
1 is the same. I am not surprised he
4956 believe this, because it would make sense and is a quite sensible
4957 thing to believe. But because the boot in Debian is slightly broken,
4958 runlevel
1 do not work properly and it isn
't the same as single user
4959 mode. I
'll try to explain what is actually happing, but it is a bit
4960 hard to explain.
</p
>
4962 <p
>Single user mode is defined like this in /etc/inittab:
4963 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
4964 executed in single user mode is sulogin. Single user mode is a boot
4965 state
"between
" the runlevels, and when booting into single user mode,
4966 only the scripts in /etc/rcS.d/ are executed before the init process
4967 enters the single user state. When switching to runlevel
1, the state
4968 is in fact not ending in runlevel
1, but it passes through runlevel
1
4969 and end up in the single user mode (see /etc/rc1.d/S03single, which
4970 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
4971 1. It is confusing that the
'S
' (single user) init mode is not the
4972 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4975 <p
>This summary might make it clearer. When booting for the first
4976 time into single user mode, the following commands are executed:
4977 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
4978 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
4979 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
4980 trying to continue after visiting single user mode. Not all services
4981 are started again as they should, causing the machine to end up in an
4982 unpredicatble state. This is why Debian admins recommend rebooting
4983 after visiting single user mode.
</p
>
4985 <p
>A similar problem with runlevel
1 is caused by the amount of
4986 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
4987 to runlevel
1, the services started from /etc/rcS.d/ are not properly
4988 stopped when passing through the scripts in /etc/rc1.d/, and not
4989 started again when switching away from runlevel
1 to the runlevels
4990 2-
5. I believe the problem is best fixed by moving all the scripts
4991 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
4992 functioning single user mode during boot.
</p
>
4994 <p
>I have spent several years investigating the Debian boot system,
4995 and discovered this problem a few years ago. I suspect it originates
4996 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5001 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5002 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5004 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5005 <description><p
>In the Debian boot system, several packages include scripts that
5006 are started from /etc/rcS.d/. In fact, there is a bite more of them
5007 than make sense, and this causes a few problems. What kind of
5008 problems, you might ask. There are at least two problems. The first
5009 is that it is not possible to recover a machine after switching to
5010 runlevel
1. One need to actually reboot to get the machine back to
5011 the expected state. The other is that single user boot will sometimes
5012 run into problems because some of the subsystems are activated before
5013 the root login is presented, causing problems when trying to recover a
5014 machine from a problem in that subsystem. A minor additional point is
5015 that moving more scripts out of rcS.d/ and into the other rc#.d/
5016 directories will increase the amount of scripts that can run in
5017 parallel during boot, and thus decrease the boot time.
</p
>
5019 <p
>So, which scripts should start from rcS.d/. In short, only the
5020 scripts that _have_ to execute before the root login prompt is
5021 presented during a single user boot should go there. Everything else
5022 should go into the numeric runlevels. This means things like
5023 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5024 the numeric runlevels. Today in Debian, there are around
115 init.d
5025 scripts that are started from rcS.d/, and most of them should be moved
5026 out. Do your package have one of them? Please help us make single
5027 user and runlevel
1 better by moving it.
</p
>
5029 <p
>Scripts setting up the screen, keyboard, system partitions
5030 etc. should still be started from rcS.d/, but there is for example no
5031 need to have the network enabled before the single user login prompt
5032 is presented.
</p
>
5034 <p
>As always, things are not so easy to fix as they sound. To keep
5035 Debian systems working while scripts migrate and during upgrades, the
5036 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5037 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5038 and the next ones can only be moved when their dependencies have been
5039 moved first. This migration must be done sequentially while we ensure
5040 that the package system upgrade packages in the right order to keep
5041 the system state correct. This will require some coordination when it
5042 comes to network related packages, but most of the packages with
5043 scripts that should migrate do not have anything in rcS.d/ depending
5044 on them. Some packages have already been updated, like the sudo
5045 package, while others are still left to do. I wish I had time to work
5046 on this myself, but real live constrains make it unlikely that I will
5047 find time to push this forward.
</p
>
5052 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5053 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5055 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5056 <description><p
>While at Debconf11, I have several times during discussions
5057 mentioned the issues I believe should be improved in Debian for its
5058 desktop to be useful for more people. The use case for this is my
5059 parents, which are currently running Kubuntu which solve the
5062 <p
>I suspect these four missing features are not very hard to
5063 implement. After all, they are present in Ubuntu, so if we wanted to
5064 do this in Debian we would have a source.
</p
>
5068 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5069 are new packages available for upgrades, a icon in the KDE status bar
5070 indicate this, and clicking on it will activate the simple upgrade
5071 tool to handle it. I have no problem guiding both of my parents
5072 through the process over the phone. If a kernel reboot is required,
5073 this too is indicated by the status bars and the upgrade tool. Last
5074 time I checked, nothing with the same features was working in KDE in
5077 <li
><strong
>Simple handling of missing Firefox browser
5078 plugins.
</strong
> When the browser encounter a MIME type it do not
5079 currently have a handler for, it will ask the user if the system
5080 should search for a package that would add support for this MIME type,
5081 and if the user say yes, the APT sources will be searched for packages
5082 advertising the MIME type in their control file (visible in the
5083 Packages file in the APT archive). If one or more packages are found,
5084 it is a simple click of the mouse to add support for the missing mime
5085 type. If the package require the user to accept some non-free
5086 license, this is explained to the user. The entire process make it
5087 more clear to the user why something do not work in the browser, and
5088 make the chances higher for the user to blame the web page authors and
5089 not the browser for any missing features.
</li
>
5091 <li
><strong
>Simple handling of missing multimedia codec/format
5092 handlers.
</strong
> When the media players encounter a format or codec
5093 it is not supporting, a dialog pop up asking the user if the system
5094 should search for a package that would add support for it. This
5095 happen with things like MP3, Windows Media or H
.264. The selection
5096 and installation procedure is very similar to the Firefox browser
5097 plugin handling. This is as far as I know implemented using a
5098 gstreamer hook. The end result is that the user easily get access to
5099 the codecs that are present from the APT archives available, while
5100 explaining more on why a given format is unsupported by Ubuntu.
</li
>
5102 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
5103 displaying a text/plain file in my Debian browser, it will propose to
5104 start emacs to show it. If I remember correctly, when doing the same
5105 in Kunbutu it show the file as a text file in the browser. At least I
5106 know Opera will show text files within the browser. I much prefer the
5107 latter behaviour.
</li
>
5111 <p
>There are other nice features as well, like the simplified suite
5112 upgrader, but given that I am the one mostly doing the dist-upgrade,
5113 it do not matter much.
</p
>
5115 <p
>I really hope we could get these features in place for the next
5116 Debian release. It would require the coordinated effort of several
5117 maintainers, but would make the end user experience a lot better.
</p
>
5122 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
5123 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
5124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
5125 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
5126 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
5127 site is build on Debian/Squeeze, and this platform was chosen because
5128 I am most familiar with Debian (being a Debian Developer for around
10
5129 years) because it is the latest stable Debian release which should get
5130 security support for a few years.
</p
>
5132 <p
>The web service is written in Perl, and depend on some perl modules
5133 that are missing in Debian at the moment. It would be great if these
5134 modules were added to the Debian archive, allowing anyone to set up
5135 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
5136 in their own country using only Debian packages. The list of modules
5137 missing in Debian/Squeeze isn
't very long, and I hope the perl group
5138 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
5139 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5140 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5141 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5142 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5143 easier in the future.
</p
>
5145 <p
>Thanks to the great tools in Debian, getting the missing modules
5146 installed on my server was a simple call to
'cpan2deb Module::Name
'
5147 and
'dpkg -i
' to install the resulting package. But this leave me
5148 with the responsibility of tracking security problems, which I really
5149 do not have time for.
</p
>
5154 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
5155 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
5156 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
5157 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
5158 <description><p
>Here is a small update for my English readers. Most of my blog
5159 posts have been in Norwegian the last few weeks, so here is a short
5160 update in English.
</p
>
5162 <p
>The kids still keep me too busy to get much free software work
5163 done, but I did manage to organise a project to get a Norwegian port
5164 of the British service
5165 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
5166 and it has been running for a month now. The entire project has been
5167 organised by me and two others. Around Christmas we gathered sponsors
5168 to fund the development work. In January I drafted a contract with
5169 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
5170 and in February the development took place. Most of it involved
5171 converting the source to use GPS coordinates instead of British
5172 easting/northing, and the resulting code should be a lot easier to get
5173 running in any country by now. The Norwegian
5174 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
5175 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
5176 source and the source for administrative borders in Norway, and
5177 support for this had to be added/fixed.
</p
>
5179 <p
>The Norwegian version went live March
3th, and we spent the weekend
5180 polishing the system before we announced it March
7th. The system is
5181 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
5182 problem reports in a few weeks. Soon we hope to announce the Android
5183 and iPhone versions making it even easier to report problems with the
5184 public infrastructure.
</p
>
5186 <p
>Perhaps something to consider for those of you in countries without
5187 such service?
</p
>
5192 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
5193 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
5194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
5195 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
5196 <description><p
>The last few days I have looked at ways to track open security
5197 issues here at my work with the University of Oslo. My idea is that
5198 it should be possible to use the information about security issues
5199 available on the Internet, and check our locally
5200 maintained/distributed software against this information. It should
5201 allow us to verify that no known security issues are forgotten. The
5202 CVE database listing vulnerabilities seem like a great central point,
5203 and by using the package lists from Debian mapped to CVEs provided by
5204 the testing security team, I believed it should be possible to figure
5205 out which security holes were present in our free software
5206 collection.
</p
>
5208 <p
>After reading up on the topic, it became obvious that the first
5209 building block is to be able to name software packages in a unique and
5210 consistent way across data sources. I considered several ways to do
5211 this, for example coming up with my own naming scheme like using URLs
5212 to project home pages or URLs to the Freshmeat entries, or using some
5213 existing naming scheme. And it seem like I am not the first one to
5214 come across this problem, as MITRE already proposed and implemented a
5215 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5216 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5217 software, hardware and other platform components. The CPE ids are
5218 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5219 Vulnerability Database
</a
>, allowing me to look up know security
5220 issues for any CPE name. With this in place, all I need to do is to
5221 locate the CPE id for the software packages we use at the university.
5222 This is fairly trivial (I google for
'cve cpe $package
' and check the
5223 NVD entry if a CVE for the package exist).
</p
>
5225 <p
>To give you an example. The GNU gzip source package have the CPE
5226 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5227 check out, one could look up
5228 <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
5229 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5230 The most recent one is
5231 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5232 and at the bottom of the NVD page for this vulnerability the complete
5233 list of affected versions is provided.
</p
>
5235 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5236 for offline processing of issues. Using this dump, I
've written a
5237 small script taking a list of CPEs as input and list all CVEs
5238 affecting the packages represented by these CPEs. One give it CPEs
5239 with version numbers as specified above and get a list of open
5240 security issues out.
</p
>
5242 <p
>Of course for this approach to be useful, the quality of the NVD
5243 information need to be high. For that to happen, I believe as many as
5244 possible need to use and contribute to the NVD database. I notice
5246 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5247 map from CVE to CPE
</a
>, indicating that they are using the CPE
5248 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5250 <p
>To get an idea about the quality for free software, I spent some
5251 time making it possible to compare the CVE database from Debian with
5252 the CVE database in NVD. The result look fairly good, but there are
5253 some inconsistencies in NVD (same software package having several
5254 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5255 Debian believe are affected by a CVE). Hope to find time to improve
5256 the quality of NVD, but that require being able to get in touch with
5257 someone maintaining it. So far my three emails with questions and
5258 corrections have not seen any reply, but I hope contact can be
5259 established soon.
</p
>
5261 <p
>An interesting application for CPEs is cross platform package
5262 mapping. It would be useful to know which packages in for example
5263 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5264 this would be trivial if all linux distributions provided CPE entries
5265 for their packages.
</p
>
5270 <title>Which module is loaded for a given PCI and USB device?
</title>
5271 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5273 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5274 <description><p
>In the
5275 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5276 package in Debian, there is a script to report useful information
5277 about the running hardware for use when people report missing
5278 information. One part of this script that I find very useful when
5279 debugging hardware problems, is the part mapping loaded kernel module
5280 to the PCI device it claims. It allow me to quickly see if the kernel
5281 module I expect is driving the hardware I am struggling with. To see
5282 the output, make sure discover-data is installed and run
5283 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
5284 one of my machines like this:
</p
>
5288 10de:
03eb i2c_nforce2
5291 10de:
03f0 snd_hda_intel
5300 <p
>The code in question look like this, slightly modified for
5301 readability and to drop the output to file descriptor
3:
</p
>
5304 if [ -d /sys/bus/pci/devices/ ] ; then
5305 echo loaded pci modules:
5307 cd /sys/bus/pci/devices/
5308 for address in * ; do
5309 if [ -d
"$address/driver/module
" ] ; then
5310 module=`cd $address/driver/module ; pwd -P | xargs basename`
5311 if grep -q
"^$module
" /proc/modules ; then
5312 address=$(echo $address |sed s/
0000://)
5313 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
5314 echo
"$id $module
"
5323 <p
>Similar code could be used to extract USB device module
5327 if [ -d /sys/bus/usb/devices/ ] ; then
5328 echo loaded usb modules:
5330 cd /sys/bus/usb/devices/
5331 for address in * ; do
5332 if [ -d
"$address/driver/module
" ] ; then
5333 module=`cd $address/driver/module ; pwd -P | xargs basename`
5334 if grep -q
"^$module
" /proc/modules ; then
5335 address=$(echo $address |sed s/
0000://)
5336 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
5337 if [
"$id
" ] ; then
5338 echo
"$id $module
"
5348 <p
>This might perhaps be something to include in other tools as
5354 <title>How to test if a laptop is working with Linux
</title>
5355 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
5356 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
5357 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
5358 <description><p
>The last few days I have spent at work here at the
<a
5359 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
5360 batch of computers will work with Linux. Every year for the last few
5361 years the university have organised shared bid of a few thousand
5362 computers, and this year HP won the bid. Two different desktops and
5363 five different laptops are on the list this year. We in the UNIX
5364 group want to know which one of these computers work well with RHEL
5365 and Ubuntu, the two Linux distributions we currently handle at the
5366 university.
</p
>
5368 <p
>My test method is simple, and I share it here to get feedback and
5369 perhaps inspire others to test hardware as well. To test, I PXE
5370 install the OS version of choice, and log in as my normal user and run
5371 a few applications and plug in selected pieces of hardware. When
5372 something fail, I make a note about this in the test matrix and move
5373 on. If I have some spare time I try to report the bug to the OS
5374 vendor, but as I only have the machines for a short time, I rarely
5375 have the time to do this for all the problems I find.
</p
>
5377 <p
>Anyway, to get to the point of this post. Here is the simple tests
5378 I perform on a new model.
</p
>
5382 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
5383 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5384 RHEL5 and Debian Edu/Squeeze.
</li
>
5386 <li
>Is X.org working? If the graphical login screen show up after
5387 installation, X.org is working.
</li
>
5389 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
5390 package mesa-utils on Ubuntu) and writing down the frames per second
5391 reported by the program.
</li
>
5393 <li
>Is sound working? With Gnome and KDE, a sound is played when
5394 logging in, and if I can hear this the test is successful. If there
5395 are several audio exits on the machine, I try them all and check if
5396 the Gnome/KDE audio mixer can control where to send the sound. I
5397 normally test this by playing
5398 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
5399 video
</a
> in Firefox/Iceweasel.
</li
>
5401 <li
>Is the USB subsystem working? I test this by plugging in a USB
5402 memory stick and see if Gnome/KDE notices this.
</li
>
5404 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
5405 I have lying around, and see if Gnome/KDE notices this.
</li
>
5407 <li
>Is any built in camera working? Test using cheese, and see if a
5408 picture from the v4l device show up.
</li
>
5410 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5411 any bluetooth devices are discovered. In my office, I normally see a
5414 <li
>For laptops, is the SD or Compaq Flash reader working. I have
5415 memory modules lying around, and stick them in and see if Gnome/KDE
5416 notice this.
</li
>
5418 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
5419 special button work, and if the laptop continue to work after
5422 <li
>For laptops, is the extra buttons working, like audio level,
5423 adjusting background light, switching on/off external video output,
5424 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5425 laptop to laptop, so I just write down which are working and which are
5428 <li
>Some laptops have smart card readers, finger print readers,
5429 acceleration sensors etc. I rarely test these, as I do not know how
5430 to quickly test if they are working or not, so I only document their
5431 existence.
</li
>
5435 <p
>By now I suspect you are really curious what the test results are
5436 for the HP machines I am testing. I
'm not done yet, so I will report
5437 the test results later. For now I can report that HP
8100 Elite work
5438 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
5439 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
5440 can see, I have most machines left to test. One interesting
5441 observation is that Ubuntu Lucid has almost twice the frame rate than
5442 RHEL6 with glxgears. No idea why.
</p
>
5447 <title>Some thoughts on BitCoins
</title>
5448 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
5449 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
5450 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
5451 <description><p
>As I continue to explore
5452 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
5453 what properties the system have, and how it will be affected by laws
5454 and regulations here in Norway. Here are some random notes.
</p
>
5456 <p
>One interesting thing to note is that since the transactions are
5457 verified using a peer to peer network, all details about a transaction
5458 is known to everyone. This means that if a BitCoin address has been
5459 published like I did with mine in my initial post about BitCoin, it is
5460 possible for everyone to see how many BitCoins have been transfered to
5461 that address. There is even a web service to look at the details for
5462 all transactions. There I can see that my address
5463 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
5464 have received
16.06 Bitcoin, the
5465 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
5466 address of Simon Phipps have received
181.97 BitCoin and the address
5467 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
5468 of EFF have received
2447.38 BitCoins so far. Thank you to each and
5469 every one of you that donated bitcoins to support my activity. The
5470 fact that anyone can see how much money was transfered to a given
5471 address make it more obvious why the BitCoin community recommend to
5472 generate and hand out a new address for each transaction. I
'm told
5473 there is no way to track which addresses belong to a given person or
5474 organisation without the person or organisation revealing it
5475 themselves, as Simon, EFF and I have done.
</p
>
5477 <p
>In Norway, and in most other countries, there are laws and
5478 regulations limiting how much money one can transfer across the border
5479 without declaring it. There are money laundering, tax and accounting
5480 laws and regulations I would expect to apply to the use of BitCoin.
5481 If the Skolelinux foundation
5482 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
5483 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
5484 normal bank transfers like EFF is doing, how should this be accounted?
5485 Given that it is impossible to know if money can cross the border or
5486 not, should everything or nothing be declared? What exchange rate
5487 should be used when calculating taxes? Would receivers have to pay
5488 income tax if the foundation were to pay Skolelinux contributors in
5489 BitCoin? I have no idea, but it would be interesting to know.
</p
>
5491 <p
>For a currency to be useful and successful, it must be trusted and
5492 accepted by a lot of users. It must be possible to get easy access to
5493 the currency (as a wage or using currency exchanges), and it must be
5494 easy to spend it. At the moment BitCoin seem fairly easy to get
5495 access to, but there are very few places to spend it. I am not really
5496 a regular user of any of the vendor types currently accepting BitCoin,
5497 so I wonder when my kind of shop would start accepting BitCoins. I
5498 would like to buy electronics, travels and subway tickets, not herbs
5499 and books. :) The currency is young, and this will improve over time
5500 if it become popular, but I suspect regular banks will start to lobby
5501 to get BitCoin declared illegal if it become popular. I
'm sure they
5502 will claim it is helping fund terrorism and money laundering (which
5503 probably would be true, as is any currency in existence), but I
5504 believe the problems should be solved elsewhere and not by blaming
5505 currencies.
</p
>
5507 <p
>The process of creating new BitCoins is called mining, and it is
5508 CPU intensive process that depend on a bit of luck as well (as one is
5509 competing against all the other miners currently spending CPU cycles
5510 to see which one get the next lump of cash). The
"winner
" get
50
5511 BitCoin when this happen. Yesterday I came across the obvious way to
5512 join forces to increase ones changes of getting at least some coins,
5513 by coordinating the work on mining BitCoins across several machines
5514 and people, and sharing the result if one is lucky and get the
50
5516 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
5517 if this sounds interesting. I have not had time to try to set up a
5518 machine to participate there yet, but have seen that running on ones
5519 own for a few days have not yield any BitCoins througth mining
5522 <p
>Update
2010-
12-
15: Found an
<a
5523 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
5524 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
5525 it was interesting to read. The arguments presented seem to be
5526 equally valid for gold, which was used as a currency for many years.
</p
>
5531 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
5532 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
5533 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
5534 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
5535 <description><p
>With this weeks lawless
5536 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
5537 attacks
</a
> on Wikileak and
5538 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
5539 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
5540 not be trusted to handle money transactions.
5542 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
5543 Phipps on bitcoin
</a
> reminded me about a project that a friend of
5544 mine mentioned earlier. I decided to follow Simon
's example, and get
5545 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
5546 some help from my friend to get it all running, and he even handed me
5547 some bitcoins to get started. I even donated a few bitcoins to Simon
5548 for helping me remember BitCoin.
</p
>
5550 <p
>So, what is bitcoins, you probably wonder? It is a digital
5551 crypto-currency, decentralised and handled using peer-to-peer
5552 networks. It allows anonymous transactions and prohibits central
5553 control over the transactions, making it impossible for governments
5554 and companies alike to block donations and other transactions. The
5555 source is free software, and while the key dependency wxWidgets
2.9
5556 for the graphical user interface is missing in Debian, the command
5557 line client builds just fine. Hopefully Jonas
5558 <a href=
"http://bugs.debian.org/
578157">will get the package into
5559 Debian
</a
> soon.
</p
>
5561 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
5562 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
5563 bitcoins
</a
> when selling services and goods, and there are even
5564 currency
"stock
" markets where the exchange rate is decided. There
5565 are not many users so far, but the concept seems promising. If you
5566 want to get started and lack a friend with any bitcoins to spare,
5568 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
5569 bitcoin at the time of writing). Use
5570 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
5571 on the current exchange rates.
</p
>
5573 <p
>As an experiment, I have decided to set up bitcoind on one of my
5574 machines. If you want to support my activity, please send Bitcoin
5575 donations to the address
5576 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
5581 <title>Why isn
't Debian Edu using VLC?
</title>
5582 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
5583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
5584 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
5585 <description><p
>In the latest issue of Linux Journal, the readers choices were
5586 presented, and the winner among the multimedia player were VLC.
5587 Personally, I like VLC, and it is my player of choice when I first try
5588 to play a video file or stream. Only if VLC fail will I drag out
5589 gmplayer to see if it can do better. The reason is mostly the failure
5590 model and trust. When VLC fail, it normally pop up a error message
5591 reporting the problem. When mplayer fail, it normally segfault or
5592 just hangs. The latter failure mode drain my trust in the program.
<p
>
5594 <p
>But even if VLC is my player of choice, we have choosen to use
5595 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
5596 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
5597 plugin to play web videos seamlessly, and the VLC browser plugin is
5598 not very good. For example, it lack in-line control buttons, so there
5599 is no way for the user to pause the video. Also, when I
5600 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
5601 tested the browser plugins
</a
> available in Debian, the VLC plugin
5602 failed on several video pages where mplayer based plugins worked. If
5603 the browser plugin for VLC was as good as the gecko-mediaplayer
5604 package (which uses mplayer), we would switch.
</P
>
5606 <p
>While VLC is a good player, its user interface is slightly
5607 annoying. The most annoying feature is its inconsistent use of
5608 keyboard shortcuts. When the player is in full screen mode, its
5609 shortcuts are different from when it is playing the video in a window.
5610 For example, space only work as pause when in full screen mode. I
5611 wish it had consisten shortcuts and that space also would work when in
5612 window mode. Another nice shortcut in gmplayer is [enter] to restart
5613 the current video. It is very nice when playing short videos from the
5614 web and want to restart it when new people arrive to have a look at
5615 what is going on.
</p
>
5620 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
5621 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
5622 <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>
5623 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
5624 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
5625 upgrade testing of the
5626 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5627 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
5628 This seem like a very good idea, so I adjusted by test scripts and
5629 can now present the updated result from today:
</p
>
5631 <p
>This is for Gnome:
</p
>
5633 <p
>Installed using apt-get, missing with aptitude
</p
>
5635 <blockquote
><p
>
5640 browser-plugin-gnash
5647 freedesktop-sound-theme
5649 gconf-defaults-service
5664 gnome-desktop-environment
5668 gnome-session-canberra
5673 gstreamer0.10-fluendo-mp3
5679 libapache2-mod-dnssd
5682 libaprutil1-dbd-sqlite3
5685 libboost-date-time1.42
.0
5686 libboost-python1.42
.0
5687 libboost-thread1.42
.0
5689 libchamplain-gtk-
0.4-
0
5691 libclutter-gtk-
0.10-
0
5698 libfreerdp-plugins-standard
5713 libgnomepanel2.24-cil
5718 libgtksourceview2.0-common
5719 libmono-addins-gui0.2-cil
5720 libmono-addins0.2-cil
5721 libmono-cairo2.0-cil
5722 libmono-corlib2.0-cil
5723 libmono-i18n-west2.0-cil
5724 libmono-posix2.0-cil
5725 libmono-security2.0-cil
5726 libmono-sharpzip2.84-cil
5727 libmono-system2.0-cil
5730 libndesk-dbus-glib1.0-cil
5731 libndesk-dbus1.0-cil
5741 libtelepathy-farsight0
5750 nautilus-sendto-empathy
5754 python-aptdaemon-gtk
5756 python-beautifulsoup
5771 python-gtksourceview2
5782 python-pkg-resources
5789 python-twisted-conch
5795 python-zope.interface
5800 rhythmbox-plugin-cdrecorder
5807 system-config-printer-udev
5809 telepathy-mission-control-
5
5820 </p
></blockquote
>
5822 <p
>Installed using apt-get, removed with aptitude
</p
>
5824 <blockquote
><p
>
5830 fast-user-switch-applet
5849 libgtksourceview2.0-
0
5851 libsdl1.2debian-alsa
5857 system-config-printer
5862 </p
></blockquote
>
5864 <p
>Installed using aptitude, missing with apt-get
</p
>
5866 <blockquote
><p
>
5867 gstreamer0.10-gnomevfs
5868 </p
></blockquote
>
5870 <p
>Installed using aptitude, removed with apt-get
</p
>
5872 <blockquote
><p
>
5874 </p
></blockquote
>
5876 <p
>This is for KDE:
</p
>
5878 <p
>Installed using apt-get, missing with aptitude
</p
>
5880 <blockquote
><p
>
5882 </p
></blockquote
>
5884 <p
>Installed using apt-get, removed with aptitude
</p
>
5886 <blockquote
><p
>
5889 </p
></blockquote
>
5891 <p
>Installed using aptitude, missing with apt-get
</p
>
5893 <blockquote
><p
>
5907 kdeartwork-emoticons
5909 kdeartwork-theme-icon
5913 kdebase-workspace-bin
5914 kdebase-workspace-data
5928 kscreensaver-xsavers
5943 plasma-dataengines-workspace
5945 plasma-desktopthemes-artwork
5946 plasma-runners-addons
5947 plasma-scriptengine-googlegadgets
5948 plasma-scriptengine-python
5949 plasma-scriptengine-qedje
5950 plasma-scriptengine-ruby
5951 plasma-scriptengine-webkit
5952 plasma-scriptengines
5953 plasma-wallpapers-addons
5954 plasma-widget-folderview
5955 plasma-widget-networkmanagement
5959 xscreensaver-data-extra
5961 xscreensaver-gl-extra
5962 xscreensaver-screensaver-bsod
5963 </p
></blockquote
>
5965 <p
>Installed using aptitude, removed with apt-get
</p
>
5967 <blockquote
><p
>
5969 google-gadgets-common
5987 libggadget-qt-
1.0-
0b
5992 libkonqsidebarplugin4a
6001 libplasma-geolocation-interface4
6003 libplasmagenericshell4
6017 libsmokeknewstuff2-
3
6018 libsmokeknewstuff3-
3
6020 libsmokektexteditor3
6028 libsmokeqtnetwork4-
3
6034 libsmokeqtuitools4-
3
6046 plasma-dataengines-addons
6047 plasma-scriptengine-superkaramba
6048 plasma-widget-lancelot
6049 plasma-widgets-addons
6050 plasma-widgets-workspace
6054 update-notifier-common
6055 </p
></blockquote
>
6057 <p
>Running apt-get autoremove made the results using apt-get and
6058 aptitude a bit more similar, but there are still quite a lott of
6059 differences. I have no idea what packages should be installed after
6060 the upgrade, but hope those that do can have a look.
</p
>
6065 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6066 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6068 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6069 <description><p
>Most of the computers in use by the
6070 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6071 are virtual machines. And they have been Xen machines running on a
6072 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6073 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6074 bit harder that it could have been, because we set up the Xen virtual
6075 machines to get the virtual partitions from LVM, which as far as I
6076 know is not supported by KVM. So to migrate, we had to convert
6077 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6080 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6081 nice recipe
</a
> to do this, and wrote the following script to do the
6082 migration. It uses qemu-img from the qemu package to make the disk
6083 image, parted to partition it, losetup and kpartx to present the disk
6084 image partions as devices, and dd to copy the data. I NFS mounted the
6085 new servers storage area on the old server to do the migration.
</p
>
6091 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6096 if [ -z
"$
1" ] ; then
6097 echo
"Usage: $
0 &lt;hostname
&gt;
"
6103 if [ ! -e /dev/vg_data/$host-disk ] ; then
6104 echo
"error: unable to find LVM volume for $host
"
6108 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6109 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6110 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6111 totalsize=$(( ( $disksize + $swapsize ) ))
6114 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
6115 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6117 parted $img mklabel msdos
6118 parted $img mkpart primary linux-swap
0 $disksize
6119 parted $img mkpart primary ext2 $disksize $totalsize
6120 parted $img set
1 boot on
6123 losetup /dev/loop0 $img
6124 kpartx -a /dev/loop0
6126 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
6127 fsck.ext3 -f /dev/mapper/loop0p1 || true
6128 mkswap /dev/mapper/loop0p2
6130 kpartx -d /dev/loop0
6131 losetup -d /dev/loop0
6134 <p
>The script is perhaps so simple that it is not copyrightable, but
6135 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
6137 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
6138 the new disk image attached, installed grub-pc and linux-image-
686 and
6139 set up grub to boot from the disk image. After this, the KVM machines
6140 seem to work just fine.
</p
>
6145 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
6146 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
6147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
6148 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
6149 <description><p
>I
'm still running upgrade testing of the
6150 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6151 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
6152 status. Here is a short update based on a test I ran
20101118.
</p
>
6154 <p
>I still do not know what a correct migration should look like, so I
6155 report any differences between apt and aptitude and hope someone else
6156 can see if anything should be changed.
</p
>
6158 <p
>This is for Gnome:
</p
>
6160 <p
>Installed using apt-get, missing with aptitude
</p
>
6162 <blockquote
><p
>
6163 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6164 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
6165 dmz-cursor-theme empathy empathy-common finger
6166 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6167 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6168 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6169 gnome-cards-data gnome-codec-install gnome-core
6170 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6171 gnome-search-tool gnome-session-canberra gnome-spell
6172 gnome-system-log gnome-themes-extras gnome-themes-more
6173 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6174 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6175 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6176 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6177 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
6178 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
6179 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
6180 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
6181 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
6182 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6183 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
6184 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6185 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6186 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6187 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6188 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6189 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6190 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6191 libmono-security2.0-cil libmono-sharpzip2.84-cil
6192 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
6193 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
6194 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
6195 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
6196 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
6197 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
6198 libxalan2-java libxerces2-java media-player-info mesa-utils
6199 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
6200 nautilus-sendto-empathy openoffice.org-writer2latex
6201 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
6202 python-aptdaemon python-aptdaemon-gtk python-axiom
6203 python-beautifulsoup python-bugbuddy python-clientform
6204 python-coherence python-configobj python-crypto python-cupshelpers
6205 python-cupsutils python-eggtrayicon python-elementtree
6206 python-epsilon python-evolution python-feedparser python-gdata
6207 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6208 python-gtksourceview2 python-httplib2 python-louie python-mako
6209 python-markupsafe python-mechanize python-nevow python-notify
6210 python-opengl python-openssl python-pam python-pkg-resources
6211 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6212 python-tagpy python-twisted-bin python-twisted-conch
6213 python-twisted-core python-twisted-web python-utidylib python-webkit
6214 python-xdg python-zope.interface remmina remmina-plugin-data
6215 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6216 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6217 software-center svgalibg1 system-config-printer-udev
6218 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6219 totem totem-coherence totem-mozilla totem-plugins
6220 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6222 </p
></blockquote
>
6224 Installed using apt-get, removed with aptitude
6226 <blockquote
><p
>
6227 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6228 epiphany-extensions epiphany-gecko evolution-exchange
6229 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6230 gedit-common gnome-app-install gnome-games gnome-games-data
6231 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6232 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6233 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6234 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6235 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6236 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6237 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6238 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6239 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6240 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6241 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6242 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6243 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6244 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6245 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6246 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6247 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6248 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6249 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6250 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6251 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6252 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6253 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6254 sound-juicer swfdec-gnome system-config-printer totem-common
6255 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6256 </p
></blockquote
>
6258 <p
>Installed using aptitude, missing with apt-get
</p
>
6260 <blockquote
><p
>
6261 gstreamer0.10-gnomevfs
6262 </p
></blockquote
>
6264 <p
>Installed using aptitude, removed with apt-get
</p
>
6266 <blockquote
><p
>
6268 </p
></blockquote
>
6270 <p
>This is for KDE:
</p
>
6272 <p
>Installed using apt-get, missing with aptitude
</p
>
6274 <blockquote
><p
>
6275 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6276 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6277 ghostscript-x git gnome-audio gnugo granatier gs-common
6278 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6279 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6280 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6281 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6282 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6283 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6284 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6285 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6286 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6287 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6288 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6289 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
6290 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6291 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6292 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6293 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6294 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6295 libkrossui4 libmailtools-perl libmime-tools-perl
6296 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6297 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6298 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6299 lirc luatex marble networkstatus noatun-plugins
6300 openoffice.org-writer2latex palapeli palapeli-data parley
6301 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6302 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6303 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6305 </p
></blockquote
>
6307 <p
>Installed using apt-get, removed with aptitude
</p
>
6309 <blockquote
><p
>
6310 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6311 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6312 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6313 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6314 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6315 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6316 kitchensync kiten kjumpingcube klatin klettres klickety klines
6317 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6318 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6319 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6320 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6321 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6322 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6323 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6324 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6325 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6326 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
6327 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
6328 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6329 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
6330 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
6331 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6332 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6333 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6334 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6335 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6336 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6337 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
6338 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
6339 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6340 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6341 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6342 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6343 </p
></blockquote
>
6345 <p
>Installed using aptitude, missing with apt-get
</p
>
6347 <blockquote
><p
>
6348 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6349 kdeartwork kdebase kdebase-apps kdebase-workspace
6350 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6351 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6352 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6353 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6354 xscreensaver-screensaver-bsod
6355 </p
></blockquote
>
6357 <p
>Installed using aptitude, removed with apt-get
</p
>
6359 <blockquote
><p
>
6360 kdebase-bin konq-plugins konqueror
6361 </p
></blockquote
>
6366 <title>Gnash buildbot slave and Debian kfreebsd
</title>
6367 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
6368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
6369 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
6370 <description><p
>Answering
6371 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
6372 call from the Gnash project
</a
> for
6373 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
6374 current source, I have set up a virtual KVM machine on the Debian
6375 Edu/Skolelinux virtualization host to test the git source on
6376 Debian/Squeeze. I hope this can help the developers in getting new
6377 releases out more often.
</p
>
6379 <p
>As the developers want less main-stream build platforms tested to,
6380 I have considered setting up a
<a
6381 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
6382 machine as well. I have also considered using the kfreebsd
6383 architecture in Debian as a file server in NUUG to get access to the
5
6384 TB zfs volume we currently use to store DV video. Because of this, I
6385 finally got around to do a test installation of Debian/Squeeze with
6386 kfreebsd. Installation went fairly smooth, thought I noticed some
6387 visual glitches in the cdebconf dialogs (black cursor left on the
6388 screen at random locations). Have not gotten very far with the
6389 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6390 fatal problem. Have to spend some more time on it to see if it is
6391 useful as a file server for NUUG. Will try to find time to set up a
6392 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
6397 <title>Debian in
3D
</title>
6398 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
6399 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
6400 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
6401 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
6403 <p
>3D printing is just great. I just came across this Debian logo in
6405 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
6406 thingiverse blog
</a
>.
</p
>
6411 <title>Software updates
2010-
10-
24</title>
6412 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
6413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
6414 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
6415 <description><p
>Some updates.
</p
>
6417 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
6418 raise money for the project is going well. The lower limit of
10
6419 signers was reached in
24 hours, and so far
13 people have signed it.
6420 More signers and more funding is most welcome, and I am really curious
6421 how far we can get before the time limit of December
24 is reached.
6424 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
6425 about what appear to be a great code coverage tool capable of
6426 generating code coverage stats without any changes to the source code.
6428 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
6429 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
6430 It is missing in Debian, but the git source built just fine in Squeeze
6431 after I installed libelf-dev, libdwarf-dev, pkg-config and
6432 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6433 solvable. I hope kcov make it into Debian soon.
</p
>
6435 <p
>Finally found time to wrap up the release notes for
<a
6436 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
6437 new alpha release of Debian Edu
</a
>, and just published the second
6438 alpha test release of the Squeeze based Debian Edu /
6439 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
6440 release. Give it a try if you need a complete linux solution for your
6441 school, including central infrastructure server, workstations, thin
6442 client servers and diskless workstations. A nice touch added
6443 yesterday is RDP support on the thin client servers, for windows
6444 clients to get a Linux desktop on request.
</p
>
6449 <title>Some notes on Flash in Debian and Debian Edu
</title>
6450 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
6451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
6452 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
6453 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
6454 popularity-contest numbers
</a
>, the adobe-flashplugin package the
6455 second most popular used package that is missing in Debian. The sixth
6456 most popular is flashplayer-mozilla. This is a clear indication that
6457 working flash is important for Debian users. Around
10 percent of the
6458 users submitting data to popcon.debian.org have this package
6459 installed.
</p
>
6461 <p
>In the report written by Lars Risan in August
2008
6462 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
6463 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6464 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
6465 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
6466 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
6467 web sites require Flash to work, and lacking working Flash support in
6468 the web browser and the problems with installing it was perceived as a
6469 good reason to stay with Windows.
</p
>
6471 <p
>I once saw a funny and sad comment in a web forum, where Linux was
6472 said to be the retarded cousin that did not really understand
6473 everything you told him but could work fairly well. This was a
6474 comment regarding the problems Linux have with proprietary formats and
6475 non-standard web pages, and is sad because it exposes a fairly common
6476 understanding of whose fault it is if web pages that only work in for
6477 example Internet Explorer
6 fail to work on Firefox, and funny because
6478 it explain very well how annoying it is for users when Linux
6479 distributions do not work with the documents they receive or the web
6480 pages they want to visit.
</p
>
6482 <p
>This is part of the reason why I believe it is important for Debian
6483 and Debian Edu to have a well working Flash implementation in the
6484 distribution, to get at least popular sites as Youtube and Google
6485 Video to working out of the box. For Squeeze, Debian have the chance
6486 to include the latest version of Gnash that will make this happen, as
6487 the new release
0.8.8 was published a few weeks ago and is resting in
6488 unstable. The new version work with more sites that version
0.8.7.
6489 The Gnash maintainers have asked for a freeze exception, but the
6490 release team have not had time to reply to it yet. I hope they agree
6491 with me that Flash is important for the Debian desktop users, and thus
6492 accept the new package into Squeeze.
</p
>
6497 <title>Circular package dependencies harms apt recovery
</title>
6498 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
6499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
6500 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
6501 <description><p
>I discovered this while doing
6502 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
6503 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
6504 in Debian still got circular dependencies, and it is often claimed
6505 that apt and aptitude should be able to handle this just fine, but
6506 some times these dependency loops causes apt to fail.
</p
>
6508 <p
>An example is from todays
6509 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
6510 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
6511 causes perl-modules to fail to upgrade. The cause is simple. If a
6512 package fail to unpack, then only part of packages with the circular
6513 dependency might end up being unpacked when unpacking aborts, and the
6514 ones already unpacked will fail to configure in the recovery phase
6515 because its dependencies are unavailable.
</p
>
6517 <p
>In this log, the problem manifest itself with this error:
</p
>
6519 <blockquote
><pre
>
6520 dpkg: dependency problems prevent configuration of perl-modules:
6521 perl-modules depends on perl (
>=
5.10.1-
1); however:
6522 Version of perl on system is
5.10.0-
19lenny
2.
6523 dpkg: error processing perl-modules (--configure):
6524 dependency problems - leaving unconfigured
6525 </pre
></blockquote
>
6527 <p
>The perl/perl-modules circular dependency is already
6528 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
6529 hopefully be solved as soon as possible, but it is not the only one,
6530 and each one of these loops in the dependency tree can cause similar
6531 failures. Of course, they only occur when there are bugs in other
6532 packages causing the unpacking to fail, but it is rather nasty when
6533 the failure of one package causes the problem to become worse because
6534 of dependency loops.
</p
>
6537 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
6538 tireless effort by Bill Allombert
</a
>, the number of circular
6540 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
6541 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
6543 <p
>Todays testing also exposed a bug in
6544 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
6545 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
6546 apt-get and aptitude, the latter possibly caused by some circular
6547 dependency. Reported both to BTS to try to get someone to look at
6553 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
6554 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
6555 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
6556 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
6557 <description><p
>This is a
6558 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
6560 <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
6562 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
6563 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
6565 <p
>As a step to try to see if it possible to merge the DNS and DHCP
6566 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6567 and dhcp3-server-ldap in Debian use the LDAP server. The two
6568 implementations are quite different in how they use LDAP.
</p
>
6570 To get this information, I started slapd with debugging enabled and
6571 dumped the debug output to a file to get the LDAP searches performed
6572 on a Debian Edu main-server. Here is a summary.
6574 <p
><strong
>powerdns
</strong
></p
>
6576 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
6577 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
6580 <p
>PowerDNS have two modes of operation using LDAP as its backend.
6581 One
"strict
" mode where the forward and reverse DNS lookups are done
6582 using the same LDAP objects, and a
"tree
" mode where the forward and
6583 reverse entries are in two different subtrees in LDAP with a structure
6584 based on the DNS names, as in tjener.intern and
6585 2.2.0.10.in-addr.arpa.
</p
>
6587 <p
>In tree mode, the server is set up to use a LDAP subtree as its
6588 base, and uses a
"base
" scoped search for the DNS name by adding
6589 "dc=tjener,dc=intern,
" to the base with a filter for
6590 "(associateddomain=tjener.intern)
" for the forward entry and
6591 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
6592 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
6593 forward entries, it is looking for attributes named dnsttl, arecord,
6594 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6595 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6596 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6597 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6598 spfrecord and modifytimestamp. For reverse entries it is looking for
6599 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6600 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6601 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6602 ldapsearch commands could look like this:
</p
>
6604 <blockquote
><pre
>
6605 ldapsearch -h ldap \
6606 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6607 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6608 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6609 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6610 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6611 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6613 ldapsearch -h ldap \
6614 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6615 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
6616 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6617 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6618 srvrecord naptrrecord modifytimestamp
6619 </pre
></blockquote
>
6621 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
6622 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6623 example LDAP objects used there. In addition to these objects, the
6624 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6625 also exist.
</p
>
6627 <blockquote
><pre
>
6628 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6630 objectclass: dnsdomain
6631 objectclass: domainrelatedobject
6634 associateddomain: tjener.intern
6636 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6638 objectclass: dnsdomain2
6639 objectclass: domainrelatedobject
6641 ptrrecord: tjener.intern
6642 associateddomain:
2.2.0.10.in-addr.arpa
6643 </pre
></blockquote
>
6645 <p
>In strict mode, the server behaves differently. When looking for
6646 forward DNS entries, it is doing a
"subtree
" scoped search with the
6647 same base as in the tree mode for a object with filter
6648 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
6649 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6650 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6651 naptrrecord and modifytimestamp. For reverse entires it also do a
6652 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
6653 and the requested attributes are associateddomain, dnsttl and
6654 modifytimestamp. In short, in strict mode the objects with ptrrecord
6655 go away, and the arecord attribute in the forward object is used
6658 <p
>The forward and reverse searches can be simulated using ldapsearch
6659 like this:
</p
>
6661 <blockquote
><pre
>
6662 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6663 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6664 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6665 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6666 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6667 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6669 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6670 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
6671 </pre
></blockquote
>
6673 <p
>In addition to the forward and reverse searches , there is also a
6674 search for SOA records, which behave similar to the forward and
6675 reverse lookups.
</p
>
6677 <p
>A thing to note with the PowerDNS behaviour is that it do not
6678 specify any objectclass names, and instead look for the attributes it
6679 need to generate a DNS reply. This make it able to work with any
6680 objectclass that provide the needed attributes.
</p
>
6682 <p
>The attributes are normally provided in the cosine (RFC
1274) and
6683 dnsdomain2 schemas. The latter is used for reverse entries like
6684 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
6686 <p
>In Debian Edu, we have created DNS objects using the object classes
6687 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6688 attributes) and domainrelatedobject (for associatedDomain). The use
6689 of structural object classes make it impossible to combine these
6690 classes with the object classes used by DHCP.
</p
>
6692 <p
>There are other schemas that could be used too, for example the
6693 dnszone structural object class used by Gosa and bind-sdb for the DNS
6694 attributes combined with the domainrelatedobject object class, but in
6695 this case some unused attributes would have to be included as well
6696 (zonename and relativedomainname).
</p
>
6698 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
6699 mode and not use any of the existing objectclasses (dnsdomain,
6700 dnsdomain2 and dnszone) when one want to combine the DNS information
6701 with DHCP information, and instead create a auxiliary object class
6702 defined something like this (using the attributes defined for
6703 dnsdomain and dnsdomain2 or dnszone):
</p
>
6705 <blockquote
><pre
>
6706 objectclass ( some-oid NAME
'dnsDomainAux
'
6709 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6710 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6711 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6712 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6713 A6Record $ DNAMERecord
6715 </pre
></blockquote
>
6717 <p
>This will allow any object to become a DNS entry when combined with
6718 the domainrelatedobject object class, and allow any entity to include
6719 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
6720 developers asking for their view on this schema and if they are
6721 interested in providing such schema with PowerDNS, and I hope my
6722 message will be accepted into their mailing list soon.
</p
>
6724 <p
><strong
>ISC dhcp
</strong
></p
>
6726 <p
>The DHCP server searches for specific objectclass and requests all
6727 the object attributes, and then uses the attributes it want. This
6728 make it harder to figure out exactly what attributes are used, but
6729 thanks to the working example in Debian Edu I can at least get an idea
6730 what is needed without having to read the source code.
</p
>
6732 <p
>In the DHCP server configuration, the LDAP base to use and the
6733 search filter to use to locate the correct dhcpServer entity is
6734 stored. These are the relevant entries from
6735 /etc/dhcp3/dhcpd.conf:
</p
>
6737 <blockquote
><pre
>
6738 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
6739 ldap-dhcp-server-cn
"dhcp
";
6740 </pre
></blockquote
>
6742 <p
>The DHCP server uses this information to nest all the DHCP
6743 configuration it need. The cn
"dhcp
" is located using the given LDAP
6744 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
6745 search result is this entry:
</p
>
6747 <blockquote
><pre
>
6748 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6751 objectClass: dhcpServer
6752 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6753 </pre
></blockquote
>
6755 <p
>The content of the dhcpServiceDN attribute is next used to locate the
6756 subtree with DHCP configuration. The DHCP configuration subtree base
6757 is located using a base scope search with base
"cn=DHCP
6758 Config,dc=skole,dc=skolelinux,dc=no
" and filter
6759 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
6760 The search result is this entry:
</p
>
6762 <blockquote
><pre
>
6763 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6766 objectClass: dhcpService
6767 objectClass: dhcpOptions
6768 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6769 dhcpStatements: ddns-update-style none
6770 dhcpStatements: authoritative
6771 dhcpOption: smtp-server code
69 = array of ip-address
6772 dhcpOption: www-server code
72 = array of ip-address
6773 dhcpOption: wpad-url code
252 = text
6774 </pre
></blockquote
>
6776 <p
>Next, the entire subtree is processed, one level at the time. When
6777 all the DHCP configuration is loaded, it is ready to receive requests.
6778 The subtree in Debian Edu contain objects with object classes
6779 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6780 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6781 and information about netmasks, dynamic range etc. Leaving out the
6782 details here because it is not relevant for the focus of my
6783 investigation, which is to see if it is possible to merge dns and dhcp
6784 related computer objects.
</p
>
6786 <p
>When a DHCP request come in, LDAP is searched for the MAC address
6787 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
6788 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
6789 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6790 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
6793 <blockquote
><pre
>
6794 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6797 objectClass: dhcpHost
6798 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6799 dhcpStatements: fixed-address hostname
6800 </pre
></blockquote
>
6802 <p
>There is less flexiblity in the way LDAP searches are done here.
6803 The object classes need to have fixed names, and the configuration
6804 need to be stored in a fairly specific LDAP structure. On the
6805 positive side, the invidiual dhcpHost entires can be anywhere without
6806 the DN pointed to by the dhcpServer entries. The latter should make
6807 it possible to group all host entries in a subtree next to the
6808 configuration entries, and this subtree can also be shared with the
6809 DNS server if the schema proposed above is combined with the dhcpHost
6810 structural object class.
6812 <p
><strong
>Conclusion
</strong
></p
>
6814 <p
>The PowerDNS implementation seem to be very flexible when it come
6815 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
6816 come to the the LDAP structure, the
"strict
" mode is very flexible,
6817 allowing DNS objects to be stored anywhere under the base cn specified
6818 in the configuration.
</p
>
6820 <p
>The DHCP implementation on the other hand is very inflexible, both
6821 regarding which LDAP schemas to use and which LDAP structure to use.
6822 I guess one could implement ones own schema, as long as the
6823 objectclasses and attributes have the names used, but this do not
6824 really help when the DHCP subtree need to have a fairly fixed
6825 structure.
</p
>
6827 <p
>Based on the observed behaviour, I suspect a LDAP structure like
6828 this might work for Debian Edu:
</p
>
6830 <blockquote
><pre
>
6832 cn=machine-info (dhcpService) - dhcpServiceDN points here
6833 cn=dhcp (dhcpServer)
6834 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6835 cn=
10.0.2.0 (dhcpSubnet)
6836 cn=group1 (dhcpGroup/dhcpOptions)
6837 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6838 cn=
192.168.0.0 (dhcpSubnet)
6839 cn=group1 (dhcpGroup/dhcpOptions)
6840 ou=machines - PowerDNS base points here
6841 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6842 </pre
></blockquote
>
6844 <P
>This is not tested yet. If the DHCP server require the dhcpHost
6845 entries to be in the dhcpGroup subtrees, the entries can be stored
6846 there instead of a common machines subtree, and the PowerDNS base
6847 would have to be moved one level up to the machine-info subtree.
</p
>
6849 <p
>The combined object under the machines subtree would look something
6850 like this:
</p
>
6852 <blockquote
><pre
>
6853 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6856 objectClass: dhcpHost
6857 objectclass: domainrelatedobject
6858 objectclass: dnsDomainAux
6859 associateddomain: hostname.intern
6860 arecord:
10.11.12.13
6861 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6862 dhcpStatements: fixed-address hostname.intern
6863 </pre
></blockquote
>
6865 </p
>One could even add the LTSP configuration associated with a given
6866 machine, as long as the required attributes are available in a
6867 auxiliary object class.
</p
>
6872 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
6873 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
6874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
6875 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
6876 <description><p
>For a while now, I have wanted to find a way to change the DNS and
6877 DHCP services in Debian Edu to use the same LDAP objects for a given
6878 computer, to avoid the possibility of having a inconsistent state for
6879 a computer in LDAP (as in DHCP but no DNS entry or the other way
6880 around) and make it easier to add computers to LDAP.
</p
>
6882 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
6883 information finally found a solution that seem to work.
</p
>
6885 <p
>The old setup required three LDAP objects for a given computer.
6886 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6887 we switch powerdns to use its strict LDAP method (ldap-method=strict
6888 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6889 merged into one while making it impossible to transfer the reverse map
6890 to a slave DNS server.
</p
>
6892 <p
>If we also replace the object class used to get the DNS related
6893 attributes to one allowing these attributes to be combined with the
6894 dhcphost object class, we can merge the DNS and DHCP entries into one.
6895 I
've written such object class in the dnsdomainaux.schema file (need
6896 proper OIDs, but that is a minor issue), and tested the setup. It
6897 seem to work.
</p
>
6899 <p
>With this test setup in place, we can get away with one LDAP object
6900 for both DNS and DHCP, and even the LTSP configuration I suggested in
6901 an earlier email. The combined LDAP object will look something like
6904 <blockquote
><pre
>
6905 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6907 objectClass: dhcphost
6908 objectclass: domainrelatedobject
6909 objectclass: dnsdomainaux
6910 associateddomain: hostname.intern
6911 arecord:
10.11.12.13
6912 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
6913 dhcpstatements: fixed-address hostname
6915 </pre
></blockquote
>
6917 <p
>The DNS server uses the associateddomain and arecord entries, while
6918 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6919 before asking DNS to resolve the fixed-adddress. LTSP will use
6920 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
6922 <p
>I am not yet sure if I can get the DHCP server to look for its
6923 dhcphost in a different location, to allow us to put the objects
6924 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
6925 that. If I can
't figure out a way to do that, we can still get rid of
6926 the hosts subtree and move all its content into the DHCP Config tree
6927 (which probably should be renamed to be more related to the new
6928 content. I suspect cn=dnsdhcp,ou=services or something like that
6929 might be a good place to put it.
</p
>
6931 <p
>If you want to help out with implementing this for Debian Edu,
6932 please contact us on debian-edu@lists.debian.org.
</p
>
6937 <title>Idea for storing LTSP configuration in LDAP
</title>
6938 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
6939 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
6940 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
6941 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
6942 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6943 clients, and that this can be used to fetch configuration from LDAP if
6944 Debian Edu choose to store configuration there.
</p
>
6946 <p
>Armed with this information, I got inspired and wrote a test module
6947 to get configuration from LDAP. The idea is to look up the MAC
6948 address of the client in LDAP, and look for attributes on the form
6949 ltspconfigsetting=value, and use this to export SETTING=value to the
6950 LTSP clients.
</p
>
6952 <p
>The goal is to be able to store the LTSP configuration attributes
6953 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
6954 allowing us to store all information about a computer in one place.
</p
>
6956 <p
>This is a untested draft implementation, and I welcome feedback on
6957 this approach. A real LDAP schema for the ltspClientAux objectclass
6958 need to be written. Comments, suggestions, etc?
</p
>
6960 <blockquote
><pre
>
6961 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6963 # Fetch LTSP client settings from LDAP based on MAC address
6965 # Uses ethernet address as stored in the dhcpHost objectclass using
6966 # the dhcpHWAddress attribute or ethernet address stored in the
6967 # ieee802Device objectclass with the macAddress attribute.
6969 # This module is written to be schema agnostic, and only depend on the
6970 # existence of attribute names.
6972 # The LTSP configuration variables are saved directly using a
6973 # ltspConfig prefix and uppercasing the rest of the attribute name.
6974 # To set the SERVER variable, set the ltspConfigServer attribute.
6976 # Some LDAP schema should be created with all the relevant
6977 # configuration settings. Something like this should work:
6979 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
6982 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6984 LDAPSERVER=$(debian-edu-ldapserver)
6985 if [
"$LDAPSERVER
" ] ; then
6986 LDAPBASE=$(debian-edu-ldapserver -b)
6987 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
6988 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
6989 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
6990 grep
'^ltspConfig
' | while read attr value ; do
6991 # Remove prefix and convert to upper case
6992 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
6993 # bass value on to clients
6994 eval
"$attr=$value; export $attr
"
6998 </pre
></blockquote
>
7000 <p
>I
'm not sure this shell construction will work, because I suspect
7001 the while block might end up in a subshell causing the variables set
7002 there to not show up in ltsp-config, but if that is the case I am sure
7003 the code can be restructured to make sure the variables are passed on.
7004 I expect that can be solved with some testing. :)
</p
>
7006 <p
>If you want to help out with implementing this for Debian Edu,
7007 please contact us on debian-edu@lists.debian.org.
</p
>
7009 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7010 configuration in LDAP that was created around year
2000 by
7011 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7012 Xperience, Inc.,
2000</a
>. I found its
7013 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7014 personal home page over at redhat.com.
</p
>
7019 <title>jXplorer, a very nice LDAP GUI
</title>
7020 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7021 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7022 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7023 <description><p
>Since
7024 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7025 last post
</a
> about available LDAP tools in Debian, I was told about a
7026 LDAP GUI that is even better than luma. The java application
7027 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7028 moving LDAP objects and subtrees using drag-and-drop, and can
7029 authenticate using Kerberos. I have only tested the Kerberos
7030 authentication, but do not have a LDAP setup allowing me to rewrite
7031 LDAP with my test user yet. It is
7032 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7033 Debian
</a
> testing and unstable at the moment. The only problem I
7034 have with it is how it handle errors. If something go wrong, its
7035 non-intuitive behaviour require me to go through some query work list
7036 and remove the failing query. Nothing big, but very annoying.
</p
>
7041 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7042 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7043 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7044 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7045 <description><p
>Here is a short update on my
<a
7046 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7047 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7048 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7049 not reporting the status for KDE, because the upgrade crashes when
7050 aptitude try because of missing conflicts
7051 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7052 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7054 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7055 complete list of the installed packages. Based on this I see these
7056 differences when I did a test run today. As usual, I do not really
7057 know what the correct set of packages would be, but thought it best to
7058 publish the difference.
</p
>
7060 <p
>Installed using apt-get, missing with aptitude
</p
>
7062 <blockquote
><p
>
7063 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7064 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7065 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7066 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7067 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7068 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7069 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7070 python-gtkmozembed svgalibg1 xserver-xephyr zip
7071 </p
></blockquote
>
7073 <p
>Installed using apt-get, removed with aptitude
</p
>
7075 <blockquote
><p
>
7076 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7077 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7078 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7079 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7080 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7081 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7082 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7083 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7084 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7085 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
7086 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
7087 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
7088 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7089 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
7090 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7091 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
7092 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
7093 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7094 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7095 mysql-common swfdec-gnome totem-gstreamer wodim
7096 </p
></blockquote
>
7098 <p
>Installed using aptitude, missing with apt-get
</p
>
7100 <blockquote
><p
>
7101 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7102 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7103 xserver-xorg-input-all xserver-xorg-input-evdev
7104 xserver-xorg-input-kbd xserver-xorg-input-mouse
7105 xserver-xorg-input-synaptics xserver-xorg-video-all
7106 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7107 xserver-xorg-video-chips xserver-xorg-video-cirrus
7108 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7109 xserver-xorg-video-glint xserver-xorg-video-i128
7110 xserver-xorg-video-i740 xserver-xorg-video-mach64
7111 xserver-xorg-video-mga xserver-xorg-video-neomagic
7112 xserver-xorg-video-nouveau xserver-xorg-video-nv
7113 xserver-xorg-video-r128 xserver-xorg-video-radeon
7114 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7115 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7116 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7117 xserver-xorg-video-sis xserver-xorg-video-sisusb
7118 xserver-xorg-video-tdfx xserver-xorg-video-tga
7119 xserver-xorg-video-trident xserver-xorg-video-tseng
7120 xserver-xorg-video-vesa xserver-xorg-video-vmware
7121 xserver-xorg-video-voodoo
7122 </p
></blockquote
>
7124 <p
>Installed using aptitude, removed with apt-get
</p
>
7126 <blockquote
><p
>
7127 deskbar-applet xserver-xorg xserver-xorg-core
7128 xserver-xorg-input-wacom xserver-xorg-video-intel
7129 xserver-xorg-video-openchrome
7130 </p
></blockquote
>
7132 <p
>I was told on IRC that the xorg-xserver package was
7133 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
7134 in git
</a
> today to try to get apt-get to not remove xorg completely.
7135 No idea when it hits Squeeze, but when it does I hope it will reduce
7136 the difference somewhat.
7141 <title>LUMA, a very nice LDAP GUI
</title>
7142 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
7143 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
7144 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
7145 <description><p
>The last few days I have been looking into the status of the LDAP
7146 directory in Debian Edu, and in the process I started to miss a GUI
7147 tool to browse the LDAP tree. The only one I was able to find in
7148 Debian/Squeeze and Lenny is
7149 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
7150 be a great tool to get a overview of the current LDAP directory
7151 populated by default in Skolelinux. Thanks to it, I have been able to
7152 find empty and obsolete subtrees, misplaced objects and duplicate
7153 objects. It will be installed by default in Debian/Squeeze. If you
7154 are working with LDAP, give it a go. :)
</p
>
7156 <p
>I did notice one problem with it I have not had time to report to
7157 the BTS yet. There is no .desktop file in the package, so the tool do
7158 not show up in the Gnome and KDE menus, but only deep down in in the
7159 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7162 <p
>I have not yet been able to get it to modify the tree yet. I would
7163 like to move objects and remove subtrees directly in the GUI, but have
7164 not found a way to do that with LUMA yet. So in the mean time, I use
7165 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
7167 <p
>If you have tips on other GUI tools for LDAP that might be useful
7168 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
7170 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
7171 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
7172 useful GUI alternative. It seem like a good tool, but is unmaintained
7173 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7174 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
7179 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
7180 <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>
7181 <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>
7182 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
7183 <description><p
>A while back, I
7184 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
7185 about the fact
</a
> that it is not possible with the provided schemas
7186 for storing DNS and DHCP information in LDAP to combine the two sets
7187 of information into one LDAP object representing a computer.
</p
>
7189 <p
>In the mean time, I discovered that a simple fix would be to make
7190 the dhcpHost object class auxiliary, to allow it to be combined with
7191 the dNSDomain object class, and thus forming one object for one
7192 computer when storing both DHCP and DNS information in LDAP.
</p
>
7194 <p
>If I understand this correctly, it is not safe to do this change
7195 without also changing the assigned number for the object class, and I
7196 do not know enough about LDAP schema design to do that properly for
7197 Debian Edu.
</p
>
7199 <p
>Anyway, for future reference, this is how I believe we could change
7201 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
7202 schema
</a
> to solve at least part of the problem with the LDAP schemas
7203 available today from IETF.
</p
>
7206 --- dhcp.schema (revision
65192)
7207 +++ dhcp.schema (working copy)
7209 objectclass (
2.16.840.1.113719.1.203.6.6
7210 NAME
'dhcpHost
'
7211 DESC
'This represents information about a particular client
'
7215 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7216 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7219 <p
>I very much welcome clues on how to do this properly for Debian
7220 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7221 package, and should thus be free to rewrite it as we see fit.
</p
>
7223 <p
>If you want to help out with implementing this for Debian Edu,
7224 please contact us on debian-edu@lists.debian.org.
</p
>
7229 <title>Calling tasksel like the installer, while still getting useful output
</title>
7230 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7231 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7232 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7233 <description><p
>A few times I have had the need to simulate the way tasksel
7234 installs packages during the normal debian-installer run. Until now,
7235 I have ended up letting tasksel do the work, with the annoying problem
7236 of not getting any feedback at all when something fails (like a
7237 conffile question from dpkg or a download that fails), using code like
7240 <blockquote
><pre
>
7241 export DEBIAN_FRONTEND=noninteractive
7242 tasksel --new-install
7243 </pre
></blockquote
>
7245 This would invoke tasksel, let its automatic task selection pick the
7246 tasks to install, and continue to install the requested tasks without
7247 any output what so ever.
7249 Recently I revisited this problem while working on the automatic
7250 package upgrade testing, because tasksel would some times hang without
7251 any useful feedback, and I want to see what is going on when it
7252 happen. Then it occured to me, I can parse the output from tasksel
7253 when asked to run in test mode, and use that aptitude command line
7254 printed by tasksel then to simulate the tasksel run. I ended up using
7257 <blockquote
><pre
>
7258 export DEBIAN_FRONTEND=noninteractive
7259 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7261 </pre
></blockquote
>
7263 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7264 --without-recommends -o APT::Install-Recommends=no -y install
7265 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7266 ~pimportant
</tt
>", which will install the gnome desktop task, the
7267 laptop task and all packages with priority standard , required and
7268 important, just like tasksel would have done it during
7269 installation.
</p
>
7271 <p
>A better approach is probably to extend tasksel to be able to
7272 install packages without using debconf-apt-progress, for use cases
7273 like this.
</p
>
7278 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
7279 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
7280 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
7281 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
7282 <description><p
>My
7283 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
7284 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
7285 finally made the upgrade logs available from
7286 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
7287 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7288 apt and aptitude, and found their differences interesting. This time
7289 I will only focus on their removal plans.
</p
>
7291 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
7292 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
7293 surprising part is that it want to remove xorg and all
7294 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7295 sure why. When asking aptitude to do the same, it want to remove
129
7296 packages, but most of them are library packages I suspect are no
7297 longer needed. Both of them want to remove bluetooth packages, which
7298 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
7300 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
7301 which seem like a bad idea and xorg the same way as with Gnome. Asking
7302 aptitude for the same, it wants to remove
192 packages, none which are
7303 too surprising.
</p
>
7305 <p
>I guess the removal of xorg during upgrades should be investigated
7306 and avoided, and perhaps others as well. Here are the complete list
7307 of planned removals. The complete logs is available from the URL
7308 above. Note if you want to repeat these tests, that the upgrade test
7309 for kde+apt-get hung in the tasksel setup because of dpkg asking
7310 conffile questions. No idea why. I worked around it by using
7311 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
7314 <p
><b
>apt-get gnome
72</b
>
7315 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
7316 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7317 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
7318 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7319 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7320 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7321 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7322 xserver-xorg-input-kbd xserver-xorg-input-mouse
7323 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7324 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7325 xserver-xorg-video-ati xserver-xorg-video-chips
7326 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7327 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7328 xserver-xorg-video-glint xserver-xorg-video-i128
7329 xserver-xorg-video-i740 xserver-xorg-video-imstt
7330 xserver-xorg-video-intel xserver-xorg-video-mach64
7331 xserver-xorg-video-mga xserver-xorg-video-neomagic
7332 xserver-xorg-video-nsc xserver-xorg-video-nv
7333 xserver-xorg-video-openchrome xserver-xorg-video-r128
7334 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7335 xserver-xorg-video-rendition xserver-xorg-video-s3
7336 xserver-xorg-video-s3virge xserver-xorg-video-savage
7337 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7338 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7339 xserver-xorg-video-tga xserver-xorg-video-trident
7340 xserver-xorg-video-tseng xserver-xorg-video-v4l
7341 xserver-xorg-video-vesa xserver-xorg-video-vga
7342 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
7343 xulrunner-
1.9-gnome-support
</p
>
7345 <p
><b
>aptitude gnome
129</b
>
7347 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
7348 djvulibre-desktop finger gnome-app-install gnome-mount
7349 gnome-network-admin gnome-spell gnome-vfs-obexftp
7350 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7351 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7352 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7353 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
7354 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
7355 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
7356 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
7357 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
7358 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
7359 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
7360 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
7361 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
7362 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7363 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
7364 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
7365 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
7366 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
7367 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
7368 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7369 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7370 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7371 openoffice.org-writer2latex openssl-blacklist p7zip
7372 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
7373 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7374 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7375 swfdec-mozilla totem-gstreamer update-manager wodim
7376 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7377 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7380 <p
><b
>apt-get kde
82</b
>
7382 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7383 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7384 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7385 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7386 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7387 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7388 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7389 xserver-xorg-input-kbd xserver-xorg-input-mouse
7390 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7391 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7392 xserver-xorg-video-ati xserver-xorg-video-chips
7393 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7394 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7395 xserver-xorg-video-glint xserver-xorg-video-i128
7396 xserver-xorg-video-i740 xserver-xorg-video-imstt
7397 xserver-xorg-video-intel xserver-xorg-video-mach64
7398 xserver-xorg-video-mga xserver-xorg-video-neomagic
7399 xserver-xorg-video-nsc xserver-xorg-video-nv
7400 xserver-xorg-video-openchrome xserver-xorg-video-r128
7401 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7402 xserver-xorg-video-rendition xserver-xorg-video-s3
7403 xserver-xorg-video-s3virge xserver-xorg-video-savage
7404 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7405 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7406 xserver-xorg-video-tga xserver-xorg-video-trident
7407 xserver-xorg-video-tseng xserver-xorg-video-v4l
7408 xserver-xorg-video-vesa xserver-xorg-video-vga
7409 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
7411 <p
><b
>aptitude kde
192</b
>
7412 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
7413 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7414 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7415 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7416 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7417 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7418 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7419 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7420 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7421 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7422 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7423 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7424 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7425 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7426 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7427 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7428 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7429 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7430 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
7431 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7432 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7433 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
7434 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7435 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7436 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7437 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7438 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7439 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
7440 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
7441 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7442 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7443 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7444 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7445 texlive-common texlive-doc-base texlive-fonts-recommended
7446 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7447 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7448 xulrunner-
1.9</p
>
7454 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
7455 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
7456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
7457 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
7458 <description><p
>The last few days I have done some upgrade testing in Debian, to
7459 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7460 have been discovered and reported in the process
7461 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
7462 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
7463 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
7464 kdebase-workspace-data), and to get a more regular testing going on, I
7465 am working on a script to automate the test.
</p
>
7467 <p
>The idea is to create a Lenny chroot and use tasksel to install a
7468 Gnome or KDE desktop installation inside the chroot before upgrading
7469 it. To ensure no services are started in the chroot, a policy-rc.d
7470 script is inserted. To make sure tasksel believe it is to install a
7471 desktop on a laptop, the tasksel tests are replaced in the chroot
7472 (only acceptable because this is a throw-away chroot).
</p
>
7474 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7475 currently always fail because udev refuses to upgrade with the kernel
7476 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7477 is created. The bug report
7478 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
7479 this problem do not trigger in a chroot, but I touch the file anyway
7480 to make sure the upgrade go well. Testing on virtual and real
7481 hardware have failed me because of udev so far, and creating this file
7482 do the trick in such settings anyway. This is a
7483 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
7484 issue
</a
> and the current udev behaviour is intended by the udev
7485 maintainer because he lack the resources to rewrite udev to keep
7486 working with old kernels or something like that. I really wish the
7487 udev upstream would keep udev backwards compatible, to avoid such
7488 upgrade problem, but given that they fail to do so, I guess
7489 documenting the way out of this mess is the best option we got for
7490 Debian Squeeze.
</p
>
7492 <p
>Anyway, back to the task at hand, testing upgrades. This test
7493 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
7496 <blockquote
><pre
>
7500 if [
"$
1" ] ; then
7509 exec
&lt; /dev/null
7511 mirror=http://ftp.skolelinux.org/debian
7512 tmpdir=chroot-$from-upgrade-$to-$desktop
7514 debootstrap $from $tmpdir $mirror
7515 chroot $tmpdir aptitude update
7516 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
7520 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7524 mount -t proc proc $tmpdir/proc
7525 # Make sure proc is unmounted also on failure
7526 trap exit_cleanup EXIT INT
7528 chroot $tmpdir aptitude -y install debconf-utils
7530 # Make sure tasksel autoselection trigger. It need the test scripts
7531 # to return the correct answers.
7532 echo tasksel tasksel/desktop multiselect $desktop | \
7533 chroot $tmpdir debconf-set-selections
7535 # Include the desktop and laptop task
7536 for test in desktop laptop ; do
7537 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
7541 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7544 DEBIAN_FRONTEND=noninteractive
7545 DEBIAN_PRIORITY=critical
7546 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7547 chroot $tmpdir tasksel --new-install
7549 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
7550 chroot $tmpdir aptitude update
7551 touch $tmpdir/etc/udev/kernel-upgrade
7552 chroot $tmpdir aptitude -y dist-upgrade
7554 </pre
></blockquote
>
7556 <p
>I suspect it would be useful to test upgrades with both apt-get and
7557 with aptitude, but I have not had time to look at how they behave
7558 differently so far. I hope to get a cron job running to do the test
7559 regularly and post the result on the web. The Gnome upgrade currently
7560 work, while the KDE upgrade fail because of the bug in
7561 kdebase-workspace-data
</p
>
7563 <p
>I am not quite sure what kind of extract from the huge upgrade logs
7564 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
7565 post, so I will refrain from trying. I can report that for Gnome,
7566 aptitude report
760 packages upgraded,
448 newly installed,
129 to
7567 remove and
1 not upgraded and
1024MB need to be downloaded while for
7568 KDE the same numbers are
702 packages upgraded,
507 newly installed,
7569 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
7571 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
7572 is able to migrate to dependency based boot sequencing and parallel
7573 booting without a hitch. Was unsure if there were still bugs with
7574 packages failing to clean up their obsolete init.d script during
7575 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7581 <title>Upstart or sysvinit - as init.d scripts see it
</title>
7582 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
7583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
7584 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
7585 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
7586 scripts to migrate (some of) their operations to upstart job while
7587 keeping the init.d for hurd and kfreebsd. The packages with such
7588 needs will need a way to get their init.d scripts to behave
7589 differently when used with sysvinit and with upstart. Because of
7590 this, I had a look at the environment variables set when a init.d
7591 script is running under upstart, and when it is not.
</p
>
7593 <p
>With upstart, I notice these environment variables are set when a
7594 script is started from rcS.d/ (ignoring some irrelevant ones like
7597 <blockquote
><pre
>
7603 UPSTART_EVENTS=startup
7605 UPSTART_JOB=rc-sysinit
7606 </pre
></blockquote
>
7608 <p
>With sysvinit, these environment variables are set for the same
7611 <blockquote
><pre
>
7612 INIT_VERSION=sysvinit-
2.88
7617 </pre
></blockquote
>
7619 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
7620 sysvinit are not set by upstart. Not sure if it is intentional or not
7621 to not be compatible with sysvinit in this regard.
</p
>
7623 <p
>For scripts needing to behave differently when upstart is used,
7624 looking for the UPSTART_JOB environment variable seem to be a good
7630 <title>A manual for standards wars...
</title>
7631 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
7632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
7633 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
7634 <description><p
>Via the
7635 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
7636 of Rob Weir
</a
> I came across the very interesting essay named
7637 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
7638 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
7639 following the standards wars of today.
</p
>
7644 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
7645 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
7646 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
7647 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
7648 <description><p
>When using sitesummary at a site to track machines, it is possible
7649 to get a list of the machine types in use thanks to the DMI
7650 information extracted from each machine. The script to do so is
7651 included in the sitesummary package, and here is example output from
7652 the Skolelinux build servers:
</p
>
7654 <blockquote
><pre
>
7655 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7657 Dell Computer Corporation
1
7660 eserver xSeries
345 -[
8670M1X]-
1
7664 </pre
></blockquote
>
7666 <p
>The quality of the report depend on the quality of the DMI tables
7667 provided in each machine. Here there are Intel machines without model
7668 information listed with Intel as vendor and no model, and virtual Xen
7669 machines listed as [no-dmi-info]. One can add -l as a command line
7670 option to list the individual machines.
</p
>
7672 <p
>A larger list is
7673 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
7674 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
7675 provide the basic sitesummary report publicly. In their report there
7676 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
7677 their machines, and as sitesummary is available in both distributions,
7678 it is trivial to get all of them to report to the same central
7679 collector.
</p
>
7684 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
7685 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
7686 <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>
7687 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
7688 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
7689 start at boot when an NVidia video card is used is handled. The
7690 problem seem to be that the nvidia X.org driver uses a long time to
7691 initialize, and this duration is longer than kdm is configured to
7694 <p
>I came across two bugs related to this issue,
7695 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
7696 against initscripts and passed on to nvidia-glx when it became obvious
7697 that the nvidia drivers were involved, and
7698 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
7699 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
7701 <p
>To me, it seem that no-one is interested in actually solving the
7702 problem nvidia video card owners experience and make sure the Debian
7703 distribution work out of the box for these users. The nvidia driver
7704 maintainers expect kdm to be set up to wait longer, while kdm expect
7705 the nvidia driver maintainers to fix the driver to start faster, and
7706 while they wait for each other I guess the users end up switching to a
7707 distribution that work for them. I have no idea what the solution is,
7708 but I am pretty sure that waiting for each other is not it.
</p
>
7710 <p
>I wonder why we end up handling bugs this way.
</p
>
7715 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
7716 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
7717 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
7718 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
7719 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
7720 The feature seem to hold up pretty well, but three fairly serious
7721 issues are known and should be solved:
7725 <li
>The wicd package seen to
7726 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
7727 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
7728 parallel booting is enabled. No idea why, but the wicd maintainer
7729 seem to be on the case.
</li
>
7731 <li
>The nvidia X driver seem to
7732 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
7733 triggered more easily when parallel booting is in effect. The
7734 maintainer is on the case.
</li
>
7736 <li
>The sysv-rc package fail to properly enable dependency based boot
7737 sequencing (the shutdown is broken) when old file-rc users
7738 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
7739 sysv-rc. One way to solve it would be for file-rc to create
7740 /etc/init.d/.legacy-bootordering, and another is to try to make
7741 sysv-rc more robust. Will investigate some more and probably upload a
7742 workaround in sysv-rc to help those trying to move from file-rc to
7743 sysv-rc get a working shutdown.
</li
>
7745 </ul
></p
>
7747 <p
>All in all not many surprising issues, and all of them seem
7748 solvable before Squeeze is released. In addition to these there are
7749 some packages with bugs in their dependencies and run level settings,
7750 which I expect will be fixed in a reasonable time span.
</p
>
7752 <p
>If you report any problems with dependencies in init.d scripts to
7753 the BTS, please usertag the report to get it to show up at
7754 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7755 list of usertagged bugs related to this
</a
>.
</p
>
7757 <p
>Update: Correct bug number to file-rc issue.
</p
>
7762 <title>More flexible firmware handling in debian-installer
</title>
7763 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
7764 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
7765 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
7766 <description><p
>After a long break from debian-installer development, I finally
7767 found time today to return to the project. Having to spend less time
7768 working dependency based boot in debian, as it is almost complete now,
7769 definitely helped freeing some time.
</p
>
7771 <p
>A while back, I ran into a problem while working on Debian Edu. We
7772 include some firmware packages on the Debian Edu CDs, those needed to
7773 get disk and network controllers working. Without having these
7774 firmware packages available during installation, it is impossible to
7775 install Debian Edu on the given machine, and because our target group
7776 are non-technical people, asking them to provide firmware packages on
7777 an external medium is a support pain. Initially, I expected it to be
7778 enough to include the firmware packages on the CD to get
7779 debian-installer to find and use them. This proved to be wrong.
7780 Next, I hoped it was enough to symlink the relevant firmware packages
7781 to some useful location on the CD (tried /cdrom/ and
7782 /cdrom/firmware/). This also proved to not work, and at this point I
7783 found time to look at the debian-installer code to figure out what was
7784 going to work.
</p
>
7786 <p
>The firmware loading code is in the hw-detect package, and a closer
7787 look revealed that it would only look for firmware packages outside
7788 the installation media, so the CD was never checked for firmware
7789 packages. It would only check USB sticks, floppies and other
7790 "external
" media devices. Today I changed it to also look in the
7791 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7792 solve the problem I ran into with Debian edu. I also changed it to
7793 look in /firmware/, to make sure the installer also find firmware
7794 provided in the initrd when booting the installer via PXE, to allow us
7795 to provide the same feature in the PXE setup included in Debian
7798 <p
>To make sure firmware deb packages with a license questions are not
7799 activated without asking if the license is accepted, I extended
7800 hw-detect to look for preinst scripts in the firmware packages, and
7801 run these before activating the firmware during installation. The
7802 license question is asked using debconf in the preinst, so this should
7803 solve the issue for the firmware packages I have looked at so far.
</p
>
7805 <p
>If you want to discuss the details of these features, please
7806 contact us on debian-boot@lists.debian.org.
</p
>
7811 <title>Parallellized boot is now the default in Debian/unstable
</title>
7812 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
7813 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
7814 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
7815 <description><p
>Since this evening, parallel booting is the default in
7816 Debian/unstable for machines using dependency based boot sequencing.
7817 Apparently the testing of concurrent booting has been wider than
7818 expected, if I am to believe the
7819 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7820 on debian-devel@
</a
>, and I concluded a few days ago to move forward
7821 with the feature this weekend, to give us some time to detect any
7822 remaining problems before Squeeze is frozen. If serious problems are
7823 detected, it is simple to change the default back to sequential boot.
7824 The upload of the new sysvinit package also activate a new upstream
7827 More information about
7828 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7829 based boot sequencing
</a
> is available from the Debian wiki. It is
7830 currently possible to disable parallel booting when one run into
7831 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
7833 <blockquote
><pre
>
7835 </pre
></blockquote
>
7837 <p
>If you report any problems with dependencies in init.d scripts to
7838 the BTS, please usertag the report to get it to show up at
7839 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7840 list of usertagged bugs related to this
</a
>.
</p
>
7845 <title>Sitesummary tip: Listing MAC address of all clients
</title>
7846 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
7847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
7848 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
7849 <description><p
>In the recent Debian Edu versions, the
7850 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
7851 system
</a
> is used to keep track of the machines in the school
7852 network. Each machine will automatically report its status to the
7853 central server after boot and once per night. The network setup is
7854 also reported, and using this information it is possible to get the
7855 MAC address of all network interfaces in the machines. This is useful
7856 to update the DHCP configuration.
</p
>
7858 <p
>To give some idea how to use sitesummary, here is a one-liner to
7859 ist all MAC addresses of all machines reporting to sitesummary. Run
7860 this on the collector host:
</p
>
7862 <blockquote
><pre
>
7863 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
7864 </pre
></blockquote
>
7866 <p
>This will list all MAC addresses assosiated with all machine, one
7867 line per machine and with space between the MAC addresses.
</p
>
7869 <p
>To allow system administrators easier job at adding static DHCP
7870 addresses for hosts, it would be possible to extend this to fetch
7871 machine information from sitesummary and update the DHCP and DNS
7872 tables in LDAP using this information. Such tool is unfortunately not
7873 written yet.
</p
>
7878 <title>systemd, an interesting alternative to upstart
</title>
7879 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
7880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
7881 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
7882 <description><p
>The last few days a new boot system called
7883 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
7885 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
7887 to the free software world. I have not yet had time to play around
7888 with it, but it seem to be a very interesting alternative to
7889 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
7890 a good alternative for Debian when we are able to switch to an event
7891 based boot system. Tollef is
7892 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
7893 systemd into Debian, and I look forward to seeing how well it work. I
7894 like the fact that systemd handles init.d scripts with dependency
7895 information natively, allowing them to run in parallel where upstart
7896 at the moment do not.
</p
>
7898 <p
>Unfortunately do systemd have the same problem as upstart regarding
7899 platform support. It only work on recent Linux kernels, and also need
7900 some new kernel features enabled to function properly. This means
7901 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7902 system. Not sure how that will be handled if systemd proves to be the
7903 way forward.
</p
>
7905 <p
>In the mean time, based on the
7906 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7907 on debian-devel@
</a
> regarding parallel booting in Debian, I have
7908 decided to enable full parallel booting as the default in Debian as
7909 soon as possible (probably this weekend or early next week), to see if
7910 there are any remaining serious bugs in the init.d dependencies. A
7911 new version of the sysvinit package implementing this change is
7912 already in experimental. If all go well, Squeeze will be released
7913 with parallel booting enabled by default.
</p
>
7918 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
7919 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
7920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
7921 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
7922 <description><p
>These days, the init.d script dependencies in Squeeze are quite
7923 complete, so complete that it is actually possible to run all the
7924 init.d scripts in parallell based on these dependencies. If you want
7925 to test your Squeeze system, make sure
7926 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7927 based boot sequencing
</a
> is enabled, and add this line to
7928 /etc/default/rcS:
</p
>
7930 <blockquote
><pre
>
7931 CONCURRENCY=makefile
7932 </pre
></blockquote
>
7934 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
7935 scripts in parallel using the dependency information stored in
7936 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7937 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7938 to try to start the kdm and gdm scripts as early as possible, and will
7939 start the facilities required by kdm or gdm as early as possible to
7940 make this happen.
</p
>
7942 <p
>Give it a try, and see if you like the result. If some services
7943 fail to start properly, it is most likely because they have incomplete
7944 init.d script dependencies in their startup script (or some of their
7945 dependent scripts have incomplete dependencies). Report bugs and get
7946 the package maintainers to fix it. :)
</p
>
7948 <p
>Running scripts in parallel could be the default in Debian when we
7949 manage to get the init.d script dependencies complete and correct. I
7950 expect we will get there in Squeeze+
1, if we get manage to test and
7951 fix the remaining issues.
</p
>
7953 <p
>If you report any problems with dependencies in init.d scripts to
7954 the BTS, please usertag the report to get it to show up at
7955 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7956 list of usertagged bugs related to this
</a
>.
</p
>
7961 <title>Debian has switched to dependency based boot sequencing
</title>
7962 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
7963 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
7964 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
7965 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
7966 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
7967 have been migrated to using dependency based boot sequencing. This
7968 conclude work me and others have been doing for the last three days.
7969 It feels great to see this finally part of the default Debian
7970 installation. Now we just need to weed out the last few problems that
7971 are bound to show up, to get everything ready for Squeeze.
</p
>
7973 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
7974 fixing the more fundamental problem of handing the event based
7975 non-predictable kernel in the early boot.
</p
>
7980 <title>Taking over sysvinit development
</title>
7981 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
7982 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
7983 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
7984 <description><p
>After several years of frustration with the lack of activity from
7985 the existing sysvinit upstream developer, I decided a few weeks ago to
7986 take over the package and become the new upstream. The number of
7987 patches to track for the Debian package was becoming a burden, and the
7988 lack of synchronization between the distribution made it hard to keep
7989 the package up to date.
</p
>
7991 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7992 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
7993 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
7994 and Fedora), based on the patches currently in use in these
7995 distributions. We Debian maintainers plan to move to this tarball as
7996 the new upstream as soon as we find time to do the merge. Since the
7997 new tarball was created, we agreed with Werner at SuSe to make a new
7998 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
7999 development there. The project is registered and currently waiting
8000 for approval by the Savannah administrators, and as soon as it is
8001 approved, we will import the old versions from svn and continue
8002 working on the future release.
</p
>
8004 <p
>It is a bit ironic that this is done now, when some of the involved
8005 distributions are moving to upstart as a syvinit replacement.
</p
>
8010 <title>Debian boots quicker and quicker
</title>
8011 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8013 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8014 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8015 people involved in the boot system on Debian and Ubuntu, to see if we
8016 could find more ways to speed up the boot system. This was an Ubuntu
8018 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8019 gathering
</a
>. It was quite productive. We also discussed the future
8020 of boot systems, and ways to handle the increasing number of boot
8021 issues introduced by the Linux kernel becoming more and more
8022 asynchronous and event base. The Ubuntu approach using udev and
8023 upstart might be a good way forward. Time will show.
</p
>
8025 <p
>Anyway, there are a few ways at the moment to speed up the boot
8026 process in Debian. All of these should be applied to get a quick
8031 <li
>Use dash as /bin/sh.
</li
>
8033 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8034 clock is in UTC.
</li
>
8036 <li
>Install and activate the insserv package to enable
8037 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8038 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8042 These points are based on the Google summer of code work done by
8043 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8046 <p
>Support for makefile-style concurrency during boot was uploaded to
8047 unstable yesterday. When we tested it, we were able to cut
6 seconds
8048 from the boot sequence. It depend on very correct dependency
8049 declaration in all init.d scripts, so I expect us to find edge cases
8050 where the dependences in some scripts are slightly wrong when we start
8051 using this.
</p
>
8053 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8054 introduced by Raphael Geissert today, one that could affect the
8055 startup speed as well. Instead of starting some scripts concurrently
8056 from rcS.d/ and another set of scripts from rc2.d/, it would be
8057 possible to run a of them in the same process. A quick way to test
8058 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8059 insserv
'. Will need to test if that work. :)
</p
>
8064 <title>BSAs påstander om piratkopiering møter motstand
</title>
8065 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8066 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8067 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8068 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8069 programvareselskapene som Microsoft og Apple, publisert en rapport der
8070 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8071 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8073 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8074 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8075 dagene. Et spesielt interessant kommentar fra Sverige,
8076 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8077 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8080 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8081 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8082 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8083 exakta
", säger BSAs Sverigechef John Hugosson.
8086 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
8087 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
8088 piracy figures need a shot of reality
</a
> og
<a
8089 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
8090 Copyright Treaty Work?
</a
></p
>
8092 <p
>Fant lenkene via
<a
8093 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
8094 på Slashdot
</a
>.
</p
>
8099 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
8100 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
8101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
8102 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
8103 <description><p
>Kom over
8104 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
8105 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8106 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8107 jobber til daglig. En rask opptelling forteller meg at vi har
490
8108 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
8109 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
8110 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
8115 <title>Kryptert harddisk - naturligvis
</title>
8116 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
8117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
8118 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
8119 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
8120 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
8121 når en tar tap av arbeidstid, fortrolige dokumenter,
8122 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8123 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8124 til at jeg har kryptert harddisken på både kontormaskinen og min
8125 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8126 komme på avveie, den første informasjon relatert til jobben min ved
8127 Universitetet i Oslo, og den andre relatert til blant annet
8128 foreningsarbeide. Kryptering av diskene gjør at det er lite
8129 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8130 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8131 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8132 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8133 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8134 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8135 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8136 det er gjort slik jeg gjør det er minimale, og gevinstene er
8137 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8138 maskinen reinstalleres og alt er tapt.
</p
>
8140 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8141 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8142 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8143 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8144 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8145 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8146 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8147 betydelige.
</p
>
8152 <title>Two projects that have improved the quality of free software a lot
</title>
8153 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
8154 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
8155 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
8156 <description><p
>There are two software projects that have had huge influence on the
8157 quality of free software, and I wanted to mention both in case someone
8158 do not yet know them.
</p
>
8160 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
8161 tool to detect and expose errors in the memory handling of programs.
8162 It is easy to use, all one need to do is to run
'valgrind program
',
8163 and it will report any problems on stdout. It is even better if the
8164 program include debug information. With debug information, it is able
8165 to report the source file name and line number where the problem
8166 occurs. It can report things like
'reading past memory block in file
8167 X line N, the memory block was allocated in file Y, line M
', and
8168 'using uninitialised value in control logic
'. This tool has made it
8169 trivial to investigate reproducible crash bugs in programs, and have
8170 reduced the number of this kind of bugs in free software a lot.
8172 <p
>The second one is
8173 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
8174 a source code checker. It is able to process the source of a program
8175 and find problems in the logic without running the program. It
8176 started out as the Stanford Checker and became well known when it was
8177 used to find bugs in the Linux kernel. It is now a commercial tool
8178 and the company behind it is running
8179 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
8180 free software community, where a lot of free software projects get
8181 their source checked for free. Several thousand defects have been
8182 found and fixed so far. It can find errors like
'lock L taken in file
8183 X line N is never released if exiting in line M
', or
'the code in file
8184 Y lines O to P can never be executed
'. The projects included in the
8185 community service project have managed to get rid of a lot of
8186 reliability problems thanks to Coverity.
</p
>
8188 <p
>I believe tools like this, that are able to automatically find
8189 errors in the source, are vital to improve the quality of software and
8190 make sure we can get rid of the crashing and failing software we are
8191 surrounded by today.
</p
>
8196 <title>No patch is not better than a useless patch
</title>
8197 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
8198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
8199 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
8200 <description><p
>Julien Blache
8201 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
8202 patch is better than a useless patch
</a
>. I completely disagree, as a
8203 patch allow one to discuss a concrete and proposed solution, and also
8204 prove that the issue at hand is important enough for someone to spent
8205 time on fixing it. No patch do not provide any of these positive
8206 properties.
</p
>
8211 <title>Standardize on protocols and formats, not vendors and applications
</title>
8212 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8214 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8215 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8216 very good one to form a long lived computer infrastructure. It is the
8217 simple one, lost by many in todays computer industry: Standardize on
8218 open network protocols and open exchange/storage formats, not applications.
8219 Applications come and go, while protocols and files tend to stay, and
8220 thus one want to make it easy to change application and vendor, while
8221 avoiding conversion costs and locking users to a specific platform or
8222 application.
</p
>
8224 <p
>This approach make it possible to replace the client applications
8225 independently of the server applications. One can even allow users to
8226 use several different applications as long as they handle the selected
8227 protocol and format. In the normal case, only one client application
8228 is recommended and users only get help if they choose to use this
8229 application, but those that want to deviate from the easy path are not
8230 blocked from doing so.
</p
>
8232 <p
>It also allow us to replace the server side without forcing the
8233 users to replace their applications, and thus allow us to select the
8234 best server implementation at any moment, when scale and resouce
8235 requirements change.
</p
>
8237 <p
>I strongly recommend standardizing - on open network protocols and
8238 open formats, but I would never recommend standardizing on a single
8239 application that do not use open network protocol or open formats.
</p
>
8244 <title>Returning from Skolelinux developer gathering
</title>
8245 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8247 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8248 <description><p
>I
'm sitting on the train going home from this weekends Debian
8249 Edu/Skolelinux development gathering. I got a bit done tuning the
8250 desktop, and looked into the dynamic service location protocol
8251 implementation avahi. It look like it could be useful for us. Almost
8252 30 people participated, and I believe it was a great environment to
8253 get to know the Skolelinux system. Walter Bender, involved in the
8254 development of the Sugar educational platform, presented his stuff and
8255 also helped me improve my OLPC installation. He also showed me that
8256 his Turtle Art application can be used in standalone mode, and we
8257 agreed that I would help getting it packaged for Debian. As a
8258 standalone application it would be great for Debian Edu. We also
8259 tried to get the video conferencing working with two OLPCs, but that
8260 proved to be too hard for us. The application seem to need more work
8261 before it is ready for me. I look forward to getting home and relax
8267 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8268 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8270 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8271 <description><p
>The state of standardized LDAP schemas on Linux is far from
8272 optimal. There is RFC
2307 documenting one way to store NIS maps in
8273 LDAP, and a modified version of this normally called RFC
2307bis, with
8274 some modifications to be compatible with Active Directory. The RFC
8275 specification handle the content of a lot of system databases, but do
8276 not handle DNS zones and DHCP configuration.
</p
>
8278 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
8279 we would like to store information about users, SMB clients/hosts,
8280 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8281 and LTSP configuration in LDAP. These objects have a lot in common,
8282 but with the current LDAP schemas it is not possible to have one
8283 object per entity. For example, one need to have at least three LDAP
8284 objects for a given computer, one with the SMB related stuff, one with
8285 DNS information and another with DHCP information. The schemas
8286 provided for DNS and DHCP are impossible to combine into one LDAP
8287 object. In addition, it is impossible to implement quick queries for
8288 netgroup membership, because of the way NIS triples are implemented.
8289 It just do not scale. I believe it is time for a few RFC
8290 specifications to cleam up this mess.
</p
>
8292 <p
>I would like to have one LDAP object representing each computer in
8293 the network, and this object can then keep the SMB (ie host key), DHCP
8294 (mac address/name) and DNS (name/IP address) settings in one place.
8295 It need to be efficently stored to make sure it scale well.
</p
>
8297 <p
>I would also like to have a quick way to map from a user or
8298 computer and to the net group this user or computer is a member.
</p
>
8300 <p
>Active Directory have done a better job than unix heads like myself
8301 in this regard, and the unix side need to catch up. Time to start a
8302 new IETF work group?
</p
>
8307 <title>Endelig er Debian Lenny gitt ut
</title>
8308 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
8309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
8310 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
8311 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
8312 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
8313 Et langt steg videre for Debian-prosjektet, og en rekke nye
8314 programpakker blir nå tilgjengelig for de av oss som bruker den
8315 stabile utgaven av Debian. Neste steg er nå å få
8316 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
8317 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
8318 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8319 slippes løs på skolene. Takk til alle debian-utviklerne som har
8320 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8321 bootsekvens tilgjengelig i stabil utgave, vha pakken
8322 <tt
>insserv
</tt
>.
</p
>
8327 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
8328 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
8329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
8330 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
8331 <description><p
>This weekend we had a small developer gathering for Debian Edu in
8332 Oslo. Most of Saturday was used for the general assemly for the
8333 member organization, but the rest of the weekend I used to tune the
8334 LTSP installation. LTSP now work out of the box on the
10-network.
8335 Acer Aspire One proved to be a very nice thin client, with both
8336 screen, mouse and keybard in a small box. Was working on getting the
8337 diskless workstation setup configured out of the box, but did not
8338 finish it before the weekend was up.
</p
>
8340 <p
>Did not find time to look at the
4 VGA cards in one box we got from
8341 the Brazilian group, so that will have to wait for the next
8342 development gathering. Would love to have the Debian Edu installer
8343 automatically detect and configure a multiseat setup when it find one
8344 of these cards.
</p
>
8349 <title>The sorry state of multimedia browser plugins in Debian
</title>
8350 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
8351 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
8352 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
8353 <description><p
>Recently I have spent some time evaluating the multimedia browser
8354 plugins available in Debian Lenny, to see which one we should use by
8355 default in Debian Edu. We need an embedded video playing plugin with
8356 control buttons to pause or stop the video, and capable of streaming
8357 all the multimedia content available on the web. The test results and
8358 notes are available on
8359 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
8360 Debian wiki
</a
>. I was surprised how few of the plugins are able to
8361 fill this need. My personal video player favorite, VLC, has a really
8362 bad plugin which fail on a lot of the test pages. A lot of the MIME
8363 types I would expect to work with any free software player (like
8364 video/ogg), just do not work. And simple formats like the
8365 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
8366 totem and vlc plugins. I hope the situation will improve soon. No
8367 wonder sites use the proprietary Adobe flash to play video.
</p
>
8369 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
8370 be the only one fitting our needs. :/
</p
>