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>Using appstream in Debian to locate packages with firmware and mime type support
</title>
11 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
13 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
14 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
15 is taking shape in Debian, and one provided feature is a very
16 convenient way to tell you which package to install to make a given
17 firmware file available when the kernel is looking for it. This can
18 be done using apt-file too, but that is for someone else to blog
21 <p
>Here is a small recipe to find the package with a given firmware
22 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
23 picked from the set of firmware announced using appstream in Debian
24 unstable. In general you would be looking for the firmware requested
25 by the kernel during kernel module loading. To find the package
26 providing the example file, do like this:
</p
>
28 <blockquote
><pre
>
29 % apt install appstream
33 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
34 awk
'/Package:/ {print $
2}
'
37 </pre
></blockquote
>
39 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
40 appstream wiki
</a
> page to learn how to embed the package metadata in
41 a way appstream can use.
</p
>
43 <p
>This same approach can be used to find any package supporting a
44 given MIME type. This is very useful when you get a file you do not
45 know how to handle. First find the mime type using
<tt
>file
46 --mime-type
</tt
>, and next look up the package providing support for
47 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
48 and you can find all packages handling this type like this:
</p
>
50 <blockquote
><pre
>
51 % apt install appstream
55 % appstreamcli what-provides mimetype image/svg+xml | \
56 awk
'/Package:/ {print $
2}
'
78 </pre
></blockquote
>
80 <p
>I believe the MIME types are fetched from the desktop file for
81 packages providing appstream metadata.
</p
>
86 <title>Creepy, visualise geotagged social media information - nice free software
</title>
87 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
88 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
89 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
90 <description><p
>Most people seem not to realise that every time they walk around
91 with the computerised radio beacon known as a mobile phone their
92 position is tracked by the phone company and often stored for a long
93 time (like every time a SMS is received or sent). And if their
94 computerised radio beacon is capable of running programs (often called
95 mobile apps) downloaded from the Internet, these programs are often
96 also capable of tracking their location (if the app requested access
97 during installation). And when these programs send out information to
98 central collection points, the location is often included, unless
99 extra care is taken to not send the location. The provided
100 information is used by several entities, for good and bad (what is
101 good and bad, depend on your point of view). What is certain, is that
102 the private sphere and the right to free movement is challenged and
103 perhaps even eradicated for those announcing their location this way,
104 when they share their whereabouts with private and public
107 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
109 <p
>The phone company logs provide a register of locations to check out
110 when one want to figure out what the tracked person was doing. It is
111 unavailable for most of us, but provided to selected government
112 officials, company staff, those illegally buying information from
113 unfaithful servants and crackers stealing the information. But the
114 public information can be collected and analysed, and a free software
115 tool to do so is called
116 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
117 discovered it when I read
118 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
119 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
120 November
2014, and decided to check if it was available in Debian.
121 The python program was in Debian, but
122 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
123 Debian
</a
> was completely broken and practically unmaintained. I
124 uploaded a new version which did not work quite right, but did not
125 have time to fix it then. This Christmas I decided to finally try to
126 get Creepy operational in Debian. Now a fixed version is available in
127 Debian unstable and testing, and almost all Debian specific patches
129 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
131 <p
>The Creepy program visualises geolocation information fetched from
132 Twitter, Instagram, Flickr and Google+, and allow one to get a
133 complete picture of every social media message posted recently in a
134 given area, or track the movement of a given individual across all
135 these services. Earlier it was possible to use the search API of at
136 least some of these services without identifying oneself, but these
137 days it is impossible. This mean that to use Creepy, you need to
138 configure it to log in as yourself on these services, and provide
139 information to them about your search interests. This should be taken
140 into account when using Creepy, as it will also share information
141 about yourself with the services.
</p
>
143 <p
>The picture above show the twitter messages sent from (or at least
144 geotagged with a position from) the city centre of Oslo, the capital
145 of Norway. One useful way to use Creepy is to first look at
146 information tagged with an area of interest, and next look at all the
147 information provided by one or more individuals who was in the area.
148 I tested it by checking out which celebrity provide their location in
149 twitter messages by checkout out who sent twitter messages near a
150 Norwegian TV station, and next could track their position over time,
151 making it possible to locate their home and work place, among other
152 things. A similar technique have been
153 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
154 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
155 tool to discover lying governments, and a useful tool to help people
156 understand the value of the private information they provide to the
159 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
160 it depend on several python modules currently missing in Jessie (at
161 least python-instagram, python-flickrapi and
162 python-requests-toolbelt).
</p
>
164 <p
>(I have uploaded
165 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
166 screenshots.debian.net
</a
> and licensed it under the same terms as the
167 Creepy program in Debian.)
</p
>
172 <title>Always download Debian packages using Tor - the simple recipe
</title>
173 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
174 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
175 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
176 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
177 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
178 that those listening on the Internet lines would have good reason to
179 believe a computer have a given security hole
</a
> if it download a
180 security fix from a Debian mirror. This is a good reason to always
181 use encrypted connections to the Debian mirror, to make sure those
182 listening do not know which IP address to attack. In August, Richard
183 Hartmann observed that encryption was not enough, when it was possible
184 to interfere download size to security patches or the fact that
185 download took place shortly after a security fix was released, and
186 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
187 to always use Tor to download packages from the Debian mirror
</a
>. He
188 was not the first to propose this, as the
189 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
190 package by Tim Retout already existed to make it easy to convince apt
191 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
192 aware of that package when I read the blog post from Richard.
</p
>
194 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
195 sysadmins, and he set up a Tor hidden service on one of the central
196 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
197 it possible to download packages directly between two tor nodes,
198 making sure the network traffic always were encrypted.
</p
>
200 <p
>Here is a short recipe for enabling this on your machine, by
201 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
202 urls with tor+http and tor+https, and using the hidden service instead
203 of the official Debian mirror site. I recommend installing
204 <tt
>etckeeper
</tt
> before you start to have a history of the changes
205 done in /etc/.
</p
>
207 <blockquote
><pre
>
208 apt install apt-transport-tor
209 sed -i
's% http://ftp.debian.org/%tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
210 sed -i
's% http% tor+http%
' /etc/apt/sources.list
211 </pre
></blockquote
>
213 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
214 the sed commands for these too. The sed command is assuming your are
215 using the ftp.debian.org Debian mirror. Adjust the command (or just
216 edit the file manually) to match your mirror.
</p
>
218 <p
>This work in Debian Jessie and later. Note that tools like
219 <tt
>apt-file
</tt
> only recently started using the apt transport
220 system, and do not work with these tor+http URLs. For
221 <tt
>apt-file
</tt
> you need the version currently in experimental,
222 which need a recent apt version currently only in unstable. So if you
223 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
225 <p
>Another advantage from this change is that your machine will start
226 using Tor regularly and at fairly random intervals (every time you
227 update the package lists or upgrade or install a new package), thus
228 masking other Tor traffic done from the same machine. Using Tor will
229 become normal for the machine in question.
</p
>
231 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
232 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
233 enabled. It would be great if it was the default on any Debian
239 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
240 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
242 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
243 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
244 call the car license plate numbers in those days. I would write the
245 numbers down in my little book and compare notes with the other kids
246 to see how many region codes we had seen and if we had seen some
247 exotic or special region codes and numbers. It was a fun game to pass
248 time, as we kids have plenty of it.
</p
>
250 <p
>A few days I came across
251 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
252 project
</a
>, a free software project to automatically discover and
253 report license plates in images and video streams, and provide the
254 "car numbers
" in a machine readable format. I
've been looking for
255 such system for a while now, because I believe it is a bad idea that the
256 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
257 number plate recognition
</a
> tool only is available in the hands of
258 the powerful, and want it to be available also for the powerless to
259 even the score when it comes to surveillance and sousveillance. I
260 discovered the developer
261 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
262 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
263 help him get it into shape to get the package uploaded into the Debian
266 <p
>Today we finally managed to get the package into shape and uploaded
267 it into Debian, where it currently
268 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
269 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
271 <p
>I guess you are wondering why on earth such tool would be useful
272 for the common folks, ie those not running a large government
273 surveillance system? Well, I plan to put it in a computer on my bike
274 and in my car, tracking the cars nearby and allowing me to be notified
275 when number plates on my watch list are discovered. Another use case
276 was suggested by a friend of mine, who wanted to set it up at his home
277 to open the car port automatically when it discovered the plate on his
278 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
279 capable of placing his license plate number of a piece of cardboard to
280 open his car port, men replied that it was always unlocked anyway. I
281 guess for such use case it make sense. I am sure there are other use
282 cases too, for those with imagination and a vision.
</p
>
284 <p
>If you want to build your own version of the Debian package, check
285 out the upstream git source and symlink ./distros/debian to ./debian/
286 before running
"debuild
" to build the source. Or wait a bit until the
287 package show up in unstable.
</p
>
292 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
293 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
294 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
295 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
296 <description><p
>Around three years ago, I created
297 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
298 system
</a
> to get a more practical solution in Debian for handing
299 hardware related packages. A GUI system in the isenkram package will
300 present a pop-up dialog when some hardware dongle supported by
301 relevant packages in Debian is inserted into the machine. The same
302 lookup mechanism to detect packages is available as command line
303 tools in the isenkram-cli package. In addition to mapping hardware,
304 it will also map kernel firmware files to packages and make it easy to
305 install needed firmware packages automatically. The key for this
306 system to work is a good way to map hardware to packages, in other
307 words, allow packages to announce what hardware they will work
310 <p
>I started by providing data files in the isenkram source, and
311 adding code to download the latest version of these data files at run
312 time, to ensure every user had the most up to date mapping available.
313 I also added support for storing the mapping in the Packages file in
314 the apt repositories, but did not push this approach because while I
315 was trying to figure out how to best store hardware/package mappings,
316 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
317 appstream system
</a
> was announced. I got in touch and suggested to
318 add the hardware mapping into that data set to be able to use
319 appstream as a data source, and this was accepted at least for the
320 Debian version of appstream.
</p
>
322 <p
>A few days ago using appstream in Debian for this became possible,
323 and today I uploaded a new version
0.20 of isenkram adding support for
324 appstream as a data source for mapping hardware to packages. The only
325 package so far using appstream to announce its hardware support is my
326 pymissile package. I got help from Matthias Klumpp with figuring out
327 how do add the required
328 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
329 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
330 this content:
</p
>
332 <blockquote
><pre
>
333 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
334 &lt;component
&gt;
335 &lt;id
&gt;pymissile
&lt;/id
&gt;
336 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
337 &lt;name
&gt;pymissile
&lt;/name
&gt;
338 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
339 &lt;description
&gt;
341 Pymissile provides a curses interface to control an original
342 Marks and Spencer / Striker USB Missile Launcher, as well as a
343 motion control script to allow a webcamera to control the
346 &lt;/description
&gt;
347 &lt;provides
&gt;
348 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
349 &lt;/provides
&gt;
350 &lt;/component
&gt;
351 </pre
></blockquote
>
353 <p
>The key for isenkram is the component/provides/modalias value,
354 which is a glob style match rule for hardware specific strings
355 (modalias strings) provided by the Linux kernel. In this case, it
356 will map to all USB devices with vendor code
1130 and product code
359 <p
>Note, it is important that the license of all the metadata files
360 are compatible to have permissions to aggregate them into archive wide
361 appstream files. Matthias suggested to use MIT or BSD licenses for
362 these files. A challenge is figuring out a good id for the data, as
363 it is supposed to be globally unique and shared across distributions
364 (in other words, best to coordinate with upstream what to use). But
365 it can be changed later or, so we went with the package name as
366 upstream for this project is dormant.
</p
>
368 <p
>To get the metadata file installed in the correct location for the
369 mirror update scripts to pick it up and include its content the
370 appstream data source, the file must be installed in the binary
371 package under /usr/share/appdata/. I did this by adding the following
372 line to debian/pymissile.install:
</p
>
374 <blockquote
><pre
>
375 debian/pymissile.metainfo.xml usr/share/appdata
376 </pre
></blockquote
>
378 <p
>With that in place, the command line tool isenkram-lookup will list
379 all packages useful on the current computer automatically, and the GUI
380 pop-up handler will propose to install the package not already
381 installed if a hardware dongle is inserted into the machine in
384 <p
>Details of the modalias field in appstream is available from the
385 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
387 <p
>To locate the modalias values of all hardware present in a machine,
388 try running this command on the command line:
</p
>
390 <blockquote
><pre
>
391 cat $(find /sys/devices/|grep modalias)
392 </pre
></blockquote
>
394 <p
>To learn more about the isenkram system, please check out
395 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
396 blog posts tagged isenkram
</a
>.
</p
>
401 <title>The GNU General Public License is not magic pixie dust
</title>
402 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
403 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
404 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
405 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
406 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
407 GPL is not magic pixie dust
</a
>" explain the importance of making sure
408 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
409 I quote the blog post from Paul in full here with his permission:
<p
>
413 <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
>
416 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
418 The first step is to choose a
419 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
422 The next step is, when someone fails to follow that copyleft license,
423 <b
>it must be enforced
</b
><br/
>
425 and its a simple fact of our modern society that such type of
428 is incredibly expensive to do and incredibly difficult to do.
431 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
432 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
433 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
434 0x57</a
></small
></p
>
436 <p
>As the Debian Website
437 <a href=
"https://bugs.debian.org/
794116">used
</a
>
438 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
439 imply, public domain and permissively licensed software can lead to
440 the production of more proprietary software as people discover useful
441 software, extend it and or incorporate it into their hardware or
442 software products. Copyleft licenses such as the GNU GPL were created
443 to close off this avenue to the production of proprietary software but
444 such licenses are not enough. With the ongoing adoption of Free
445 Software by individuals and groups, inevitably the community
's
446 expectations of license compliance are violated, usually out of
447 ignorance of the way Free Software works, but not always. As Karen
448 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
449 Freedom
">FaiF
</a
>
450 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
451 copyleft is nothing if no-one is willing and able to stand up in court
452 to protect it. The reality of today
's world is that legal
453 representation is expensive, difficult and time consuming. With
454 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
455 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
456 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
457 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
458 of the Linux project, Debian and other groups against GPL violations.
459 In March the SFC supported a
460 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
461 by Christoph Hellwig
</a
> against VMware for refusing to
462 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
463 with the GPL
</a
> in relation to their use of parts of the Linux
464 kernel. Since then two of their sponsors pulled corporate funding and
466 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
467 or cancelled their talks
</a
>. As a result they have decided to rely
468 less on corporate funding and more on the broad community of
469 individuals who support Free Software and copyleft. So the SFC has
470 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
471 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
472 a community of folks who stand up for copyleft and the GPL by
473 supporting their work on promoting and supporting copyleft and Free
476 <p
>If you support Free Software,
477 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
478 what the SFC do, agree with their
479 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
480 principles
</a
>, are happy about their
481 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
482 work on a project that is an SFC
483 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
484 just want to stand up for copyleft, please join
485 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
486 Allan Webber
</a
>,
487 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
489 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
490 Bacon
</a
>, myself and
491 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
493 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
494 next week your donation will be
495 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
496 by an anonymous donor. Please also consider asking your employer to
497 match your donation or become a sponsor of SFC. Don
't forget to
498 spread the word about your support for SFC via email, your blog and or
499 social media accounts.
</p
>
503 <p
>I agree with Paul on this topic and just signed up as a Supporter
504 of Software Freedom Conservancy myself. Perhaps you should be a
505 supporter too?
</p
>
510 <title>PGP key transition statement for key EE4E02F9
</title>
511 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
512 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
513 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
514 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
515 set it up properly. I wanted to generate it offline and have it
516 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
517 smart card
</a
> for daily use, and learning how to do it and finding
518 time to sit down with an offline machine almost took forever. But
519 finally I
've been able to complete the process, and have now moved
520 from my old GPG key to a new GPG key. See
521 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
522 full transition statement, signed with both my old and new key
</a
> for
523 the details. This is my new key:
</p
>
526 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
527 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
528 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
529 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
530 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
531 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
532 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
535 <p
>The key can be downloaded from the OpenPGP key servers, signed by
536 my old key.
</p
>
538 <p
>If you signed my old key
539 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
540 I
'd very much appreciate a signature on my new key, details and
541 instructions in the transition statement. I m happy to reciprocate if
542 you have a similarly signed transition statement to present.
</p
>
547 <title>The life and death of a laptop battery
</title>
548 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
549 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
550 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
551 <description><p
>When I get a new laptop, the battery life time at the start is OK.
552 But this do not last. The last few laptops gave me a feeling that
553 within a year, the life time is just a fraction of what it used to be,
554 and it slowly become painful to use the laptop without power connected
555 all the time. Because of this, when I got a new Thinkpad X230 laptop
556 about two years ago, I decided to monitor its battery state to have
557 more hard facts when the battery started to fail.
</p
>
559 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
561 <p
>First I tried to find a sensible Debian package to record the
562 battery status, assuming that this must be a problem already handled
563 by someone else. I found
564 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
565 which collects statistics from the battery, but it was completely
566 broken. I sent a few suggestions to the maintainer, but decided to
567 write my own collector as a shell script while I waited for feedback
569 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
570 blog post about the battery development on a MacBook Air
</a
> I also
572 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
573 available in Debian.
</p
>
575 <p
>I started my collector
2013-
07-
15, and it has been collecting
576 battery stats ever since. Now my
577 /var/log/hjemmenett-battery-status.log file contain around
115,
000
578 measurements, from the time the battery was working great until now,
579 when it is unable to charge above
7% of original capacity. My
580 collector shell script is quite simple and look like this:
</p
>
585 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
587 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
588 logfile=/var/log/hjemmenett-battery-status.log
590 files=
"manufacturer model_name technology serial_number \
591 energy_full energy_full_design energy_now cycle_count status
"
593 if [ ! -e
"$logfile
" ] ; then
595 printf
"timestamp,
"
597 printf
"%s,
" $f
600 )
> "$logfile
"
604 # Print complete message in one echo call, to avoid race condition
605 # when several log processes run in parallel.
606 msg=$(printf
"%s,
" $(date +%s); \
607 for f in $files; do \
608 printf
"%s,
" $(cat $f); \
610 echo
"$msg
"
613 cd /sys/class/power_supply
616 (cd $bat
&& log_battery
>> "$logfile
")
620 <p
>The script is called when the power management system detect a
621 change in the power status (power plug in or out), and when going into
622 and out of hibernation and suspend. In addition, it collect a value
623 every
10 minutes. This make it possible for me know when the battery
624 is discharging, charging and how the maximum charge change over time.
625 The code for the Debian package
626 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
627 available on github
</a
>.
</p
>
629 <p
>The collected log file look like this:
</p
>
632 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
633 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
635 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
636 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
639 <p
>I wrote a small script to create a graph of the charge development
640 over time. This graph depicted above show the slow death of my laptop
643 <p
>But why is this happening? Why are my laptop batteries always
644 dying in a year or two, while the batteries of space probes and
645 satellites keep working year after year. If we are to believe
646 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
647 University
</a
>, the cause is me charging the battery whenever I have a
648 chance, and the fix is to not charge the Lithium-ion batteries to
100%
649 all the time, but to stay below
90% of full charge most of the time.
650 I
've been told that the Tesla electric cars
651 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
652 the charge of their batteries to
80%
</a
>, with the option to charge to
653 100% when preparing for a longer trip (not that I would want a car
654 like Tesla where rights to privacy is abandoned, but that is another
655 story), which I guess is the option we should have for laptops on
658 <p
>Is there a good and generic way with Linux to tell the battery to
659 stop charging at
80%, unless requested to charge to
100% once in
660 preparation for a longer trip? I found
661 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
662 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
663 80%
</a
>, but could not get it to work (kernel module refused to
666 <p
>I wonder why the battery capacity was reported to be more than
100%
667 at the start. I also wonder why the
"full capacity
" increases some
668 times, and if it is possible to repeat the process to get the battery
669 back to design capacity. And I wonder if the discharge and charge
670 speed change over time, or if this stay the same. I did not yet try
671 to write a tool to calculate the derivative values of the battery
672 level, but suspect some interesting insights might be learned from
675 <p
>Update
2015-
09-
24: I got a tip to install the packages
676 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
677 packages instead of the tp-smapi-dkms package I had tried to use
678 initially, and use
'tlp setcharge
40 80' to change when charging start
679 and stop. I
've done so now, but expect my existing battery is toast
680 and need to be replaced. The proposal is unfortunately Thinkpad
686 <title>New laptop - some more clues and ideas based on feedback
</title>
687 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
688 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
689 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
690 <description><p
>Several people contacted me after my previous blog post about my
691 need for a new laptop, and provided very useful feedback. I wish to
692 thank every one of these. Several pointed me to the possibility of
693 fixing my X230, and I am already in the process of getting Lenovo to
694 do so thanks to the on site, next day support contract covering the
695 machine. But the battery is almost useless (I expect to replace it
696 with a non-official battery) and I do not expect the machine to live
697 for many more years, so it is time to plan its replacement. If I did
698 not have a support contract, it was suggested to find replacement parts
699 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
700 might present a language barrier as I do not understand French.
</p
>
702 <p
>One tip I got was to use the
703 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
704 compare laptop models. It seem to have more models available than
705 prisjakt.no. Another tip I got from someone I know have similar
706 keyboard preferences was that the HP EliteBook
840 keyboard is not
707 very good, and this matches my experience with earlier EliteBook
708 keyboards I tested. Because of this, I will not consider it any further.
710 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
711 newest Thinkpad X model. The keyboard reintroduces mouse buttons
712 (which is missing from the X240), and is working fairly well with
713 Debian Sid/Unstable according to
714 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
715 got on the keyboard quality are not consistent. Some say the keyboard
716 is good, others say it is ok, while others say it is not very good.
717 Those with experience from X41 and and X60 agree that the X250
718 keyboard is not as good as those trusty old laptops, and suggest I
719 keep and fix my X230 instead of upgrading, or get a used X230 to
720 replace it. I
'm also told that the X250 lack leds for caps lock, disk
721 activity and battery status, which is very convenient on my X230. I
'm
722 also told that the CPU fan is running very often, making it a bit
723 noisy. In any case, the X250 do not work out of the box with Debian
724 Stable/Jessie, one of my requirements.
</p
>
726 <p
>I have also gotten a few vendor proposals, one was
727 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
728 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
729 The latter look very attractive to me.
</p
>
731 <p
>Again, thank you all for the very useful feedback. It help a lot
732 as I keep looking for a replacement.
</p
>
734 <p
>Update
2015-
07-
06: I was recommended to check out the
735 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
737 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
738 thinkpad X models
</a
>, and provide one year warranty.
</p
>
743 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
744 <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>
745 <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>
746 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
747 <description><p
>My primary work horse laptop is failing, and will need a
748 replacement soon. The left
5 cm of the screen on my Thinkpad X230
749 started flickering yesterday, and I suspect the cause is a broken
750 cable, as changing the angle of the screen some times get rid of the
751 flickering.
</p
>
753 <p
>My requirements have not really changed since I bought it, and is
755 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
756 described them in
2013</a
>. The last time I bought a laptop, I had
758 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
759 where I could select at least a few of the requirements (mouse pin,
760 wifi, weight) and go through the rest manually. Three button mouse
761 and a good keyboard is not available as an option, and all the three
762 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
763 G2) lack three mouse buttons). It is also unclear to me how good the
764 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
765 the keyboard, even if the quality and robustness in the X series have
766 deteriorated since X41.
</p
>
768 <p
>I wonder how I can find a sensible laptop when none of the options
769 seem sensible to me? Are there better services around to search the
770 set of available laptops for features? Please send me an email if you
771 have suggestions.
</p
>
773 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
774 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
775 of endorsed hardware
</a
>, which is useful background information.
</p
>
780 <title>How to stay with sysvinit in Debian Jessie
</title>
781 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
783 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
784 <description><p
>By now, it is well known that Debian Jessie will not be using
785 sysvinit as its boot system by default. But how can one keep using
786 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
788 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
789 Schubert
</a
> and
790 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
793 <p
>If you already are using Wheezy and want to upgrade to Jessie and
794 keep sysvinit as your boot system, create a file
795 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
796 you upgrade:
</p
>
798 <p
><blockquote
><pre
>
799 Package: systemd-sysv
800 Pin: release o=Debian
802 </pre
></blockquote
><p
>
804 <p
>This file content will tell apt and aptitude to not consider
805 installing systemd-sysv as part of any installation and upgrade
806 solution when resolving dependencies, and thus tell it to avoid
807 systemd as a default boot system. The end result should be that the
808 upgraded system keep using sysvinit.
</p
>
810 <p
>If you are installing Jessie for the first time, there is no way to
811 get sysvinit installed by default (debootstrap used by
812 debian-installer have no option for this), but one can tell the
813 installer to switch to sysvinit before the first boot. Either by
814 using a kernel argument to the installer, or by adding a line to the
815 preseed file used. First, the kernel command line argument:
817 <p
><blockquote
><pre
>
818 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
819 </pre
></blockquote
><p
>
821 <p
>Next, the line to use in a preseed file:
</p
>
823 <p
><blockquote
><pre
>
824 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
825 </pre
></blockquote
><p
>
827 <p
>One can of course also do this after the first boot by installing
828 the sysvinit-core package.
</p
>
830 <p
>I recommend only using sysvinit if you really need it, as the
831 sysvinit boot sequence in Debian have several hardware specific bugs
832 on Linux caused by the fact that it is unpredictable when hardware
833 devices show up during boot. But on the other hand, the new default
834 boot system still have a few rough edges I hope will be fixed before
835 Jessie is released.
</p
>
837 <p
>Update
2014-
11-
26: Inspired by
838 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
839 blog post by Torsten Glaser
</a
>, added --purge to the preseed
845 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
846 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
848 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
849 <description><p
>The right to communicate with your friends and family in private,
850 without anyone snooping, is a right every citicen have in a liberal
851 democracy. But this right is under serious attack these days.
</p
>
853 <p
>A while back it occurred to me that one way to make the dragnet
854 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
855 the whisleblower Snowden) more expensive for Internet email,
856 is to deliver all email using SMTP via Tor. Such SMTP option would be
857 a nice addition to the FreedomBox project if we could send email
858 between FreedomBox machines without leaking metadata about the emails
859 to the people peeking on the wire. I
860 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
861 this on the FreedomBox project mailing list in October
</a
> and got a
862 lot of useful feedback and suggestions. It also became obvious to me
863 that this was not a novel idea, as the same idea was tested and
864 documented by Johannes Berg as early as
2006, and both
865 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
866 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
867 propose a similar method / protocol to pass emails between users.
</p
>
869 <p
>To implement such system one need to set up a Tor hidden service
870 providing the SMTP protocol on port
25, and use email addresses
871 looking like username@hidden-service-name.onion. With such addresses
872 the connections to port
25 on hidden-service-name.onion using Tor will
873 go to the correct SMTP server. To do this, one need to configure the
874 Tor daemon to provide the hidden service and the mail server to accept
875 emails for this .onion domain. To learn more about Exim configuration
876 in Debian and test the design provided by Johannes Berg in his FAQ, I
877 set out yesterday to create a Debian package for making it trivial to
878 set up such SMTP over Tor service based on Debian. Getting it to work
879 were fairly easy, and
880 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
881 source code for the Debian package
</a
> is available from github. I
882 plan to move it into Debian if further testing prove this to be a
883 useful approach.
</p
>
885 <p
>If you want to test this, set up a blank Debian machine without any
886 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
887 get rid of exim4). Install tor, clone the git repository mentioned
888 above, build the deb and install it on the machine. Next, run
889 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
890 the instructions to get the service up and running. Restart tor and
891 exim when it is done, and test mail delivery using swaks like
894 <p
><blockquote
><pre
>
895 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
896 --to fbx@dutlqrrmjhtfa3vp.onion
897 </pre
></blockquote
></p
>
899 <p
>This will test the SMTP delivery using tor. Replace the email
900 address with your own address to test your server. :)
</p
>
902 <p
>The setup procedure is still to complex, and I hope it can be made
903 easier and more automatic. Especially the tor setup need more work.
904 Also, the package include a tor-smtp tool written in C, but its task
905 should probably be rewritten in some script language to make the deb
906 architecture independent. It would probably also make the code easier
907 to review. The tor-smtp tool currently need to listen on a socket for
908 exim to talk to it and is started using xinetd. It would be better if
909 no daemon and no socket is needed. I suspect it is possible to get
910 exim to run a command line tool for delivery instead of talking to a
911 socket, and hope to figure out how in a future version of this
914 <p
>Until I wipe my test machine, I can be reached using the
915 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
921 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
922 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
924 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
925 <description><p
>If you ever had to moderate a mailman list, like the ones on
926 alioth.debian.org, you know the web interface is fairly slow to
927 operate. First you visit one web page, enter the moderation password
928 and get a new page shown with a list of all the messages to moderate
929 and various options for each email address. This take a while for
930 every list you moderate, and you need to do it regularly to do a good
931 job as a list moderator. But there is a quick alternative,
932 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
933 listadmin program
</a
>. It allow you to check lists for new messages
934 to moderate in a fraction of a second. Here is a test run on two
935 lists I recently took over:
</p
>
937 <p
><blockquote
><pre
>
938 % time listadmin xiph
939 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
940 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
946 </pre
></blockquote
></p
>
948 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
949 there are no message in the moderation queue. Every morning I
950 currently moderate
68 mailman lists, and it normally take around two
951 minutes. When I took over the two pkg-xiph lists above a few days
952 ago, there were
400 emails waiting in the moderator queue. It took me
953 less than
15 minutes to process them all using the listadmin
956 <p
>If you install
957 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
958 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
959 with content like this, the moderation task is a breeze:
</p
>
961 <p
><blockquote
><pre
>
962 username username@example.org
965 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
968 adminurl https://{domain}/mailman/admindb/{list}
969 mailman-list@lists.example.com
972 other-list@otherserver.example.org
973 </pre
></blockquote
></p
>
975 <p
>There are other options to set as well. Check the manual page to
976 learn the details.
</p
>
978 <p
>If you are forced to moderate lists on a mailman installation where
979 the SSL certificate is self signed or not properly signed by a
980 generally accepted signing authority, you can set a environment
981 variable when calling listadmin to disable SSL verification:
</p
>
983 <p
><blockquote
><pre
>
984 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
985 </pre
></blockquote
></p
>
987 <p
>If you want to moderate a subset of the lists you take care of, you
988 can provide an argument to the listadmin script like I do in the
989 initial screen dump (the xiph argument). Using an argument, only
990 lists matching the argument string will be processed. This make it
991 quick to accept messages if you notice the moderation request in your
994 <p
>Without the listadmin program, I would never be the moderator of
68
995 mailing lists, as I simply do not have time to spend on that if the
996 process was any slower. The listadmin program have saved me hours of
997 time I could spend elsewhere over the years. It truly is nice free
1000 <p
>As usual, if you use Bitcoin and want to show your support of my
1001 activities, please send Bitcoin donations to my address
1002 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1004 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1005 configuration example. Also, I
've been told that the
1006 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1012 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1013 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1014 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1015 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1016 <description><p
>When PXE installing laptops with Debian, I often run into the
1017 problem that the WiFi card require some firmware to work properly.
1018 And it has been a pain to fix this using preseeding in Debian.
1019 Normally something more is needed. But thanks to
1020 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1021 package
</a
> and its recent tasksel extension, it has now become easy
1022 to do this using simple preseeding.
</p
>
1024 <p
>The isenkram-cli package provide tasksel tasks which will install
1025 firmware for the hardware found in the machine (actually, requested by
1026 the kernel modules for the hardware). (It can also install user space
1027 programs supporting the hardware detected, but that is not the focus
1028 of this story.)
</p
>
1030 <p
>To get this working in the default installation, two preeseding
1031 values are needed. First, the isenkram-cli package must be installed
1032 into the target chroot (aka the hard drive) before tasksel is executed
1033 in the pkgsel step of the debian-installer system. This is done by
1034 preseeding the base-installer/includes debconf value to include the
1035 isenkram-cli package. The package name is next passed to debootstrap
1036 for installation. With the isenkram-cli package in place, tasksel
1037 will automatically use the isenkram tasks to detect hardware specific
1038 packages for the machine being installed and install them, because
1039 isenkram-cli contain tasksel tasks.
</p
>
1041 <p
>Second, one need to enable the non-free APT repository, because
1042 most firmware unfortunately is non-free. This is done by preseeding
1043 the apt-mirror-setup step. This is unfortunate, but for a lot of
1044 hardware it is the only option in Debian.
</p
>
1046 <p
>The end result is two lines needed in your preseeding file to get
1047 firmware installed automatically by the installer:
</p
>
1049 <p
><blockquote
><pre
>
1050 base-installer base-installer/includes string isenkram-cli
1051 apt-mirror-setup apt-setup/non-free boolean true
1052 </pre
></blockquote
></p
>
1054 <p
>The current version of isenkram-cli in testing/jessie will install
1055 both firmware and user space packages when using this method. It also
1056 do not work well, so use version
0.15 or later. Installing both
1057 firmware and user space packages might give you a bit more than you
1058 want, so I decided to split the tasksel task in two, one for firmware
1059 and one for user space programs. The firmware task is enabled by
1060 default, while the one for user space programs is not. This split is
1061 implemented in the package currently in unstable.
</p
>
1063 <p
>If you decide to give this a go, please let me know (via email) how
1064 this recipe work for you. :)
</p
>
1066 <p
>So, I bet you are wondering, how can this work. First and
1067 foremost, it work because tasksel is modular, and driven by whatever
1068 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1069 isenkram-cli package place two files for tasksel to find. First there
1070 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1072 <p
><blockquote
><pre
>
1073 Task: isenkram-packages
1075 Description: Hardware specific packages (autodetected by isenkram)
1076 Based on the detected hardware various hardware specific packages are
1078 Test-new-install: show show
1080 Packages: for-current-hardware
1082 Task: isenkram-firmware
1084 Description: Hardware specific firmware packages (autodetected by isenkram)
1085 Based on the detected hardware various hardware specific firmware
1086 packages are proposed.
1087 Test-new-install: mark show
1089 Packages: for-current-hardware-firmware
1090 </pre
></blockquote
></p
>
1092 <p
>The key parts are Test-new-install which indicate how the task
1093 should be handled and the Packages line referencing to a script in
1094 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1095 list of packages to install. The for-current-hardware-firmware script
1096 look like this to list relevant firmware for the machine:
1098 <p
><blockquote
><pre
>
1101 PATH=/usr/sbin:$PATH
1103 isenkram-autoinstall-firmware -l
1104 </pre
></blockquote
></p
>
1106 <p
>With those two pieces in place, the firmware is installed by
1107 tasksel during the normal d-i run. :)
</p
>
1109 <p
>If you want to test what tasksel will install when isenkram-cli is
1110 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1111 --new-install
</tt
> to get the list of packages that tasksel would
1114 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1115 pilots in testing this feature, as isenkram is used there now to
1116 install firmware, replacing the earlier scripts.
</p
>
1121 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1122 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1123 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1124 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1125 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1126 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1127 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1128 on a screen normally showing the bread types and prizes:
</p
>
1130 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1132 <p
>If it had booted as it was supposed to, I would never had known
1133 about this hidden Linux installation. It is interesting what
1134 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1139 <title>New lsdvd release version
0.17 is ready
</title>
1140 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1141 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1142 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1143 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1144 got a new set of developers a few weeks ago, after the original
1145 developer decided to step down and pass the project to fresh blood.
1146 This project is now maintained by Petter Reinholdtsen and Steve
1149 <p
>I just wrapped up
1150 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1151 new lsdvd release
</a
>, available in git or from
1152 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1153 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1158 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1159 <li
>Check for garbage in the program chains, which indicate that a track is
1160 non-existant, to work around additional copy protection
</li
>
1161 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
1162 <li
>Fix pallete display of first entry
</li
>
1163 <li
>Fix include orders
</li
>
1164 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
1165 <li
>Fix the chapter count
</li
>
1166 <li
>Make sure the array size and the array limit used when initialising
1167 the palette size is the same.
</li
>
1168 <li
>Fix array printing.
</li
>
1169 <li
>Correct subsecond calculations.
</li
>
1170 <li
>Add sector information to the output format.
</li
>
1171 <li
>Clean up code to be closer to ANSI C and compile without warnings
1172 with more GCC compiler warnings.
</li
>
1176 <p
>This change bring together patches for lsdvd in use in various
1177 Linux and Unix distributions, as well as patches submitted to the
1178 project the last nine years. Please check it out. :)
</p
>
1183 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
1184 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
1185 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
1186 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
1187 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1188 project
</a
> provide a Linux solution for schools, including a
1189 powerful desktop with education software, a central server providing
1190 web pages, user database, user home directories, central login and PXE
1191 boot of both clients without disk and the installation to install Debian
1192 Edu on machines with disk (and a few other services perhaps to small
1193 to mention here). We in the Debian Edu team are currently working on
1194 the Jessie based version, trying to get everything in shape before the
1195 freeze, to avoid having to maintain our own package repository in the
1197 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
1198 status
</a
> can be seen on the Debian wiki, and there is still heaps of
1199 work left. Some fatal problems block testing, breaking the installer,
1200 but it is possible to work around these to get anyway. Here is a
1201 recipe on how to get the installation limping along.
</p
>
1203 <p
>First, download the test ISO via
1204 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
1205 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
1207 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
1208 The ISO build was broken on Tuesday, so we do not get a new ISO every
1209 12 hours or so, but thankfully the ISO we already got we are able to
1210 install with some tweaking.
</p
>
1212 <p
>When you get to the Debian Edu profile question, go to tty2
1213 (use Alt-Ctrl-F2), run
</p
>
1215 <p
><blockquote
><pre
>
1216 nano /usr/bin/edu-eatmydata-install
1217 </pre
></blockquote
></p
>
1219 <p
>and add
'exit
0' as the second line, disabling the eatmydata
1220 optimization. Return to the installation, select the profile you want
1221 and continue. Without this change, exim4-config will fail to install
1222 due to a known bug in eatmydata.
</p
>
1224 <p
>When you get the grub question at the end, answer /dev/sda (or if
1225 this do not work, figure out what your correct value would be. All my
1226 test machines need /dev/sda, so I have no advice if it do not fit
1227 your need.
</p
>
1229 <p
>If you installed a profile including a graphical desktop, log in as
1230 root after the initial boot from hard drive, and install the
1231 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1232 or mate. If you want several desktop options, install more than one
1233 metapackage. Once this is done, reboot and you should have a working
1234 graphical login screen. This workaround should no longer be needed
1235 once the education-tasks package version
1.801 enter testing in two
1238 <p
>I believe the ISO build will start working on two days when the new
1239 tasksel package enter testing and Steve McIntyre get a chance to
1240 update the debian-cd git repository. The eatmydata, grub and desktop
1241 issues are already fixed in unstable and testing, and should show up
1242 on the ISO as soon as the ISO build start working again. Well the
1243 eatmydata optimization is really just disabled. The proper fix
1244 require an upload by the eatmydata maintainer applying the patch
1245 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
1246 The rest have proper fixes in unstable.
</p
>
1248 <p
>I hope this get you going with the installation testing, as we are
1249 quickly running out of time trying to get our Jessie based
1250 installation ready before the distribution freeze in a month.
</p
>
1255 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
1256 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
1257 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
1258 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
1259 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
1260 to handle my fairly large DVD collection. It is a nice command line
1261 tool to get details about a DVD, like title, tracks, track length,
1262 etc, in XML, Perl or human readable format. But lsdvd have not seen
1263 any new development since
2006 and had a few irritating bugs affecting
1264 its use with some DVDs. Upstream seemed to be dead, and in January I
1265 sent a small probe asking for a version control repository for the
1266 project, without any reply. But I use it regularly and would like to
1267 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
1268 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
1269 the project admin, and after getting a reply from him explaining that
1270 he was no longer interested in the project, I asked if I could take
1271 over. And yesterday, I became project admin.
</p
>
1273 <p
>I
've been in touch with a Gentoo developer and the Debian
1274 maintainer interested in joining forces to maintain the upstream
1275 project, and I hope we can get a new release out fairly quickly,
1276 collecting the patches spread around on the internet into on place.
1277 I
've added the relevant Debian patches to the freshly created git
1278 repository, and expect the Gentoo patches to make it too. If you got
1279 a DVD collection and care about command line tools, check out
1280 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
1281 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1282 list
</a
>. :)
</p
>
1287 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1288 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1290 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1291 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1292 a lot quicker. When we install more than
2000 packages in
1293 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1294 tasksel in the installer, unpacking the binary packages take forever.
1295 A part of the slow I/O issue was discussed in
1296 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1297 much file system sync-ing done by dpkg, which is the package
1298 responsible for unpacking the binary packages. Other parts (like code
1299 executed by postinst scripts) might also sync to disk during
1300 installation. All this sync-ing to disk do not really make sense to
1301 me. If the machine crash half-way through, I start over, I do not try
1302 to salvage the half installed system. So the failure sync-ing is
1303 supposed to protect against, hardware or system crash, is not really
1304 relevant while the installer is running.
</p
>
1306 <p
>A few days ago, I thought of a way to get rid of all the file
1307 system sync()-ing in a fairly non-intrusive way, without the need to
1308 change the code in several packages. The idea is not new, but I have
1309 not heard anyone propose the approach using dpkg-divert before. It
1310 depend on the small and clever package
1311 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1312 uses LD_PRELOAD to replace the system functions for syncing data to
1313 disk with functions doing nothing, thus allowing programs to live
1314 dangerous while speeding up disk I/O significantly. Instead of
1315 modifying the implementation of dpkg, apt and tasksel (which are the
1316 packages responsible for selecting, fetching and installing packages),
1317 it occurred to me that we could just divert the programs away, replace
1318 them with a simple shell wrapper calling
1319 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1320 Two days ago I decided to test the idea, and wrapped up a simple
1321 implementation for the Debian Edu udeb.
</p
>
1323 <p
>The effect was stunning. In my first test it reduced the running
1324 time of the pkgsel step (installing tasks) from
64 to less than
44
1325 minutes (
20 minutes shaved off the installation) on an old Dell
1326 Latitude D505 machine. I am not quite sure what the optimised time
1327 would have been, as I messed up the testing a bit, causing the debconf
1328 priority to get low enough for two questions to pop up during
1329 installation. As soon as I saw the questions I moved the installation
1330 along, but do not know how long the question were holding up the
1331 installation. I did some more measurements using Debian Edu Jessie,
1332 and got these results. The time measured is the time stamp in
1333 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1334 "pkgsel: finishing up
" lines, if you want to do the same measurement
1335 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1336 timing thus do not depend on how quickly the user handle the tasksel
1339 <p
><table
>
1342 <th
>Machine/setup
</th
>
1343 <th
>Original tasksel
</th
>
1344 <th
>Optimised tasksel
</th
>
1345 <th
>Reduction
</th
>
1349 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1350 <td
>64 min (
07:
46-
08:
50)
</td
>
1351 <td
><44 min (
11:
27-
12:
11)
</td
>
1352 <td
>>20 min
18%
</td
>
1356 <td
>Latitude D505 Roaming LXDE
</td
>
1357 <td
>57 min (
08:
48-
09:
45)
</td
>
1358 <td
>34 min (
07:
43-
08:
17)
</td
>
1359 <td
>23 min
40%
</td
>
1363 <td
>Latitude D505 Minimal
</td
>
1364 <td
>22 min (
10:
37-
10:
59)
</td
>
1365 <td
>11 min (
11:
16-
11:
27)
</td
>
1366 <td
>11 min
50%
</td
>
1370 <td
>Thinkpad X200 Minimal
</td
>
1371 <td
>6 min (
08:
19-
08:
25)
</td
>
1372 <td
>4 min (
08:
04-
08:
08)
</td
>
1373 <td
>2 min
33%
</td
>
1377 <td
>Thinkpad X200 Roaming KDE
</td
>
1378 <td
>19 min (
09:
21-
09:
40)
</td
>
1379 <td
>15 min (
10:
25-
10:
40)
</td
>
1380 <td
>4 min
21%
</td
>
1383 </table
></p
>
1385 <p
>The test is done using a netinst ISO on a USB stick, so some of the
1386 time is spent downloading packages. The connection to the Internet
1387 was
100Mbit/s during testing, so downloading should not be a
1388 significant factor in the measurement. Download typically took a few
1389 seconds to a few minutes, depending on the amount of packages being
1390 installed.
</p
>
1392 <p
>The speedup is implemented by using two hooks in
1393 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
1394 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
1395 finish-install.d hook to remove the divert at the end of the
1396 installation. I picked the pre-pkgsel.d hook instead of the
1397 post-base-installer.d hook because I test using an ISO without the
1398 eatmydata package included, and the post-base-installer.d hook in
1399 Debian Edu can only operate on packages included in the ISO. The
1400 negative effect of this is that I am unable to activate this
1401 optimization for the kernel installation step in d-i. If the code is
1402 moved to the post-base-installer.d hook, the speedup would be larger
1403 for the entire installation.
</p
>
1405 <p
>I
've implemented this in the
1406 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
1407 git repository, and plan to provide the optimization as part of the
1408 Debian Edu installation. If you want to test this yourself, you can
1409 create two files in the installer (or in an udeb). One shell script
1410 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
1412 <p
><blockquote
><pre
>
1415 . /usr/share/debconf/confmodule
1417 logger -t my-pkgsel
"info: $*
"
1420 logger -t my-pkgsel
"error: $*
"
1422 override_install() {
1423 apt-install eatmydata || true
1424 if [ -x /target/usr/bin/eatmydata ] ; then
1425 for bin in dpkg apt-get aptitude tasksel ; do
1427 # Test that the file exist and have not been diverted already.
1428 if [ -f /target$file ] ; then
1429 info
"diverting $file using eatmydata
"
1430 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
1431 > /target$file.edu
1432 chmod
755 /target$file.edu
1433 in-target dpkg-divert --package debian-edu-config \
1434 --rename --quiet --add $file
1435 ln -sf ./$bin.edu /target$file
1437 error
"unable to divert $file, as it is missing.
"
1441 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
1446 </pre
></blockquote
></p
>
1448 <p
>To clean up, another shell script should go into
1449 /usr/lib/finish-install.d/ with code like this:
1451 <p
><blockquote
><pre
>
1453 . /usr/share/debconf/confmodule
1455 logger -t my-finish-install
"error: $@
"
1457 remove_install_override() {
1458 for bin in dpkg apt-get aptitude tasksel ; do
1460 if [ -x /target$file.edu ] ; then
1462 in-target dpkg-divert --package debian-edu-config \
1463 --rename --quiet --remove $file
1466 error
"Missing divert for $file.
"
1469 sync # Flush file buffers before continuing
1472 remove_install_override
1473 </pre
></blockquote
></p
>
1475 <p
>In Debian Edu, I placed both code fragments in a separate script
1476 edu-eatmydata-install and call it from the pre-pkgsel.d and
1477 finish-install.d scripts.
</p
>
1479 <p
>By now you might ask if this change should get into the normal
1480 Debian installer too? I suspect it should, but am not sure the
1481 current debian-installer coordinators find it useful enough. It also
1482 depend on the side effects of the change. I
'm not aware of any, but I
1483 guess we will see if the change is safe after some more testing.
1484 Perhaps there is some package in Debian depending on sync() and
1485 fsync() having effect? Perhaps it should go into its own udeb, to
1486 allow those of us wanting to enable it to do so without affecting
1489 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
1490 will break installation of all programs using gnutls because of
1491 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
1492 eatmydata package in Debian will solve it.
</p
>
1494 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
1495 the optimization work again. And I have discovered that the
1496 dpkg-divert trick is not really needed and implemented a slightly
1497 simpler approach as part of the debian-edu-install package. See
1498 tools/edu-eatmydata-install in the source package.
</p
>
1500 <p
>Update
2014-
11-
11: Unfortunately, a new
1501 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
1502 triggering on i386 made it into testing, and broke this installation
1503 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
1504 request
768893</a
> is accepted, it should be working again.
</p
>
1509 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
1510 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
1511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
1512 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
1513 <description><p
>Yesterday, I had the pleasure of attending a talk with the
1514 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
1515 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
1516 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
1517 learn that there is a large set of publicly available key servers to
1518 use when looking for peoples public key. So far I have used
1519 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1520 were misbehaving, but those days are ended. The servers I have used
1521 up until yesterday have been slow and some times unavailable. I hope
1522 those problems are gone now.
</p
>
1524 <p
>Behind the round robin DNS entry of the
1525 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
1526 there is a pool of more than
100 keyservers which are checked every
1527 day to ensure they are well connected and up to date. It must be
1528 better than what I have used so far. :)
</p
>
1530 <p
>Yesterdays speaker told me that the service is the default
1531 keyserver provided by the default configuration in GnuPG, but this do
1532 not seem to be used in Debian. Perhaps it should?
</p
>
1534 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
1537 <p
><blockquote
><pre
>
1538 keyserver pool.sks-keyservers.net
1539 </pre
></blockquote
></p
>
1541 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
1542 entries in DNS. Just for fun, I did just that at work, so now every
1543 user of GnuPG at the University of Oslo should find a OpenGPG
1544 keyserver automatically should their need it:
</p
>
1546 <p
><blockquote
><pre
>
1547 % host -t srv _pgpkey-http._tcp.uio.no
1548 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
1550 </pre
></blockquote
></p
>
1552 <p
>Now if only
1553 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
1554 HKP lookup protocol
</a
> supported finding signature paths, I would be
1555 very happy. It can look up a given key or search for a user ID, but I
1556 normally do not want that, but to find a trust path from my key to
1557 another key. Given a user ID or key ID, I would like to find (and
1558 download) the keys representing a signature path from my key to the
1559 key in question, to be able to get a trust path between the two keys.
1560 This is as far as I can tell not possible today. Perhaps something
1561 for a future version of the protocol?
</p
>
1566 <title>From English wiki to translated PDF and epub via Docbook
</title>
1567 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
1568 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
1569 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
1570 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1571 project
</a
> provide an instruction manual for teachers, system
1572 administrators and other users that contain useful tips for setting up
1573 and maintaining a Debian Edu installation. This text is about how the
1574 text processing of this manual is handled in the project.
</p
>
1576 <p
>One goal of the project is to provide information in the native
1577 language of its users, and for this we need to handle translations.
1578 But we also want to make sure each language contain the same
1579 information, so for this we need a good way to keep the translations
1580 in sync. And we want it to be easy for our users to improve the
1581 documentation, avoiding the need to learn special formats or tools to
1582 contribute, and the obvious way to do this is to make it possible to
1583 edit the documentation using a web browser. We also want it to be
1584 easy for translators to keep the translation up to date, and give them
1585 help in figuring out what need to be translated. Here is the list of
1586 tools and the process we have found trying to reach all these
1589 <p
>We maintain the authoritative source of our manual in the
1590 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
1591 wiki
</a
>, as several wiki pages written in English. It consist of one
1592 front page with references to the different chapters, several pages
1593 for each chapter, and finally one
"collection page
" gluing all the
1594 chapters together into one large web page (aka
1595 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
1596 AllInOne page
</a
>). The AllInOne page is the one used for further
1597 processing and translations. Thanks to the fact that the
1598 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
1599 wiki.debian.org support exporting pages in
1600 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
1601 the list of pages to export using the raw version of the AllInOne
1602 page, loop over each of them to generate a Docbook XML version of the
1603 manual. This process also download images and transform image
1604 references to use the locally downloaded images. The generated
1605 Docbook XML files are slightly broken, so some post-processing is done
1606 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
1607 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1608 a handfull of images. The XML file can now be used to generate PDF, HTML
1609 and epub versions of the English manual. This is the basic step of
1610 our process, making PDF (using dblatex), HTML (using xsltproc) and
1611 epub (using dbtoepub) version from Docbook XML, and the resulting files
1612 are placed in the debian-edu-doc-en binary package.
</p
>
1614 <p
>But English documentation is not enough for us. We want translated
1615 documentation too, and we want to make it easy for translators to
1616 track the English original. For this we use the
1617 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
1618 which allow us to transform the English Docbook XML file into a
1619 translation file (a .pot file), usable with the normal gettext based
1620 translation tools used by those translating free software. The pot
1621 file is used to create and maintain translation files (several .po
1622 files), which the translations update with the native language
1623 translations of all titles, paragraphs and blocks of text in the
1624 original. The next step is combining the original English Docbook XML
1625 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1626 create a translated Docbook XML file (in this case
1627 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1628 translated, if the translation is not complete) Docbook XML file can
1629 then be used like the original to create a PDF, HTML and epub version
1630 of the documentation.
</p
>
1632 <p
>The translators use different tools to edit the .po files. We
1634 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
1635 while some use emacs and vi, others can use web based editors like
1636 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
1637 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
1638 is where the .po file end up, in our git repository. Updated
1639 translations can either be committed directly to git, or submitted as
1640 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
1641 against the debian-edu-doc package
</a
>.
</p
>
1643 <p
>One challenge is images, which both might need to be translated (if
1644 they show translated user applications), and are needed in different
1645 formats when creating PDF and HTML versions (epub is a HTML version in
1646 this regard). For this we transform the original PNG images to the
1647 needed density and format during build, and have a way to provide
1648 translated images by storing translated versions in
1649 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1650 package maintainers know more.
</p
>
1652 <p
>If you wonder what the result look like, we provide
1653 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
1654 of the documentation packages on the web
</a
>. See for example the
1655 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
1656 PDF version
</a
> or the
1657 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
1658 HTML version
</a
>. We do not yet build the epub version by default,
1659 but perhaps it will be done in the future.
</p
>
1661 <p
>To learn more, check out
1662 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
1663 debian-edu-doc package
</a
>,
1664 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
1665 manual on the wiki
</a
> and
1666 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
1667 translation instructions
</a
> in the manual.
</p
>
1672 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
1673 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
1674 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
1675 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
1676 <description><p
>It would be nice if it was easier in Debian to get all the hardware
1677 related packages relevant for the computer installed automatically.
1678 So I implemented one, using
1679 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
1680 package
</a
>. To use it, install the tasksel and isenkram packages and
1681 run tasksel as user root. You should be presented with a new option,
1682 "Hardware specific packages (autodetected by isenkram)
". When you
1683 select it, tasksel will install the packages isenkram claim is fit for
1684 the current hardware, hot pluggable or not.
<p
>
1686 <p
>The implementation is in two files, one is the tasksel menu entry
1687 description, and the other is the script used to extract the list of
1688 packages to install. The first part is in
1689 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
1692 <p
><blockquote
><pre
>
1695 Description: Hardware specific packages (autodetected by isenkram)
1696 Based on the detected hardware various hardware specific packages are
1698 Test-new-install: mark show
1700 Packages: for-current-hardware
1701 </pre
></blockquote
></p
>
1703 <p
>The second part is in
1704 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
1707 <p
><blockquote
><pre
>
1712 isenkram-autoinstall-firmware -l
1714 </pre
></blockquote
></p
>
1716 <p
>All in all, a very short and simple implementation making it
1717 trivial to install the hardware dependent package we all may want to
1718 have installed on our machines. I
've not been able to find a way to
1719 get tasksel to tell you exactly which packages it plan to install
1720 before doing the installation. So if you are curious or careful,
1721 check the output from the isenkram-* command line tools first.
</p
>
1723 <p
>The information about which packages are handling which hardware is
1724 fetched either from the isenkram package itself in
1725 /usr/share/isenkram/, from git.debian.org or from the APT package
1726 database (using the Modaliases header). The APT package database
1727 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1728 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
1729 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
1730 the python-apt code (bug
1731 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
1732 workaround I was able to get rid of the file descriptor leak and
1733 reduce the memory leak from ~
30 MiB per hardware detection down to
1734 around
2 MiB per hardware detection. It should make the desktop
1735 daemon a lot more useful. The fix is in version
0.7 uploaded to
1736 unstable today.
</p
>
1738 <p
>I believe the current way of mapping hardware to packages in
1739 Isenkram is is a good draft, but in the future I expect isenkram to
1740 use the AppStream data source for this. A proposal for getting proper
1741 AppStream support into Debian is floating around as
1742 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
1743 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
1744 project
</a
> will take place this summer to improve the situation. I
1745 look forward to seeing the result, and welcome patches for isenkram to
1746 start using the information when it is ready.
</p
>
1748 <p
>If you want your package to map to some specific hardware, either
1749 add a
"Xb-Modaliases
" header to your control file like I did in
1750 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
1751 package
</a
> or submit a bug report with the details to the isenkram
1753 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
1754 blog posts tagged isenkram
</a
> for details on the notation. I expect
1755 the information will be migrated to AppStream eventually, but for the
1756 moment I got no better place to store it.
</p
>
1761 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
1762 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
1763 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
1764 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
1765 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1766 project
</a
> is working on providing the software and hardware to make
1767 it easy for non-technical people to host their data and communication
1768 at home, and being able to communicate with their friends and family
1769 encrypted and away from prying eyes. It is still going strong, and
1770 today a major mile stone was reached.
</p
>
1772 <p
>Today, the last of the packages currently used by the project to
1773 created the system images were accepted into Debian Unstable. It was
1774 the freedombox-setup package, which is used to configure the images
1775 during build and on the first boot. Now all one need to get going is
1776 the build code from the freedom-maker git repository and packages from
1777 Debian. And once the freedombox-setup package enter testing, we can
1778 build everything directly from Debian. :)
</p
>
1780 <p
>Some key packages used by Freedombox are
1781 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
1782 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
1783 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
1784 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
1785 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
1786 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
1787 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
1788 are plans to integrate more packages into the setup. User
1789 documentation is maintained on the Debian wiki. Please
1790 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
1791 the manual
</a
> and help us improve it.
</p
>
1793 <p
>To test for yourself and create boot images with the FreedomBox
1794 setup, run this on a Debian machine using a user with sudo rights to
1795 become root:
</p
>
1797 <p
><pre
>
1798 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1799 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1801 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1803 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1804 </pre
></p
>
1806 <p
>Root access is needed to run debootstrap and mount loopback
1807 devices. See the README in the freedom-maker git repo for more
1808 details on the build. If you do not want all three images, trim the
1809 make line. Note that the virtualbox-image target is not really
1810 virtualbox specific. It create a x86 image usable in kvm, qemu,
1811 vmware and any other x86 virtual machine environment. You might need
1812 the version of vmdebootstrap in Jessie to get the build working, as it
1813 include fixes for a race condition with kpartx.
</p
>
1815 <p
>If you instead want to install using a Debian CD and the preseed
1816 method, boot a Debian Wheezy ISO and use this boot argument to load
1817 the preseed values:
</p
>
1819 <p
><pre
>
1820 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1821 </pre
></p
>
1823 <p
>I have not tested it myself the last few weeks, so I do not know if
1824 it still work.
</p
>
1826 <p
>If you wonder how to help, one task you could look at is using
1827 systemd as the boot system. It will become the default for Linux in
1828 Jessie, so we need to make sure it is usable on the Freedombox. I did
1829 a simple test a few weeks ago, and noticed dnsmasq failed to start
1830 during boot when using systemd. I suspect there are other problems
1831 too. :) To detect problems, there is a test suite included, which can
1832 be run from the plinth web interface.
</p
>
1834 <p
>Give it a go and let us know how it goes on the mailing list, and help
1835 us get the new release published. :) Please join us on
1836 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1837 irc.debian.org)
</a
> and
1838 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1839 mailing list
</a
> if you want to help make this vision come true.
</p
>
1844 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
1845 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
1846 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
1847 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
1848 <description><p
>For a while now, I have been looking for a sensible offsite backup
1849 solution for use at home. My requirements are simple, it must be
1850 cheap and locally encrypted (in other words, I keep the encryption
1851 keys, the storage provider do not have access to my private files).
1852 One idea me and my friends had many years ago, before the cloud
1853 storage providers showed up, was to use Google mail as storage,
1854 writing a Linux block device storing blocks as emails in the mail
1855 service provided by Google, and thus get heaps of free space. On top
1856 of this one can add encryption, RAID and volume management to have
1857 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1858 I never found time to implement such system. But the last few weeks I
1859 have looked at a system called
1860 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
1861 mounted network backed file system with the features I need.
</p
>
1863 <p
>S3QL is a fuse file system with a local cache and cloud storage,
1864 handling several different storage providers, any with Amazon S3,
1865 Google Drive or OpenStack API. There are heaps of such storage
1866 providers. S3QL can also use a local directory as storage, which
1867 combined with sshfs allow for file storage on any ssh server. S3QL
1868 include support for encryption, compression, de-duplication, snapshots
1869 and immutable file systems, allowing me to mount the remote storage as
1870 a local mount point, look at and use the files as if they were local,
1871 while the content is stored in the cloud as well. This allow me to
1872 have a backup that should survive fire. The file system can not be
1873 shared between several machines at the same time, as only one can
1874 mount it at the time, but any machine with the encryption key and
1875 access to the storage service can mount it if it is unmounted.
</p
>
1877 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
1878 package is included already. So to get started, run
<tt
>apt-get
1879 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
1880 Greenqloud, after reading their nice recipe on
1881 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
1882 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
1883 in Iceland more than those in USA when it come to keeping my personal
1884 data safe and private, and thus would rather spend money on a company
1885 in Iceland. Another nice recipe is available from the article
1886 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
1887 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
1888 Admin magazine. When the provider is picked, figure out how to get
1889 the API key needed to connect to the storage API. With Greencloud,
1890 the key did not show up until I had added payment details to my
1893 <p
>Armed with the API access details, it is time to create the file
1894 system. First, create a new bucket in the cloud. This bucket is the
1895 file system storage area. I picked a bucket name reflecting the
1896 machine that was going to store data there, but any name will do.
1897 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
1898 the API login and password, and a locally created password. Store it
1899 all in ~root/.s3ql/authinfo2 like this:
1901 <p
><blockquote
><pre
>
1903 storage-url: s3c://s.greenqloud.com:
443/bucket-name
1904 backend-login: API-login
1905 backend-password: API-password
1906 fs-passphrase: local-password
1907 </pre
></blockquote
></p
>
1909 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
1910 but any sensible way to create a fairly random password should do it.
1911 Armed with these details, it is now time to run mkfs, entering the API
1912 details and password to create it:
</p
>
1914 <p
><blockquote
><pre
>
1915 # mkdir -m
700 /var/lib/s3ql-cache
1916 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1917 --ssl s3c://s.greenqloud.com:
443/bucket-name
1918 Enter backend login:
1919 Enter backend password:
1920 Before using S3QL, make sure to read the user
's guide, especially
1921 the
'Important Rules to Avoid Loosing Data
' section.
1922 Enter encryption password:
1923 Confirm encryption password:
1924 Generating random encryption key...
1925 Creating metadata tables...
1935 Compressing and uploading metadata...
1936 Wrote
0.00 MB of compressed metadata.
1937 #
</pre
></blockquote
></p
>
1939 <p
>The next step is mounting the file system to make the storage available.
1941 <p
><blockquote
><pre
>
1942 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1943 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1944 Using
4 upload threads.
1945 Downloading and decompressing metadata...
1955 Mounting filesystem...
1957 Filesystem Size Used Avail Use% Mounted on
1958 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
1960 </pre
></blockquote
></p
>
1962 <p
>The file system is now ready for use. I use rsync to store my
1963 backups in it, and as the metadata used by rsync is downloaded at
1964 mount time, no network traffic (and storage cost) is triggered by
1965 running rsync. To unmount, one should not use the normal umount
1966 command, as this will not flush the cache to the cloud storage, but
1967 instead running the umount.s3ql command like this:
1969 <p
><blockquote
><pre
>
1972 </pre
></blockquote
></p
>
1974 <p
>There is a fsck command available to check the file system and
1975 correct any problems detected. This can be used if the local server
1976 crashes while the file system is mounted, to reset the
"already
1977 mounted
" flag. This is what it look like when processing a working
1978 file system:
</p
>
1980 <p
><blockquote
><pre
>
1981 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
1982 Using cached metadata.
1983 File system seems clean, checking anyway.
1984 Checking DB integrity...
1985 Creating temporary extra indices...
1986 Checking lost+found...
1987 Checking cached objects...
1988 Checking names (refcounts)...
1989 Checking contents (names)...
1990 Checking contents (inodes)...
1991 Checking contents (parent inodes)...
1992 Checking objects (reference counts)...
1993 Checking objects (backend)...
1994 ..processed
5000 objects so far..
1995 ..processed
10000 objects so far..
1996 ..processed
15000 objects so far..
1997 Checking objects (sizes)...
1998 Checking blocks (referenced objects)...
1999 Checking blocks (refcounts)...
2000 Checking inode-block mapping (blocks)...
2001 Checking inode-block mapping (inodes)...
2002 Checking inodes (refcounts)...
2003 Checking inodes (sizes)...
2004 Checking extended attributes (names)...
2005 Checking extended attributes (inodes)...
2006 Checking symlinks (inodes)...
2007 Checking directory reachability...
2008 Checking unix conventions...
2009 Checking referential integrity...
2010 Dropping temporary indices...
2011 Backing up old metadata...
2021 Compressing and uploading metadata...
2022 Wrote
0.89 MB of compressed metadata.
2024 </pre
></blockquote
></p
>
2026 <p
>Thanks to the cache, working on files that fit in the cache is very
2027 quick, about the same speed as local file access. Uploading large
2028 amount of data is to me limited by the bandwidth out of and into my
2029 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2030 which is very close to my upload speed, and downloading the same
2031 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2032 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2033 network, not the file system code. I do not know what a good cache
2034 size would be, but suspect that the cache should e larger than your
2035 working set.
</p
>
2037 <p
>I mentioned that only one machine can mount the file system at the
2038 time. If another machine try, it is told that the file system is
2041 <p
><blockquote
><pre
>
2042 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2043 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2044 Using
8 upload threads.
2045 Backend reports that fs is still mounted elsewhere, aborting.
2047 </pre
></blockquote
></p
>
2049 <p
>The file content is uploaded when the cache is full, while the
2050 metadata is uploaded once every
24 hour by default. To ensure the
2051 file system content is flushed to the cloud, one can either umount the
2052 file system, or ask S3QL to flush the cache and metadata using
2055 <p
><blockquote
><pre
>
2056 # s3qlctrl upload-meta /s3ql
2057 # s3qlctrl flushcache /s3ql
2059 </pre
></blockquote
></p
>
2061 <p
>If you are curious about how much space your data uses in the
2062 cloud, and how much compression and deduplication cut down on the
2063 storage usage, you can use s3qlstat on the mounted file system to get
2066 <p
><blockquote
><pre
>
2068 Directory entries:
9141
2071 Total data size:
22049.38 MB
2072 After de-duplication:
21955.46 MB (
99.57% of total)
2073 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2074 Database size:
2.39 MB (uncompressed)
2075 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2077 </pre
></blockquote
></p
>
2079 <p
>I mentioned earlier that there are several possible suppliers of
2080 storage. I did not try to locate them all, but am aware of at least
2081 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2082 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2083 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2084 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2085 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2086 accept payment in Bitcoin. Pick one that suit your need. Some of
2087 them provide several GiB of free storage, but the prize models are
2088 quite different and you will have to figure out what suits you
2091 <p
>While researching this blog post, I had a look at research papers
2092 and posters discussing the S3QL file system. There are several, which
2093 told me that the file system is getting a critical check by the
2094 science community and increased my confidence in using it. One nice
2096 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2097 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2098 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2099 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2100 and Pamela Smith. Please have a look.
</p
>
2102 <p
>Given my problems with different file systems earlier, I decided to
2103 check out the mounted S3QL file system to see if it would be usable as
2104 a home directory (in other word, that it provided POSIX semantics when
2105 it come to locking and umask handling etc). Running
2106 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2107 test code to check file system semantics
</a
>, I was happy to discover that
2108 no error was found. So the file system can be used for home
2109 directories, if one chooses to do so.
</p
>
2111 <p
>If you do not want a locally file system, and want something that
2112 work without the Linux fuse file system, I would like to mention the
2113 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2114 provide locally encrypted backup using a command line client. It have
2115 a nicer access control system, where one can split out read and write
2116 access, allowing some systems to write to the backup and others to
2117 only read from it.
</p
>
2119 <p
>As usual, if you use Bitcoin and want to show your support of my
2120 activities, please send Bitcoin donations to my address
2121 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2126 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2127 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2129 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2130 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2131 project
</a
> is working on providing the software and hardware for
2132 making it easy for non-technical people to host their data and
2133 communication at home, and being able to communicate with their
2134 friends and family encrypted and away from prying eyes. It has been
2135 going on for a while, and is slowly progressing towards a new test
2136 release (
0.2).
</p
>
2138 <p
>And what day could be better than the Pi day to announce that the
2139 new version will provide
"hard drive
" / SD card / USB stick images for
2140 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2141 system), and can also be installed using a Debian installer preseed
2142 file. The Debian based Freedombox is now based on Debian Jessie,
2143 where most of the needed packages used are already present. Only one,
2144 the freedombox-setup package, is missing. To try to build your own
2145 boot image to test the current status, fetch the freedom-maker scripts
2147 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2148 with a user with sudo access to become root:
2151 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2153 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2154 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2156 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2159 <p
>Root access is needed to run debootstrap and mount loopback
2160 devices. See the README for more details on the build. If you do not
2161 want all three images, trim the make line. But note that thanks to
<a
2162 href=
"https://bugs.debian.org/
741407">a race condition in
2163 vmdebootstrap
</a
>, the build might fail without the patch to the
2164 kpartx call.
</p
>
2166 <p
>If you instead want to install using a Debian CD and the preseed
2167 method, boot a Debian Wheezy ISO and use this boot argument to load
2168 the preseed values:
</p
>
2171 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2174 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
2175 recently introduced bug in apt in Jessie
</a
>, the installer will
2176 currently hang while setting up APT sources. Killing the
2177 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
2178 installation will get the installation going. This affect all
2179 installations in Jessie, and I expect it will be fixed soon.
</p
>
2181 <p
>Give it a go and let us know how it goes on the mailing list, and help
2182 us get the new release published. :) Please join us on
2183 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2184 irc.debian.org)
</a
> and
2185 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2186 mailing list
</a
> if you want to help make this vision come true.
</p
>
2191 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
2192 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
2193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
2194 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
2195 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
2196 innetgr tools, because I needed them in
2197 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
2198 ng-utils, and it has served me well. I placed the project under the
2199 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
2200 repository. But many years ago, the CVS repository was dropped (lost,
2201 not migrated to new hardware, not sure), and the project have lacked a
2202 proper home since then.
</p
>
2204 <p
>Last summer, I had a look at the package and made a new release
2205 fixing a irritating crash bug, but was unable to store the changes in
2206 a proper source control system. I applied for a project on
2207 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
2208 to follow up on it. Until today. :)
</p
>
2210 <p
>After many hours of cleaning and migration, the ng-utils project
2211 now have a new home, and a git repository with the highlight of the
2212 history of the project. I published all release tarballs and imported
2213 them into the git repository. As the project is really stable and not
2214 expected to gain new features any time soon, I decided to make a new
2215 release and call it
1.0. Visit the new project home on
2216 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
2217 if you want to check it out. The new version is also uploaded into
2218 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
2223 <title>Testing sysvinit from experimental in Debian Hurd
</title>
2224 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
2225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
2226 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
2227 <description><p
>A few days ago I decided to try to help the Hurd people to get
2228 their changes into sysvinit, to allow them to use the normal sysvinit
2229 boot system instead of their old one. This follow up on the
2230 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
2231 Google Summer of Code work
</a
> done last summer by Justus Winter to
2232 get Debian on Hurd working more like Debian on Linux. To get started,
2233 I downloaded a prebuilt hard disk image from
2234 <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
>,
2235 and started it using virt-manager.
</p
>
2237 <p
>The first think I had to do after logging in (root without any
2238 password) was to get the network operational. I followed
2239 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
2240 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
2241 commands as root to get the machine to accept a IP address from the
2242 kvm internal DHCP server:
</p
>
2244 <p
><blockquote
><pre
>
2245 settrans -fgap /dev/netdde /hurd/netdde
2246 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
2247 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
2249 </pre
></blockquote
></p
>
2251 <p
>After this, the machine had internet connectivity, and I could
2252 upgrade it and install the sysvinit packages from experimental and
2253 enable it as the default boot system in Hurd.
</p
>
2255 <p
>But before I did that, I set a password on the root user, as ssh is
2256 running on the machine it for ssh login to work a password need to be
2257 set. Also, note that a bug somewhere in openssh on Hurd block
2258 compression from working. Remember to turn that off on the client
2261 <p
>Run these commands as root to upgrade and test the new sysvinit
2264 <p
><blockquote
><pre
>
2265 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
2266 deb http://http.debian.net/debian/ experimental main
2269 apt-get dist-upgrade
2270 apt-get install -t experimental initscripts sysv-rc sysvinit \
2271 sysvinit-core sysvinit-utils
2272 update-alternatives --config runsystem
2273 </pre
></blockquote
></p
>
2275 <p
>To reboot after switching boot system, you have to use
2276 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
2277 yet a sysvinit process able to receive the signals from the normal
2278 'reboot
' command. After switching to sysvinit as the boot system,
2279 upgrading every package and rebooting, the network come up with DHCP
2280 after boot as it should, and the settrans/pkill hack mentioned at the
2281 start is no longer needed. But for some strange reason, there are no
2282 longer any login prompt in the virtual console, so I logged in using
2285 <p
>Note that there are some race conditions in Hurd making the boot
2286 fail some times. No idea what the cause is, but hope the Hurd porters
2287 figure it out. At least Justus said on IRC (#debian-hurd on
2288 irc.debian.org) that they are aware of the problem. A way to reduce
2289 the impact is to upgrade to the Hurd packages built by Justus by
2290 adding this repository to the machine:
</p
>
2292 <p
><blockquote
><pre
>
2293 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2294 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2296 </pre
></blockquote
></p
>
2298 <p
>At the moment the prebuilt virtual machine get some packages from
2299 http://ftp.debian-ports.org/debian, because some of the packages in
2300 unstable do not yet include the required patches that are lingering in
2301 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2303 <p
><blockquote
><pre
>
2304 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2305 i emacs - GNU Emacs editor (metapackage)
2306 i gdb - GNU Debugger
2307 i hurd-recommended - Miscellaneous translators
2308 i isc-dhcp-client - ISC DHCP client
2309 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2310 i libc-bin - Embedded GNU C Library: Binaries
2311 i libc-dev-bin - Embedded GNU C Library: Development binaries
2312 i libc0.3 - Embedded GNU C Library: Shared libraries
2313 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2314 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2315 i multiarch-support - Transitional package to ensure multiarch compatibilit
2316 i A x11-common - X Window System (X.Org) infrastructure
2317 i xorg - X.Org X Window System
2318 i A xserver-xorg - X.Org X server
2319 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2321 </pre
></blockquote
></p
>
2323 <p
>All in all, testing hurd has been an interesting experience. :)
2324 X.org did not work out of the box and I never took the time to follow
2325 the porters instructions to fix it. This time I was interested in the
2326 command line stuff.
<p
>
2331 <title>New chrpath release
0.16</title>
2332 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2333 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2334 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2335 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2336 find problems in C, C++ and Java code using static source code
2337 analysis. It can detect a lot of different problems, and is very
2338 useful to find memory and locking bugs in the error handling part of
2339 the source. The company behind it provide
2340 <a href=
"https://scan.coverity.com/
">check of free software projects as
2341 a community service
</a
>, and many hundred free software projects are
2342 already checked. A few days ago I decided to have a closer look at
2343 the Coverity system, and discovered that the
2344 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2345 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2346 projects I am involved with was already registered. But these are
2347 fairly big, and I would also like to have a small and easy project to
2348 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2349 checking of the chrpath project
</a
>. It was
2350 added to the checker and discovered seven potential defects. Six of
2351 these were real, mostly resource
"leak
" when the program detected an
2352 error. Nothing serious, as the resources would be released a fraction
2353 of a second later when the program exited because of the error, but it
2354 is nice to do it right in case the source of the program some time in
2355 the future end up in a library. Having fixed all defects and added
2356 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
2357 mailing list for the chrpath developers
</a
>, I decided it was time to
2358 publish a new release. These are the release notes:
</p
>
2360 <p
>New in
0.16 released
2014-
01-
14:
</p
>
2364 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
2365 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
2366 <li
>Mention new project mailing list in the documentation.
</li
>
2371 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2372 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
2373 project if something is wrong with the new release. The test suite
2374 did not discover any old errors, so if you find a new one, please also
2375 include a test suite check.
</p
>
2380 <title>New chrpath release
0.15</title>
2381 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
2382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
2383 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
2384 <description><p
>After many years break from the package and a vain hope that
2385 development would be continued by someone else, I finally pulled my
2386 acts together this morning and wrapped up a new release of chrpath,
2387 the command line tool to modify the rpath and runpath of already
2388 compiled ELF programs. The update was triggered by the persistence of
2389 Isha Vishnoi at IBM, which needed a new config.guess file to get
2390 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
2391 is working on. I checked the
2392 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
2393 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
2394 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
2395 packages for interesting patches (failed to find the source from
2396 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2397 These are the release notes:
</p
>
2399 <p
>New in
0.15 released
2013-
11-
24:
</p
>
2403 <li
>Updated config.sub and config.guess from the GNU project to work
2404 with newer architectures. Thanks to isha vishnoi for the heads
2407 <li
>Updated README with current URLs.
</li
>
2409 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2410 Matthias Klose.
</li
>
2412 <li
>Added missing help for -k|--keepgoing option, using patch by
2413 Petr Machata found in Fedora.
</li
>
2415 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
2416 .dynamic is a NULL terminated string. Based on patch found in
2417 Fedora credited Axel Thimm and Christian Krause.
</li
>
2422 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2423 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
2424 project if something is wrong with the new release. The test suite
2425 did not discover any old errors, so if you find a new one, please also
2426 include a testsuite check.
</p
>
2431 <title>Debian init.d boot script example for rsyslog
</title>
2432 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
2433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
2434 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
2435 <description><p
>If one of the points of switching to a new init system in Debian is
2436 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
2437 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
2438 init.d scripts at all. Here is an example init.d script, ie a rewrite
2439 of /etc/init.d/rsyslog:
</p
>
2441 <p
><pre
>
2442 #!/lib/init/init-d-script
2445 # Required-Start: $remote_fs $time
2446 # Required-Stop: umountnfs $time
2447 # X-Stop-After: sendsigs
2448 # Default-Start:
2 3 4 5
2449 # Default-Stop:
0 1 6
2450 # Short-Description: enhanced syslogd
2451 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2452 # It is quite compatible to stock sysklogd and can be
2453 # used as a drop-in replacement.
2455 DESC=
"enhanced syslogd
"
2456 DAEMON=/usr/sbin/rsyslogd
2457 </pre
></p
>
2459 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
2460 script was
137 lines, and the above is just
15 lines, most of it meta
2461 info/comments.
</p
>
2463 <p
>How to do this, you ask? Well, one create a new script
2464 /lib/init/init-d-script looking something like this:
2466 <p
><pre
>
2469 # Define LSB log_* functions.
2470 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
2471 # and status_of_proc is working.
2472 . /lib/lsb/init-functions
2475 # Function that starts the daemon/service
2481 #
0 if daemon has been started
2482 #
1 if daemon was already running
2483 #
2 if daemon could not be started
2484 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
2486 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2489 # Add code here, if necessary, that waits for the process to be ready
2490 # to handle requests from services started subsequently which depend
2491 # on this one. As a last resort, sleep for some time.
2495 # Function that stops the daemon/service
2500 #
0 if daemon has been stopped
2501 #
1 if daemon was already stopped
2502 #
2 if daemon could not be stopped
2503 # other if a failure occurred
2504 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
2505 RETVAL=
"$?
"
2506 [
"$RETVAL
" =
2 ]
&& return
2
2507 # Wait for children to finish too if this is a daemon that forks
2508 # and if the daemon is only ever run from this initscript.
2509 # If the above conditions are not satisfied then add some other code
2510 # that waits for the process to drop all resources that could be
2511 # needed by services started subsequently. A last resort is to
2512 # sleep for some time.
2513 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
2514 [
"$?
" =
2 ]
&& return
2
2515 # Many daemons don
't delete their pidfiles when they exit.
2517 return
"$RETVAL
"
2521 # Function that sends a SIGHUP to the daemon/service
2525 # If the daemon can reload its configuration without
2526 # restarting (for example, when it is sent a SIGHUP),
2527 # then implement that here.
2529 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
2534 scriptbasename=
"$(basename $
1)
"
2535 echo
"SN: $scriptbasename
"
2536 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
2537 script=
"$
1"
2544 NAME=$(basename $DAEMON)
2545 PIDFILE=/var/run/$NAME.pid
2547 # Exit if the package is not installed
2548 #[ -x
"$DAEMON
" ] || exit
0
2550 # Read configuration variable file if it is present
2551 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
2553 # Load the VERBOSE setting and other rcS variables
2556 case
"$
1" in
2558 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
2560 case
"$?
" in
2561 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2562 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2566 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
2568 case
"$?
" in
2569 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2570 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2574 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
2576 #reload|force-reload)
2578 # If do_reload() is not implemented then leave this commented out
2579 # and leave
'force-reload
' as an alias for
'restart
'.
2581 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
2585 restart|force-reload)
2587 # If the
"reload
" option is implemented then remove the
2588 #
'force-reload
' alias
2590 log_daemon_msg
"Restarting $DESC
" "$NAME
"
2592 case
"$?
" in
2595 case
"$?
" in
2597 1) log_end_msg
1 ;; # Old process is still running
2598 *) log_end_msg
1 ;; # Failed to start
2608 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
2614 </pre
></p
>
2616 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
2617 lot. I did not really polish the approach, so it might not always
2618 work out of the box, but you get the idea. I did not try very hard to
2619 optimize it nor make it more robust either.
</p
>
2621 <p
>A better argument for switching init system in Debian than reducing
2622 the size of init scripts (which is a good thing to do anyway), is to
2623 get boot system that is able to handle the kernel events sensibly and
2624 robustly, and do not depend on the boot to run sequentially. The boot
2625 and the kernel have not behaved sequentially in years.
</p
>
2630 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
2631 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
2632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
2633 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
2634 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
2635 remote display access is the preferred solution with oVirt and RedHat
2636 Enterprise Virtualization, and I was sad to discover the other day
2637 that the browser plugin needed to use these systems seamlessly was
2638 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
2639 for a package
</a
> was from
2012-
04-
10 with no progress since
2640 2013-
04-
01, so I decided to wrap up a package based on the great work
2641 from Cajus Pollmeier and put it in a collab-maint maintained git
2642 repository to get a package I could use. I would very much like
2643 others to help me maintain the package (or just take over, I do not
2644 mind), but as no-one had volunteered so far, I just uploaded it to
2645 NEW. I hope it will be available in Debian in a few days.
</p
>
2647 <p
>The source is now available from
2648 <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
>
2653 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
2654 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
2655 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
2656 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
2657 <description><p
>The
2658 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
2659 program is a a very nice system to create virtual machine images. It
2660 create a image file, add a partition table, mount it and run
2661 debootstrap in the mounted directory to create a Debian system on a
2662 stick. Yesterday, I decided to try to teach it how to make images for
2663 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
2664 of a plan to simplify the build system for
2665 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
2666 project
</a
>. The FreedomBox project already uses vmdebootstrap for
2667 the virtualbox images, but its current build system made multistrap
2668 based system for Dreamplug images, and it is lacking support for
2669 Raspberry Pi.
</p
>
2671 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
2672 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2673 code and adjusted it to be able to build armel images on my amd64
2674 Debian laptop. I ended up giving vmdebootstrap five new options,
2675 allowing me to replicate the image creation process I use to make
2676 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
2677 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
2678 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
2679 call debootstrap with --foreign and to copy the handler into the
2680 generated chroot before running the second stage. This allow
2681 vmdebootstrap to create armel images on an amd64 host. Next I added
2682 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
2683 fstype
</tt
> to teach it to create a separate /boot/ partition with the
2684 given file system type, allowing me to create an image with a vfat
2685 partition for the /boot/ stuff. I also added a
<tt
>--variant
2686 variant
</tt
> option to allow me to create smaller images without the
2687 Debian base system packages installed. Finally, I added an option
2688 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
2689 as a boot loader. It is not needed on the Raspberry Pi and probably
2690 most other non-x86 architectures. The changes were accepted by the
2691 upstream author of vmdebootstrap yesterday and today, and is now
2693 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
2694 upstream project page
</a
>.
</p
>
2696 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
2697 create a small script (the customize script) to add the non-free
2698 binary blob needed to boot the Raspberry Pi and the APT source
2701 <p
><pre
>
2703 set -e # Exit on first error
2704 rootdir=
"$
1"
2705 cd
"$rootdir
"
2706 cat
&lt;
&lt;EOF
> etc/apt/sources.list
2707 deb http://http.debian.net/debian/ jessie main contrib non-free
2709 # Install non-free binary blob needed to boot Raspberry Pi. This
2710 # install a kernel somewhere too.
2711 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2712 -O $rootdir/usr/bin/rpi-update
2713 chmod a+x $rootdir/usr/bin/rpi-update
2714 mkdir -p $rootdir/lib/modules
2715 touch $rootdir/boot/start.elf
2716 chroot $rootdir rpi-update
2717 </pre
></p
>
2719 <p
>Next, fetch the latest vmdebootstrap script and call it like this
2720 to build the image:
</p
>
2723 sudo ./vmdebootstrap \
2726 --distribution jessie \
2727 --mirror http://http.debian.net/debian \
2736 --root-password raspberry \
2737 --hostname raspberrypi \
2738 --foreign /usr/bin/qemu-arm-static \
2739 --customize `pwd`/customize \
2741 --package git-core \
2742 --package binutils \
2743 --package ca-certificates \
2746 </pre
></p
>
2748 <p
>The list of packages being installed are the ones needed by
2749 rpi-update to make the image bootable on the Raspberry Pi, with the
2750 exception of netbase, which is needed by debootstrap to find
2751 /etc/hosts with the minbase variant. I really wish there was a way to
2752 set up an Raspberry Pi using only packages in the Debian archive, but
2753 that is not possible as far as I know, because it boots from the GPU
2754 using a non-free binary blob.
</p
>
2756 <p
>The build host need debootstrap, kpartx and qemu-user-static and
2757 probably a few others installed. I have not checked the complete
2758 build dependency list.
</p
>
2760 <p
>The resulting image will not use the hardware floating point unit
2761 on the Raspberry PI, because the armel architecture in Debian is not
2762 optimized for that use. So the images created will be a bit slower
2763 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
2768 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
2769 <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>
2770 <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>
2771 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
2772 <description><p
>The last few days I came across a few good causes that should get
2773 wider attention. I recommend signing and donating to each one of
2776 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
2777 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
2778 Women program which is a Google Summer of Code like initiative to get
2779 more women involved in free software. One debian sponsor has offered
2780 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
2781 earmarked
</a
> for this initiative. I donated a few minutes ago, and
2782 hope you will to. :)
</p
>
2784 <p
>And the Electronic Frontier Foundation just announced plans to
2785 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
2786 documentaries about the excessive spying
</a
> on every Internet user that
2787 take place these days, and their need to fund the work. I
've already
2788 donated. Are you next?
</p
>
2790 <p
>For my Norwegian audience, the organisation Studentenes og
2791 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2792 statement under the heading
2793 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
2794 Access
</a
> for those of us asking for more focus on open access in the
2795 Norwegian government. So far
499 signatures. I hope you will sign it
2801 <title>Videos about the Freedombox project - for inspiration and learning
</title>
2802 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
2803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
2804 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
2805 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
2806 project
</a
> have been going on for a while, and have presented the
2807 vision, ideas and solution several places. Here is a little
2808 collection of videos of talks and presentation of the project.
</p
>
2812 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
2813 2,
5 minute marketing film
</a
> (Youtube)
</li
>
2815 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
2816 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
2818 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
2819 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2820 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
2821 (Youtube)
</li
>
2823 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
2824 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
2826 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
2827 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
2829 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
2830 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2831 York City in
2012</a
> (Youtube)
</li
>
2833 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
2834 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
2835 (Youtube)
</li
>
2837 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
2838 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
2840 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
2841 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
2843 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
2844 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2845 2013</a
> (Youtube)
</li
>
2849 <p
>A larger list is available from
2850 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
2851 Freedombox Wiki
</a
>.
</p
>
2853 <p
>On other news, I am happy to report that Freedombox based on Debian
2854 Jessie is coming along quite well, and soon both Owncloud and using
2855 Tor should be available for testers of the Freedombox solution. :) In
2856 a few weeks I hope everything needed to test it is included in Debian.
2857 The withsqlite package is already in Debian, and the plinth package is
2858 pending in NEW. The third and vital part of that puzzle is the
2859 metapackage/setup framework, which is still pending an upload. Join
2860 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
2861 (#freedombox on irc.debian.org)
</a
> and
2862 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2863 mailing list
</a
> if you want to help make this vision come true.
</p
>
2868 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
2869 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
2870 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
2871 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
2872 <description><p
>I was introduced to the
2873 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
2874 in
2010, when Eben Moglen presented his vision about serving the need
2875 of non-technical people to keep their personal information private and
2876 within the legal protection of their own homes. The idea is to give
2877 people back the power over their network and machines, and return
2878 Internet back to its intended peer-to-peer architecture. Instead of
2879 depending on a central service, the Freedombox will give everyone
2880 control over their own basic infrastructure.
</p
>
2882 <p
>I
've intended to join the effort since then, but other tasks have
2883 taken priority. But this summers nasty news about the misuse of trust
2884 and privilege exercised by the
"western
" intelligence gathering
2885 communities increased my eagerness to contribute to a point where I
2886 actually started working on the project a while back.
</p
>
2888 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
2889 Debian initiative
</a
> based on the vision from Eben Moglen, is to
2890 create a simple and cheap Debian based appliance that anyone can hook
2891 up in their home and get access to secure and private services and
2892 communication. The initial deployment platform have been the
2893 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
2894 which is a piece of hardware I do not own. So to be able to test what
2895 the current Freedombox setup look like, I had to come up with a way to install
2896 it on some hardware I do have access to. I have rewritten the
2897 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
2898 image build framework to use .deb packages instead of only copying
2899 setup into the boot images, and thanks to this rewrite I am able to
2900 set up any machine supported by Debian Wheezy as a Freedombox, using
2901 the previously mentioned deb (and a few support debs for packages
2902 missing in Debian).
</p
>
2904 <p
>The current Freedombox setup consist of a set of bootstrapping
2906 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
2907 and a administrative web interface
2908 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
2909 withsqlite), as well as a privacy enhancing proxy based on
2910 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
2911 (freedombox-privoxy). There is also a web/javascript based XMPP
2912 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
2913 trying (unsuccessfully so far) to talk to the XMPP server
2914 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
2915 web interface is pluggable, and the goal is to use it to enable OpenID
2916 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2917 this is really working yet, see
2918 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
2919 project TODO
</a
> for links to GIT repositories. Most of the code is
2920 on github at the moment. The HTTP proxy is operational out of the
2921 box, and the admin web interface can be used to add/remove plinth
2922 users. I
've not been able to do anything else with it so far, but
2923 know there are several branches spread around github and other places
2924 with lots of half baked features.
</p
>
2926 <p
>Anyway, if you want to have a look at the current state, the
2927 following recipes should work to give you a test machine to poke
2930 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
2934 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
2935 <li
>Boot from it, either as CD or USB stick.
</li
>
2936 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
2937 to the Debian installer:
<p
>
2938 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
2940 <li
>Answer the few language/region/password questions and pick disk to
2941 install on.
</li
>
2943 <li
>When the installation is finished and the machine have rebooted a
2944 few times, your Freedombox is ready for testing.
</li
>
2948 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
2952 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
2953 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
2954 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
2956 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
2957 </pre
></li
>
2958 <li
><p
>Run this as root:
</p
>
2960 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2963 apt-get install freedombox-setup
2964 /usr/lib/freedombox/setup
2965 </pre
></li
>
2966 <li
>Reboot into your freshly created Freedombox.
</li
>
2970 <p
>You can test it on other architectures too, but because the
2971 freedombox-privoxy package is binary, it will only work as intended on
2972 the architectures where I have had time to build the binary and put it
2973 in my APT repository. But do not let this stop you. It is only a
2974 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
2976 <p
>Note that by default Freedombox is a DHCP server on the
2977 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
2978 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
2979 disable
</tt
>" as root.
</p
>
2981 <p
>Please let me know if this works for you, or if you have any
2982 problems. We gather on the IRC channel
2983 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
2984 irc.debian.org and the
2985 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
2986 mailing list
</a
>.
</p
>
2988 <p
>Once you get your freedombox operational, you can visit
2989 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
2990 welcome screen (dead end - do not be surprised if you are unable to
2991 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
2992 to look at the rest of plinth. The default user is
'admin
' and the
2993 default password is
'secret
'.
</p
>
2998 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
2999 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3000 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3001 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3002 <description><p
>Earlier, I reported about
3003 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3004 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3005 told by IBM that the original disk should be thrown away. And as
3006 there no longer was a problem if I bricked the firmware, I decided
3007 today to try to install Intel firmware to replace the Lenovo firmware
3008 currently on the disk.
</p
>
3010 <p
>I searched the Intel site for firmware, and found
3011 <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
>
3012 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3013 according to the site should contain the latest firmware for SSD
3014 disks. I inserted the broken disk in one of my spare laptops and
3015 booted the ISO from a USB stick. The disk was recognized, but the
3016 program claimed the newest firmware already were installed and refused
3017 to insert any Intel firmware. So no change, and the disk is still
3018 unable to handle write load. :( I guess the only way to get them
3019 working would be if Lenovo releases new firmware. No idea how likely
3020 that is. Anyway, just blogging about this test for completeness. I
3021 got a working Samsung disk, and see no point in spending more time on
3022 the broken disks.
</p
>
3027 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3028 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3029 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3030 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3031 <description><p
>Today I switched to
3032 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3033 new laptop
</a
>. I
've previously written about the problems I had with
3034 my new Thinkpad X230, which was delivered with an
3035 <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
3036 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3037 sustained writes. My hardware supplier have been very forthcoming in
3038 trying to find a solution, and after first trying with another
3039 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3040 disk instead to fix it once and for all. The Samsung disk survived
3041 the installation of Debian with encrypted disks (filling the disk with
3042 random data during installation killed the first two), and I thus
3043 decided to trust it with my data. I have installed it as a Debian Edu
3044 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3045 server at home using Kerberos and LDAP, and will use it as my work
3046 station from now on.
</p
>
3048 <p
>As this is a solid state disk with no moving parts, I believe the
3049 Debian Wheezy default installation need to be tuned a bit to increase
3050 performance and increase life time of the disk. The Linux kernel and
3051 user space applications do not yet adjust automatically to such
3052 environment. To make it easier for my self, I created a draft Debian
3053 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3054 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3055 for the ssd-setup package
</a
> is available from collab-maint, and it
3056 is set up to adjust the setup of the machine by just installing the
3057 package. If there is any non-SSD disk in the machine, the package
3058 will refuse to install, as I did not try to write any logic to sort
3059 file systems in SSD and non-SSD file systems.
</p
>
3061 <p
>I consider the package a draft, as I am a bit unsure how to best
3062 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3063 where I set up the machine with one large encrypted partition (in
3064 addition to /boot), put LVM on top of this and set up partitions on
3065 top of this again. See the README file in the package source for the
3066 references I used to pick the settings. At the moment these
3067 parameters are tuned:
</p
>
3071 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3072 (adding discard to /etc/crypttab)
</li
>
3074 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3075 this case a cryptsetup partition) by changing issue_discards from
3076 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3078 <li
>Set relatime as a file system option for ext3 and ext4 file
3081 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3082 /etc/fstab.
</li
>
3084 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3086 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3087 cron.daily).
</li
>
3089 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3090 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3094 <p
>During installation, I cancelled the part where the installer fill
3095 the disk with random data, as this would kill the SSD performance for
3096 little gain. My goal with the encrypted file system is to ensure
3097 those stealing my laptop end up with a brick and not a working
3098 computer. I have no hope in keeping the really resourceful people
3099 from getting the data on the disk (see
3100 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3101 Thus I concluded that adding the discard option to crypttab is the
3102 right thing to do.
</p
>
3104 <p
>I considered using the noop I/O scheduler, as several recommended
3105 it for SSD, but others recommended deadline and a benchmark I found
3106 indicated that deadline might be better for interactive use.
</p
>
3108 <p
>I also considered using the
'discard
' file system option for ext3
3109 and ext4, but read that it would give a performance hit ever time a
3110 file is removed, and thought it best to that that slowdown once a day
3111 instead of during my work.
</p
>
3113 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3114 this is already done by Debian Edu.
</p
>
3116 <p
>I have not yet started on the user space tuning. I expect
3117 iceweasel need some tuning, and perhaps other applications too, but
3118 have not yet had time to investigate those parts.
</p
>
3120 <p
>The package should work on Ubuntu too, but I have not yet tested it
3123 <p
>As for the answer to the question in the title of this blog post,
3124 as far as I know, the only solution I know about is to replace the
3125 disk. It might be possible to flash it with Intel firmware instead of
3126 the Lenovo firmware. But I have not tried and did not want to do so
3127 without approval from Lenovo as I wanted to keep the warranty on the
3128 disk until a solution was found and they wanted the broken disks
3134 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3135 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3136 <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>
3137 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3138 <description><p
>A few days ago, I wrote about
3139 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3140 problems I experienced with my new X230 and its SSD disk
</a
>, which
3141 was dying during installation because it is unable to cope with
3142 sustained write. My supplier is in contact with
3143 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3144 replacement disk to try to fix the problem. They decided to send an
3145 identical model, so my hopes for a permanent fix was slim.
</p
>
3147 <p
>Anyway, today I got the replacement disk and tried to install
3148 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3149 same firmware version as the original. This time my hope raised
3150 slightly as the installation progressed, as the original disk used to
3151 die after
4-
7% of the disk was written to, while this time it kept
3152 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3153 died again and I was back on square one. I still do not have a new
3154 laptop with a disk I can trust. I can not live with a disk that might
3155 lock up when I download a new
3156 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3157 other large files. I look forward to hearing from my supplier with
3158 the next proposal from Lenovo.
</p
>
3160 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3161 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3162 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3163 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
3164 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3165 P/N
45N8295, P0C38732.
</p
>
3167 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
3168 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
3169 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3170 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
3171 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3172 P/N
45N8295, P0C38732.
</p
>
3174 <p
>The only difference is in the first number (serial number?), ISN,
3175 SA, date and WNPP values. Mentioning all the details here in case
3176 someone is able to use the information to find a way to identify the
3177 failing disk among working ones (if any such working disk actually
3183 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
3184 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
3185 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
3186 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
3187 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
3188 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3189 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
3190 member assosiation NUUG
</a
> and
3191 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
3192 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
3193 Bitraf
</a
>.
</p
>
3195 <p
>It starts
10:
00 and continue until late evening. Everyone is
3196 welcome, and there is no fee to participate. There is on the other
3197 hand limited space, and only room for
30 people. Please put your name
3198 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
3199 wiki page
</a
> if you plan to join us.
</p
>
3204 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
3205 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
3206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
3207 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
3208 <description><p
>Half a year ago, I reported that I had to find a
3209 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
3210 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
3211 time to spend on it, and it took a while to find a model I believe
3212 will do the job, but two days ago the replacement finally arrived. I
3214 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
3215 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3216 a roaming workstation, and it seemed to work flawlessly. But my
3217 second installation with encrypted disk was not as successful. More
3218 on that below.
</p
>
3220 <p
>I had a hard time trying to track down a good laptop, as my most
3221 important requirements (robust and with a good keyboard) are never
3222 listed in the feature list. But I did get good help from the search
3223 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3224 allowed me to limit the list of interesting laptops based on my other
3225 requirements. A bit surprising that SSD disk are not disks according
3226 to that search interface, so I had to drop specifying the number of
3227 disks from my search parameters. I also asked around among friends to
3228 get their impression on keyboards and robustness.
</p
>
3230 <p
>So the new laptop arrived, and it is quite a lot wider than the
3231 X41. I am not quite convinced about the keyboard, as it is
3232 significantly wider than my old keyboard, and I have to stretch my
3233 hand a lot more to reach the edges. But the key response is fairly
3234 good and the individual key shape is fairly easy to handle, so I hope
3235 I will get used to it. My old X40 was starting to fail, and I really
3236 needed a new laptop now. :)
</p
>
3238 <p
>Turning off the touch pad was simple. All it took was a quick
3239 visit to the BIOS during boot it disable it.
</p
>
3241 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
3242 lock up during load. And this happen when installing Debian Wheezy
3243 with encrypted disk, while the disk is being filled with random data.
3244 I also tested to install Ubuntu Raring, and it happen there too if I
3245 reenable the code to fill the disk with random data (it is disabled by
3246 default in Ubuntu). And the bug with is already known. It was
3247 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
3248 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
3249 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3250 kernel developers as
3251 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
3252 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
3253 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3254 Lenovo forums, both for
3255 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
3256 2012-
11-
10</a
> and for
3257 <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
3258 03-
20-
2013</a
>. The problem do not only affect installation. The
3259 reports state that the disk lock up during use if many writes are done
3260 on the disk, so it is much no use to work around the installation
3261 problem and end up with a computer that can lock up at any moment.
3263 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
3264 available
</a
> that will lock up the hard drive after running a few
3265 minutes by writing to a file.
</p
>
3267 <p
>I
've contacted my supplier and asked how to handle this, and after
3268 contacting PCHELP Norway (request
01D1FDP) which handle support
3269 requests for Lenovo, his first suggestion was to upgrade the disk
3270 firmware. Unfortunately there is no newer firmware available from
3271 Lenovo, as my disk already have the most recent one (version LF1i). I
3272 hope to hear more from him today and hope the problem can be
3278 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
3279 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
3280 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
3281 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3282 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3283 trusty old Thinkpad X41. Unfortunately I did not have much time to
3284 spend on it, but today the replacement finally arrived. I ended up
3285 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3286 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3287 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3288 this, it is installing what I hope will be a more final installation,
3289 with a encrypted hard drive to ensure any dope head stealing it end up
3290 with an expencive door stop.
</p
>
3292 <p
>I had a hard time trying to track down a good laptop, as my most
3293 important requirements (robust and with a good keyboard) are never
3294 listed in the feature list. But I did get good help from the search
3295 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3296 allowed me to limit the list of interesting laptops based on my other
3297 requirements. A bit surprising that SSD disk are not disks, so I had
3298 to drop number of disks from my search parameters.
</p
>
3300 <p
>I am not quite convinced about the keyboard, as it is significantly
3301 wider than my old keyboard, and I have to stretch my hand a lot more
3302 to reach the edges. But the key response is fairly good and the
3303 individual key shape is fairly easy to handle, so I hope I will get
3304 used to it. My old X40 was starting to fail, and I really needed a
3305 new laptop now. :)
</p
>
3307 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3312 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3313 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3314 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3315 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3316 <description><p
>It annoys me when the computer fail to do automatically what it is
3317 perfectly capable of, and I have to do it manually to get things
3318 working. One such task is to find out what firmware packages are
3319 needed to get the hardware on my computer working. Most often this
3320 affect the wifi card, but some times it even affect the RAID
3321 controller or the ethernet card. Today I pushed version
0.4 of the
3322 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3323 including a new script isenkram-autoinstall-firmware handling the
3324 process of asking all the loaded kernel modules what firmware files
3325 they want, find debian packages providing these files and install the
3326 debian packages. Here is a test run on my laptop:
</p
>
3328 <p
><pre
>
3329 # isenkram-autoinstall-firmware
3330 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3331 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3332 info: locating packages with the requested firmware files
3333 info: Updating APT sources after adding non-free APT source
3334 info: trying to install firmware-ipw2x00
3337 Preconfiguring packages ...
3338 Selecting previously deselected package firmware-ipw2x00.
3339 (Reading database ...
259727 files and directories currently installed.)
3340 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3341 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3343 </pre
></p
>
3345 <p
>When all the requested firmware is present, a simple message is
3346 printed instead:
</p
>
3348 <p
><pre
>
3349 # isenkram-autoinstall-firmware
3350 info: did not find any firmware files requested by loaded kernel modules. exiting
3352 </pre
></p
>
3354 <p
>It could use some polish, but it is already working well and saving
3355 me some time when setting up new machines. :)
</p
>
3357 <p
>So, how does it work? It look at the set of currently loaded
3358 kernel modules, and look up each one of them using modinfo, to find
3359 the firmware files listed in the module meta-information. Next, it
3360 download the Contents file from a nearby APT mirror, and search for
3361 the firmware files in this file to locate the package with the
3362 requested firmware file. If the package is in the non-free section, a
3363 non-free APT source is added and the package is installed using
3364 <tt
>apt-get install
</tt
>. The end result is a slightly better working
3367 <p
>I hope someone find time to implement a more polished version of
3368 this script as part of the hw-detect debian-installer module, to
3369 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
3370 #
655507</a
>. There really is no need to insert USB sticks with
3371 firmware during a PXE install when the packages already are available
3372 from the nearby Debian mirror.
</p
>
3377 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
3378 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
3379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
3380 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
3381 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3382 the screen just turn black when Linux boot, either during installation
3383 or on first boot from the hard disk. I
've seen it once in a while the
3384 last few years, but only recently understood the cause. I
've seen it
3385 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3386 The reason seem to be in the wiring of some laptops. The system to
3387 control the screen background light is inverted, so when Linux try to
3388 turn the brightness fully on, it end up turning it off instead. I do
3389 not know which Linux drivers are affected, but this post is about the
3390 i915 driver used by the
3391 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3392 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
3394 <p
>The problem can be worked around two ways. Either by adding
3395 i915.invert_brightness=
1 as a kernel option, or by adding a file in
3396 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
3397 option when it load the i915 kernel module. On Debian and Ubuntu, it
3398 can be done by running these commands as root:
</p
>
3401 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
3402 update-initramfs -u -k all
3405 <p
>Since March
2012 there is
3406 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
3407 mechanism in the Linux kernel
</a
> to tell the i915 driver which
3408 hardware have this problem, and get the driver to invert the
3409 brightness setting automatically. To use it, one need to add a row in
3410 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
3411 intel_quirks array
</a
> in the driver source
3412 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
3413 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
3414 number (vendor number
8086 is assumed) and subdevice vendor and device
3417 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
3418 -vvnn
</tt
> for the video card in question:
</p
>
3420 <p
><pre
>
3421 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
3422 3rd Gen Core processor Graphics Controller [
8086:
0156] \
3423 (rev
09) (prog-if
00 [VGA controller])
3424 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
3425 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3426 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3427 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
3428 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
3430 Interrupt: pin A routed to IRQ
42
3431 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
3432 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
3433 Region
4: I/O ports at
4000 [size=
64]
3434 Expansion ROM at
<unassigned
> [disabled]
3435 Capabilities:
<access denied
>
3436 Kernel driver in use: i915
3437 </pre
></p
>
3439 <p
>The resulting intel_quirks entry would then look like this:
</p
>
3441 <p
><pre
>
3442 struct intel_quirk intel_quirks[] = {
3444 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3445 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
3448 </pre
></p
>
3450 <p
>According to the kernel module instructions (as seen using
3451 <tt
>modinfo i915
</tt
>), information about hardware needing the
3452 invert_brightness flag should be sent to the
3453 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
3454 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
3455 developers. But my email about the laptop sent
2013-
06-
03 have not
3457 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
3458 web archive for the mailing list
</a
>, so I suspect they do not accept
3459 emails from non-subscribers. Because of this, I sent my patch also to
3460 the Debian bug tracking system instead as
3461 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
3462 sure the patch is not lost.
</p
>
3464 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
3465 with this problem working properly with Linux. If you use Gnome, your
3466 worries should be over at this point. But if you use KDE, there is
3467 something in KDE ignoring the invert_brightness setting and turning on
3468 the screen during login. I
've reported it to Debian as
3469 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
3470 have no idea yet how to figure out exactly what subsystem is doing
3471 this. Perhaps you can help? Perhaps you know what the Gnome
3472 developers did to handle this, and this can give a clue to the KDE
3473 developers? Or you know where in KDE the screen brightness is changed
3474 during login? If so, please update the BTS report (or get in touch if
3475 you do not know how to update BTS).
</p
>
3477 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
3478 acpi_backlight=vendor, to disable ACPI backlight support completely,
3479 as the ACPI information on the machine is trash and it is better to
3480 leave it to the intel video driver to control the screen
3481 backlight.
</p
>
3486 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
3487 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
3488 <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>
3489 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
3490 <description><p
>Two days ago, I asked
3491 <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
3492 I could install Linux on a Packard Bell EasyNote LV computer
3493 preinstalled with Windows
8</a
>. I found a solution, but am horrified
3494 with the obstacles put in the way of Linux users on a laptop with UEFI
3495 and Windows
8.
</p
>
3497 <p
>I never found out if the cause of my problems were the use of UEFI
3498 secure booting or fast boot. I suspect fast boot was the problem,
3499 causing the firmware to boot directly from HD without considering any
3500 key presses and alternative devices, but do not know UEFI settings
3501 enough to tell.
</p
>
3503 <p
>There is no way to install Linux on the machine in question without
3504 opening the box and disconnecting the hard drive! This is as far as I
3505 can tell, the only way to get access to the firmware setup menu
3506 without accepting the Windows
8 license agreement. I am told (and
3507 found description on how to) that it is possible to configure the
3508 firmware setup once booted into Windows
8. But as I believe the terms
3509 of that agreement are completely unacceptable, accepting the license
3510 was never an alternative. I do not enter agreements I do not intend
3511 to follow.
</p
>
3513 <p
>I feared I had to return the laptops and ask for a refund, and
3514 waste many hours on this, but luckily there was a way to get it to
3515 work. But I would not recommend it to anyone planning to run Linux on
3516 it, and I have become sceptical to Windows
8 certified laptops. Is
3517 this the way Linux will be forced out of the market place, by making
3518 it close to impossible for
"normal
" users to install Linux without
3519 accepting the Microsoft Windows license terms? Or at least not
3520 without risking to loose the warranty?
</p
>
3522 <p
>I
've updated the
3523 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
3524 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
3525 do not have to struggle as much as I did to get Linux into the
3528 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3529 Michael Tokarev and others for feedback and ideas.
</p
>
3534 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
3535 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
3536 <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>
3537 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
3538 <description><p
>I
've run into quite a problem the last few days. I bought three
3539 new laptops for my parents and a few others. I bought Packard Bell
3540 Easynote LV to run Kubuntu on and use as their home computer. But I
3541 am completely unable to figure out how to install Linux on it. The
3542 computer is preinstalled with Windows
8, and I suspect it uses UEFI
3543 instead of a BIOS to boot.
</p
>
3545 <p
>The problem is that I am unable to get it to PXE boot, and unable
3546 to get it to boot the Linux installer from my USB stick. I have yet
3547 to try the DVD install, and still hope it will work. when I turn on
3548 the computer, there is no information on what buttons to press to get
3549 the normal boot menu. I expect to get some boot menu to select PXE or
3550 USB stick booting. When booting, it first ask for the language to
3551 use, then for some regional settings, and finally if I will accept the
3552 Windows
8 terms of use. As these terms are completely unacceptable to
3553 me, I have no other choice but to turn off the computer and try again
3554 to get it to boot the Linux installer.
</p
>
3556 <p
>I have gathered my findings so far on a Linlap page about the
3557 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3558 EasyNote LV
</a
> model. If you have any idea how to get Linux
3559 installed on this machine, please get in touch or update that wiki
3560 page. If I can
't find a way to install Linux, I will have to return
3561 the laptop to the seller and find another machine for my parents.
</p
>
3563 <p
>I wonder, is this the way Linux will be forced out of the market
3564 using UEFI and
"secure boot
" by making it impossible to install Linux
3565 on new Laptops?
</p
>
3570 <title>How to transform a Debian based system to a Debian Edu installation
</title>
3571 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
3572 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
3573 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
3574 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
3575 an operating system based on Debian intended for use in schools. It
3576 contain a turn-key solution for the computer network provided to
3577 pupils in the primary schools. It provide both the central server,
3578 network boot servers and desktop environments with heaps of
3579 educational software. The project was founded almost
12 years ago,
3580 2001-
07-
02. If you want to support the project, which is in need for
3581 cash to fund developer gatherings and other project related activity,
3582 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
3583 donate some money
</a
>.
3585 <p
>A topic that come up again and again on the Debian Edu mailing
3586 lists and elsewhere, is the question on how to transform a Debian or
3587 Ubuntu installation into a Debian Edu installation. It isn
't very
3588 hard, and last week I wrote a script to replicate the steps done by
3589 the Debian Edu installer.
</p
>
3591 <p
>The script,
3592 <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/
>
3593 in the debian-edu-config package, will go through these six steps and
3594 transform an existing Debian Wheezy or Ubuntu (untested) installation
3595 into a Debian Edu Workstation:
</p
>
3599 <li
>Add skolelinux related APT sources.
</li
>
3600 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
3601 <li
>Install debian-edu-install to load preseeding values and pull in
3602 our configuration.
</li
>
3603 <li
>Preseed debconf database with profile setup in
3604 /etc/debian-edu/config, and run tasksel to install packages
3605 according to the profile specified in the config above,
3606 overriding some of the Debian automation machinery.
</li
>
3607 <li
>Run debian-edu-cfengine-D installation to configure everything
3608 that could not be done using preseeding.
</li
>
3609 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
3613 <p
>There are some steps in the Debian Edu installation that can not be
3614 replicated like this. Disk partitioning and LVM setup, for example.
3615 So this script just assume there is enough disk space to install all
3616 the needed packages.
</p
>
3618 <p
>The script was created to help a Debian Edu student working on
3619 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
3620 Debian Edu client, and using it he can take the existing
3621 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
3622 transform it into a fully functioning Debian Edu Workstation (or
3623 Roaming Workstation, or whatever :).
</p
>
3625 <p
>The default setting in the script is to create a KDE Workstation.
3626 If a LXDE based Roaming workstation is wanted instead, modify the
3627 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
3629 <p
><pre
>
3630 PROFILE=
"Roaming-Workstation
"
3631 DESKTOP=
"lxde
"
3632 </pre
></p
>
3634 <p
>The script could even become useful to set up Debian Edu servers in
3635 the cloud, by starting with a virtual Debian installation at some
3636 virtual hosting service and setting up all the services on first
3642 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
3643 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
3644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
3645 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
3646 <description><P
>In January,
3647 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
3648 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
3649 channel #debian-lego
</a
>, for those of us in the Debian and Linux
3650 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
3651 marvellous construction system from Denmark. We also created
3652 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
3653 a place to take notes and write down our plans and hopes. And several
3654 people showed up to help. I was very happy to see the effect of my
3655 call. Since the small start, we have a debtags tag
3656 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
3657 tag for LEGO related packages, and now count
10 packages related to
3658 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
3660 <p
><table
>
3661 <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
>
3662 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
3663 <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
>
3664 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
3665 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
3666 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
3667 <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
>
3668 <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
>
3669 <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
>
3670 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
3671 </table
></p
>
3673 <p
>Some of these are available in Wheezy, and all but one are
3674 currently available in Jessie/testing. leocad is so far only
3675 available in experimental.
</p
>
3677 <p
>If you care about LEGO in Debian, please join us on IRC and help
3678 adding the rest of the great free software tools available on Linux
3679 for LEGO designers.
</p
>
3684 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
3685 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
3686 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
3687 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
3688 <description><p
>When I woke up this morning, I was very happy to see that the
3689 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
3690 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
3691 Debian release, and I expect to move my machines at home over to it fairly
3694 <p
>The new debian release contain heaps of new stuff, and one program
3695 in particular make me very happy to see included. The
3696 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
3697 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
3698 included for the first time. Alongside similar programs like
3699 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
3700 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
3701 it allow for visual programming where syntax errors can not happen,
3702 and a friendly programming environment for learning to control the
3703 computer. Scratch will also be included in the next release of Debian
3706 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
3707 Edu/Skolelinux release too. The
3708 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
3709 alpha release
</a
> went out last week, and the next should soon
3715 <title>Isenkram
0.2 finally in the Debian archive
</title>
3716 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
3717 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
3718 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
3719 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
3720 package
</a
> finally made it into the archive, after lingering in NEW
3721 for many months. I uploaded it to the Debian experimental suite
3722 2013-
01-
27, and today it was accepted into the archive.
</p
>
3724 <p
>Isenkram is a system for suggesting to users what packages to
3725 install to work with a pluggable hardware device. The suggestion pop
3726 up when the device is plugged in. For example if a Lego Mindstorm NXT
3727 is inserted, it will suggest to install the program needed to program
3728 the NXT controller. Give it a go, and report bugs and suggestions to
3734 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
3735 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
3736 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
3737 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
3738 <description><p
>My
3739 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
3740 bitcoin related blog post
</a
> mentioned that the new
3741 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
3742 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3743 2013-
01-
19, and have been available in unstable since then. It was
3744 automatically copied to Ubuntu, and is available in their Raring
3745 version too.
</p
>
3747 <p
>But there is a strange problem with the build that block this new
3748 version from being available on the i386 and kfreebsd-i386
3749 architectures. For some strange reason, the autobuilders in Debian
3750 for these architectures fail to run the test suite on these
3751 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
3752 We are so far unable to reproduce it when building it manually, and
3753 no-one have been able to propose a fix. If you got an idea what is
3754 failing, please let us know via the BTS.
</p
>
3756 <p
>One feature that is annoying me with of the bitcoin client, because
3757 I often run low on disk space, is the fact that the client will exit
3758 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
3759 #
696715</a
>). So make sure you have enough disk space when you run
3762 <p
>As usual, if you use bitcoin and want to show your support of my
3763 activities, please send Bitcoin donations to my address
3764 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3769 <title>Welcome to the world, Isenkram!
</title>
3770 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
3771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
3772 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
3773 <description><p
>Yesterday, I
3774 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
3775 for testers
</a
> for my prototype for making Debian better at handling
3776 pluggable hardware devices, which I
3777 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
3778 out to create
</a
> earlier this month. Several valuable testers showed
3779 up, and caused me to really want to to open up the development to more
3780 people. But before I did this, I want to come up with a sensible name
3781 for this project. Today I finally decided on a new name, and I have
3782 renamed the project from hw-support-handler to this new name. In the
3783 process, I moved the source to git and made it available as a
3784 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
3785 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
3786 To fetch and build the latest version of the source, use
</p
>
3789 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3790 cd isenkram
&& git-buildpackage -us -uc
3793 <p
>I have not yet adjusted all files to use the new name yet. If you
3794 want to hack on the source or improve the package, please go ahead.
3795 But please talk to me first on IRC or via email before you do major
3796 changes, to make sure we do not step on each others toes. :)
</p
>
3798 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
3799 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3800 stuff, in other words. I
've been told it is the Norwegian variant of
3801 the German word eisenkram, for those that are familiar with that
3804 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
3805 instructions, to avoid confusing people with an error from the signing
3808 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
3809 clone argument to avoid the need for authentication.
</p
>
3814 <title>First prototype ready making hardware easier to use in Debian
</title>
3815 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
3816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
3817 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
3818 <description><p
>Early this month I set out to try to
3819 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
3820 the Debian support for pluggable hardware devices
</a
>. Now my
3821 prototype is working, and it is ready for a larger audience. To test
3823 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
3824 from the Debian Edu subversion repository
</a
>, build and install the
3825 package. You might have to log out and in again activate the
3826 autostart script.
</p
>
3828 <p
>The design is simple:
</p
>
3832 <li
>Add desktop entry in /usr/share/autostart/ causing a program
3833 hw-support-handlerd to start when the user log in.
</li
>
3835 <li
>This program listen for kernel events about new hardware (directly
3836 from the kernel like udev does), not using HAL dbus events as I
3837 initially did.
</li
>
3839 <li
>When new hardware is inserted, look up the hardware modalias in
3840 the APT database, a database
3841 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
3842 via HTTP
</a
> and a database available as part of the package.
</li
>
3844 <li
>If a package is mapped to the hardware in question, the package
3845 isn
't installed yet and this is the first time the hardware was
3846 plugged in, show a desktop notification suggesting to install the
3847 package or packages.
</li
>
3849 <li
>If the user click on the
'install package now
' button, ask
3850 aptdaemon via the PackageKit API to install the requrired package.
</li
>
3852 <li
>aptdaemon ask for root password or sudo password, and install the
3853 package while showing progress information in a window.
</li
>
3857 <p
>I still need to come up with a better name for the system. Here
3858 are some screen shots showing the prototype in action. First the
3859 notification, then the password request, and finally the request to
3860 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
3862 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
3863 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
3864 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
3865 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
3866 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
3868 <p
>The prototype still need to be improved with longer timeouts, but
3869 is already useful. The database of hardware to package mappings also
3870 need more work. It is currently compatible with the Ubuntu way of
3871 storing such information in the package control file, but could be
3872 changed to use other formats instead or in addition to the current
3873 method. I
've dropped the use of discover for this mapping, as the
3874 modalias approach is more flexible and easier to use on Linux as long
3875 as the Linux kernel expose its modalias strings directly.
</p
>
3877 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
3878 here is the command required to check out and build the source: Use
3879 '<tt
>svn checkout
3880 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3881 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
3882 devscripts package.
</p
>
3884 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
3885 renamed to Isenkram and the source moved from the Debian Edu
3886 subversion repository to a Debian collab-maint git repository. See
3887 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
3888 instructions
</a
> for details.
</p
>
3893 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
3894 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
3895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
3896 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
3897 <description><p
>This Christmas my trusty old laptop died. It died quietly and
3898 suddenly in bed. With a quiet whimper, it went completely quiet and
3899 black. The power button was no longer able to turn it on. It was a
3900 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3901 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3902 Compaq I had before that. Now I need to find a replacement. To keep
3903 going during Christmas, I moved the one year old SSD disk to my old
3904 X40 where it fitted (only one I had left that could use it), but it is
3905 not a durable solution.
3907 <p
>My laptop needs are fairly modest. This is my wishlist from when I
3908 got a new one more than
10 years ago. It still holds true.:)
</p
>
3912 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
3913 than A4).
</li
>
3914 <li
>Robust, it will be in my backpack every day.
</li
>
3915 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
3916 <li
>Long battery life time. Preferable a week.
</li
>
3917 <li
>Internal WIFI network card.
</li
>
3918 <li
>Internal Twisted Pair network card.
</li
>
3919 <li
>Some USB slots (
2-
3 is plenty)
</li
>
3920 <li
>Good keyboard - similar to the Thinkpad.
</li
>
3921 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
3923 <li
>Hardware supported by Debian Stable, ie the default kernel and
3924 X.org packages.
</li
>
3925 <li
>Quiet, preferably fan free (or at least not using the fan most of
3930 <p
>You will notice that there are no RAM and CPU requirements in the
3931 list. The reason is simply that the specifications on laptops the
3932 last
10-
15 years have been sufficient for my needs, and I have to look
3933 at other features to choose my laptop. But are there still made as
3934 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3935 robust, and Thinkpads seem to be heading in the wrong direction since
3936 Lenovo took over. But I
've been told that X220 and X1 Carbon might
3937 still be useful.
</p
>
3939 <p
>Perhaps I should rethink my needs, and look for a pad with an
3940 external keyboard? I
'll have to check the
3941 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
3942 well-supported laptops, or perhaps just buy one preinstalled from one
3943 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
3944 Pre-loaded site
</a
>.
</p
>
3949 <title>How to find a browser plugin supporting a given MIME type
</title>
3950 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
3951 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
3952 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
3953 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
3954 install to get support for a given MIME type. Thanks to
3955 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
3956 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
3957 Unfortunately, not very many packages provide the needed meta
3958 information, Anyway, here is a small script to look up all browser
3959 plugin packages announcing ther MIME support using this specification:
</p
>
3965 def pkgs_handling_mimetype(mimetype):
3970 version = pkg.candidate
3972 version = pkg.installed
3975 record = version.record
3976 if not record.has_key(
'Npp-MimeType
'):
3978 mime_types = record[
'Npp-MimeType
'].split(
',
')
3979 for t in mime_types:
3980 t = t.rstrip().strip()
3982 thepkgs.append(pkg.name)
3984 mimetype =
"audio/ogg
"
3985 if
1 < len(sys.argv):
3986 mimetype = sys.argv[
1]
3987 print
"Browser plugin packages supporting %s:
" % mimetype
3988 for pkg in pkgs_handling_mimetype(mimetype):
3989 print
" %s
" %pkg
3992 <p
>It can be used like this to look up a given MIME type:
</p
>
3995 % ./apt-find-browserplug-for-mimetype
3996 Browser plugin packages supporting audio/ogg:
3998 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3999 Browser plugin packages supporting application/x-shockwave-flash:
4000 browser-plugin-gnash
4004 <p
>In Ubuntu this mechanism is combined with support in the browser
4005 itself to query for plugins and propose to install the needed
4006 packages. It would be great if Debian supported such feature too. Is
4007 anyone working on adding it?
</p
>
4009 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4010 request for icweasel support for this feature is
4011 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4012 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4013 of manpower and wish for a different design is the reason thus feature
4014 is not yet in iceweasel from Debian.
</p
>
4019 <title>What is the most supported MIME type in Debian?
</title>
4020 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4021 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4022 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4023 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4024 proposal to add AppStream information to the Debian archive
</a
>, is a
4025 proposal to make it possible for a Desktop application to propose to
4026 the user some package to install to gain support for a given MIME
4027 type, font, library etc. that is currently missing. With such
4028 mechanism in place, it would be possible for the desktop to
4029 automatically propose and install leocad if some LDraw file is
4030 downloaded by the browser.
</p
>
4032 <p
>To get some idea about the current content of the archive, I decided
4033 to write a simple program to extract all .desktop files from the
4034 Debian archive and look up the claimed MIME support there. The result
4036 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4037 site
</a
>. Using the collected information, it become possible to
4038 answer the question in the title. Here are the
20 most supported MIME
4039 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4040 The complete list is available from the link above.
</p
>
4042 <p
><strong
>Debian Stable:
</strong
></p
>
4046 ----- -----------------------
4062 18 application/x-ogg
4069 <p
><strong
>Debian Testing:
</strong
></p
>
4073 ----- -----------------------
4089 18 application/x-ogg
4096 <p
><strong
>Debian Unstable:
</strong
></p
>
4100 ----- -----------------------
4117 18 application/x-ogg
4123 <p
>I am told that PackageKit can provide an API to access the kind of
4124 information mentioned in DEP-
11. I have not yet had time to look at
4125 it, but hope the PackageKit people in Debian are on top of these
4128 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4129 discovering a typo in my script.
</p
>
4134 <title>Using modalias info to find packages handling my hardware
</title>
4135 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4137 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4138 <description><p
>Yesterday, I wrote about the
4139 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4140 values provided by the Linux kernel
</a
> following my hope for
4141 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4142 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4143 modalias values attached to package names can be used to map packages
4144 to hardware. This allow the system to look up and suggest relevant
4145 packages when I plug in some new hardware into my machine, and replace
4146 discover and discover-data as the database used to map hardware to
4149 <p
>I create a modaliases file with entries like the following,
4150 containing package name, kernel module name (if relevant, otherwise
4151 the package name) and globs matching the relevant hardware
4154 <p
><blockquote
>
4155 Package: package-name
4156 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4157 </blockquote
></p
>
4159 <p
>It is fairly trivial to write code to find the relevant packages
4160 for a given modalias value using this file.
</p
>
4162 <p
>An entry like this would suggest the video and picture application
4163 cheese for many USB web cameras (interface bus class
0E01):
</p
>
4165 <p
><blockquote
>
4167 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
4168 </blockquote
></p
>
4170 <p
>An entry like this would suggest the pcmciautils package when a
4171 CardBus bridge (bus class
0607) PCI device is present:
</p
>
4173 <p
><blockquote
>
4174 Package: pcmciautils
4175 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4176 </blockquote
></p
>
4178 <p
>An entry like this would suggest the package colorhug-client when
4179 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
4181 <p
><blockquote
>
4182 Package: colorhug-client
4183 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
4184 </blockquote
></p
>
4186 <p
>I believe the format is compatible with the format of the Packages
4187 file in the Debian archive. Ubuntu already uses their Packages file
4188 to store their mappings from packages to hardware.
</p
>
4190 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
4191 announce the hardware it support in a way my prototype understand.
4192 This allow those publishing packages in an APT source outside the
4193 Debian archive as well as those backporting packages to make sure the
4194 hardware mapping are included in the package meta information. I
've
4195 tested such header in the pymissile package, and its modalias mapping
4196 is working as it should with my prototype. It even made it to Ubuntu
4199 <p
>To test if it was possible to look up supported hardware using only
4200 the shell tools available in the Debian installer, I wrote a shell
4201 implementation of the lookup code. The idea is to create files for
4202 each modalias and let the shell do the matching. Please check out and
4204 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
4205 shell script. It run without any extra dependencies and fetch the
4206 hardware mappings from the Debian archive and the subversion
4207 repository where I currently work on my prototype.
</p
>
4209 <p
>When I use it on a machine with a yubikey inserted, it suggest to
4210 install yubikey-personalization:
</p
>
4212 <p
><blockquote
>
4213 % ./hw-support-lookup
4214 <br
>yubikey-personalization
4216 </blockquote
></p
>
4218 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4219 propose to install the pcmciautils package:
</p
>
4221 <p
><blockquote
>
4222 % ./hw-support-lookup
4223 <br
>pcmciautils
4225 </blockquote
></p
>
4227 <p
>If you know of any hardware-package mapping that should be added to
4228 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
4229 database
</a
>, please tell me about it.
</p
>
4231 <p
>It could be possible to generate several of the mappings between
4232 packages and hardware. One source would be to look at packages with
4233 kernel modules, ie packages with *.ko files in /lib/modules/, and
4234 extract their modalias information. Another would be to look at
4235 packages with udev rules, ie packages with files in
4236 /lib/udev/rules.d/, and extract their vendor/model information to
4237 generate a modalias matching rule. I have not tested any of these to
4238 see if it work.
</p
>
4240 <p
>If you want to help implementing a system to let us propose what
4241 packages to install when new hardware is plugged into a Debian
4242 machine, please send me an email or talk to me on
4243 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4248 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
4249 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
4250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
4251 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
4252 <description><p
>While looking into how to look up Debian packages based on hardware
4253 information, to find the packages that support a given piece of
4254 hardware, I refreshed my memory regarding modalias values, and decided
4255 to document the details. Here are my findings so far, also available
4257 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4258 Debian Edu subversion repository
</a
>:
4260 <p
><strong
>Modalias decoded
</strong
></p
>
4262 <p
>This document try to explain what the different types of modalias
4263 values stands for. It is in part based on information from
4264 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
4265 &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;,
4266 &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
4267 &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;.
4269 <p
>The modalias entries for a given Linux machine can be found using
4270 this shell script:
</p
>
4273 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
4276 <p
>The supported modalias globs for a given kernel module can be found
4277 using modinfo:
</p
>
4280 % /sbin/modinfo psmouse | grep alias:
4281 alias: serio:ty05pr*id*ex*
4282 alias: serio:ty01pr*id*ex*
4286 <p
><strong
>PCI subtype
</strong
></p
>
4288 <p
>A typical PCI entry can look like this. This is an Intel Host
4289 Bridge memory controller:
</p
>
4291 <p
><blockquote
>
4292 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4293 </blockquote
></p
>
4295 <p
>This represent these values:
</p
>
4300 sv
00001028 (subvendor)
4301 sd
000001AD (subdevice)
4303 sc
00 (bus subclass)
4307 <p
>The vendor/device values are the same values outputted from
'lspci
4308 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4309 0600. The
0600 class is a host bridge. Other useful bus values are
4310 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4312 <p
>Not sure how to figure out the interface value, nor what it
4315 <p
><strong
>USB subtype
</strong
></p
>
4317 <p
>Some typical USB entries can look like this. This is an internal
4318 USB hub in a laptop:
</p
>
4320 <p
><blockquote
>
4321 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4322 </blockquote
></p
>
4324 <p
>Here is the values included in this alias:
</p
>
4327 v
1D6B (device vendor)
4328 p
0001 (device product)
4330 dc
09 (device class)
4331 dsc
00 (device subclass)
4332 dp
00 (device protocol)
4333 ic
09 (interface class)
4334 isc
00 (interface subclass)
4335 ip
00 (interface protocol)
4338 <p
>The
0900 device class/subclass means hub. Some times the relevant
4339 class is in the interface class section. For a simple USB web camera,
4340 these alias entries show up:
</p
>
4342 <p
><blockquote
>
4343 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4344 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4345 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4346 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4347 </blockquote
></p
>
4349 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4350 camera),
0101 is audio control device and
0102 is audio streaming (aka
4351 microphone). Thus this is a camera with microphone included.
</p
>
4353 <p
><strong
>ACPI subtype
</strong
></p
>
4355 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
4356 receiver in a Thinkpad X40:
</p
>
4358 <p
><blockquote
>
4359 acpi:IBM0071:PNP0511:
4360 </blockquote
></p
>
4362 <p
>The values between the colons are IDs.
</p
>
4364 <p
><strong
>DMI subtype
</strong
></p
>
4366 <p
>The DMI table contain lots of information about the computer case
4367 and model. This is an entry for a IBM Thinkpad X40, fetched from
4368 /sys/devices/virtual/dmi/id/modalias:
</p
>
4370 <p
><blockquote
>
4371 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4372 </blockquote
></p
>
4374 <p
>The values present are
</p
>
4377 bvn IBM (BIOS vendor)
4378 bvr
1UETB
6WW(
1.66) (BIOS version)
4379 bd
06/
15/
2005 (BIOS date)
4380 svn IBM (system vendor)
4381 pn
2371H4G (product name)
4382 pvr ThinkPadX40 (product version)
4383 rvn IBM (board vendor)
4384 rn
2371H4G (board name)
4385 rvr NotAvailable (board version)
4386 cvn IBM (chassis vendor)
4387 ct
10 (chassis type)
4388 cvr NotAvailable (chassis version)
4391 <p
>The chassis type
10 is Notebook. Other interesting values can be
4392 found in the dmidecode source:
</p
>
4396 4 Low Profile Desktop
4409 17 Main Server Chassis
4410 18 Expansion Chassis
4412 20 Bus Expansion Chassis
4413 21 Peripheral Chassis
4415 23 Rack Mount Chassis
4424 <p
>The chassis type values are not always accurately set in the DMI
4425 table. For example my home server is a tower, but the DMI modalias
4426 claim it is a desktop.
</p
>
4428 <p
><strong
>SerIO subtype
</strong
></p
>
4430 <p
>This type is used for PS/
2 mouse plugs. One example is from my
4431 test machine:
</p
>
4433 <p
><blockquote
>
4434 serio:ty01pr00id00ex00
4435 </blockquote
></p
>
4437 <p
>The values present are
</p
>
4446 <p
>This type is supported by the psmouse driver. I am not sure what
4447 the valid values are.
</p
>
4449 <p
><strong
>Other subtypes
</strong
></p
>
4451 <p
>There are heaps of other modalias subtypes according to
4452 file2alias.c. There is the rest of the list from that source: amba,
4453 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4454 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4455 vmbus, x86cpu and zorro. I did not spend time documenting all of
4456 these, as they do not seem relevant for my intended use with mapping
4457 hardware to packages when new stuff is inserted during run time.
</p
>
4459 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
4461 <p
>To check which kernel modules provide support for a given modalias,
4462 one can use the following shell script:
</p
>
4465 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
4466 echo
"$id
" ; \
4467 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
4471 <p
>The output can look like this (only the first few entries as the
4472 list is very long on my test machine):
</p
>
4476 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
4478 FATAL: Module acpi:device: not found.
4480 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
4481 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
4482 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
4483 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4484 acpi:IBM0071:PNP0511:
4485 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
4486 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
4487 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
4491 <p
>If you want to help implementing a system to let us propose what
4492 packages to install when new hardware is plugged into a Debian
4493 machine, please send me an email or talk to me on
4494 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4496 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
4497 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
4498 in /sys/ with space in them.
</p
>
4503 <title>Moved the pymissile Debian packaging to collab-maint
</title>
4504 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
4505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
4506 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
4507 <description><p
>As part of my investigation on how to improve the support in Debian
4508 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4509 Launcher and updated the Debian package
4510 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
4511 sure udev will fix the device permissions when it is plugged in. I
4512 also added a
"Modaliases
" header to test it in the Debian archive and
4513 hopefully make the package be proposed by jockey in Ubuntu when a user
4514 plug in his rocket launcher. In the process I moved the source to a
4515 git repository under collab-maint, to make it easier for any DD to
4516 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
4517 is not very active, but the software still work for me even after five
4518 years of relative silence. The new git repository is not listed in
4519 the uploaded package yet, because I want to test the other changes a
4520 bit more before I upload the new version. If you want to check out
4521 the new version with a .desktop file included, visit the
4522 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
4523 view
</a
> or use
"<tt
>git clone
4524 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
4529 <title>Lets make hardware dongles easier to use in Debian
</title>
4530 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
4531 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
4532 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
4533 <description><p
>One thing that annoys me with Debian and Linux distributions in
4534 general, is that there is a great package management system with the
4535 ability to automatically install software packages by downloading them
4536 from the distribution mirrors, but no way to get it to automatically
4537 install the packages I need to use the hardware I plug into my
4538 machine. Even if the package to use it is easily available from the
4539 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4540 suggest to automatically install the python-nxt, nbc and t2n packages
4541 I need to talk to it. When I plug in a Yubikey, it could propose the
4542 yubikey-personalization package. The information required to do this
4543 is available, but no-one have pulled all the pieces together.
</p
>
4545 <p
>Some years ago, I proposed to
4546 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
4547 the discover subsystem to implement this
</a
>. The idea is fairly
4552 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
4553 starting when a user log in.
</li
>
4555 <li
>Set this program up to listen for kernel events emitted when new
4556 hardware is inserted into the computer.
</li
>
4558 <li
>When new hardware is inserted, look up the hardware ID in a
4559 database mapping to packages, and take note of any non-installed
4560 packages.
</li
>
4562 <li
>Show a message to the user proposing to install the discovered
4563 package, and make it easy to install it.
</li
>
4567 <p
>I am not sure what the best way to implement this is, but my
4568 initial idea was to use dbus events to discover new hardware, the
4569 discover database to find packages and
4570 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
4573 <p
>Yesterday, I found time to try to implement this idea, and the
4574 draft package is now checked into
4575 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4576 Debian Edu subversion repository
</a
>. In the process, I updated the
4577 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
4578 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4579 the relevant packages in Debian, and uploaded a new version
4580 2.2013.01.09 to unstable. I also discovered that the current
4581 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
4582 package in Debian no longer discovered any USB devices, because
4583 /proc/bus/usb/devices is no longer present. I ported it to use
4584 libusb as a fall back option to get it working. The fixed package
4585 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
4586 because of the freeze).
</p
>
4588 <p
>With this prototype in place, I can insert my Yubikey, and get this
4589 desktop notification to show up (only once, the first time it is
4590 inserted):
</p
>
4592 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
4594 <p
>For this prototype to be really useful, some way to automatically
4595 install the proposed packages by pressing the
"Please install
4596 program(s)
" button should to be implemented.
</p
>
4598 <p
>If this idea seem useful to you, and you want to help make it
4599 happen, please help me update the discover-data database with mappings
4600 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
4601 list the package you would like to have installed when a given
4602 hardware device is inserted into your computer, and report bugs using
4603 reportbug if it isn
't. Or, if you know of a better way to provide
4604 such mapping, please let me know.
</p
>
4606 <p
>This prototype need more work, and there are several questions that
4607 should be considered before it is ready for production use. Is dbus
4608 the correct way to detect new hardware? At the moment I look for HAL
4609 dbus events on the system bus, because that is the events I could see
4610 on my Debian Squeeze KDE desktop. Are there better events to use?
4611 How should the user be notified? Is the desktop notification
4612 mechanism the best option, or should the background daemon raise a
4613 popup instead? How should packages be installed? When should they
4614 not be installed?
</p
>
4616 <p
>If you want to help getting such feature implemented in Debian,
4617 please send me an email. :)
</p
>
4622 <title>New IRC channel for LEGO designers using Debian
</title>
4623 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
4624 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
4625 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
4626 <description><p
>During Christmas, I have worked a bit on the Debian support for
4627 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
4628 NXT
</a
>. My son and I have played a bit with my NXT set, and I
4629 discovered I had to build all the tools myself because none were
4630 already in Debian Squeeze. If Debian support for LEGO is something
4631 you care about, please join me on the IRC channel
4632 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
4633 irc.debian.org). There is a lot that could be done to improve the
4634 Debian support for LEGO designers. For example both CAD software
4635 and Mindstorm compilers are missing. :)
</p
>
4637 <p
>Update
2012-
01-
03: A
4638 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
4639 including links to Lego related packages is now available.
</p
>
4644 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
4645 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
4646 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
4647 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
4648 <description><p
>Let me start by wishing you all marry Christmas and a happy new
4649 year! I hope next year will prove to be a good year.
</p
>
4651 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
4652 decentralised
"currency
" that allow people to transfer bitcoins
4653 between each other with minimal overhead, is a very interesting
4654 experiment. And as I wrote a few days ago, the bitcoin situation in
4655 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
4656 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
4657 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
4658 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
4659 for one of the ftpmasters to approve the new bitcoin-qt package
4662 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
4663 team in Debian, you can easily test the package in Debian Squeeze
4664 using the following steps to get a set of working packages:
</p
>
4666 <blockquote
><pre
>
4667 git clone git://git.debian.org/git/collab-maint/bitcoin
4669 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4670 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4671 </pre
></blockquote
>
4673 <p
>You might have to install some build dependencies as well. The
4674 list of commands should give you two packages, bitcoind and
4675 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4676 client will download the complete set of bitcoin
"blocks
", which need
4677 around
5.6 GiB of data on my machine at the moment. Make sure your
4678 ~/.bitcoin/ directory have lots of spare room if you want to download
4679 all the blocks. The client will warn if the disk is getting full, so
4680 there is not really a problem if you got too little room, but you will
4681 not be able to get all the features out of the client.
</p
>
4683 <p
>As usual, if you use bitcoin and want to show your support of my
4684 activities, please send Bitcoin donations to my address
4685 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4690 <title>A word on bitcoin support in Debian
</title>
4691 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
4692 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
4693 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
4694 <description><p
>It has been a while since I wrote about
4695 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
4696 peer-to-peer based crypto-currency, and the reason is simply that I
4697 have been busy elsewhere. But two days ago, I started looking at the
4698 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
4699 Debian
</a
> again to try to recover my old bitcoin wallet. The package
4700 is now maintained by a
4701 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
4702 people
</a
>, and the grunt work had already been done by this team. We
4703 owe a huge thank you to all these team members. :)
4704 But I was sad to discover that the bitcoin client is missing in
4705 Wheezy. It is only available in Sid (and an outdated client from
4706 backports). The client had several RC bugs registered in BTS blocking
4707 it from entering testing. To try to help the team and improve the
4708 situation, I spent some time providing patches and triaging the bug
4709 reports. I also had a look at the bitcoin package available from Matt
4711 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
4712 Ubuntu
</a
>, and moved the useful pieces from that version into the
4713 Debian package.
</p
>
4715 <p
>After checking with the main package maintainer Jonas Smedegaard on
4716 IRC, I pushed several patches into the collab-maint git repository to
4717 improve the package. It now contains fixes for the RC issues (not from
4718 me, but fixed by Scott Howard), build rules for a Qt GUI client
4719 package, konqueror support for the bitcoin: URI and bash completion
4720 setup. As I work on Debian Squeeze, I also created
4721 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
4722 patch to backport
</a
> the latest version. Jonas is going to look at
4723 it and try to integrate it into the git repository before uploading a
4724 new version to unstable.
4726 <p
>I would very much like bitcoin to succeed, to get rid of the
4727 centralized control currently exercised in the monetary system. I
4728 find it completely unacceptable that the USA government is collecting
4729 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4730 that the major credit card companies can block legal money
4731 transactions to Wikileaks. But for bitcoin to succeed, more people
4732 need to use bitcoins, and more people need to accept bitcoins when
4733 they sell products and services. Improving the bitcoin support in
4734 Debian is a small step in the right direction, but not enough.
4735 Unfortunately the user experience when browsing the web and wanting to
4736 pay with bitcoin is still not very good. The bitcoin: URI is a step
4737 in the right direction, but need to work in most or every browser in
4738 use. Also the bitcoin-qt client is too heavy to fire up to do a
4739 quick transaction. I believe there are other clients available, but
4740 have not tested them.
</p
>
4743 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
4744 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
4745 I received
20.15 BTC so far on the address I provided in my blog two
4746 years ago, as can be
4747 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
4748 on the blockexplorer service
</a
>. Thank you everyone for your
4749 donation. The blockexplorer service demonstrates quite well that
4750 bitcoin is not quite anonymous and untracked. :) I wonder if the
4751 number of users have gone up since then. If you use bitcoin and want
4752 to show your support of my activity, please send Bitcoin donations to
4753 the same address as last time,
4754 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4759 <title>Git repository for song book for Computer Scientists
</title>
4760 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
4761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
4762 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
4763 <description><p
>As I
4764 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
4765 this summer
</a
>, I have created a Computer Science song book a few
4766 years ago, and today I finally found time to create a public
4767 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
4768 repository for the project
</a
>.
</p
>
4770 <p
>If you want to help out, please clone the source and submit patches
4771 to the HTML version. To generate the PDF and PostScript version,
4772 please use prince XML, or let me know about a useful free software
4773 processor capable of creating a good looking PDF from the HTML.
</p
>
4775 <p
>Want to sing? You can still find the song book in HTML, PDF and
4776 PostScript formats at
4777 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
4778 Science Songbook
</a
>.
</p
>
4783 <title>Gratulerer med
19-årsdagen, Debian!
</title>
4784 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
4785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
4786 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
4787 <description><p
>I dag fyller
4788 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
4789 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
4790 si gratulerer med dagen, Debian!
</p
>
4795 <title>Song book for Computer Scientists
</title>
4796 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
4797 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
4798 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
4799 <description><p
>Many years ago, while studying Computer Science at the
4800 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
4801 collecting computer related songs for use at parties. The original
4802 version was written in LaTeX, but a few years ago I got help from
4803 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4804 while keeping the ability to create a nice book in PDF format. I have
4805 not had time to maintain the book for a while now, and guess I should
4806 put it up on some public version control repository where others can
4807 help me extend and update the book. If anyone is volunteering to help
4808 me with this, send me an email. Also let me know if there are songs
4809 missing in my book.
</p
>
4811 <p
>I have not mentioned the book on my blog so far, and it occured to
4812 me today that I really should let all my readers share the joys of
4813 singing out load about programming, computers and computer networks.
4814 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
4815 12</a
> is about to start (and I am not going). Want to sing? Check
4816 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
4817 Computer Science Songbook
</a
>.
4822 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
4823 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
4824 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
4825 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
4826 <description><p
>At work we have heaps of servers. I believe the total count is
4827 around
1000 at the moment. To be able to get help from the vendors
4828 when something go wrong, we want to keep the firmware on the servers
4829 up to date. If the firmware isn
't the latest and greatest, the
4830 vendors typically refuse to start debugging any problems until the
4831 firmware is upgraded. So before every reboot, we want to upgrade the
4832 firmware, and we would really like everyone handling servers at the
4833 university to do this themselves when they plan to reboot a machine.
4834 For that to happen we at the unix server admin group need to provide
4835 the tools to do so.
</p
>
4837 <p
>To make firmware upgrading easier, I am working on a script to
4838 fetch and install the latest firmware for the servers we got. Most of
4839 our hardware are from Dell and HP, so I have focused on these servers
4840 so far. This blog post is about the Dell part.
</P
>
4842 <p
>On the Dell FTP site I was lucky enough to find
4843 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
4844 with firmware information for all
11th generation servers, listing
4845 which firmware should be used on a given model and where on the FTP
4846 site I can find it. Using a simple perl XML parser I can then
4847 download the shell scripts Dell provides to do firmware upgrades from
4848 within Linux and reboot when all the firmware is primed and ready to
4849 be activated on the first reboot.
</p
>
4851 <p
>This is the Dell related fragment of the perl code I am working on.
4852 Are there anyone working on similar tools for firmware upgrading all
4853 servers at a site? Please get in touch and lets share resources.
</p
>
4855 <p
><pre
>
4859 use File::Temp qw(tempdir);
4861 # Install needed RHEL packages if missing
4863 'XML::Simple
' =
> 'perl-XML-Simple
',
4865 for my $module (keys %rhelmodules) {
4866 eval
"use $module;
";
4868 my $pkg = $rhelmodules{$module};
4869 system(
"yum install -y $pkg
");
4870 eval
"use $module;
";
4874 my $errorsto =
'pere@hungry.com
';
4880 sub run_firmware_script {
4881 my ($opts, $script) = @_;
4883 print STDERR
"fail: missing script name\n
";
4886 print STDERR
"Running $script\n\n
";
4888 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
4889 print STDERR
"success: firmware script ran succcessfully\n
";
4891 print STDERR
"fail: firmware script returned error\n
";
4895 sub run_firmware_scripts {
4896 my ($opts, @dirs) = @_;
4897 # Run firmware packages
4898 for my $dir (@dirs) {
4899 print STDERR
"info: Running scripts in $dir\n
";
4900 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
4901 while (my $s = readdir $dh) {
4902 next if $s =~ m/^\.\.?/;
4903 run_firmware_script($opts,
"$dir/$s
");
4911 print STDERR
"info: Downloading $url\n
";
4912 system(
"wget --quiet \
"$url\
"");
4917 my $product = `dmidecode -s system-product-name`;
4920 if ($product =~ m/PowerEdge/) {
4922 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4923 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
4925 my $tmpdir = tempdir(
4929 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
4930 system(
'gunzip Catalog.xml.gz
');
4931 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
4932 # -q is quiet, disabling interactivity and reducing console output
4933 my $fwopts =
"-q
";
4935 for my $url (@paths) {
4936 fetch_dell_fw($url);
4938 run_firmware_scripts($fwopts, $tmpdir);
4940 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4941 print STDERR
"error: Please report to $errorsto.\n
";
4945 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4946 print STDERR
"error: Please report to $errorsto.\n
";
4952 my $url =
"ftp://ftp.us.dell.com/$path
";
4956 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4957 # firmware packages to download from Dell. Only work for Linux
4958 # machines and
11th generation Dell servers.
4959 sub fetch_dell_fw_list {
4960 my $filename = shift;
4962 my $product = `dmidecode -s system-product-name`;
4964 my ($mybrand, $mymodel) = split(/\s+/, $product);
4966 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
4968 my $xml = XMLin($filename);
4970 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
4971 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
4972 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
4974 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
4975 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
4977 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
4979 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
4981 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
4984 for my $component (@{$xml-
>{SoftwareComponent}}) {
4985 my $componenttype = $component-
>{ComponentType}-
>{value};
4987 # Drop application packages, only firmware and BIOS
4988 next if
'APAC
' eq $componenttype;
4990 my $cpath = $component-
>{path};
4991 for my $path (@paths) {
4992 if ($cpath =~ m%/$path$%) {
4993 push(@paths, $cpath);
5001 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5002 it could work on other platforms with some tweaking. Anyone know a
5003 index like Catalog.xml is available from HP for HP servers? At the
5004 moment I maintain a similar list manually and it is quickly getting
5010 <title>How is booting into runlevel
1 different from single user boots?
</title>
5011 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5013 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5014 <description><p
>Wouter Verhelst have some
5015 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5016 comments and opinions
</a
> on my blog post on
5017 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5018 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5019 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5020 default KDE desktop in Debian
</a
>. I only have time to address one
5021 small piece of his comment now, and though it best to address the
5022 misunderstanding he bring forward:
</p
>
5024 <p
><blockquote
>
5025 Currently, a system admin has four options: [...] boot to a
5026 single-user system (by adding
'single
' to the kernel command line;
5027 this runs rcS and rc1 scripts)
5028 </blockquote
></p
>
5030 <p
>This make me believe Wouter believe booting into single user mode
5031 and booting into runlevel
1 is the same. I am not surprised he
5032 believe this, because it would make sense and is a quite sensible
5033 thing to believe. But because the boot in Debian is slightly broken,
5034 runlevel
1 do not work properly and it isn
't the same as single user
5035 mode. I
'll try to explain what is actually happing, but it is a bit
5036 hard to explain.
</p
>
5038 <p
>Single user mode is defined like this in /etc/inittab:
5039 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5040 executed in single user mode is sulogin. Single user mode is a boot
5041 state
"between
" the runlevels, and when booting into single user mode,
5042 only the scripts in /etc/rcS.d/ are executed before the init process
5043 enters the single user state. When switching to runlevel
1, the state
5044 is in fact not ending in runlevel
1, but it passes through runlevel
1
5045 and end up in the single user mode (see /etc/rc1.d/S03single, which
5046 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5047 1. It is confusing that the
'S
' (single user) init mode is not the
5048 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5051 <p
>This summary might make it clearer. When booting for the first
5052 time into single user mode, the following commands are executed:
5053 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5054 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5055 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5056 trying to continue after visiting single user mode. Not all services
5057 are started again as they should, causing the machine to end up in an
5058 unpredicatble state. This is why Debian admins recommend rebooting
5059 after visiting single user mode.
</p
>
5061 <p
>A similar problem with runlevel
1 is caused by the amount of
5062 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5063 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5064 stopped when passing through the scripts in /etc/rc1.d/, and not
5065 started again when switching away from runlevel
1 to the runlevels
5066 2-
5. I believe the problem is best fixed by moving all the scripts
5067 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5068 functioning single user mode during boot.
</p
>
5070 <p
>I have spent several years investigating the Debian boot system,
5071 and discovered this problem a few years ago. I suspect it originates
5072 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5077 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5078 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5080 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5081 <description><p
>In the Debian boot system, several packages include scripts that
5082 are started from /etc/rcS.d/. In fact, there is a bite more of them
5083 than make sense, and this causes a few problems. What kind of
5084 problems, you might ask. There are at least two problems. The first
5085 is that it is not possible to recover a machine after switching to
5086 runlevel
1. One need to actually reboot to get the machine back to
5087 the expected state. The other is that single user boot will sometimes
5088 run into problems because some of the subsystems are activated before
5089 the root login is presented, causing problems when trying to recover a
5090 machine from a problem in that subsystem. A minor additional point is
5091 that moving more scripts out of rcS.d/ and into the other rc#.d/
5092 directories will increase the amount of scripts that can run in
5093 parallel during boot, and thus decrease the boot time.
</p
>
5095 <p
>So, which scripts should start from rcS.d/. In short, only the
5096 scripts that _have_ to execute before the root login prompt is
5097 presented during a single user boot should go there. Everything else
5098 should go into the numeric runlevels. This means things like
5099 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5100 the numeric runlevels. Today in Debian, there are around
115 init.d
5101 scripts that are started from rcS.d/, and most of them should be moved
5102 out. Do your package have one of them? Please help us make single
5103 user and runlevel
1 better by moving it.
</p
>
5105 <p
>Scripts setting up the screen, keyboard, system partitions
5106 etc. should still be started from rcS.d/, but there is for example no
5107 need to have the network enabled before the single user login prompt
5108 is presented.
</p
>
5110 <p
>As always, things are not so easy to fix as they sound. To keep
5111 Debian systems working while scripts migrate and during upgrades, the
5112 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5113 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5114 and the next ones can only be moved when their dependencies have been
5115 moved first. This migration must be done sequentially while we ensure
5116 that the package system upgrade packages in the right order to keep
5117 the system state correct. This will require some coordination when it
5118 comes to network related packages, but most of the packages with
5119 scripts that should migrate do not have anything in rcS.d/ depending
5120 on them. Some packages have already been updated, like the sudo
5121 package, while others are still left to do. I wish I had time to work
5122 on this myself, but real live constrains make it unlikely that I will
5123 find time to push this forward.
</p
>
5128 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5129 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5131 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5132 <description><p
>While at Debconf11, I have several times during discussions
5133 mentioned the issues I believe should be improved in Debian for its
5134 desktop to be useful for more people. The use case for this is my
5135 parents, which are currently running Kubuntu which solve the
5138 <p
>I suspect these four missing features are not very hard to
5139 implement. After all, they are present in Ubuntu, so if we wanted to
5140 do this in Debian we would have a source.
</p
>
5144 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5145 are new packages available for upgrades, a icon in the KDE status bar
5146 indicate this, and clicking on it will activate the simple upgrade
5147 tool to handle it. I have no problem guiding both of my parents
5148 through the process over the phone. If a kernel reboot is required,
5149 this too is indicated by the status bars and the upgrade tool. Last
5150 time I checked, nothing with the same features was working in KDE in
5153 <li
><strong
>Simple handling of missing Firefox browser
5154 plugins.
</strong
> When the browser encounter a MIME type it do not
5155 currently have a handler for, it will ask the user if the system
5156 should search for a package that would add support for this MIME type,
5157 and if the user say yes, the APT sources will be searched for packages
5158 advertising the MIME type in their control file (visible in the
5159 Packages file in the APT archive). If one or more packages are found,
5160 it is a simple click of the mouse to add support for the missing mime
5161 type. If the package require the user to accept some non-free
5162 license, this is explained to the user. The entire process make it
5163 more clear to the user why something do not work in the browser, and
5164 make the chances higher for the user to blame the web page authors and
5165 not the browser for any missing features.
</li
>
5167 <li
><strong
>Simple handling of missing multimedia codec/format
5168 handlers.
</strong
> When the media players encounter a format or codec
5169 it is not supporting, a dialog pop up asking the user if the system
5170 should search for a package that would add support for it. This
5171 happen with things like MP3, Windows Media or H
.264. The selection
5172 and installation procedure is very similar to the Firefox browser
5173 plugin handling. This is as far as I know implemented using a
5174 gstreamer hook. The end result is that the user easily get access to
5175 the codecs that are present from the APT archives available, while
5176 explaining more on why a given format is unsupported by Ubuntu.
</li
>
5178 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
5179 displaying a text/plain file in my Debian browser, it will propose to
5180 start emacs to show it. If I remember correctly, when doing the same
5181 in Kunbutu it show the file as a text file in the browser. At least I
5182 know Opera will show text files within the browser. I much prefer the
5183 latter behaviour.
</li
>
5187 <p
>There are other nice features as well, like the simplified suite
5188 upgrader, but given that I am the one mostly doing the dist-upgrade,
5189 it do not matter much.
</p
>
5191 <p
>I really hope we could get these features in place for the next
5192 Debian release. It would require the coordinated effort of several
5193 maintainers, but would make the end user experience a lot better.
</p
>
5198 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
5199 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
5200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
5201 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
5202 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
5203 site is build on Debian/Squeeze, and this platform was chosen because
5204 I am most familiar with Debian (being a Debian Developer for around
10
5205 years) because it is the latest stable Debian release which should get
5206 security support for a few years.
</p
>
5208 <p
>The web service is written in Perl, and depend on some perl modules
5209 that are missing in Debian at the moment. It would be great if these
5210 modules were added to the Debian archive, allowing anyone to set up
5211 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
5212 in their own country using only Debian packages. The list of modules
5213 missing in Debian/Squeeze isn
't very long, and I hope the perl group
5214 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
5215 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5216 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5217 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5218 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5219 easier in the future.
</p
>
5221 <p
>Thanks to the great tools in Debian, getting the missing modules
5222 installed on my server was a simple call to
'cpan2deb Module::Name
'
5223 and
'dpkg -i
' to install the resulting package. But this leave me
5224 with the responsibility of tracking security problems, which I really
5225 do not have time for.
</p
>
5230 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
5231 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
5232 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
5233 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
5234 <description><p
>Here is a small update for my English readers. Most of my blog
5235 posts have been in Norwegian the last few weeks, so here is a short
5236 update in English.
</p
>
5238 <p
>The kids still keep me too busy to get much free software work
5239 done, but I did manage to organise a project to get a Norwegian port
5240 of the British service
5241 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
5242 and it has been running for a month now. The entire project has been
5243 organised by me and two others. Around Christmas we gathered sponsors
5244 to fund the development work. In January I drafted a contract with
5245 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
5246 and in February the development took place. Most of it involved
5247 converting the source to use GPS coordinates instead of British
5248 easting/northing, and the resulting code should be a lot easier to get
5249 running in any country by now. The Norwegian
5250 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
5251 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
5252 source and the source for administrative borders in Norway, and
5253 support for this had to be added/fixed.
</p
>
5255 <p
>The Norwegian version went live March
3th, and we spent the weekend
5256 polishing the system before we announced it March
7th. The system is
5257 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
5258 problem reports in a few weeks. Soon we hope to announce the Android
5259 and iPhone versions making it even easier to report problems with the
5260 public infrastructure.
</p
>
5262 <p
>Perhaps something to consider for those of you in countries without
5263 such service?
</p
>
5268 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
5269 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
5270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
5271 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
5272 <description><p
>The last few days I have looked at ways to track open security
5273 issues here at my work with the University of Oslo. My idea is that
5274 it should be possible to use the information about security issues
5275 available on the Internet, and check our locally
5276 maintained/distributed software against this information. It should
5277 allow us to verify that no known security issues are forgotten. The
5278 CVE database listing vulnerabilities seem like a great central point,
5279 and by using the package lists from Debian mapped to CVEs provided by
5280 the testing security team, I believed it should be possible to figure
5281 out which security holes were present in our free software
5282 collection.
</p
>
5284 <p
>After reading up on the topic, it became obvious that the first
5285 building block is to be able to name software packages in a unique and
5286 consistent way across data sources. I considered several ways to do
5287 this, for example coming up with my own naming scheme like using URLs
5288 to project home pages or URLs to the Freshmeat entries, or using some
5289 existing naming scheme. And it seem like I am not the first one to
5290 come across this problem, as MITRE already proposed and implemented a
5291 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5292 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5293 software, hardware and other platform components. The CPE ids are
5294 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5295 Vulnerability Database
</a
>, allowing me to look up know security
5296 issues for any CPE name. With this in place, all I need to do is to
5297 locate the CPE id for the software packages we use at the university.
5298 This is fairly trivial (I google for
'cve cpe $package
' and check the
5299 NVD entry if a CVE for the package exist).
</p
>
5301 <p
>To give you an example. The GNU gzip source package have the CPE
5302 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5303 check out, one could look up
5304 <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
5305 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5306 The most recent one is
5307 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5308 and at the bottom of the NVD page for this vulnerability the complete
5309 list of affected versions is provided.
</p
>
5311 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5312 for offline processing of issues. Using this dump, I
've written a
5313 small script taking a list of CPEs as input and list all CVEs
5314 affecting the packages represented by these CPEs. One give it CPEs
5315 with version numbers as specified above and get a list of open
5316 security issues out.
</p
>
5318 <p
>Of course for this approach to be useful, the quality of the NVD
5319 information need to be high. For that to happen, I believe as many as
5320 possible need to use and contribute to the NVD database. I notice
5322 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5323 map from CVE to CPE
</a
>, indicating that they are using the CPE
5324 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5326 <p
>To get an idea about the quality for free software, I spent some
5327 time making it possible to compare the CVE database from Debian with
5328 the CVE database in NVD. The result look fairly good, but there are
5329 some inconsistencies in NVD (same software package having several
5330 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5331 Debian believe are affected by a CVE). Hope to find time to improve
5332 the quality of NVD, but that require being able to get in touch with
5333 someone maintaining it. So far my three emails with questions and
5334 corrections have not seen any reply, but I hope contact can be
5335 established soon.
</p
>
5337 <p
>An interesting application for CPEs is cross platform package
5338 mapping. It would be useful to know which packages in for example
5339 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5340 this would be trivial if all linux distributions provided CPE entries
5341 for their packages.
</p
>
5346 <title>Which module is loaded for a given PCI and USB device?
</title>
5347 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5348 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5349 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5350 <description><p
>In the
5351 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5352 package in Debian, there is a script to report useful information
5353 about the running hardware for use when people report missing
5354 information. One part of this script that I find very useful when
5355 debugging hardware problems, is the part mapping loaded kernel module
5356 to the PCI device it claims. It allow me to quickly see if the kernel
5357 module I expect is driving the hardware I am struggling with. To see
5358 the output, make sure discover-data is installed and run
5359 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
5360 one of my machines like this:
</p
>
5364 10de:
03eb i2c_nforce2
5367 10de:
03f0 snd_hda_intel
5376 <p
>The code in question look like this, slightly modified for
5377 readability and to drop the output to file descriptor
3:
</p
>
5380 if [ -d /sys/bus/pci/devices/ ] ; then
5381 echo loaded pci modules:
5383 cd /sys/bus/pci/devices/
5384 for address in * ; do
5385 if [ -d
"$address/driver/module
" ] ; then
5386 module=`cd $address/driver/module ; pwd -P | xargs basename`
5387 if grep -q
"^$module
" /proc/modules ; then
5388 address=$(echo $address |sed s/
0000://)
5389 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
5390 echo
"$id $module
"
5399 <p
>Similar code could be used to extract USB device module
5403 if [ -d /sys/bus/usb/devices/ ] ; then
5404 echo loaded usb modules:
5406 cd /sys/bus/usb/devices/
5407 for address in * ; do
5408 if [ -d
"$address/driver/module
" ] ; then
5409 module=`cd $address/driver/module ; pwd -P | xargs basename`
5410 if grep -q
"^$module
" /proc/modules ; then
5411 address=$(echo $address |sed s/
0000://)
5412 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
5413 if [
"$id
" ] ; then
5414 echo
"$id $module
"
5424 <p
>This might perhaps be something to include in other tools as
5430 <title>How to test if a laptop is working with Linux
</title>
5431 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
5432 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
5433 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
5434 <description><p
>The last few days I have spent at work here at the
<a
5435 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
5436 batch of computers will work with Linux. Every year for the last few
5437 years the university have organised shared bid of a few thousand
5438 computers, and this year HP won the bid. Two different desktops and
5439 five different laptops are on the list this year. We in the UNIX
5440 group want to know which one of these computers work well with RHEL
5441 and Ubuntu, the two Linux distributions we currently handle at the
5442 university.
</p
>
5444 <p
>My test method is simple, and I share it here to get feedback and
5445 perhaps inspire others to test hardware as well. To test, I PXE
5446 install the OS version of choice, and log in as my normal user and run
5447 a few applications and plug in selected pieces of hardware. When
5448 something fail, I make a note about this in the test matrix and move
5449 on. If I have some spare time I try to report the bug to the OS
5450 vendor, but as I only have the machines for a short time, I rarely
5451 have the time to do this for all the problems I find.
</p
>
5453 <p
>Anyway, to get to the point of this post. Here is the simple tests
5454 I perform on a new model.
</p
>
5458 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
5459 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5460 RHEL5 and Debian Edu/Squeeze.
</li
>
5462 <li
>Is X.org working? If the graphical login screen show up after
5463 installation, X.org is working.
</li
>
5465 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
5466 package mesa-utils on Ubuntu) and writing down the frames per second
5467 reported by the program.
</li
>
5469 <li
>Is sound working? With Gnome and KDE, a sound is played when
5470 logging in, and if I can hear this the test is successful. If there
5471 are several audio exits on the machine, I try them all and check if
5472 the Gnome/KDE audio mixer can control where to send the sound. I
5473 normally test this by playing
5474 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
5475 video
</a
> in Firefox/Iceweasel.
</li
>
5477 <li
>Is the USB subsystem working? I test this by plugging in a USB
5478 memory stick and see if Gnome/KDE notices this.
</li
>
5480 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
5481 I have lying around, and see if Gnome/KDE notices this.
</li
>
5483 <li
>Is any built in camera working? Test using cheese, and see if a
5484 picture from the v4l device show up.
</li
>
5486 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5487 any bluetooth devices are discovered. In my office, I normally see a
5490 <li
>For laptops, is the SD or Compaq Flash reader working. I have
5491 memory modules lying around, and stick them in and see if Gnome/KDE
5492 notice this.
</li
>
5494 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
5495 special button work, and if the laptop continue to work after
5498 <li
>For laptops, is the extra buttons working, like audio level,
5499 adjusting background light, switching on/off external video output,
5500 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5501 laptop to laptop, so I just write down which are working and which are
5504 <li
>Some laptops have smart card readers, finger print readers,
5505 acceleration sensors etc. I rarely test these, as I do not know how
5506 to quickly test if they are working or not, so I only document their
5507 existence.
</li
>
5511 <p
>By now I suspect you are really curious what the test results are
5512 for the HP machines I am testing. I
'm not done yet, so I will report
5513 the test results later. For now I can report that HP
8100 Elite work
5514 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
5515 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
5516 can see, I have most machines left to test. One interesting
5517 observation is that Ubuntu Lucid has almost twice the frame rate than
5518 RHEL6 with glxgears. No idea why.
</p
>
5523 <title>Some thoughts on BitCoins
</title>
5524 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
5525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
5526 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
5527 <description><p
>As I continue to explore
5528 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
5529 what properties the system have, and how it will be affected by laws
5530 and regulations here in Norway. Here are some random notes.
</p
>
5532 <p
>One interesting thing to note is that since the transactions are
5533 verified using a peer to peer network, all details about a transaction
5534 is known to everyone. This means that if a BitCoin address has been
5535 published like I did with mine in my initial post about BitCoin, it is
5536 possible for everyone to see how many BitCoins have been transfered to
5537 that address. There is even a web service to look at the details for
5538 all transactions. There I can see that my address
5539 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
5540 have received
16.06 Bitcoin, the
5541 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
5542 address of Simon Phipps have received
181.97 BitCoin and the address
5543 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
5544 of EFF have received
2447.38 BitCoins so far. Thank you to each and
5545 every one of you that donated bitcoins to support my activity. The
5546 fact that anyone can see how much money was transfered to a given
5547 address make it more obvious why the BitCoin community recommend to
5548 generate and hand out a new address for each transaction. I
'm told
5549 there is no way to track which addresses belong to a given person or
5550 organisation without the person or organisation revealing it
5551 themselves, as Simon, EFF and I have done.
</p
>
5553 <p
>In Norway, and in most other countries, there are laws and
5554 regulations limiting how much money one can transfer across the border
5555 without declaring it. There are money laundering, tax and accounting
5556 laws and regulations I would expect to apply to the use of BitCoin.
5557 If the Skolelinux foundation
5558 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
5559 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
5560 normal bank transfers like EFF is doing, how should this be accounted?
5561 Given that it is impossible to know if money can cross the border or
5562 not, should everything or nothing be declared? What exchange rate
5563 should be used when calculating taxes? Would receivers have to pay
5564 income tax if the foundation were to pay Skolelinux contributors in
5565 BitCoin? I have no idea, but it would be interesting to know.
</p
>
5567 <p
>For a currency to be useful and successful, it must be trusted and
5568 accepted by a lot of users. It must be possible to get easy access to
5569 the currency (as a wage or using currency exchanges), and it must be
5570 easy to spend it. At the moment BitCoin seem fairly easy to get
5571 access to, but there are very few places to spend it. I am not really
5572 a regular user of any of the vendor types currently accepting BitCoin,
5573 so I wonder when my kind of shop would start accepting BitCoins. I
5574 would like to buy electronics, travels and subway tickets, not herbs
5575 and books. :) The currency is young, and this will improve over time
5576 if it become popular, but I suspect regular banks will start to lobby
5577 to get BitCoin declared illegal if it become popular. I
'm sure they
5578 will claim it is helping fund terrorism and money laundering (which
5579 probably would be true, as is any currency in existence), but I
5580 believe the problems should be solved elsewhere and not by blaming
5581 currencies.
</p
>
5583 <p
>The process of creating new BitCoins is called mining, and it is
5584 CPU intensive process that depend on a bit of luck as well (as one is
5585 competing against all the other miners currently spending CPU cycles
5586 to see which one get the next lump of cash). The
"winner
" get
50
5587 BitCoin when this happen. Yesterday I came across the obvious way to
5588 join forces to increase ones changes of getting at least some coins,
5589 by coordinating the work on mining BitCoins across several machines
5590 and people, and sharing the result if one is lucky and get the
50
5592 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
5593 if this sounds interesting. I have not had time to try to set up a
5594 machine to participate there yet, but have seen that running on ones
5595 own for a few days have not yield any BitCoins througth mining
5598 <p
>Update
2010-
12-
15: Found an
<a
5599 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
5600 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
5601 it was interesting to read. The arguments presented seem to be
5602 equally valid for gold, which was used as a currency for many years.
</p
>
5607 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
5608 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
5609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
5610 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
5611 <description><p
>With this weeks lawless
5612 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
5613 attacks
</a
> on Wikileak and
5614 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
5615 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
5616 not be trusted to handle money transactions.
5618 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
5619 Phipps on bitcoin
</a
> reminded me about a project that a friend of
5620 mine mentioned earlier. I decided to follow Simon
's example, and get
5621 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
5622 some help from my friend to get it all running, and he even handed me
5623 some bitcoins to get started. I even donated a few bitcoins to Simon
5624 for helping me remember BitCoin.
</p
>
5626 <p
>So, what is bitcoins, you probably wonder? It is a digital
5627 crypto-currency, decentralised and handled using peer-to-peer
5628 networks. It allows anonymous transactions and prohibits central
5629 control over the transactions, making it impossible for governments
5630 and companies alike to block donations and other transactions. The
5631 source is free software, and while the key dependency wxWidgets
2.9
5632 for the graphical user interface is missing in Debian, the command
5633 line client builds just fine. Hopefully Jonas
5634 <a href=
"http://bugs.debian.org/
578157">will get the package into
5635 Debian
</a
> soon.
</p
>
5637 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
5638 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
5639 bitcoins
</a
> when selling services and goods, and there are even
5640 currency
"stock
" markets where the exchange rate is decided. There
5641 are not many users so far, but the concept seems promising. If you
5642 want to get started and lack a friend with any bitcoins to spare,
5644 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
5645 bitcoin at the time of writing). Use
5646 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
5647 on the current exchange rates.
</p
>
5649 <p
>As an experiment, I have decided to set up bitcoind on one of my
5650 machines. If you want to support my activity, please send Bitcoin
5651 donations to the address
5652 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
5657 <title>Why isn
't Debian Edu using VLC?
</title>
5658 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
5659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
5660 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
5661 <description><p
>In the latest issue of Linux Journal, the readers choices were
5662 presented, and the winner among the multimedia player were VLC.
5663 Personally, I like VLC, and it is my player of choice when I first try
5664 to play a video file or stream. Only if VLC fail will I drag out
5665 gmplayer to see if it can do better. The reason is mostly the failure
5666 model and trust. When VLC fail, it normally pop up a error message
5667 reporting the problem. When mplayer fail, it normally segfault or
5668 just hangs. The latter failure mode drain my trust in the program.
<p
>
5670 <p
>But even if VLC is my player of choice, we have choosen to use
5671 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
5672 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
5673 plugin to play web videos seamlessly, and the VLC browser plugin is
5674 not very good. For example, it lack in-line control buttons, so there
5675 is no way for the user to pause the video. Also, when I
5676 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
5677 tested the browser plugins
</a
> available in Debian, the VLC plugin
5678 failed on several video pages where mplayer based plugins worked. If
5679 the browser plugin for VLC was as good as the gecko-mediaplayer
5680 package (which uses mplayer), we would switch.
</P
>
5682 <p
>While VLC is a good player, its user interface is slightly
5683 annoying. The most annoying feature is its inconsistent use of
5684 keyboard shortcuts. When the player is in full screen mode, its
5685 shortcuts are different from when it is playing the video in a window.
5686 For example, space only work as pause when in full screen mode. I
5687 wish it had consisten shortcuts and that space also would work when in
5688 window mode. Another nice shortcut in gmplayer is [enter] to restart
5689 the current video. It is very nice when playing short videos from the
5690 web and want to restart it when new people arrive to have a look at
5691 what is going on.
</p
>
5696 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
5697 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
5698 <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>
5699 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
5700 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
5701 upgrade testing of the
5702 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5703 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
5704 This seem like a very good idea, so I adjusted by test scripts and
5705 can now present the updated result from today:
</p
>
5707 <p
>This is for Gnome:
</p
>
5709 <p
>Installed using apt-get, missing with aptitude
</p
>
5711 <blockquote
><p
>
5716 browser-plugin-gnash
5723 freedesktop-sound-theme
5725 gconf-defaults-service
5740 gnome-desktop-environment
5744 gnome-session-canberra
5749 gstreamer0.10-fluendo-mp3
5755 libapache2-mod-dnssd
5758 libaprutil1-dbd-sqlite3
5761 libboost-date-time1.42
.0
5762 libboost-python1.42
.0
5763 libboost-thread1.42
.0
5765 libchamplain-gtk-
0.4-
0
5767 libclutter-gtk-
0.10-
0
5774 libfreerdp-plugins-standard
5789 libgnomepanel2.24-cil
5794 libgtksourceview2.0-common
5795 libmono-addins-gui0.2-cil
5796 libmono-addins0.2-cil
5797 libmono-cairo2.0-cil
5798 libmono-corlib2.0-cil
5799 libmono-i18n-west2.0-cil
5800 libmono-posix2.0-cil
5801 libmono-security2.0-cil
5802 libmono-sharpzip2.84-cil
5803 libmono-system2.0-cil
5806 libndesk-dbus-glib1.0-cil
5807 libndesk-dbus1.0-cil
5817 libtelepathy-farsight0
5826 nautilus-sendto-empathy
5830 python-aptdaemon-gtk
5832 python-beautifulsoup
5847 python-gtksourceview2
5858 python-pkg-resources
5865 python-twisted-conch
5871 python-zope.interface
5876 rhythmbox-plugin-cdrecorder
5883 system-config-printer-udev
5885 telepathy-mission-control-
5
5896 </p
></blockquote
>
5898 <p
>Installed using apt-get, removed with aptitude
</p
>
5900 <blockquote
><p
>
5906 fast-user-switch-applet
5925 libgtksourceview2.0-
0
5927 libsdl1.2debian-alsa
5933 system-config-printer
5938 </p
></blockquote
>
5940 <p
>Installed using aptitude, missing with apt-get
</p
>
5942 <blockquote
><p
>
5943 gstreamer0.10-gnomevfs
5944 </p
></blockquote
>
5946 <p
>Installed using aptitude, removed with apt-get
</p
>
5948 <blockquote
><p
>
5950 </p
></blockquote
>
5952 <p
>This is for KDE:
</p
>
5954 <p
>Installed using apt-get, missing with aptitude
</p
>
5956 <blockquote
><p
>
5958 </p
></blockquote
>
5960 <p
>Installed using apt-get, removed with aptitude
</p
>
5962 <blockquote
><p
>
5965 </p
></blockquote
>
5967 <p
>Installed using aptitude, missing with apt-get
</p
>
5969 <blockquote
><p
>
5983 kdeartwork-emoticons
5985 kdeartwork-theme-icon
5989 kdebase-workspace-bin
5990 kdebase-workspace-data
6004 kscreensaver-xsavers
6019 plasma-dataengines-workspace
6021 plasma-desktopthemes-artwork
6022 plasma-runners-addons
6023 plasma-scriptengine-googlegadgets
6024 plasma-scriptengine-python
6025 plasma-scriptengine-qedje
6026 plasma-scriptengine-ruby
6027 plasma-scriptengine-webkit
6028 plasma-scriptengines
6029 plasma-wallpapers-addons
6030 plasma-widget-folderview
6031 plasma-widget-networkmanagement
6035 xscreensaver-data-extra
6037 xscreensaver-gl-extra
6038 xscreensaver-screensaver-bsod
6039 </p
></blockquote
>
6041 <p
>Installed using aptitude, removed with apt-get
</p
>
6043 <blockquote
><p
>
6045 google-gadgets-common
6063 libggadget-qt-
1.0-
0b
6068 libkonqsidebarplugin4a
6077 libplasma-geolocation-interface4
6079 libplasmagenericshell4
6093 libsmokeknewstuff2-
3
6094 libsmokeknewstuff3-
3
6096 libsmokektexteditor3
6104 libsmokeqtnetwork4-
3
6110 libsmokeqtuitools4-
3
6122 plasma-dataengines-addons
6123 plasma-scriptengine-superkaramba
6124 plasma-widget-lancelot
6125 plasma-widgets-addons
6126 plasma-widgets-workspace
6130 update-notifier-common
6131 </p
></blockquote
>
6133 <p
>Running apt-get autoremove made the results using apt-get and
6134 aptitude a bit more similar, but there are still quite a lott of
6135 differences. I have no idea what packages should be installed after
6136 the upgrade, but hope those that do can have a look.
</p
>
6141 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6142 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6143 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6144 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6145 <description><p
>Most of the computers in use by the
6146 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6147 are virtual machines. And they have been Xen machines running on a
6148 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6149 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6150 bit harder that it could have been, because we set up the Xen virtual
6151 machines to get the virtual partitions from LVM, which as far as I
6152 know is not supported by KVM. So to migrate, we had to convert
6153 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6156 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6157 nice recipe
</a
> to do this, and wrote the following script to do the
6158 migration. It uses qemu-img from the qemu package to make the disk
6159 image, parted to partition it, losetup and kpartx to present the disk
6160 image partions as devices, and dd to copy the data. I NFS mounted the
6161 new servers storage area on the old server to do the migration.
</p
>
6167 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6172 if [ -z
"$
1" ] ; then
6173 echo
"Usage: $
0 &lt;hostname
&gt;
"
6179 if [ ! -e /dev/vg_data/$host-disk ] ; then
6180 echo
"error: unable to find LVM volume for $host
"
6184 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6185 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6186 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6187 totalsize=$(( ( $disksize + $swapsize ) ))
6190 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
6191 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6193 parted $img mklabel msdos
6194 parted $img mkpart primary linux-swap
0 $disksize
6195 parted $img mkpart primary ext2 $disksize $totalsize
6196 parted $img set
1 boot on
6199 losetup /dev/loop0 $img
6200 kpartx -a /dev/loop0
6202 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
6203 fsck.ext3 -f /dev/mapper/loop0p1 || true
6204 mkswap /dev/mapper/loop0p2
6206 kpartx -d /dev/loop0
6207 losetup -d /dev/loop0
6210 <p
>The script is perhaps so simple that it is not copyrightable, but
6211 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
6213 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
6214 the new disk image attached, installed grub-pc and linux-image-
686 and
6215 set up grub to boot from the disk image. After this, the KVM machines
6216 seem to work just fine.
</p
>
6221 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
6222 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
6223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
6224 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
6225 <description><p
>I
'm still running upgrade testing of the
6226 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6227 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
6228 status. Here is a short update based on a test I ran
20101118.
</p
>
6230 <p
>I still do not know what a correct migration should look like, so I
6231 report any differences between apt and aptitude and hope someone else
6232 can see if anything should be changed.
</p
>
6234 <p
>This is for Gnome:
</p
>
6236 <p
>Installed using apt-get, missing with aptitude
</p
>
6238 <blockquote
><p
>
6239 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6240 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
6241 dmz-cursor-theme empathy empathy-common finger
6242 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6243 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6244 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6245 gnome-cards-data gnome-codec-install gnome-core
6246 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6247 gnome-search-tool gnome-session-canberra gnome-spell
6248 gnome-system-log gnome-themes-extras gnome-themes-more
6249 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6250 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6251 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6252 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6253 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
6254 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
6255 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
6256 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
6257 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
6258 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6259 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
6260 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6261 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6262 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6263 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6264 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6265 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6266 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6267 libmono-security2.0-cil libmono-sharpzip2.84-cil
6268 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
6269 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
6270 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
6271 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
6272 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
6273 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
6274 libxalan2-java libxerces2-java media-player-info mesa-utils
6275 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
6276 nautilus-sendto-empathy openoffice.org-writer2latex
6277 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
6278 python-aptdaemon python-aptdaemon-gtk python-axiom
6279 python-beautifulsoup python-bugbuddy python-clientform
6280 python-coherence python-configobj python-crypto python-cupshelpers
6281 python-cupsutils python-eggtrayicon python-elementtree
6282 python-epsilon python-evolution python-feedparser python-gdata
6283 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6284 python-gtksourceview2 python-httplib2 python-louie python-mako
6285 python-markupsafe python-mechanize python-nevow python-notify
6286 python-opengl python-openssl python-pam python-pkg-resources
6287 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6288 python-tagpy python-twisted-bin python-twisted-conch
6289 python-twisted-core python-twisted-web python-utidylib python-webkit
6290 python-xdg python-zope.interface remmina remmina-plugin-data
6291 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6292 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6293 software-center svgalibg1 system-config-printer-udev
6294 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6295 totem totem-coherence totem-mozilla totem-plugins
6296 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6298 </p
></blockquote
>
6300 Installed using apt-get, removed with aptitude
6302 <blockquote
><p
>
6303 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6304 epiphany-extensions epiphany-gecko evolution-exchange
6305 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6306 gedit-common gnome-app-install gnome-games gnome-games-data
6307 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6308 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6309 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6310 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6311 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6312 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6313 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6314 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6315 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6316 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6317 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6318 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6319 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6320 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6321 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6322 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6323 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6324 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6325 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6326 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6327 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6328 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6329 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6330 sound-juicer swfdec-gnome system-config-printer totem-common
6331 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6332 </p
></blockquote
>
6334 <p
>Installed using aptitude, missing with apt-get
</p
>
6336 <blockquote
><p
>
6337 gstreamer0.10-gnomevfs
6338 </p
></blockquote
>
6340 <p
>Installed using aptitude, removed with apt-get
</p
>
6342 <blockquote
><p
>
6344 </p
></blockquote
>
6346 <p
>This is for KDE:
</p
>
6348 <p
>Installed using apt-get, missing with aptitude
</p
>
6350 <blockquote
><p
>
6351 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6352 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6353 ghostscript-x git gnome-audio gnugo granatier gs-common
6354 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6355 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6356 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6357 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6358 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6359 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6360 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6361 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6362 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6363 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6364 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6365 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
6366 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6367 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6368 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6369 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6370 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6371 libkrossui4 libmailtools-perl libmime-tools-perl
6372 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6373 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6374 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6375 lirc luatex marble networkstatus noatun-plugins
6376 openoffice.org-writer2latex palapeli palapeli-data parley
6377 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6378 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6379 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6381 </p
></blockquote
>
6383 <p
>Installed using apt-get, removed with aptitude
</p
>
6385 <blockquote
><p
>
6386 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6387 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6388 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6389 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6390 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6391 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6392 kitchensync kiten kjumpingcube klatin klettres klickety klines
6393 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6394 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6395 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6396 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6397 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6398 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6399 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6400 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6401 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6402 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
6403 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
6404 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6405 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
6406 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
6407 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6408 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6409 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6410 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6411 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6412 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6413 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
6414 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
6415 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6416 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6417 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6418 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6419 </p
></blockquote
>
6421 <p
>Installed using aptitude, missing with apt-get
</p
>
6423 <blockquote
><p
>
6424 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6425 kdeartwork kdebase kdebase-apps kdebase-workspace
6426 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6427 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6428 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6429 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6430 xscreensaver-screensaver-bsod
6431 </p
></blockquote
>
6433 <p
>Installed using aptitude, removed with apt-get
</p
>
6435 <blockquote
><p
>
6436 kdebase-bin konq-plugins konqueror
6437 </p
></blockquote
>
6442 <title>Gnash buildbot slave and Debian kfreebsd
</title>
6443 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
6444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
6445 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
6446 <description><p
>Answering
6447 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
6448 call from the Gnash project
</a
> for
6449 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
6450 current source, I have set up a virtual KVM machine on the Debian
6451 Edu/Skolelinux virtualization host to test the git source on
6452 Debian/Squeeze. I hope this can help the developers in getting new
6453 releases out more often.
</p
>
6455 <p
>As the developers want less main-stream build platforms tested to,
6456 I have considered setting up a
<a
6457 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
6458 machine as well. I have also considered using the kfreebsd
6459 architecture in Debian as a file server in NUUG to get access to the
5
6460 TB zfs volume we currently use to store DV video. Because of this, I
6461 finally got around to do a test installation of Debian/Squeeze with
6462 kfreebsd. Installation went fairly smooth, thought I noticed some
6463 visual glitches in the cdebconf dialogs (black cursor left on the
6464 screen at random locations). Have not gotten very far with the
6465 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6466 fatal problem. Have to spend some more time on it to see if it is
6467 useful as a file server for NUUG. Will try to find time to set up a
6468 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
6473 <title>Debian in
3D
</title>
6474 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
6475 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
6476 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
6477 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
6479 <p
>3D printing is just great. I just came across this Debian logo in
6481 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
6482 thingiverse blog
</a
>.
</p
>
6487 <title>Software updates
2010-
10-
24</title>
6488 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
6489 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
6490 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
6491 <description><p
>Some updates.
</p
>
6493 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
6494 raise money for the project is going well. The lower limit of
10
6495 signers was reached in
24 hours, and so far
13 people have signed it.
6496 More signers and more funding is most welcome, and I am really curious
6497 how far we can get before the time limit of December
24 is reached.
6500 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
6501 about what appear to be a great code coverage tool capable of
6502 generating code coverage stats without any changes to the source code.
6504 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
6505 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
6506 It is missing in Debian, but the git source built just fine in Squeeze
6507 after I installed libelf-dev, libdwarf-dev, pkg-config and
6508 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6509 solvable. I hope kcov make it into Debian soon.
</p
>
6511 <p
>Finally found time to wrap up the release notes for
<a
6512 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
6513 new alpha release of Debian Edu
</a
>, and just published the second
6514 alpha test release of the Squeeze based Debian Edu /
6515 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
6516 release. Give it a try if you need a complete linux solution for your
6517 school, including central infrastructure server, workstations, thin
6518 client servers and diskless workstations. A nice touch added
6519 yesterday is RDP support on the thin client servers, for windows
6520 clients to get a Linux desktop on request.
</p
>
6525 <title>Some notes on Flash in Debian and Debian Edu
</title>
6526 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
6527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
6528 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
6529 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
6530 popularity-contest numbers
</a
>, the adobe-flashplugin package the
6531 second most popular used package that is missing in Debian. The sixth
6532 most popular is flashplayer-mozilla. This is a clear indication that
6533 working flash is important for Debian users. Around
10 percent of the
6534 users submitting data to popcon.debian.org have this package
6535 installed.
</p
>
6537 <p
>In the report written by Lars Risan in August
2008
6538 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
6539 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6540 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
6541 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
6542 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
6543 web sites require Flash to work, and lacking working Flash support in
6544 the web browser and the problems with installing it was perceived as a
6545 good reason to stay with Windows.
</p
>
6547 <p
>I once saw a funny and sad comment in a web forum, where Linux was
6548 said to be the retarded cousin that did not really understand
6549 everything you told him but could work fairly well. This was a
6550 comment regarding the problems Linux have with proprietary formats and
6551 non-standard web pages, and is sad because it exposes a fairly common
6552 understanding of whose fault it is if web pages that only work in for
6553 example Internet Explorer
6 fail to work on Firefox, and funny because
6554 it explain very well how annoying it is for users when Linux
6555 distributions do not work with the documents they receive or the web
6556 pages they want to visit.
</p
>
6558 <p
>This is part of the reason why I believe it is important for Debian
6559 and Debian Edu to have a well working Flash implementation in the
6560 distribution, to get at least popular sites as Youtube and Google
6561 Video to working out of the box. For Squeeze, Debian have the chance
6562 to include the latest version of Gnash that will make this happen, as
6563 the new release
0.8.8 was published a few weeks ago and is resting in
6564 unstable. The new version work with more sites that version
0.8.7.
6565 The Gnash maintainers have asked for a freeze exception, but the
6566 release team have not had time to reply to it yet. I hope they agree
6567 with me that Flash is important for the Debian desktop users, and thus
6568 accept the new package into Squeeze.
</p
>
6573 <title>Circular package dependencies harms apt recovery
</title>
6574 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
6575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
6576 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
6577 <description><p
>I discovered this while doing
6578 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
6579 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
6580 in Debian still got circular dependencies, and it is often claimed
6581 that apt and aptitude should be able to handle this just fine, but
6582 some times these dependency loops causes apt to fail.
</p
>
6584 <p
>An example is from todays
6585 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
6586 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
6587 causes perl-modules to fail to upgrade. The cause is simple. If a
6588 package fail to unpack, then only part of packages with the circular
6589 dependency might end up being unpacked when unpacking aborts, and the
6590 ones already unpacked will fail to configure in the recovery phase
6591 because its dependencies are unavailable.
</p
>
6593 <p
>In this log, the problem manifest itself with this error:
</p
>
6595 <blockquote
><pre
>
6596 dpkg: dependency problems prevent configuration of perl-modules:
6597 perl-modules depends on perl (
>=
5.10.1-
1); however:
6598 Version of perl on system is
5.10.0-
19lenny
2.
6599 dpkg: error processing perl-modules (--configure):
6600 dependency problems - leaving unconfigured
6601 </pre
></blockquote
>
6603 <p
>The perl/perl-modules circular dependency is already
6604 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
6605 hopefully be solved as soon as possible, but it is not the only one,
6606 and each one of these loops in the dependency tree can cause similar
6607 failures. Of course, they only occur when there are bugs in other
6608 packages causing the unpacking to fail, but it is rather nasty when
6609 the failure of one package causes the problem to become worse because
6610 of dependency loops.
</p
>
6613 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
6614 tireless effort by Bill Allombert
</a
>, the number of circular
6616 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
6617 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
6619 <p
>Todays testing also exposed a bug in
6620 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
6621 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
6622 apt-get and aptitude, the latter possibly caused by some circular
6623 dependency. Reported both to BTS to try to get someone to look at
6629 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
6630 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
6631 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
6632 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
6633 <description><p
>This is a
6634 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
6636 <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
6638 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
6639 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
6641 <p
>As a step to try to see if it possible to merge the DNS and DHCP
6642 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6643 and dhcp3-server-ldap in Debian use the LDAP server. The two
6644 implementations are quite different in how they use LDAP.
</p
>
6646 To get this information, I started slapd with debugging enabled and
6647 dumped the debug output to a file to get the LDAP searches performed
6648 on a Debian Edu main-server. Here is a summary.
6650 <p
><strong
>powerdns
</strong
></p
>
6652 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
6653 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
6656 <p
>PowerDNS have two modes of operation using LDAP as its backend.
6657 One
"strict
" mode where the forward and reverse DNS lookups are done
6658 using the same LDAP objects, and a
"tree
" mode where the forward and
6659 reverse entries are in two different subtrees in LDAP with a structure
6660 based on the DNS names, as in tjener.intern and
6661 2.2.0.10.in-addr.arpa.
</p
>
6663 <p
>In tree mode, the server is set up to use a LDAP subtree as its
6664 base, and uses a
"base
" scoped search for the DNS name by adding
6665 "dc=tjener,dc=intern,
" to the base with a filter for
6666 "(associateddomain=tjener.intern)
" for the forward entry and
6667 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
6668 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
6669 forward entries, it is looking for attributes named dnsttl, arecord,
6670 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6671 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6672 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6673 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6674 spfrecord and modifytimestamp. For reverse entries it is looking for
6675 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6676 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6677 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6678 ldapsearch commands could look like this:
</p
>
6680 <blockquote
><pre
>
6681 ldapsearch -h ldap \
6682 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6683 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6684 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6685 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6686 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6687 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6689 ldapsearch -h ldap \
6690 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6691 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
6692 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6693 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6694 srvrecord naptrrecord modifytimestamp
6695 </pre
></blockquote
>
6697 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
6698 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6699 example LDAP objects used there. In addition to these objects, the
6700 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6701 also exist.
</p
>
6703 <blockquote
><pre
>
6704 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6706 objectclass: dnsdomain
6707 objectclass: domainrelatedobject
6710 associateddomain: tjener.intern
6712 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6714 objectclass: dnsdomain2
6715 objectclass: domainrelatedobject
6717 ptrrecord: tjener.intern
6718 associateddomain:
2.2.0.10.in-addr.arpa
6719 </pre
></blockquote
>
6721 <p
>In strict mode, the server behaves differently. When looking for
6722 forward DNS entries, it is doing a
"subtree
" scoped search with the
6723 same base as in the tree mode for a object with filter
6724 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
6725 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6726 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6727 naptrrecord and modifytimestamp. For reverse entires it also do a
6728 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
6729 and the requested attributes are associateddomain, dnsttl and
6730 modifytimestamp. In short, in strict mode the objects with ptrrecord
6731 go away, and the arecord attribute in the forward object is used
6734 <p
>The forward and reverse searches can be simulated using ldapsearch
6735 like this:
</p
>
6737 <blockquote
><pre
>
6738 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6739 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6740 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6741 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6742 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6743 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6745 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6746 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
6747 </pre
></blockquote
>
6749 <p
>In addition to the forward and reverse searches , there is also a
6750 search for SOA records, which behave similar to the forward and
6751 reverse lookups.
</p
>
6753 <p
>A thing to note with the PowerDNS behaviour is that it do not
6754 specify any objectclass names, and instead look for the attributes it
6755 need to generate a DNS reply. This make it able to work with any
6756 objectclass that provide the needed attributes.
</p
>
6758 <p
>The attributes are normally provided in the cosine (RFC
1274) and
6759 dnsdomain2 schemas. The latter is used for reverse entries like
6760 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
6762 <p
>In Debian Edu, we have created DNS objects using the object classes
6763 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6764 attributes) and domainrelatedobject (for associatedDomain). The use
6765 of structural object classes make it impossible to combine these
6766 classes with the object classes used by DHCP.
</p
>
6768 <p
>There are other schemas that could be used too, for example the
6769 dnszone structural object class used by Gosa and bind-sdb for the DNS
6770 attributes combined with the domainrelatedobject object class, but in
6771 this case some unused attributes would have to be included as well
6772 (zonename and relativedomainname).
</p
>
6774 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
6775 mode and not use any of the existing objectclasses (dnsdomain,
6776 dnsdomain2 and dnszone) when one want to combine the DNS information
6777 with DHCP information, and instead create a auxiliary object class
6778 defined something like this (using the attributes defined for
6779 dnsdomain and dnsdomain2 or dnszone):
</p
>
6781 <blockquote
><pre
>
6782 objectclass ( some-oid NAME
'dnsDomainAux
'
6785 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6786 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6787 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6788 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6789 A6Record $ DNAMERecord
6791 </pre
></blockquote
>
6793 <p
>This will allow any object to become a DNS entry when combined with
6794 the domainrelatedobject object class, and allow any entity to include
6795 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
6796 developers asking for their view on this schema and if they are
6797 interested in providing such schema with PowerDNS, and I hope my
6798 message will be accepted into their mailing list soon.
</p
>
6800 <p
><strong
>ISC dhcp
</strong
></p
>
6802 <p
>The DHCP server searches for specific objectclass and requests all
6803 the object attributes, and then uses the attributes it want. This
6804 make it harder to figure out exactly what attributes are used, but
6805 thanks to the working example in Debian Edu I can at least get an idea
6806 what is needed without having to read the source code.
</p
>
6808 <p
>In the DHCP server configuration, the LDAP base to use and the
6809 search filter to use to locate the correct dhcpServer entity is
6810 stored. These are the relevant entries from
6811 /etc/dhcp3/dhcpd.conf:
</p
>
6813 <blockquote
><pre
>
6814 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
6815 ldap-dhcp-server-cn
"dhcp
";
6816 </pre
></blockquote
>
6818 <p
>The DHCP server uses this information to nest all the DHCP
6819 configuration it need. The cn
"dhcp
" is located using the given LDAP
6820 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
6821 search result is this entry:
</p
>
6823 <blockquote
><pre
>
6824 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6827 objectClass: dhcpServer
6828 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6829 </pre
></blockquote
>
6831 <p
>The content of the dhcpServiceDN attribute is next used to locate the
6832 subtree with DHCP configuration. The DHCP configuration subtree base
6833 is located using a base scope search with base
"cn=DHCP
6834 Config,dc=skole,dc=skolelinux,dc=no
" and filter
6835 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
6836 The search result is this entry:
</p
>
6838 <blockquote
><pre
>
6839 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6842 objectClass: dhcpService
6843 objectClass: dhcpOptions
6844 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6845 dhcpStatements: ddns-update-style none
6846 dhcpStatements: authoritative
6847 dhcpOption: smtp-server code
69 = array of ip-address
6848 dhcpOption: www-server code
72 = array of ip-address
6849 dhcpOption: wpad-url code
252 = text
6850 </pre
></blockquote
>
6852 <p
>Next, the entire subtree is processed, one level at the time. When
6853 all the DHCP configuration is loaded, it is ready to receive requests.
6854 The subtree in Debian Edu contain objects with object classes
6855 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6856 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6857 and information about netmasks, dynamic range etc. Leaving out the
6858 details here because it is not relevant for the focus of my
6859 investigation, which is to see if it is possible to merge dns and dhcp
6860 related computer objects.
</p
>
6862 <p
>When a DHCP request come in, LDAP is searched for the MAC address
6863 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
6864 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
6865 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6866 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
6869 <blockquote
><pre
>
6870 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6873 objectClass: dhcpHost
6874 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6875 dhcpStatements: fixed-address hostname
6876 </pre
></blockquote
>
6878 <p
>There is less flexiblity in the way LDAP searches are done here.
6879 The object classes need to have fixed names, and the configuration
6880 need to be stored in a fairly specific LDAP structure. On the
6881 positive side, the invidiual dhcpHost entires can be anywhere without
6882 the DN pointed to by the dhcpServer entries. The latter should make
6883 it possible to group all host entries in a subtree next to the
6884 configuration entries, and this subtree can also be shared with the
6885 DNS server if the schema proposed above is combined with the dhcpHost
6886 structural object class.
6888 <p
><strong
>Conclusion
</strong
></p
>
6890 <p
>The PowerDNS implementation seem to be very flexible when it come
6891 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
6892 come to the the LDAP structure, the
"strict
" mode is very flexible,
6893 allowing DNS objects to be stored anywhere under the base cn specified
6894 in the configuration.
</p
>
6896 <p
>The DHCP implementation on the other hand is very inflexible, both
6897 regarding which LDAP schemas to use and which LDAP structure to use.
6898 I guess one could implement ones own schema, as long as the
6899 objectclasses and attributes have the names used, but this do not
6900 really help when the DHCP subtree need to have a fairly fixed
6901 structure.
</p
>
6903 <p
>Based on the observed behaviour, I suspect a LDAP structure like
6904 this might work for Debian Edu:
</p
>
6906 <blockquote
><pre
>
6908 cn=machine-info (dhcpService) - dhcpServiceDN points here
6909 cn=dhcp (dhcpServer)
6910 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6911 cn=
10.0.2.0 (dhcpSubnet)
6912 cn=group1 (dhcpGroup/dhcpOptions)
6913 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6914 cn=
192.168.0.0 (dhcpSubnet)
6915 cn=group1 (dhcpGroup/dhcpOptions)
6916 ou=machines - PowerDNS base points here
6917 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6918 </pre
></blockquote
>
6920 <P
>This is not tested yet. If the DHCP server require the dhcpHost
6921 entries to be in the dhcpGroup subtrees, the entries can be stored
6922 there instead of a common machines subtree, and the PowerDNS base
6923 would have to be moved one level up to the machine-info subtree.
</p
>
6925 <p
>The combined object under the machines subtree would look something
6926 like this:
</p
>
6928 <blockquote
><pre
>
6929 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6932 objectClass: dhcpHost
6933 objectclass: domainrelatedobject
6934 objectclass: dnsDomainAux
6935 associateddomain: hostname.intern
6936 arecord:
10.11.12.13
6937 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6938 dhcpStatements: fixed-address hostname.intern
6939 </pre
></blockquote
>
6941 </p
>One could even add the LTSP configuration associated with a given
6942 machine, as long as the required attributes are available in a
6943 auxiliary object class.
</p
>
6948 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
6949 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
6950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
6951 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
6952 <description><p
>For a while now, I have wanted to find a way to change the DNS and
6953 DHCP services in Debian Edu to use the same LDAP objects for a given
6954 computer, to avoid the possibility of having a inconsistent state for
6955 a computer in LDAP (as in DHCP but no DNS entry or the other way
6956 around) and make it easier to add computers to LDAP.
</p
>
6958 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
6959 information finally found a solution that seem to work.
</p
>
6961 <p
>The old setup required three LDAP objects for a given computer.
6962 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6963 we switch powerdns to use its strict LDAP method (ldap-method=strict
6964 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6965 merged into one while making it impossible to transfer the reverse map
6966 to a slave DNS server.
</p
>
6968 <p
>If we also replace the object class used to get the DNS related
6969 attributes to one allowing these attributes to be combined with the
6970 dhcphost object class, we can merge the DNS and DHCP entries into one.
6971 I
've written such object class in the dnsdomainaux.schema file (need
6972 proper OIDs, but that is a minor issue), and tested the setup. It
6973 seem to work.
</p
>
6975 <p
>With this test setup in place, we can get away with one LDAP object
6976 for both DNS and DHCP, and even the LTSP configuration I suggested in
6977 an earlier email. The combined LDAP object will look something like
6980 <blockquote
><pre
>
6981 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6983 objectClass: dhcphost
6984 objectclass: domainrelatedobject
6985 objectclass: dnsdomainaux
6986 associateddomain: hostname.intern
6987 arecord:
10.11.12.13
6988 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
6989 dhcpstatements: fixed-address hostname
6991 </pre
></blockquote
>
6993 <p
>The DNS server uses the associateddomain and arecord entries, while
6994 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6995 before asking DNS to resolve the fixed-adddress. LTSP will use
6996 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
6998 <p
>I am not yet sure if I can get the DHCP server to look for its
6999 dhcphost in a different location, to allow us to put the objects
7000 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7001 that. If I can
't figure out a way to do that, we can still get rid of
7002 the hosts subtree and move all its content into the DHCP Config tree
7003 (which probably should be renamed to be more related to the new
7004 content. I suspect cn=dnsdhcp,ou=services or something like that
7005 might be a good place to put it.
</p
>
7007 <p
>If you want to help out with implementing this for Debian Edu,
7008 please contact us on debian-edu@lists.debian.org.
</p
>
7013 <title>Idea for storing LTSP configuration in LDAP
</title>
7014 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7016 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7017 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7018 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7019 clients, and that this can be used to fetch configuration from LDAP if
7020 Debian Edu choose to store configuration there.
</p
>
7022 <p
>Armed with this information, I got inspired and wrote a test module
7023 to get configuration from LDAP. The idea is to look up the MAC
7024 address of the client in LDAP, and look for attributes on the form
7025 ltspconfigsetting=value, and use this to export SETTING=value to the
7026 LTSP clients.
</p
>
7028 <p
>The goal is to be able to store the LTSP configuration attributes
7029 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7030 allowing us to store all information about a computer in one place.
</p
>
7032 <p
>This is a untested draft implementation, and I welcome feedback on
7033 this approach. A real LDAP schema for the ltspClientAux objectclass
7034 need to be written. Comments, suggestions, etc?
</p
>
7036 <blockquote
><pre
>
7037 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7039 # Fetch LTSP client settings from LDAP based on MAC address
7041 # Uses ethernet address as stored in the dhcpHost objectclass using
7042 # the dhcpHWAddress attribute or ethernet address stored in the
7043 # ieee802Device objectclass with the macAddress attribute.
7045 # This module is written to be schema agnostic, and only depend on the
7046 # existence of attribute names.
7048 # The LTSP configuration variables are saved directly using a
7049 # ltspConfig prefix and uppercasing the rest of the attribute name.
7050 # To set the SERVER variable, set the ltspConfigServer attribute.
7052 # Some LDAP schema should be created with all the relevant
7053 # configuration settings. Something like this should work:
7055 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7058 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7060 LDAPSERVER=$(debian-edu-ldapserver)
7061 if [
"$LDAPSERVER
" ] ; then
7062 LDAPBASE=$(debian-edu-ldapserver -b)
7063 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7064 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7065 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7066 grep
'^ltspConfig
' | while read attr value ; do
7067 # Remove prefix and convert to upper case
7068 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7069 # bass value on to clients
7070 eval
"$attr=$value; export $attr
"
7074 </pre
></blockquote
>
7076 <p
>I
'm not sure this shell construction will work, because I suspect
7077 the while block might end up in a subshell causing the variables set
7078 there to not show up in ltsp-config, but if that is the case I am sure
7079 the code can be restructured to make sure the variables are passed on.
7080 I expect that can be solved with some testing. :)
</p
>
7082 <p
>If you want to help out with implementing this for Debian Edu,
7083 please contact us on debian-edu@lists.debian.org.
</p
>
7085 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7086 configuration in LDAP that was created around year
2000 by
7087 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7088 Xperience, Inc.,
2000</a
>. I found its
7089 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7090 personal home page over at redhat.com.
</p
>
7095 <title>jXplorer, a very nice LDAP GUI
</title>
7096 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7098 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7099 <description><p
>Since
7100 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7101 last post
</a
> about available LDAP tools in Debian, I was told about a
7102 LDAP GUI that is even better than luma. The java application
7103 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7104 moving LDAP objects and subtrees using drag-and-drop, and can
7105 authenticate using Kerberos. I have only tested the Kerberos
7106 authentication, but do not have a LDAP setup allowing me to rewrite
7107 LDAP with my test user yet. It is
7108 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7109 Debian
</a
> testing and unstable at the moment. The only problem I
7110 have with it is how it handle errors. If something go wrong, its
7111 non-intuitive behaviour require me to go through some query work list
7112 and remove the failing query. Nothing big, but very annoying.
</p
>
7117 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7118 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7119 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7120 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7121 <description><p
>Here is a short update on my
<a
7122 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7123 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7124 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7125 not reporting the status for KDE, because the upgrade crashes when
7126 aptitude try because of missing conflicts
7127 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7128 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7130 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7131 complete list of the installed packages. Based on this I see these
7132 differences when I did a test run today. As usual, I do not really
7133 know what the correct set of packages would be, but thought it best to
7134 publish the difference.
</p
>
7136 <p
>Installed using apt-get, missing with aptitude
</p
>
7138 <blockquote
><p
>
7139 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7140 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7141 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7142 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7143 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7144 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7145 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7146 python-gtkmozembed svgalibg1 xserver-xephyr zip
7147 </p
></blockquote
>
7149 <p
>Installed using apt-get, removed with aptitude
</p
>
7151 <blockquote
><p
>
7152 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7153 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7154 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7155 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7156 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7157 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7158 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7159 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7160 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7161 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
7162 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
7163 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
7164 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7165 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
7166 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7167 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
7168 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
7169 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7170 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7171 mysql-common swfdec-gnome totem-gstreamer wodim
7172 </p
></blockquote
>
7174 <p
>Installed using aptitude, missing with apt-get
</p
>
7176 <blockquote
><p
>
7177 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7178 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7179 xserver-xorg-input-all xserver-xorg-input-evdev
7180 xserver-xorg-input-kbd xserver-xorg-input-mouse
7181 xserver-xorg-input-synaptics xserver-xorg-video-all
7182 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7183 xserver-xorg-video-chips xserver-xorg-video-cirrus
7184 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7185 xserver-xorg-video-glint xserver-xorg-video-i128
7186 xserver-xorg-video-i740 xserver-xorg-video-mach64
7187 xserver-xorg-video-mga xserver-xorg-video-neomagic
7188 xserver-xorg-video-nouveau xserver-xorg-video-nv
7189 xserver-xorg-video-r128 xserver-xorg-video-radeon
7190 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7191 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7192 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7193 xserver-xorg-video-sis xserver-xorg-video-sisusb
7194 xserver-xorg-video-tdfx xserver-xorg-video-tga
7195 xserver-xorg-video-trident xserver-xorg-video-tseng
7196 xserver-xorg-video-vesa xserver-xorg-video-vmware
7197 xserver-xorg-video-voodoo
7198 </p
></blockquote
>
7200 <p
>Installed using aptitude, removed with apt-get
</p
>
7202 <blockquote
><p
>
7203 deskbar-applet xserver-xorg xserver-xorg-core
7204 xserver-xorg-input-wacom xserver-xorg-video-intel
7205 xserver-xorg-video-openchrome
7206 </p
></blockquote
>
7208 <p
>I was told on IRC that the xorg-xserver package was
7209 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
7210 in git
</a
> today to try to get apt-get to not remove xorg completely.
7211 No idea when it hits Squeeze, but when it does I hope it will reduce
7212 the difference somewhat.
7217 <title>LUMA, a very nice LDAP GUI
</title>
7218 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
7219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
7220 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
7221 <description><p
>The last few days I have been looking into the status of the LDAP
7222 directory in Debian Edu, and in the process I started to miss a GUI
7223 tool to browse the LDAP tree. The only one I was able to find in
7224 Debian/Squeeze and Lenny is
7225 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
7226 be a great tool to get a overview of the current LDAP directory
7227 populated by default in Skolelinux. Thanks to it, I have been able to
7228 find empty and obsolete subtrees, misplaced objects and duplicate
7229 objects. It will be installed by default in Debian/Squeeze. If you
7230 are working with LDAP, give it a go. :)
</p
>
7232 <p
>I did notice one problem with it I have not had time to report to
7233 the BTS yet. There is no .desktop file in the package, so the tool do
7234 not show up in the Gnome and KDE menus, but only deep down in in the
7235 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7238 <p
>I have not yet been able to get it to modify the tree yet. I would
7239 like to move objects and remove subtrees directly in the GUI, but have
7240 not found a way to do that with LUMA yet. So in the mean time, I use
7241 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
7243 <p
>If you have tips on other GUI tools for LDAP that might be useful
7244 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
7246 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
7247 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
7248 useful GUI alternative. It seem like a good tool, but is unmaintained
7249 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7250 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
7255 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
7256 <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>
7257 <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>
7258 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
7259 <description><p
>A while back, I
7260 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
7261 about the fact
</a
> that it is not possible with the provided schemas
7262 for storing DNS and DHCP information in LDAP to combine the two sets
7263 of information into one LDAP object representing a computer.
</p
>
7265 <p
>In the mean time, I discovered that a simple fix would be to make
7266 the dhcpHost object class auxiliary, to allow it to be combined with
7267 the dNSDomain object class, and thus forming one object for one
7268 computer when storing both DHCP and DNS information in LDAP.
</p
>
7270 <p
>If I understand this correctly, it is not safe to do this change
7271 without also changing the assigned number for the object class, and I
7272 do not know enough about LDAP schema design to do that properly for
7273 Debian Edu.
</p
>
7275 <p
>Anyway, for future reference, this is how I believe we could change
7277 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
7278 schema
</a
> to solve at least part of the problem with the LDAP schemas
7279 available today from IETF.
</p
>
7282 --- dhcp.schema (revision
65192)
7283 +++ dhcp.schema (working copy)
7285 objectclass (
2.16.840.1.113719.1.203.6.6
7286 NAME
'dhcpHost
'
7287 DESC
'This represents information about a particular client
'
7291 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7292 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7295 <p
>I very much welcome clues on how to do this properly for Debian
7296 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7297 package, and should thus be free to rewrite it as we see fit.
</p
>
7299 <p
>If you want to help out with implementing this for Debian Edu,
7300 please contact us on debian-edu@lists.debian.org.
</p
>
7305 <title>Calling tasksel like the installer, while still getting useful output
</title>
7306 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7307 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7308 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7309 <description><p
>A few times I have had the need to simulate the way tasksel
7310 installs packages during the normal debian-installer run. Until now,
7311 I have ended up letting tasksel do the work, with the annoying problem
7312 of not getting any feedback at all when something fails (like a
7313 conffile question from dpkg or a download that fails), using code like
7316 <blockquote
><pre
>
7317 export DEBIAN_FRONTEND=noninteractive
7318 tasksel --new-install
7319 </pre
></blockquote
>
7321 This would invoke tasksel, let its automatic task selection pick the
7322 tasks to install, and continue to install the requested tasks without
7323 any output what so ever.
7325 Recently I revisited this problem while working on the automatic
7326 package upgrade testing, because tasksel would some times hang without
7327 any useful feedback, and I want to see what is going on when it
7328 happen. Then it occured to me, I can parse the output from tasksel
7329 when asked to run in test mode, and use that aptitude command line
7330 printed by tasksel then to simulate the tasksel run. I ended up using
7333 <blockquote
><pre
>
7334 export DEBIAN_FRONTEND=noninteractive
7335 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7337 </pre
></blockquote
>
7339 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7340 --without-recommends -o APT::Install-Recommends=no -y install
7341 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7342 ~pimportant
</tt
>", which will install the gnome desktop task, the
7343 laptop task and all packages with priority standard , required and
7344 important, just like tasksel would have done it during
7345 installation.
</p
>
7347 <p
>A better approach is probably to extend tasksel to be able to
7348 install packages without using debconf-apt-progress, for use cases
7349 like this.
</p
>
7354 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
7355 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
7356 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
7357 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
7358 <description><p
>My
7359 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
7360 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
7361 finally made the upgrade logs available from
7362 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
7363 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7364 apt and aptitude, and found their differences interesting. This time
7365 I will only focus on their removal plans.
</p
>
7367 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
7368 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
7369 surprising part is that it want to remove xorg and all
7370 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7371 sure why. When asking aptitude to do the same, it want to remove
129
7372 packages, but most of them are library packages I suspect are no
7373 longer needed. Both of them want to remove bluetooth packages, which
7374 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
7376 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
7377 which seem like a bad idea and xorg the same way as with Gnome. Asking
7378 aptitude for the same, it wants to remove
192 packages, none which are
7379 too surprising.
</p
>
7381 <p
>I guess the removal of xorg during upgrades should be investigated
7382 and avoided, and perhaps others as well. Here are the complete list
7383 of planned removals. The complete logs is available from the URL
7384 above. Note if you want to repeat these tests, that the upgrade test
7385 for kde+apt-get hung in the tasksel setup because of dpkg asking
7386 conffile questions. No idea why. I worked around it by using
7387 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
7390 <p
><b
>apt-get gnome
72</b
>
7391 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
7392 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7393 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
7394 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7395 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7396 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7397 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7398 xserver-xorg-input-kbd xserver-xorg-input-mouse
7399 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7400 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7401 xserver-xorg-video-ati xserver-xorg-video-chips
7402 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7403 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7404 xserver-xorg-video-glint xserver-xorg-video-i128
7405 xserver-xorg-video-i740 xserver-xorg-video-imstt
7406 xserver-xorg-video-intel xserver-xorg-video-mach64
7407 xserver-xorg-video-mga xserver-xorg-video-neomagic
7408 xserver-xorg-video-nsc xserver-xorg-video-nv
7409 xserver-xorg-video-openchrome xserver-xorg-video-r128
7410 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7411 xserver-xorg-video-rendition xserver-xorg-video-s3
7412 xserver-xorg-video-s3virge xserver-xorg-video-savage
7413 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7414 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7415 xserver-xorg-video-tga xserver-xorg-video-trident
7416 xserver-xorg-video-tseng xserver-xorg-video-v4l
7417 xserver-xorg-video-vesa xserver-xorg-video-vga
7418 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
7419 xulrunner-
1.9-gnome-support
</p
>
7421 <p
><b
>aptitude gnome
129</b
>
7423 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
7424 djvulibre-desktop finger gnome-app-install gnome-mount
7425 gnome-network-admin gnome-spell gnome-vfs-obexftp
7426 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7427 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7428 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7429 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
7430 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
7431 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
7432 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
7433 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
7434 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
7435 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
7436 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
7437 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
7438 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7439 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
7440 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
7441 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
7442 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
7443 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
7444 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7445 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7446 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7447 openoffice.org-writer2latex openssl-blacklist p7zip
7448 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
7449 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7450 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7451 swfdec-mozilla totem-gstreamer update-manager wodim
7452 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7453 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7456 <p
><b
>apt-get kde
82</b
>
7458 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7459 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7460 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7461 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7462 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7463 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7464 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7465 xserver-xorg-input-kbd xserver-xorg-input-mouse
7466 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7467 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7468 xserver-xorg-video-ati xserver-xorg-video-chips
7469 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7470 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7471 xserver-xorg-video-glint xserver-xorg-video-i128
7472 xserver-xorg-video-i740 xserver-xorg-video-imstt
7473 xserver-xorg-video-intel xserver-xorg-video-mach64
7474 xserver-xorg-video-mga xserver-xorg-video-neomagic
7475 xserver-xorg-video-nsc xserver-xorg-video-nv
7476 xserver-xorg-video-openchrome xserver-xorg-video-r128
7477 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7478 xserver-xorg-video-rendition xserver-xorg-video-s3
7479 xserver-xorg-video-s3virge xserver-xorg-video-savage
7480 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7481 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7482 xserver-xorg-video-tga xserver-xorg-video-trident
7483 xserver-xorg-video-tseng xserver-xorg-video-v4l
7484 xserver-xorg-video-vesa xserver-xorg-video-vga
7485 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
7487 <p
><b
>aptitude kde
192</b
>
7488 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
7489 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7490 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7491 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7492 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7493 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7494 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7495 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7496 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7497 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7498 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7499 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7500 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7501 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7502 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7503 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7504 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7505 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7506 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
7507 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7508 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7509 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
7510 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7511 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7512 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7513 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7514 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7515 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
7516 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
7517 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7518 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7519 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7520 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7521 texlive-common texlive-doc-base texlive-fonts-recommended
7522 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7523 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7524 xulrunner-
1.9</p
>
7530 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
7531 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
7532 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
7533 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
7534 <description><p
>The last few days I have done some upgrade testing in Debian, to
7535 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7536 have been discovered and reported in the process
7537 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
7538 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
7539 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
7540 kdebase-workspace-data), and to get a more regular testing going on, I
7541 am working on a script to automate the test.
</p
>
7543 <p
>The idea is to create a Lenny chroot and use tasksel to install a
7544 Gnome or KDE desktop installation inside the chroot before upgrading
7545 it. To ensure no services are started in the chroot, a policy-rc.d
7546 script is inserted. To make sure tasksel believe it is to install a
7547 desktop on a laptop, the tasksel tests are replaced in the chroot
7548 (only acceptable because this is a throw-away chroot).
</p
>
7550 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7551 currently always fail because udev refuses to upgrade with the kernel
7552 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7553 is created. The bug report
7554 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
7555 this problem do not trigger in a chroot, but I touch the file anyway
7556 to make sure the upgrade go well. Testing on virtual and real
7557 hardware have failed me because of udev so far, and creating this file
7558 do the trick in such settings anyway. This is a
7559 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
7560 issue
</a
> and the current udev behaviour is intended by the udev
7561 maintainer because he lack the resources to rewrite udev to keep
7562 working with old kernels or something like that. I really wish the
7563 udev upstream would keep udev backwards compatible, to avoid such
7564 upgrade problem, but given that they fail to do so, I guess
7565 documenting the way out of this mess is the best option we got for
7566 Debian Squeeze.
</p
>
7568 <p
>Anyway, back to the task at hand, testing upgrades. This test
7569 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
7572 <blockquote
><pre
>
7576 if [
"$
1" ] ; then
7585 exec
&lt; /dev/null
7587 mirror=http://ftp.skolelinux.org/debian
7588 tmpdir=chroot-$from-upgrade-$to-$desktop
7590 debootstrap $from $tmpdir $mirror
7591 chroot $tmpdir aptitude update
7592 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
7596 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7600 mount -t proc proc $tmpdir/proc
7601 # Make sure proc is unmounted also on failure
7602 trap exit_cleanup EXIT INT
7604 chroot $tmpdir aptitude -y install debconf-utils
7606 # Make sure tasksel autoselection trigger. It need the test scripts
7607 # to return the correct answers.
7608 echo tasksel tasksel/desktop multiselect $desktop | \
7609 chroot $tmpdir debconf-set-selections
7611 # Include the desktop and laptop task
7612 for test in desktop laptop ; do
7613 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
7617 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7620 DEBIAN_FRONTEND=noninteractive
7621 DEBIAN_PRIORITY=critical
7622 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7623 chroot $tmpdir tasksel --new-install
7625 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
7626 chroot $tmpdir aptitude update
7627 touch $tmpdir/etc/udev/kernel-upgrade
7628 chroot $tmpdir aptitude -y dist-upgrade
7630 </pre
></blockquote
>
7632 <p
>I suspect it would be useful to test upgrades with both apt-get and
7633 with aptitude, but I have not had time to look at how they behave
7634 differently so far. I hope to get a cron job running to do the test
7635 regularly and post the result on the web. The Gnome upgrade currently
7636 work, while the KDE upgrade fail because of the bug in
7637 kdebase-workspace-data
</p
>
7639 <p
>I am not quite sure what kind of extract from the huge upgrade logs
7640 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
7641 post, so I will refrain from trying. I can report that for Gnome,
7642 aptitude report
760 packages upgraded,
448 newly installed,
129 to
7643 remove and
1 not upgraded and
1024MB need to be downloaded while for
7644 KDE the same numbers are
702 packages upgraded,
507 newly installed,
7645 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
7647 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
7648 is able to migrate to dependency based boot sequencing and parallel
7649 booting without a hitch. Was unsure if there were still bugs with
7650 packages failing to clean up their obsolete init.d script during
7651 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7657 <title>Upstart or sysvinit - as init.d scripts see it
</title>
7658 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
7659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
7660 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
7661 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
7662 scripts to migrate (some of) their operations to upstart job while
7663 keeping the init.d for hurd and kfreebsd. The packages with such
7664 needs will need a way to get their init.d scripts to behave
7665 differently when used with sysvinit and with upstart. Because of
7666 this, I had a look at the environment variables set when a init.d
7667 script is running under upstart, and when it is not.
</p
>
7669 <p
>With upstart, I notice these environment variables are set when a
7670 script is started from rcS.d/ (ignoring some irrelevant ones like
7673 <blockquote
><pre
>
7679 UPSTART_EVENTS=startup
7681 UPSTART_JOB=rc-sysinit
7682 </pre
></blockquote
>
7684 <p
>With sysvinit, these environment variables are set for the same
7687 <blockquote
><pre
>
7688 INIT_VERSION=sysvinit-
2.88
7693 </pre
></blockquote
>
7695 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
7696 sysvinit are not set by upstart. Not sure if it is intentional or not
7697 to not be compatible with sysvinit in this regard.
</p
>
7699 <p
>For scripts needing to behave differently when upstart is used,
7700 looking for the UPSTART_JOB environment variable seem to be a good
7706 <title>A manual for standards wars...
</title>
7707 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
7708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
7709 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
7710 <description><p
>Via the
7711 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
7712 of Rob Weir
</a
> I came across the very interesting essay named
7713 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
7714 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
7715 following the standards wars of today.
</p
>
7720 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
7721 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
7722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
7723 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
7724 <description><p
>When using sitesummary at a site to track machines, it is possible
7725 to get a list of the machine types in use thanks to the DMI
7726 information extracted from each machine. The script to do so is
7727 included in the sitesummary package, and here is example output from
7728 the Skolelinux build servers:
</p
>
7730 <blockquote
><pre
>
7731 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7733 Dell Computer Corporation
1
7736 eserver xSeries
345 -[
8670M1X]-
1
7740 </pre
></blockquote
>
7742 <p
>The quality of the report depend on the quality of the DMI tables
7743 provided in each machine. Here there are Intel machines without model
7744 information listed with Intel as vendor and no model, and virtual Xen
7745 machines listed as [no-dmi-info]. One can add -l as a command line
7746 option to list the individual machines.
</p
>
7748 <p
>A larger list is
7749 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
7750 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
7751 provide the basic sitesummary report publicly. In their report there
7752 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
7753 their machines, and as sitesummary is available in both distributions,
7754 it is trivial to get all of them to report to the same central
7755 collector.
</p
>
7760 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
7761 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
7762 <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>
7763 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
7764 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
7765 start at boot when an NVidia video card is used is handled. The
7766 problem seem to be that the nvidia X.org driver uses a long time to
7767 initialize, and this duration is longer than kdm is configured to
7770 <p
>I came across two bugs related to this issue,
7771 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
7772 against initscripts and passed on to nvidia-glx when it became obvious
7773 that the nvidia drivers were involved, and
7774 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
7775 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
7777 <p
>To me, it seem that no-one is interested in actually solving the
7778 problem nvidia video card owners experience and make sure the Debian
7779 distribution work out of the box for these users. The nvidia driver
7780 maintainers expect kdm to be set up to wait longer, while kdm expect
7781 the nvidia driver maintainers to fix the driver to start faster, and
7782 while they wait for each other I guess the users end up switching to a
7783 distribution that work for them. I have no idea what the solution is,
7784 but I am pretty sure that waiting for each other is not it.
</p
>
7786 <p
>I wonder why we end up handling bugs this way.
</p
>
7791 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
7792 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
7793 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
7794 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
7795 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
7796 The feature seem to hold up pretty well, but three fairly serious
7797 issues are known and should be solved:
7801 <li
>The wicd package seen to
7802 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
7803 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
7804 parallel booting is enabled. No idea why, but the wicd maintainer
7805 seem to be on the case.
</li
>
7807 <li
>The nvidia X driver seem to
7808 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
7809 triggered more easily when parallel booting is in effect. The
7810 maintainer is on the case.
</li
>
7812 <li
>The sysv-rc package fail to properly enable dependency based boot
7813 sequencing (the shutdown is broken) when old file-rc users
7814 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
7815 sysv-rc. One way to solve it would be for file-rc to create
7816 /etc/init.d/.legacy-bootordering, and another is to try to make
7817 sysv-rc more robust. Will investigate some more and probably upload a
7818 workaround in sysv-rc to help those trying to move from file-rc to
7819 sysv-rc get a working shutdown.
</li
>
7821 </ul
></p
>
7823 <p
>All in all not many surprising issues, and all of them seem
7824 solvable before Squeeze is released. In addition to these there are
7825 some packages with bugs in their dependencies and run level settings,
7826 which I expect will be fixed in a reasonable time span.
</p
>
7828 <p
>If you report any problems with dependencies in init.d scripts to
7829 the BTS, please usertag the report to get it to show up at
7830 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7831 list of usertagged bugs related to this
</a
>.
</p
>
7833 <p
>Update: Correct bug number to file-rc issue.
</p
>
7838 <title>More flexible firmware handling in debian-installer
</title>
7839 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
7840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
7841 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
7842 <description><p
>After a long break from debian-installer development, I finally
7843 found time today to return to the project. Having to spend less time
7844 working dependency based boot in debian, as it is almost complete now,
7845 definitely helped freeing some time.
</p
>
7847 <p
>A while back, I ran into a problem while working on Debian Edu. We
7848 include some firmware packages on the Debian Edu CDs, those needed to
7849 get disk and network controllers working. Without having these
7850 firmware packages available during installation, it is impossible to
7851 install Debian Edu on the given machine, and because our target group
7852 are non-technical people, asking them to provide firmware packages on
7853 an external medium is a support pain. Initially, I expected it to be
7854 enough to include the firmware packages on the CD to get
7855 debian-installer to find and use them. This proved to be wrong.
7856 Next, I hoped it was enough to symlink the relevant firmware packages
7857 to some useful location on the CD (tried /cdrom/ and
7858 /cdrom/firmware/). This also proved to not work, and at this point I
7859 found time to look at the debian-installer code to figure out what was
7860 going to work.
</p
>
7862 <p
>The firmware loading code is in the hw-detect package, and a closer
7863 look revealed that it would only look for firmware packages outside
7864 the installation media, so the CD was never checked for firmware
7865 packages. It would only check USB sticks, floppies and other
7866 "external
" media devices. Today I changed it to also look in the
7867 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7868 solve the problem I ran into with Debian edu. I also changed it to
7869 look in /firmware/, to make sure the installer also find firmware
7870 provided in the initrd when booting the installer via PXE, to allow us
7871 to provide the same feature in the PXE setup included in Debian
7874 <p
>To make sure firmware deb packages with a license questions are not
7875 activated without asking if the license is accepted, I extended
7876 hw-detect to look for preinst scripts in the firmware packages, and
7877 run these before activating the firmware during installation. The
7878 license question is asked using debconf in the preinst, so this should
7879 solve the issue for the firmware packages I have looked at so far.
</p
>
7881 <p
>If you want to discuss the details of these features, please
7882 contact us on debian-boot@lists.debian.org.
</p
>
7887 <title>Parallellized boot is now the default in Debian/unstable
</title>
7888 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
7889 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
7890 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
7891 <description><p
>Since this evening, parallel booting is the default in
7892 Debian/unstable for machines using dependency based boot sequencing.
7893 Apparently the testing of concurrent booting has been wider than
7894 expected, if I am to believe the
7895 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7896 on debian-devel@
</a
>, and I concluded a few days ago to move forward
7897 with the feature this weekend, to give us some time to detect any
7898 remaining problems before Squeeze is frozen. If serious problems are
7899 detected, it is simple to change the default back to sequential boot.
7900 The upload of the new sysvinit package also activate a new upstream
7903 More information about
7904 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7905 based boot sequencing
</a
> is available from the Debian wiki. It is
7906 currently possible to disable parallel booting when one run into
7907 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
7909 <blockquote
><pre
>
7911 </pre
></blockquote
>
7913 <p
>If you report any problems with dependencies in init.d scripts to
7914 the BTS, please usertag the report to get it to show up at
7915 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7916 list of usertagged bugs related to this
</a
>.
</p
>
7921 <title>Sitesummary tip: Listing MAC address of all clients
</title>
7922 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
7923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
7924 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
7925 <description><p
>In the recent Debian Edu versions, the
7926 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
7927 system
</a
> is used to keep track of the machines in the school
7928 network. Each machine will automatically report its status to the
7929 central server after boot and once per night. The network setup is
7930 also reported, and using this information it is possible to get the
7931 MAC address of all network interfaces in the machines. This is useful
7932 to update the DHCP configuration.
</p
>
7934 <p
>To give some idea how to use sitesummary, here is a one-liner to
7935 ist all MAC addresses of all machines reporting to sitesummary. Run
7936 this on the collector host:
</p
>
7938 <blockquote
><pre
>
7939 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
7940 </pre
></blockquote
>
7942 <p
>This will list all MAC addresses assosiated with all machine, one
7943 line per machine and with space between the MAC addresses.
</p
>
7945 <p
>To allow system administrators easier job at adding static DHCP
7946 addresses for hosts, it would be possible to extend this to fetch
7947 machine information from sitesummary and update the DHCP and DNS
7948 tables in LDAP using this information. Such tool is unfortunately not
7949 written yet.
</p
>
7954 <title>systemd, an interesting alternative to upstart
</title>
7955 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
7956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
7957 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
7958 <description><p
>The last few days a new boot system called
7959 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
7961 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
7963 to the free software world. I have not yet had time to play around
7964 with it, but it seem to be a very interesting alternative to
7965 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
7966 a good alternative for Debian when we are able to switch to an event
7967 based boot system. Tollef is
7968 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
7969 systemd into Debian, and I look forward to seeing how well it work. I
7970 like the fact that systemd handles init.d scripts with dependency
7971 information natively, allowing them to run in parallel where upstart
7972 at the moment do not.
</p
>
7974 <p
>Unfortunately do systemd have the same problem as upstart regarding
7975 platform support. It only work on recent Linux kernels, and also need
7976 some new kernel features enabled to function properly. This means
7977 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7978 system. Not sure how that will be handled if systemd proves to be the
7979 way forward.
</p
>
7981 <p
>In the mean time, based on the
7982 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7983 on debian-devel@
</a
> regarding parallel booting in Debian, I have
7984 decided to enable full parallel booting as the default in Debian as
7985 soon as possible (probably this weekend or early next week), to see if
7986 there are any remaining serious bugs in the init.d dependencies. A
7987 new version of the sysvinit package implementing this change is
7988 already in experimental. If all go well, Squeeze will be released
7989 with parallel booting enabled by default.
</p
>
7994 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
7995 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
7996 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
7997 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
7998 <description><p
>These days, the init.d script dependencies in Squeeze are quite
7999 complete, so complete that it is actually possible to run all the
8000 init.d scripts in parallell based on these dependencies. If you want
8001 to test your Squeeze system, make sure
8002 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8003 based boot sequencing
</a
> is enabled, and add this line to
8004 /etc/default/rcS:
</p
>
8006 <blockquote
><pre
>
8007 CONCURRENCY=makefile
8008 </pre
></blockquote
>
8010 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8011 scripts in parallel using the dependency information stored in
8012 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8013 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8014 to try to start the kdm and gdm scripts as early as possible, and will
8015 start the facilities required by kdm or gdm as early as possible to
8016 make this happen.
</p
>
8018 <p
>Give it a try, and see if you like the result. If some services
8019 fail to start properly, it is most likely because they have incomplete
8020 init.d script dependencies in their startup script (or some of their
8021 dependent scripts have incomplete dependencies). Report bugs and get
8022 the package maintainers to fix it. :)
</p
>
8024 <p
>Running scripts in parallel could be the default in Debian when we
8025 manage to get the init.d script dependencies complete and correct. I
8026 expect we will get there in Squeeze+
1, if we get manage to test and
8027 fix the remaining issues.
</p
>
8029 <p
>If you report any problems with dependencies in init.d scripts to
8030 the BTS, please usertag the report to get it to show up at
8031 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8032 list of usertagged bugs related to this
</a
>.
</p
>
8037 <title>Debian has switched to dependency based boot sequencing
</title>
8038 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8040 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8041 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8042 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8043 have been migrated to using dependency based boot sequencing. This
8044 conclude work me and others have been doing for the last three days.
8045 It feels great to see this finally part of the default Debian
8046 installation. Now we just need to weed out the last few problems that
8047 are bound to show up, to get everything ready for Squeeze.
</p
>
8049 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8050 fixing the more fundamental problem of handing the event based
8051 non-predictable kernel in the early boot.
</p
>
8056 <title>Taking over sysvinit development
</title>
8057 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8058 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8059 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8060 <description><p
>After several years of frustration with the lack of activity from
8061 the existing sysvinit upstream developer, I decided a few weeks ago to
8062 take over the package and become the new upstream. The number of
8063 patches to track for the Debian package was becoming a burden, and the
8064 lack of synchronization between the distribution made it hard to keep
8065 the package up to date.
</p
>
8067 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8068 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8069 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8070 and Fedora), based on the patches currently in use in these
8071 distributions. We Debian maintainers plan to move to this tarball as
8072 the new upstream as soon as we find time to do the merge. Since the
8073 new tarball was created, we agreed with Werner at SuSe to make a new
8074 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8075 development there. The project is registered and currently waiting
8076 for approval by the Savannah administrators, and as soon as it is
8077 approved, we will import the old versions from svn and continue
8078 working on the future release.
</p
>
8080 <p
>It is a bit ironic that this is done now, when some of the involved
8081 distributions are moving to upstart as a syvinit replacement.
</p
>
8086 <title>Debian boots quicker and quicker
</title>
8087 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8088 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8089 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8090 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8091 people involved in the boot system on Debian and Ubuntu, to see if we
8092 could find more ways to speed up the boot system. This was an Ubuntu
8094 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8095 gathering
</a
>. It was quite productive. We also discussed the future
8096 of boot systems, and ways to handle the increasing number of boot
8097 issues introduced by the Linux kernel becoming more and more
8098 asynchronous and event base. The Ubuntu approach using udev and
8099 upstart might be a good way forward. Time will show.
</p
>
8101 <p
>Anyway, there are a few ways at the moment to speed up the boot
8102 process in Debian. All of these should be applied to get a quick
8107 <li
>Use dash as /bin/sh.
</li
>
8109 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8110 clock is in UTC.
</li
>
8112 <li
>Install and activate the insserv package to enable
8113 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8114 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8118 These points are based on the Google summer of code work done by
8119 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8122 <p
>Support for makefile-style concurrency during boot was uploaded to
8123 unstable yesterday. When we tested it, we were able to cut
6 seconds
8124 from the boot sequence. It depend on very correct dependency
8125 declaration in all init.d scripts, so I expect us to find edge cases
8126 where the dependences in some scripts are slightly wrong when we start
8127 using this.
</p
>
8129 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8130 introduced by Raphael Geissert today, one that could affect the
8131 startup speed as well. Instead of starting some scripts concurrently
8132 from rcS.d/ and another set of scripts from rc2.d/, it would be
8133 possible to run a of them in the same process. A quick way to test
8134 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8135 insserv
'. Will need to test if that work. :)
</p
>
8140 <title>BSAs påstander om piratkopiering møter motstand
</title>
8141 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8143 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8144 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8145 programvareselskapene som Microsoft og Apple, publisert en rapport der
8146 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8147 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8149 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8150 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8151 dagene. Et spesielt interessant kommentar fra Sverige,
8152 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8153 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8156 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8157 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8158 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8159 exakta
", säger BSAs Sverigechef John Hugosson.
8162 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
8163 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
8164 piracy figures need a shot of reality
</a
> og
<a
8165 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
8166 Copyright Treaty Work?
</a
></p
>
8168 <p
>Fant lenkene via
<a
8169 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
8170 på Slashdot
</a
>.
</p
>
8175 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
8176 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
8177 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
8178 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
8179 <description><p
>Kom over
8180 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
8181 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8182 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8183 jobber til daglig. En rask opptelling forteller meg at vi har
490
8184 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
8185 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
8186 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
8191 <title>Kryptert harddisk - naturligvis
</title>
8192 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
8193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
8194 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
8195 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
8196 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
8197 når en tar tap av arbeidstid, fortrolige dokumenter,
8198 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8199 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8200 til at jeg har kryptert harddisken på både kontormaskinen og min
8201 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8202 komme på avveie, den første informasjon relatert til jobben min ved
8203 Universitetet i Oslo, og den andre relatert til blant annet
8204 foreningsarbeide. Kryptering av diskene gjør at det er lite
8205 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8206 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8207 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8208 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8209 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8210 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8211 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8212 det er gjort slik jeg gjør det er minimale, og gevinstene er
8213 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8214 maskinen reinstalleres og alt er tapt.
</p
>
8216 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8217 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8218 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8219 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8220 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8221 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8222 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8223 betydelige.
</p
>
8228 <title>Two projects that have improved the quality of free software a lot
</title>
8229 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
8230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
8231 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
8232 <description><p
>There are two software projects that have had huge influence on the
8233 quality of free software, and I wanted to mention both in case someone
8234 do not yet know them.
</p
>
8236 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
8237 tool to detect and expose errors in the memory handling of programs.
8238 It is easy to use, all one need to do is to run
'valgrind program
',
8239 and it will report any problems on stdout. It is even better if the
8240 program include debug information. With debug information, it is able
8241 to report the source file name and line number where the problem
8242 occurs. It can report things like
'reading past memory block in file
8243 X line N, the memory block was allocated in file Y, line M
', and
8244 'using uninitialised value in control logic
'. This tool has made it
8245 trivial to investigate reproducible crash bugs in programs, and have
8246 reduced the number of this kind of bugs in free software a lot.
8248 <p
>The second one is
8249 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
8250 a source code checker. It is able to process the source of a program
8251 and find problems in the logic without running the program. It
8252 started out as the Stanford Checker and became well known when it was
8253 used to find bugs in the Linux kernel. It is now a commercial tool
8254 and the company behind it is running
8255 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
8256 free software community, where a lot of free software projects get
8257 their source checked for free. Several thousand defects have been
8258 found and fixed so far. It can find errors like
'lock L taken in file
8259 X line N is never released if exiting in line M
', or
'the code in file
8260 Y lines O to P can never be executed
'. The projects included in the
8261 community service project have managed to get rid of a lot of
8262 reliability problems thanks to Coverity.
</p
>
8264 <p
>I believe tools like this, that are able to automatically find
8265 errors in the source, are vital to improve the quality of software and
8266 make sure we can get rid of the crashing and failing software we are
8267 surrounded by today.
</p
>
8272 <title>No patch is not better than a useless patch
</title>
8273 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
8274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
8275 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
8276 <description><p
>Julien Blache
8277 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
8278 patch is better than a useless patch
</a
>. I completely disagree, as a
8279 patch allow one to discuss a concrete and proposed solution, and also
8280 prove that the issue at hand is important enough for someone to spent
8281 time on fixing it. No patch do not provide any of these positive
8282 properties.
</p
>
8287 <title>Standardize on protocols and formats, not vendors and applications
</title>
8288 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8290 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8291 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8292 very good one to form a long lived computer infrastructure. It is the
8293 simple one, lost by many in todays computer industry: Standardize on
8294 open network protocols and open exchange/storage formats, not applications.
8295 Applications come and go, while protocols and files tend to stay, and
8296 thus one want to make it easy to change application and vendor, while
8297 avoiding conversion costs and locking users to a specific platform or
8298 application.
</p
>
8300 <p
>This approach make it possible to replace the client applications
8301 independently of the server applications. One can even allow users to
8302 use several different applications as long as they handle the selected
8303 protocol and format. In the normal case, only one client application
8304 is recommended and users only get help if they choose to use this
8305 application, but those that want to deviate from the easy path are not
8306 blocked from doing so.
</p
>
8308 <p
>It also allow us to replace the server side without forcing the
8309 users to replace their applications, and thus allow us to select the
8310 best server implementation at any moment, when scale and resouce
8311 requirements change.
</p
>
8313 <p
>I strongly recommend standardizing - on open network protocols and
8314 open formats, but I would never recommend standardizing on a single
8315 application that do not use open network protocol or open formats.
</p
>
8320 <title>Returning from Skolelinux developer gathering
</title>
8321 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8322 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8323 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8324 <description><p
>I
'm sitting on the train going home from this weekends Debian
8325 Edu/Skolelinux development gathering. I got a bit done tuning the
8326 desktop, and looked into the dynamic service location protocol
8327 implementation avahi. It look like it could be useful for us. Almost
8328 30 people participated, and I believe it was a great environment to
8329 get to know the Skolelinux system. Walter Bender, involved in the
8330 development of the Sugar educational platform, presented his stuff and
8331 also helped me improve my OLPC installation. He also showed me that
8332 his Turtle Art application can be used in standalone mode, and we
8333 agreed that I would help getting it packaged for Debian. As a
8334 standalone application it would be great for Debian Edu. We also
8335 tried to get the video conferencing working with two OLPCs, but that
8336 proved to be too hard for us. The application seem to need more work
8337 before it is ready for me. I look forward to getting home and relax
8343 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8344 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8345 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8346 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8347 <description><p
>The state of standardized LDAP schemas on Linux is far from
8348 optimal. There is RFC
2307 documenting one way to store NIS maps in
8349 LDAP, and a modified version of this normally called RFC
2307bis, with
8350 some modifications to be compatible with Active Directory. The RFC
8351 specification handle the content of a lot of system databases, but do
8352 not handle DNS zones and DHCP configuration.
</p
>
8354 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
8355 we would like to store information about users, SMB clients/hosts,
8356 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8357 and LTSP configuration in LDAP. These objects have a lot in common,
8358 but with the current LDAP schemas it is not possible to have one
8359 object per entity. For example, one need to have at least three LDAP
8360 objects for a given computer, one with the SMB related stuff, one with
8361 DNS information and another with DHCP information. The schemas
8362 provided for DNS and DHCP are impossible to combine into one LDAP
8363 object. In addition, it is impossible to implement quick queries for
8364 netgroup membership, because of the way NIS triples are implemented.
8365 It just do not scale. I believe it is time for a few RFC
8366 specifications to cleam up this mess.
</p
>
8368 <p
>I would like to have one LDAP object representing each computer in
8369 the network, and this object can then keep the SMB (ie host key), DHCP
8370 (mac address/name) and DNS (name/IP address) settings in one place.
8371 It need to be efficently stored to make sure it scale well.
</p
>
8373 <p
>I would also like to have a quick way to map from a user or
8374 computer and to the net group this user or computer is a member.
</p
>
8376 <p
>Active Directory have done a better job than unix heads like myself
8377 in this regard, and the unix side need to catch up. Time to start a
8378 new IETF work group?
</p
>
8383 <title>Endelig er Debian Lenny gitt ut
</title>
8384 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
8385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
8386 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
8387 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
8388 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
8389 Et langt steg videre for Debian-prosjektet, og en rekke nye
8390 programpakker blir nå tilgjengelig for de av oss som bruker den
8391 stabile utgaven av Debian. Neste steg er nå å få
8392 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
8393 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
8394 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8395 slippes løs på skolene. Takk til alle debian-utviklerne som har
8396 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8397 bootsekvens tilgjengelig i stabil utgave, vha pakken
8398 <tt
>insserv
</tt
>.
</p
>
8403 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
8404 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
8405 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
8406 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
8407 <description><p
>This weekend we had a small developer gathering for Debian Edu in
8408 Oslo. Most of Saturday was used for the general assemly for the
8409 member organization, but the rest of the weekend I used to tune the
8410 LTSP installation. LTSP now work out of the box on the
10-network.
8411 Acer Aspire One proved to be a very nice thin client, with both
8412 screen, mouse and keybard in a small box. Was working on getting the
8413 diskless workstation setup configured out of the box, but did not
8414 finish it before the weekend was up.
</p
>
8416 <p
>Did not find time to look at the
4 VGA cards in one box we got from
8417 the Brazilian group, so that will have to wait for the next
8418 development gathering. Would love to have the Debian Edu installer
8419 automatically detect and configure a multiseat setup when it find one
8420 of these cards.
</p
>
8425 <title>The sorry state of multimedia browser plugins in Debian
</title>
8426 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
8427 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
8428 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
8429 <description><p
>Recently I have spent some time evaluating the multimedia browser
8430 plugins available in Debian Lenny, to see which one we should use by
8431 default in Debian Edu. We need an embedded video playing plugin with
8432 control buttons to pause or stop the video, and capable of streaming
8433 all the multimedia content available on the web. The test results and
8434 notes are available on
8435 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
8436 Debian wiki
</a
>. I was surprised how few of the plugins are able to
8437 fill this need. My personal video player favorite, VLC, has a really
8438 bad plugin which fail on a lot of the test pages. A lot of the MIME
8439 types I would expect to work with any free software player (like
8440 video/ogg), just do not work. And simple formats like the
8441 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
8442 totem and vlc plugins. I hope the situation will improve soon. No
8443 wonder sites use the proprietary Adobe flash to play video.
</p
>
8445 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
8446 be the only one fitting our needs. :/
</p
>