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>Experience and updated recipe for Using the Signal app without a mobile phone
</title>
11 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_Using_the_Signal_app_without_a_mobile_phone.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_Using_the_Signal_app_without_a_mobile_phone.html
</guid>
13 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
14 <description><p
>In July
15 <a href=
"http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
16 wrote how to get the Signal Chrome/Chromium app working
</a
> without
17 the ability to receive SMS messages (aka without a cell phone). It is
18 time to share some experiences and provide an updated setup.
</p
>
20 <p
>The Signal app have worked fine for several months now, and I use
21 it regularly to chat with my loved ones. I had a major snag at the
22 end of my summer vacation, when the the app completely forgot my
23 setup, identify and keys. The reason behind this major mess was
24 running out of disk space. To avoid that ever happening again I have
25 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
26 roll back to an earlier version if the files are wiped by mistake. I
27 had to use it once after introducing the git backup. When rolling
28 back to an earlier version, one need to use the
'reset session
' option
29 in Signal to get going, and notify the people you talk with about the
30 problem. I assume there is some sequence number tracking in the
31 protocol to detect rollback attacks. The git repository is rather big
32 (
674 MiB so far), but I have not tried to figure out if some of the
33 content can be added to a .gitignore file due to lack of spare
36 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
37 make it impossible to send messages using Signal. I could still
38 receive them, but had to patch the code with a new timestamp to send.
39 I believe the timeout is added by the developers to force people to
40 upgrade to the latest version of the app, even when there is no
41 protocol changes, to reduce the version skew among the user base and
42 thus try to keep the number of support requests down.
</p
>
44 <p
>Since my original recipe, the Signal source code changed slightly,
45 making the old patch fail to apply cleanly. Below is an updated
46 patch, including the shell wrapper I use to start Signal. The
47 original version required a new user to locate the JavaScript console
48 and call a function from there. I got help from a friend with more
49 JavaScript knowledge than me to modify the code to provide a GUI
50 button instead. This mean that to get started you just need to run
51 the wrapper and click the
'Register without mobile phone
' to get going
52 now. I
've also modified the timeout code to always set it to
90 days
53 in the future, to avoid having to patch the code regularly.
</p
>
55 <p
>So, the updated recipe for Debian Jessie:
</p
>
59 <li
>First, install required packages to get the source code and the
60 browser you need. Signal only work with Chrome/Chromium, as far as I
61 know, so you need to install it.
64 apt install git tor chromium
65 git clone https://github.com/WhisperSystems/Signal-Desktop.git
66 </pre
></li
>
68 <li
>Modify the source code using command listed in the the patch
69 block below.
</li
>
71 <li
>Start Signal using the run-signal-app wrapper (for example using
72 <tt
>`pwd`/run-signal-app
</tt
>).
74 <li
>Click on the
'Register without mobile phone
', will in a phone
75 number you can receive calls to the next minute, receive the
76 verification code and enter it into the form field and press
77 'Register
'. Note, the phone number you use will be user Signal
78 username, ie the way others can find you on Signal.
</li
>
80 <li
>You can now use Signal to contact others. Note, new contacts do
81 not show up in the contact list until you restart Signal, and there is
82 no way to assign names to Contacts. There is also no way to create or
83 update chat groups. I suspect this is because the web app do not have
84 a associated contact database.
</li
>
88 <p
>I am still a bit uneasy about using Signal, because of the way its
89 main author moxie0 reject federation and accept dependencies to major
90 corporations like Google (part of the code is fetched from Google) and
91 Amazon (the central coordination point is owned by Amazon). See for
93 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
94 LibreSignal issue tracker
</a
> for a thread documenting the authors
95 view on these issues. But the network effect is strong in this case,
96 and several of the people I want to communicate with already use
97 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
98 once it
<a href=
"https://bugs.debian.org/
830265">work on my
99 laptop
</a
>? It already work on Windows and Android, and is included
100 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
101 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
102 working on Debian Stable.
</p
>
104 <p
>Anyway, this is the patch I apply to the Signal code to get it
105 working. It switch to the production servers, disable to timeout,
106 make registration easier and add the shell wrapper:
</p
>
109 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
110 diff --git a/js/background.js b/js/background.js
111 index
24b4c1d.
.579345f
100644
112 --- a/js/background.js
113 +++ b/js/background.js
118 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
119 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
120 var SERVER_PORTS = [
80,
4433,
8443];
121 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
122 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
124 window.getSocketStatus = function() {
125 if (messageReceiver) {
126 diff --git a/js/expire.js b/js/expire.js
127 index
639aeae..beb91c3
100644
132 'use strict
';
133 - var BUILD_EXPIRATION =
0;
134 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
136 window.extension = window.extension || {};
138 diff --git a/js/views/install_view.js b/js/views/install_view.js
139 index
7816f4f.
.1d6233b
100644
140 --- a/js/views/install_view.js
141 +++ b/js/views/install_view.js
144 'click .step1
': this.selectStep.bind(this,
1),
145 'click .step2
': this.selectStep.bind(this,
2),
146 -
'click .step3
': this.selectStep.bind(this,
3)
147 +
'click .step3
': this.selectStep.bind(this,
3),
148 +
'click .callreg
': function() { extension.install(
'standalone
') },
151 clearQR: function() {
152 diff --git a/options.html b/options.html
153 index dc0f28e.
.8d709f6
100644
157 &lt;div class=
'nav
'>
158 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
159 &lt;p
>{{ installTagline }}
&lt;/p
>
160 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
161 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
162 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
165 &lt;span class=
'dot step1 selected
'>&lt;/span
>
166 &lt;span class=
'dot step2
'>&lt;/span
>
167 &lt;span class=
'dot step3
'>&lt;/span
>
168 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
169 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
175 +userdata=
"`pwd`/userdata
"
176 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
177 + (cd $userdata
&& git init)
179 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
181 + --proxy-server=
"socks://localhost:
9050" \
182 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
184 chmod a+rx run-signal-app
187 <p
>As usual, if you use Bitcoin and want to show your support of my
188 activities, please send Bitcoin donations to my address
189 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
194 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
195 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
197 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
198 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
199 system
</a
> provide a practical and easy way to figure out which
200 packages support the hardware in a given machine. The command line
201 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
202 convenient way to list and install packages relevant for the current
203 hardware during system installation, both user space packages and
204 firmware packages. The GUI background daemon on the other hand provide
205 a pop-up proposing to install packages when a new dongle is inserted
206 while using the computer. For example, if you plug in a smart card
207 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
208 that package isn
't already installed, and if you plug in a USB video
209 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
210 cheese is currently missing. This already work just fine.
</p
>
212 <p
>But Isenkram depend on a database mapping from hardware IDs to
213 package names. When I started no such database existed in Debian, so
214 I made my own data set and included it with the isenkram package and
215 made isenkram fetch the latest version of this database from git using
216 http. This way the isenkram users would get updated package proposals
217 as soon as I learned more about hardware related packages.
</p
>
219 <p
>The hardware is identified using modalias strings. The modalias
220 design is from the Linux kernel where most hardware descriptors are
221 made available as a strings that can be matched using filename style
222 globbing. It handle USB, PCI, DMI and a lot of other hardware related
223 identifiers.
</p
>
225 <p
>The downside to the Isenkram specific database is that there is no
226 information about relevant distribution / Debian version, making
227 isenkram propose obsolete packages too. But along came AppStream, a
228 cross distribution mechanism to store and collect metadata about
229 software packages. When I heard about the proposal, I contacted the
230 people involved and suggested to add a hardware matching rule using
231 modalias strings in the specification, to be able to use AppStream for
232 mapping hardware to packages. This idea was accepted and AppStream is
233 now a great way for a package to announce the hardware it support in a
234 distribution neutral way. I wrote
235 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
236 recipe on how to add such meta-information
</a
> in a blog post last
237 December. If you have a hardware related package in Debian, please
238 announce the relevant hardware IDs using AppStream.
</p
>
240 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
241 RCX or NXT unit, announce this support using AppStream. The effect is
242 that when you insert such LEGO robot controller into your Debian
243 machine, Isenkram will propose to install the packages needed to get
244 it working. The intention is that this should allow the local user to
245 start programming his robot controller right away without having to
246 guess what packages to use or which permissions to fix.
</p
>
248 <p
>But when I sat down with my son the other day to program our NXT
249 unit using his Debian Stretch computer, I discovered something
250 annoying. The local console user (ie my son) did not get access to
251 the USB device for programming the unit. This used to work, but no
252 longer in Jessie and Stretch. After some investigation and asking
253 around on #debian-devel, I discovered that this was because udev had
254 changed the mechanism used to grant access to local devices. The
255 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
256 no longer applied, because LDAP users no longer was added to the
257 plugdev group during login. Michael Biebl told me that this method
258 was obsolete and the new method used ACLs instead. This was good
259 news, as the plugdev mechanism is a mess when using a remote user
260 directory like LDAP. Using ACLs would make sure a user lost device
261 access when she logged out, even if the user left behind a background
262 process which would retain the plugdev membership with the ConsoleKit
263 setup. Armed with this knowledge I moved on to fix the access problem
264 for the LEGO Mindstorms related packages.
</p
>
266 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
267 applied directly for a device, or is applied in
268 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
269 LEGO Mindstorms udev rules did not have a class, I decided to add the
270 tag directly in the udev rules files included in the packages. Here
271 is one example. For the nqc C compiler for the RCX, the
272 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
275 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
276 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
277 </pre
></p
>
279 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
280 packages using plugdev in their /lib/udev/rules.d/ files should be
281 changed to use this tag (either directly or indirectly via
282 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
283 to detect this?
</p
>
285 <p
>I
've been unable to find good documentation on the uaccess feature.
286 It is unclear to me if the uaccess tag is an internal implementation
287 detail like the udev-acl tag used by
288 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
289 indirect method is the preferred way. Michael
290 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
291 documentation from the systemd project
</a
> and I hope it will make
292 this clearer. For now I use the generic classes when they exist and
293 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
294 directly if no such class exist.
</p
>
296 <p
>To learn more about the isenkram system, please check out
297 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
298 blog posts tagged isenkram
</a
>.
</p
>
300 <p
>To help out making life for LEGO constructors in Debian easier,
301 please join us on our IRC channel
302 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
303 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
304 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
305 list is not yet created, but we are working on it. :)
</p
>
307 <p
>As usual, if you use Bitcoin and want to show your support of my
308 activities, please send Bitcoin donations to my address
309 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
314 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
315 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
316 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</guid>
317 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
318 <description><p
>In April we
319 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
320 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
321 how to set up and administrate a Debian system. Today I am happy to
322 report that the first draft is now publicly available. You can find
323 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
324 Administrator
's Handbook page
</a
> (under Other languages). The first
325 eight chapters have a first draft translation, and we are working on
326 proofreading the content. If you want to help out, please start
328 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
329 hosted weblate project page
</a
>, and get in touch using
330 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
331 translators mailing list
</a
>. Please also check out
332 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
333 contributors
</a
>. A good way to contribute is to proofread the text
334 and update weblate if you find errors.
</p
>
336 <p
>Our goal is still to make the Norwegian book available on paper as well as
337 electronic form.
</p
>
342 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
343 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
345 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
346 <description><p
>This summer, I read a great article
347 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
348 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
349 how to profile multi-threaded programs. It presented a system for
350 profiling software by running experiences in the running program,
351 testing how run time performance is affected by
"speeding up
" parts of
352 the code to various degrees compared to a normal run. It does this by
353 slowing down parallel threads while the
"faster up
" code is running
354 and measure how this affect processing time. The processing time is
355 measured using probes inserted into the code, either using progress
356 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
357 can also measure unmodified code by measuring complete the program
358 runtime and running the program several times instead.
</p
>
360 <p
>The project and presentation was so inspiring that I would like to
361 get the system into Debian. I
362 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
363 a WNPP request for it
</a
> and contacted upstream to try to make the
364 system ready for Debian by sending patches. The build process need to
365 be changed a bit to avoid running
'git clone
' to get dependencies, and
366 to include the JavaScript web page used to visualize the collected
367 profiling information included in the source package.
368 But I expect that should work out fairly soon.
</p
>
370 <p
>The way the system work is fairly simple. To run an coz experiment
371 on a binary with debug symbols available, start the program like this:
373 <p
><blockquote
><pre
>
374 coz run --- program-to-run
375 </pre
></blockquote
></p
>
377 <p
>This will create a text file profile.coz with the instrumentation
378 information. To show what part of the code affect the performance
379 most, use a web browser and either point it to
380 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
381 or use the copy from git (in the gh-pages branch). Check out this web
382 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
383 profiling more useful you include
&lt;coz.h
&gt; and insert the
384 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
385 code, rebuild and run the profiler. This allow coz to do more
386 targeted experiments.
</p
>
388 <p
>A video published by ACM
389 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
390 Coz profiler
</a
> is available from Youtube. There is also a paper
391 from the
25th Symposium on Operating Systems Principles available
393 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
394 finding code that counts with causal profiling
</a
>.
</p
>
396 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
397 for Coz is available from github. It will only build with clang
399 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
400 feature missing in GCC
</a
>, but I
've submitted
401 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
402 it
</a
> and hope it will be included in the upstream source soon.
</p
>
404 <p
>Please get in touch if you, like me, would like to see this piece
405 of software in Debian. I would very much like some help with the
406 packaging effort, as I lack the in depth knowledge on how to package
407 C++ libraries.
</p
>
412 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
413 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
414 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
415 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
416 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
417 to be a slight challenge. Here is the recipe if I ever need to do it
418 again. It all started by me wanting to try the recipe to set up
419 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
420 hardened Android installation
</a
> from the Tor project blog on a
421 device I had access to. It is a old mobile phone with a broken
422 microphone The initial idea had been to just
423 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
424 CyanogenMod on it
</a
>, but did not quite find time to start on it
425 until a few days ago.
</p
>
427 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
428 loader (press volume down and power at the same time), (
2) select
429 'fastboot
' before (
3) connecting the device via USB to a Linux
430 machine, (
4) request the device identifier token by running
'fastboot
431 oem get_identifier_token
', (
5) request the device unlocking key using
432 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
433 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
435 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
436 or newer, and the device I was working on had
2.00.0027. This
437 apparently can be easily fixed by downloading a Windows program and
438 running it on your Windows machine, if you accept the terms Microsoft
439 require you to accept to use Windows - which I do not. So I had to
440 come up with a different approach. I got a lot of help from AndyCap
441 on #nuug, and would not have been able to get this working without
444 <p
>First I needed to extract the hboot firmware from
445 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
446 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
447 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
448 project named unruu
</a
> using libunshield. The unshield tool did not
449 recognise the file format, but unruu worked and extracted rom.zip,
450 containing the new hboot firmware and a text file describing which
451 devices it would work for.
</p
>
453 <p
>Next, I needed to get the new firmware into the device. For this I
454 followed some instructions
455 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
456 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
457 machine with Debian testing:
</p
>
460 adb reboot-bootloader
461 fastboot oem rebootRUU
462 fastboot flash zip rom.zip
463 fastboot flash zip rom.zip
465 </pre
></p
>
467 <p
>The flash command apparently need to be done twice to take effect,
468 as the first is just preparations and the second one do the flashing.
469 The adb command is just to get to the boot loader menu, so turning the
470 device on while holding volume down and the power button should work
473 <p
>With the new hboot version in place I could start following the
474 instructions on the HTC developer web site. I got the device token
478 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
481 <p
>And once I got the unlock code via email, I could use it like
485 fastboot flash unlocktoken Unlock_code.bin
486 </pre
></p
>
488 <p
>And with that final step in place, the phone was unlocked and I
489 could start stuffing the software of my own choosing into the device.
490 So far I only inserted a replacement recovery image to wipe the phone
491 before I start. We will see what happen next. Perhaps I should
492 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
497 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
498 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
500 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
501 <description><p
>For a while now, I have wanted to test
502 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
503 said to provide end to end encrypted communication and several of my
504 friends and family are already using it. As I by choice do not own a
505 mobile phone, this proved to be harder than expected. And I wanted to
506 have the source of the client and know that it was the code used on my
507 machine. But yesterday I managed to get it working. I used the
508 Github source, compared it to the source in
509 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
510 Signal Chrome app
</a
> available from the Chrome web store, applied
511 patches to use the production Signal servers, started the app and
512 asked for the hidden
"register without a smart phone
" form. Here is
513 the recipe how I did it.
</p
>
515 <p
>First, I fetched the Signal desktop source from Github, using
518 git clone https://github.com/WhisperSystems/Signal-Desktop.git
521 <p
>Next, I patched the source to use the production servers, to be
522 able to talk to other Signal users:
</p
>
525 cat
&lt;
&lt;EOF | patch -p0
526 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
527 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
528 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
533 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
534 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
535 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
536 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
538 window.getSocketStatus = function() {
539 if (messageReceiver) {
540 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
541 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
542 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
545 'use strict
';
546 - var BUILD_EXPIRATION =
0;
547 + var BUILD_EXPIRATION =
1474492690000;
549 window.extension = window.extension || {};
554 <p
>The first part is changing the servers, and the second is updating
555 an expiration timestamp. This timestamp need to be updated regularly.
556 It is set
90 days in the future by the build process (Gruntfile.js).
557 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
559 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
560 script to launch Signal in Chromium.
</p
>
567 --proxy-server=
"socks://localhost:
9050" \
568 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
571 <p
> The script start the app and configure Chromium to use the Tor
572 SOCKS5 proxy to make sure those controlling the Signal servers (today
573 Amazon and Whisper Systems) as well as those listening on the lines
574 will have a harder time location my laptop based on the Signal
575 connections if they use source IP address.
</p
>
577 <p
>When the script starts, one need to follow the instructions under
578 "Standalone Registration
" in the CONTRIBUTING.md file in the git
579 repository. I right clicked on the Signal window to get up the
580 Chromium debugging tool, visited the
'Console
' tab and wrote
581 'extension.install(
"standalone
")
' on the console prompt to get the
582 registration form. Then I entered by land line phone number and
583 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
584 repeated the verification code three times. After entering the number
585 into the verification code field in the form, I could start using
586 Signal from my laptop.
588 <p
>As far as I can tell, The Signal app will leak who is talking to
589 whom and thus who know who to those controlling the central server,
590 but such leakage is hard to avoid with a centrally controlled server
591 setup. It is something to keep in mind when using Signal - the
592 content of your chats are harder to intercept, but the meta data
593 exposing your contact network is available to people you do not know.
594 So better than many options, but not great. And sadly the usage is
595 connected to my land line, thus allowing those controlling the server
596 to associate it to my home and person. I would prefer it if only
597 those I knew could tell who I was on Signal. There are options
598 avoiding such information leakage, but most of my friends are not
599 using them, so I am stuck with Signal for now.
</p
>
604 <title>The new
"best
" multimedia player in Debian?
</title>
605 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
606 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
607 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
608 <description><p
>When I set out a few weeks ago to figure out
609 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
610 multimedia player in Debian claimed to support most file formats /
611 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
612 the various players claimed support for. The range was from
55 to
130
613 MIME types. I suspect most media formats are supported by all
614 players, but this is not really reflected in the MimeTypes values in
615 their desktop files. There are probably also some bogus MIME types
616 listed, but it is hard to identify which one this is.
</p
>
618 <p
>Anyway, in the mean time I got in touch with upstream for some of
619 the players suggesting to add more MIME types to their desktop files,
620 and decided to spend some time myself improving the situation for my
621 favorite media player VLC. The fixes for VLC entered Debian unstable
622 yesterday. The complete list of MIME types can be seen on the
623 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
624 player MIME type support status
</a
> Debian wiki page.
</p
>
626 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
627 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
628 kmplayer. I am sure some of the other players desktop files support
629 several of the formats currently listed as working only with vlc,
630 toten and parole.
</p
>
632 <p
>A sad observation is that only
14 MIME types are listed as
633 supported by all the tested multimedia players in Debian in their
634 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
635 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
636 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
637 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
638 it sad that video/ogg and video/webm is not supported by all the media
639 players in Debian. As far as I can tell, all of them can handle both
645 <title>A program should be able to open its own files on Linux
</title>
646 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
647 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
648 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
649 <description><p
>Many years ago, when koffice was fresh and with few users, I
650 decided to test its presentation tool when making the slides for a
651 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
652 wrote the first draft of the slides, saved the result and went to bed
653 the day before I would give the talk. The next day I took a plane to
654 the location where the meeting should take place, and on the plane I
655 started up koffice again to polish the talk a bit, only to discover
656 that kpresenter refused to load its own data file. I cursed a bit and
657 started making the slides again from memory, to have something to
658 present when I arrived. I tested that the saved files could be
659 loaded, and the day seemed to be rescued. I continued to polish the
660 slides until I suddenly discovered that the saved file could no longer
661 be loaded into kpresenter. In the end I had to rewrite the slides
662 three times, condensing the content until the talk became shorter and
663 shorter. After the talk I was able to pinpoint the problem
&ndash;
664 kpresenter wrote inline images in a way itself could not understand.
665 Eventually that bug was fixed and kpresenter ended up being a great
666 program to make slides. The point I
'm trying to make is that we
667 expect a program to be able to load its own data files, and it is
668 embarrassing to its developers if it can
't.
</p
>
670 <p
>Did you ever experience a program failing to load its own data
671 files from the desktop file browser? It is not a uncommon problem. A
672 while back I discovered that the screencast recorder
673 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
674 browser would refuse to open. No video player claimed to understand
675 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
676 returning the application/ogg MIME type, which no video player I had
677 installed listed as a MIME type they would understand. I asked for
678 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
679 behavour
</a
> and use the MIME type video/ogg instead. I also asked
680 several video players to add video/ogg to their desktop files, to give
681 the file browser an idea what to do about Ogg Theora files. After a
682 while, the desktop file browsers in Debian started to handle the
683 output from gtk-recordmydesktop properly.
</p
>
685 <p
>But history repeats itself. A few days ago I tested the music
686 system Rosegarden again, and I discovered that the KDE and xfce file
687 browsers did not know what to do with the Rosegarden project files
688 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
689 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
690 included in the next upload. To increase the chance of me remembering
691 how to fix the problem next time some program fail to load its files
692 from the file browser, here are some notes on how to fix it.
</p
>
694 <p
>The file browsers in Debian in general operates on MIME types.
695 There are two sources for the MIME type of a given file. The output from
696 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
697 shared MIME type registry (under /usr/share/mime/). The file MIME
698 type is mapped to programs supporting the MIME type, and this
699 information is collected from
700 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
701 desktop files
</a
> available in /usr/share/applications/. If there is
702 one desktop file claiming support for the MIME type of the file, it is
703 activated when asking to open a given file. If there are more, one
704 can normally select which one to use by right-clicking on the file and
705 selecting the wanted one using
'Open with
' or similar. In general
706 this work well. But it depend on each program picking a good MIME
708 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
709 MIME type registered with IANA
</a
>), file and/or the shared MIME
710 registry recognizing the file and the desktop file to list the MIME
711 type in its list of supported MIME types.
</p
>
713 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
714 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
715 Shared MIME database
</a
> look like this:
</p
>
717 <p
><blockquote
><pre
>
718 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
719 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
720 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
721 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
722 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
723 &lt;glob pattern=
"*.rg
"/
&gt;
724 &lt;/mime-type
&gt;
725 &lt;/mime-info
&gt;
726 </pre
></blockquote
></p
>
728 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
729 (it is a gzipped XML file). Note, it is much better to use an
730 official MIME type registered with IANA than it is to make up ones own
731 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
733 <p
>The desktop file of the rosegarden program failed to list
734 audio/x-rosegarden in its list of supported MIME types, causing the
735 file browsers to have no idea what to do with *.rg files:
</p
>
737 <p
><blockquote
><pre
>
738 % grep Mime /usr/share/applications/rosegarden.desktop
739 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
740 X-KDE-NativeMimeType=audio/x-rosegarden-composition
742 </pre
></blockquote
></p
>
744 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
745 MimeType= line.
</p
>
747 <p
>If you run into a file which fail to open the correct program when
748 selected from the file browser, please check out the output from
749 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
750 MIME type is registered somewhere under /usr/share/mime/ and check
751 that some desktop file under /usr/share/applications/ is claiming
752 support for this MIME type. If not, please report a bug to have it
758 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
759 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
760 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
761 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
762 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
763 system
</a
> is a user-focused solution in Debian for handling hardware
764 related packages. The idea is to have a database of mappings between
765 hardware and packages, and pop up a dialog suggesting for the user to
766 install the packages to use a given hardware dongle. Some use cases
767 are when you insert a Yubikey, it proposes to install the software
768 needed to control it; when you insert a braille reader list it
769 proposes to install the packages needed to send text to the reader;
770 and when you insert a ColorHug screen calibrator it suggests to
771 install the driver for it. The system work well, and even have a few
772 command line tools to install firmware packages and packages for the
773 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
775 <p
>The system was initially written using aptdaemon, because I found
776 good documentation and example code on how to use it. But aptdaemon
777 is going away and is generally being replaced by
778 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
779 so Isenkram needed a rewrite. And today, thanks to the great patch
780 from my college Sunil Mohan Adapa in the FreedomBox project, the
781 rewrite finally took place. I
've just uploaded a new version of
782 Isenkram into Debian Unstable with the patch included, and the default
783 for the background daemon is now to use PackageKit. To check it out,
784 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
785 and see if it is recognised.
</p
>
787 <p
>If you want to know what kind of packages isenkram would propose for
788 the machine it is running on, you can check out the isenkram-lookup
789 program. This is what it look like on a Thinkpad X230:
</p
>
791 <p
><blockquote
><pre
>
807 </pre
></blockquote
></p
>
809 <p
>The hardware mappings come from several places. The preferred way
810 is for packages to announce their hardware support using
811 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
812 cross distribution appstream system
</a
>.
814 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
815 blog posts about isenkram
</a
> to learn how to do that.
</p
>
820 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
821 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
823 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
824 <description><p
>Yesterday I updated the
825 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
826 package in Debian
</a
> with a few patches sent to me by skilled and
827 enterprising users. There were some nice user and visible changes.
828 First of all, both desktop menu entries now work. A design flaw in
829 one of the script made the history graph fail to show up (its PNG was
830 dumped in ~/.xsession-errors) if no controlling TTY was available.
831 The script worked when called from the command line, but not when
832 called from the desktop menu. I changed this to look for a DISPLAY
833 variable or a TTY before deciding where to draw the graph, and now the
834 graph window pop up as expected.
</p
>
836 <p
>The next new feature is a discharge rate estimator in one of the
837 graphs (the one showing the last few hours). New is also the user of
838 colours showing charging in blue and discharge in red. The percentages
839 of this graph is relative to last full charge, not battery design
842 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
844 <p
>The other graph show the entire history of the collected battery
845 statistics, comparing it to the design capacity of the battery to
846 visualise how the battery life time get shorter over time. The red
847 line in this graph is what the previous graph considers
100 percent:
849 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
851 <p
>In this graph you can see that I only charge the battery to
80
852 percent of last full capacity, and how the capacity of the battery is
853 shrinking. :(
</p
>
855 <p
>The last new feature is in the collector, which now will handle
856 more hardware models. On some hardware, Linux power supply
857 information is stored in /sys/class/power_supply/ACAD/, while the
858 collector previously only looked in /sys/class/power_supply/AC/. Now
859 both are checked to figure if there is power connected to the
862 <p
>If you are interested in how your laptop battery is doing, please
864 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
865 in Debian unstable, or rebuild it on Jessie to get it working on
866 Debian stable. :) The upstream source is available from
<a
867 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
868 Patches are very welcome.
</p
>
870 <p
>As usual, if you use Bitcoin and want to show your support of my
871 activities, please send Bitcoin donations to my address
872 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
877 <title>Debian now with ZFS on Linux included
</title>
878 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
879 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
880 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
881 <description><p
>Today, after many years of hard work from many people,
882 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
883 Debian. The package status can be seen on
884 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
885 for zfs-linux
</a
>. and
886 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
887 team status page
</a
>. If you want to help out, please join us.
888 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
889 source code
</a
> is available via git on Alioth. It would also be
890 great if you could help out with
891 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
892 it is an important piece of the puzzle to get ZFS working.
</p
>
897 <title>What is the best multimedia player in Debian?
</title>
898 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
900 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
901 <description><p
><strong
>Where I set out to figure out which multimedia player in
902 Debian claim support for most file formats.
</strong
></p
>
904 <p
>A few years ago, I had a look at the media support for Browser
905 plugins in Debian, to get an idea which plugins to include in Debian
906 Edu. I created a script to extract the set of supported MIME types
907 for each plugin, and used this to find out which multimedia browser
908 plugin supported most file formats / media types.
909 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
910 result
</a
> can still be seen on the Debian wiki, even though it have
911 not been updated for a while. But browser plugins are less relevant
912 these days, so I thought it was time to look at standalone
915 <p
>A few days ago I was tired of VLC not being listed as a viable
916 player when I wanted to play videos from the Norwegian National
917 Broadcasting Company, and decided to investigate why. The cause is a
918 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
919 desktop file
</a
>. In the process I wrote a script to compare the set
920 of MIME types announced in the desktop file and the browser plugin,
921 only to discover that there is quite a large difference between the
922 two for VLC. This discovery made me dig up the script I used to
923 compare browser plugins, and adjust it to compare desktop files
924 instead, to try to figure out which multimedia player in Debian
925 support most file formats.
</p
>
927 <p
>The result can be seen on the Debian Wiki, as
928 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
929 table listing all MIME types supported by one of the packages included
930 in the table
</a
>, with the package supporting most MIME types being
931 listed first in the table.
</p
>
933 </p
>The best multimedia player in Debian? It is totem, followed by
934 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
935 kmplayer. Time for the other players to update their announced MIME
941 <title>The Pyra - handheld computer with Debian preinstalled
</title>
942 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
943 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
944 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
945 <description>A friend of mine made me aware of
946 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
947 handheld computer which will be delivered with Debian preinstalled. I
948 would love to get one of those for my birthday. :)
</p
>
950 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
951 plugs and many others connectors, and include a full keyboard and a
5"
952 LCD touch screen. The
6000mAh battery is claimed to provide a whole
953 day of battery life time, but I have not seen any independent tests
954 confirming this. The vendor is still collecting preorders, and the
955 last I heard last night was that
22 more orders were needed before
956 production started.
</p
>
958 <p
>As far as I know, this is the first handheld preinstalled with
959 Debian. Please let me know if you know of any others. Is it the
960 first computer being sold with Debian preinstalled?
</p
>
965 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
966 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
968 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
969 <description><p
>During this weekends
970 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
971 squashing party and developer gathering
</a
>, we decided to do our part
972 to make sure there are good books about Debian available in Norwegian
973 Bokmål, and got in touch with the people behind the
974 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
975 project
</a
> to get started. If you want to help out, please start
977 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
978 hosted weblate project page
</a
>, and get in touch using
979 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
980 translators mailing list
</a
>. Please also check out
981 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
982 contributors
</a
>.
</p
>
984 <p
>The book is already available on paper in English, French and
985 Japanese, and our goal is to get it available on paper in Norwegian
986 Bokmål too. In addition to the paper edition, there are also EPUB and
987 Mobi versions available. And there are incomplete translations
988 available for many more languages.
</p
>
993 <title>One in two hundred Debian users using ZFS on Linux?
</title>
994 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
995 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
996 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
997 <description><p
>Just for fun I had a look at the popcon number of ZFS related
998 packages in Debian, and was quite surprised with what I found. I use
999 ZFS myself at home, but did not really expect many others to do so.
1000 But I might be wrong.
</p
>
1002 <p
>According to
1003 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1004 results for spl-linux
</a
>, there are
1019 Debian installations, or
1005 0.53% of the population, with the package installed. As far as I know
1006 the only use of the spl-linux package is as a support library for ZFS
1007 on Linux, so I use it here as proxy for measuring the number of ZFS
1008 installation on Linux in Debian. In the kFreeBSD variant of Debian
1009 the ZFS feature is already available, and there
1010 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1011 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1012 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1014 <p
>But even though the Debian project leader Lucas Nussbaum
1015 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1016 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1017 cleared, the package is still not in Debian. The package is again in
1018 the NEW queue. Several uploads have been rejected so far because the
1019 debian/copyright file was incomplete or wrong, but there is no reason
1020 to give up. The current status can be seen on
1021 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1022 team status page
</a
>, and
1023 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1024 source code
</a
> is available on Alioth.
</p
>
1026 <p
>As I want ZFS to be included in next version of Debian to make sure
1027 my home server can function in the future using only official Debian
1028 packages, and the current blocker is to get the debian/copyright file
1029 accepted by the FTP masters in Debian, I decided a while back to try
1030 to help out the team. This was the background for my blog post about
1031 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1032 updating and checking debian/copyright semi-automatically
</a
>, and I
1033 used the techniques I explored there to try to find any errors in the
1034 copyright file. It is not very easy to check every one of the around
1035 2000 files in the source package, but I hope we this time got it
1036 right. If you want to help out, check out the git source and try to
1037 find missing entries in the debian/copyright file.
</p
>
1042 <title>Full battery stats collector is now available in Debian
</title>
1043 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1045 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1046 <description><p
>Since this morning, the battery-stats package in Debian include an
1047 extended collector that will collect the complete battery history for
1048 later processing and graphing. The original collector store the
1049 battery level as percentage of last full level, while the new
1050 collector also record battery vendor, model, serial number, design
1051 full level, last full level and current battery level. This make it
1052 possible to predict the lifetime of the battery as well as visualise
1053 the energy flow when the battery is charging or discharging.
</p
>
1055 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1056 in the version
0.5.1 package in unstable. Get the new battery level graph
1057 and lifetime prediction by running:
1059 <p
><pre
>
1060 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1061 </pre
></p
>
1063 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1065 <p
>The flow in/out of the battery can be seen by running (no menu
1066 entry yet):
</p
>
1068 <p
><pre
>
1069 /usr/share/battery-stats/battery-stats-graph-flow
1070 </pre
></p
>
1072 <p
>I
'm not quite happy with the way the data is visualised, at least
1073 when there are few data points. The graphs look a bit better with a
1074 few years of data.
</p
>
1076 <p
>A while back one important feature I use in the battery stats
1077 collector broke in Debian. The scripts in
1078 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1079 suspect it happened when Jessie started using systemd, but I do not
1080 know. The issue is reported as
1081 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1082 pm-utils. I managed to work around it by adding an udev rule to call
1083 the collector script every time the power connector is connected and
1084 disconnected. With this fix in place it was finally time to make a
1085 new release of the package, and get it into Debian.
</p
>
1087 <p
>If you are interested in how your laptop battery is doing, please
1089 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1090 in Debian unstable, or rebuild it on Jessie to get it working on
1091 Debian stable. :) The upstream source is available from
1092 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1093 As always, patches are very welcome.
</p
>
1098 <title>Making battery measurements a little easier in Debian
</title>
1099 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1101 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1102 <description><p
>Back in September, I blogged about
1103 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1104 system I wrote to collect statistics about my laptop battery
</a
>, and
1105 how it showed the decay and death of this battery (now replaced). I
1106 created a simple deb package to handle the collection and graphing,
1107 but did not want to upload it to Debian as there were already
1108 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1109 package in Debian
</a
> that should do the same thing, and I did not see
1110 a point of uploading a competing package when battery-stats could be
1111 fixed instead. I reported a few bugs about its non-function, and
1112 hoped someone would step in and fix it. But no-one did.
</p
>
1114 <p
>I got tired of waiting a few days ago, and took matters in my own
1115 hands. The end result is that I am now the new upstream developer of
1116 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1117 battery-stats in Debian, and the package in Debian unstable is finally
1118 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1119 information provided by the Linux kernel. If you install the
1120 battery-stats package from unstable now, you will be able to get a
1121 graph of the current battery fill level, to get some idea about the
1122 status of the battery. The source package build and work just fine in
1123 Debian testing and stable (and probably oldstable too, but I have not
1124 tested). The default graph you get for that system look like this:
</p
>
1126 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
1128 <p
>My plans for the future is to merge my old scripts into the
1129 battery-stats package, as my old scripts collected a lot more details
1130 about the battery. The scripts are merged into the upstream
1131 battery-stats git repository already, but I am not convinced they work
1132 yet, as I changed a lot of paths along the way. Will have to test a
1133 bit more before I make a new release.
</p
>
1135 <p
>I will also consider changing the file format slightly, as I
1136 suspect the way I combine several values into one field might make it
1137 impossible to know the type of the value when using it for processing
1138 and graphing.
</p
>
1140 <p
>If you would like I would like to keep an close eye on your laptop
1141 battery, check out the battery-stats package in
1142 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1144 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1145 I would love some help to improve the system further.
</p
>
1150 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1151 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1153 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1154 <description><p
>Making packages for Debian requires quite a lot of attention to
1155 details. And one of the details is the content of the
1156 debian/copyright file, which should list all relevant licenses used by
1157 the code in the package in question, preferably in
1158 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1159 readable DEP5 format
</a
>.
</p
>
1161 <p
>For large packages with lots of contributors it is hard to write
1162 and update this file manually, and if you get some detail wrong, the
1163 package is normally rejected by the ftpmasters. So getting it right
1164 the first time around get the package into Debian faster, and save
1165 both you and the ftpmasters some work.. Today, while trying to figure
1166 out what was wrong with
1167 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1168 zfsonlinux copyright file
</a
>, I decided to spend some time on
1169 figuring out the options for doing this job automatically, or at least
1170 semi-automatically.
</p
>
1172 <p
>Lucikly, there are at least two tools available for generating the
1173 file based on the code in the source package,
1174 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1175 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1176 not sure which one of them came first, but both seem to be able to
1177 create a sensible draft file. As far as I can tell, none of them can
1178 be trusted to get the result just right, so the content need to be
1179 polished a bit before the file is OK to upload. I found the debmake
1181 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1182 blog posts from
2014</a
>.
1184 <p
>To generate using debmake, use the -cc option:
1186 <p
><pre
>
1187 debmake -cc
> debian/copyright
1188 </pre
></p
>
1190 <p
>Note there are some problems with python and non-ASCII names, so
1191 this might not be the best option.
</p
>
1193 <p
>The cme option is based on a config parsing library, and I found
1195 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1196 blog post from
2015</a
>. To generate using cme, use the
'update
1197 dpkg-copyright
' option:
1199 <p
><pre
>
1200 cme update dpkg-copyright
1201 </pre
></p
>
1203 <p
>This will create or update debian/copyright. The cme tool seem to
1204 handle UTF-
8 names better than debmake.
</p
>
1206 <p
>When the copyright file is created, I would also like some help to
1207 check if the file is correct. For this I found two good options,
1208 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1209 to focus on license types and file matching, and is able to detect
1210 ineffective blocks in the copyright file. The latter reports missing
1211 copyright holders and years, but was confused by inconsistent license
1212 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1213 fix all issues reported by them before uploading. But I do not know
1214 if the tools and the ftpmasters agree on what is important to fix in a
1215 copyright file, so the package might still be rejected.
</p
>
1217 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1218 will read through the source and try to find all copyright statements.
1219 It is not comparing the result to the content of debian/copyright, but
1220 can be useful when verifying the content of the copyright file.
</p
>
1222 <p
>Are you aware of better tools in Debian to create and update
1223 debian/copyright file. Please let me know, or blog about it on
1224 planet.debian.org.
</p
>
1226 <p
>As usual, if you use Bitcoin and want to show your support of my
1227 activities, please send Bitcoin donations to my address
1228 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1230 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1231 on how to use licensecheck and cdbs to create a draft copyright file
1233 <p
><pre
>
1234 licensecheck --copyright -r `find * -type f` | \
1235 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1236 </pre
></p
>
1238 <p
>He mentioned that he normally check the generated file into the
1239 version control system to make it easier to discover license and
1240 copyright changes in the upstream source. I will try to do the same
1241 with my packages in the future.
</p
>
1243 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1244 against using -quiet for new users, so I removed it from the proposed
1245 command line.
</p
>
1250 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1251 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1252 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1253 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1254 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1255 is taking shape in Debian, and one provided feature is a very
1256 convenient way to tell you which package to install to make a given
1257 firmware file available when the kernel is looking for it. This can
1258 be done using apt-file too, but that is for someone else to blog
1261 <p
>Here is a small recipe to find the package with a given firmware
1262 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1263 picked from the set of firmware announced using appstream in Debian
1264 unstable. In general you would be looking for the firmware requested
1265 by the kernel during kernel module loading. To find the package
1266 providing the example file, do like this:
</p
>
1268 <blockquote
><pre
>
1269 % apt install appstream
1273 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1274 awk
'/Package:/ {print $
2}
'
1277 </pre
></blockquote
>
1279 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1280 appstream wiki
</a
> page to learn how to embed the package metadata in
1281 a way appstream can use.
</p
>
1283 <p
>This same approach can be used to find any package supporting a
1284 given MIME type. This is very useful when you get a file you do not
1285 know how to handle. First find the mime type using
<tt
>file
1286 --mime-type
</tt
>, and next look up the package providing support for
1287 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1288 and you can find all packages handling this type like this:
</p
>
1290 <blockquote
><pre
>
1291 % apt install appstream
1295 % appstreamcli what-provides mimetype image/svg+xml | \
1296 awk
'/Package:/ {print $
2}
'
1318 </pre
></blockquote
>
1320 <p
>I believe the MIME types are fetched from the desktop file for
1321 packages providing appstream metadata.
</p
>
1326 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1327 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1329 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1330 <description><p
>Most people seem not to realise that every time they walk around
1331 with the computerised radio beacon known as a mobile phone their
1332 position is tracked by the phone company and often stored for a long
1333 time (like every time a SMS is received or sent). And if their
1334 computerised radio beacon is capable of running programs (often called
1335 mobile apps) downloaded from the Internet, these programs are often
1336 also capable of tracking their location (if the app requested access
1337 during installation). And when these programs send out information to
1338 central collection points, the location is often included, unless
1339 extra care is taken to not send the location. The provided
1340 information is used by several entities, for good and bad (what is
1341 good and bad, depend on your point of view). What is certain, is that
1342 the private sphere and the right to free movement is challenged and
1343 perhaps even eradicated for those announcing their location this way,
1344 when they share their whereabouts with private and public
1347 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1349 <p
>The phone company logs provide a register of locations to check out
1350 when one want to figure out what the tracked person was doing. It is
1351 unavailable for most of us, but provided to selected government
1352 officials, company staff, those illegally buying information from
1353 unfaithful servants and crackers stealing the information. But the
1354 public information can be collected and analysed, and a free software
1355 tool to do so is called
1356 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1357 discovered it when I read
1358 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1359 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1360 November
2014, and decided to check if it was available in Debian.
1361 The python program was in Debian, but
1362 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1363 Debian
</a
> was completely broken and practically unmaintained. I
1364 uploaded a new version which did not work quite right, but did not
1365 have time to fix it then. This Christmas I decided to finally try to
1366 get Creepy operational in Debian. Now a fixed version is available in
1367 Debian unstable and testing, and almost all Debian specific patches
1369 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1371 <p
>The Creepy program visualises geolocation information fetched from
1372 Twitter, Instagram, Flickr and Google+, and allow one to get a
1373 complete picture of every social media message posted recently in a
1374 given area, or track the movement of a given individual across all
1375 these services. Earlier it was possible to use the search API of at
1376 least some of these services without identifying oneself, but these
1377 days it is impossible. This mean that to use Creepy, you need to
1378 configure it to log in as yourself on these services, and provide
1379 information to them about your search interests. This should be taken
1380 into account when using Creepy, as it will also share information
1381 about yourself with the services.
</p
>
1383 <p
>The picture above show the twitter messages sent from (or at least
1384 geotagged with a position from) the city centre of Oslo, the capital
1385 of Norway. One useful way to use Creepy is to first look at
1386 information tagged with an area of interest, and next look at all the
1387 information provided by one or more individuals who was in the area.
1388 I tested it by checking out which celebrity provide their location in
1389 twitter messages by checkout out who sent twitter messages near a
1390 Norwegian TV station, and next could track their position over time,
1391 making it possible to locate their home and work place, among other
1392 things. A similar technique have been
1393 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1394 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1395 tool to discover lying governments, and a useful tool to help people
1396 understand the value of the private information they provide to the
1399 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1400 it depend on several python modules currently missing in Jessie (at
1401 least python-instagram, python-flickrapi and
1402 python-requests-toolbelt).
</p
>
1404 <p
>(I have uploaded
1405 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1406 screenshots.debian.net
</a
> and licensed it under the same terms as the
1407 Creepy program in Debian.)
</p
>
1412 <title>Always download Debian packages using Tor - the simple recipe
</title>
1413 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1414 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1415 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1416 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1417 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1418 that those listening on the Internet lines would have good reason to
1419 believe a computer have a given security hole
</a
> if it download a
1420 security fix from a Debian mirror. This is a good reason to always
1421 use encrypted connections to the Debian mirror, to make sure those
1422 listening do not know which IP address to attack. In August, Richard
1423 Hartmann observed that encryption was not enough, when it was possible
1424 to interfere download size to security patches or the fact that
1425 download took place shortly after a security fix was released, and
1426 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1427 to always use Tor to download packages from the Debian mirror
</a
>. He
1428 was not the first to propose this, as the
1429 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1430 package by Tim Retout already existed to make it easy to convince apt
1431 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1432 aware of that package when I read the blog post from Richard.
</p
>
1434 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1435 sysadmins, and he set up a Tor hidden service on one of the central
1436 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1437 it possible to download packages directly between two tor nodes,
1438 making sure the network traffic always were encrypted.
</p
>
1440 <p
>Here is a short recipe for enabling this on your machine, by
1441 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1442 urls with tor+http and tor+https, and using the hidden service instead
1443 of the official Debian mirror site. I recommend installing
1444 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1445 done in /etc/.
</p
>
1447 <blockquote
><pre
>
1448 apt install apt-transport-tor
1449 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1450 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1451 </pre
></blockquote
>
1453 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1454 the sed commands for these too. The sed command is assuming your are
1455 using the ftp.debian.org Debian mirror. Adjust the command (or just
1456 edit the file manually) to match your mirror.
</p
>
1458 <p
>This work in Debian Jessie and later. Note that tools like
1459 <tt
>apt-file
</tt
> only recently started using the apt transport
1460 system, and do not work with these tor+http URLs. For
1461 <tt
>apt-file
</tt
> you need the version currently in experimental,
1462 which need a recent apt version currently only in unstable. So if you
1463 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1465 <p
>Another advantage from this change is that your machine will start
1466 using Tor regularly and at fairly random intervals (every time you
1467 update the package lists or upgrade or install a new package), thus
1468 masking other Tor traffic done from the same machine. Using Tor will
1469 become normal for the machine in question.
</p
>
1471 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1472 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1473 enabled. It would be great if it was the default on any Debian
1479 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1480 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1482 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1483 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1484 call the car license plate numbers in those days. I would write the
1485 numbers down in my little book and compare notes with the other kids
1486 to see how many region codes we had seen and if we had seen some
1487 exotic or special region codes and numbers. It was a fun game to pass
1488 time, as we kids have plenty of it.
</p
>
1490 <p
>A few days I came across
1491 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1492 project
</a
>, a free software project to automatically discover and
1493 report license plates in images and video streams, and provide the
1494 "car numbers
" in a machine readable format. I
've been looking for
1495 such system for a while now, because I believe it is a bad idea that the
1496 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1497 number plate recognition
</a
> tool only is available in the hands of
1498 the powerful, and want it to be available also for the powerless to
1499 even the score when it comes to surveillance and sousveillance. I
1500 discovered the developer
1501 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1502 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1503 help him get it into shape to get the package uploaded into the Debian
1506 <p
>Today we finally managed to get the package into shape and uploaded
1507 it into Debian, where it currently
1508 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1509 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1511 <p
>I guess you are wondering why on earth such tool would be useful
1512 for the common folks, ie those not running a large government
1513 surveillance system? Well, I plan to put it in a computer on my bike
1514 and in my car, tracking the cars nearby and allowing me to be notified
1515 when number plates on my watch list are discovered. Another use case
1516 was suggested by a friend of mine, who wanted to set it up at his home
1517 to open the car port automatically when it discovered the plate on his
1518 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1519 capable of placing his license plate number of a piece of cardboard to
1520 open his car port, men replied that it was always unlocked anyway. I
1521 guess for such use case it make sense. I am sure there are other use
1522 cases too, for those with imagination and a vision.
</p
>
1524 <p
>If you want to build your own version of the Debian package, check
1525 out the upstream git source and symlink ./distros/debian to ./debian/
1526 before running
"debuild
" to build the source. Or wait a bit until the
1527 package show up in unstable.
</p
>
1532 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1533 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1534 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1535 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1536 <description><p
>Around three years ago, I created
1537 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1538 system
</a
> to get a more practical solution in Debian for handing
1539 hardware related packages. A GUI system in the isenkram package will
1540 present a pop-up dialog when some hardware dongle supported by
1541 relevant packages in Debian is inserted into the machine. The same
1542 lookup mechanism to detect packages is available as command line
1543 tools in the isenkram-cli package. In addition to mapping hardware,
1544 it will also map kernel firmware files to packages and make it easy to
1545 install needed firmware packages automatically. The key for this
1546 system to work is a good way to map hardware to packages, in other
1547 words, allow packages to announce what hardware they will work
1550 <p
>I started by providing data files in the isenkram source, and
1551 adding code to download the latest version of these data files at run
1552 time, to ensure every user had the most up to date mapping available.
1553 I also added support for storing the mapping in the Packages file in
1554 the apt repositories, but did not push this approach because while I
1555 was trying to figure out how to best store hardware/package mappings,
1556 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1557 appstream system
</a
> was announced. I got in touch and suggested to
1558 add the hardware mapping into that data set to be able to use
1559 appstream as a data source, and this was accepted at least for the
1560 Debian version of appstream.
</p
>
1562 <p
>A few days ago using appstream in Debian for this became possible,
1563 and today I uploaded a new version
0.20 of isenkram adding support for
1564 appstream as a data source for mapping hardware to packages. The only
1565 package so far using appstream to announce its hardware support is my
1566 pymissile package. I got help from Matthias Klumpp with figuring out
1567 how do add the required
1568 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1569 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1570 this content:
</p
>
1572 <blockquote
><pre
>
1573 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1574 &lt;component
&gt;
1575 &lt;id
&gt;pymissile
&lt;/id
&gt;
1576 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1577 &lt;name
&gt;pymissile
&lt;/name
&gt;
1578 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1579 &lt;description
&gt;
1581 Pymissile provides a curses interface to control an original
1582 Marks and Spencer / Striker USB Missile Launcher, as well as a
1583 motion control script to allow a webcamera to control the
1586 &lt;/description
&gt;
1587 &lt;provides
&gt;
1588 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1589 &lt;/provides
&gt;
1590 &lt;/component
&gt;
1591 </pre
></blockquote
>
1593 <p
>The key for isenkram is the component/provides/modalias value,
1594 which is a glob style match rule for hardware specific strings
1595 (modalias strings) provided by the Linux kernel. In this case, it
1596 will map to all USB devices with vendor code
1130 and product code
1599 <p
>Note, it is important that the license of all the metadata files
1600 are compatible to have permissions to aggregate them into archive wide
1601 appstream files. Matthias suggested to use MIT or BSD licenses for
1602 these files. A challenge is figuring out a good id for the data, as
1603 it is supposed to be globally unique and shared across distributions
1604 (in other words, best to coordinate with upstream what to use). But
1605 it can be changed later or, so we went with the package name as
1606 upstream for this project is dormant.
</p
>
1608 <p
>To get the metadata file installed in the correct location for the
1609 mirror update scripts to pick it up and include its content the
1610 appstream data source, the file must be installed in the binary
1611 package under /usr/share/appdata/. I did this by adding the following
1612 line to debian/pymissile.install:
</p
>
1614 <blockquote
><pre
>
1615 debian/pymissile.metainfo.xml usr/share/appdata
1616 </pre
></blockquote
>
1618 <p
>With that in place, the command line tool isenkram-lookup will list
1619 all packages useful on the current computer automatically, and the GUI
1620 pop-up handler will propose to install the package not already
1621 installed if a hardware dongle is inserted into the machine in
1624 <p
>Details of the modalias field in appstream is available from the
1625 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1627 <p
>To locate the modalias values of all hardware present in a machine,
1628 try running this command on the command line:
</p
>
1630 <blockquote
><pre
>
1631 cat $(find /sys/devices/|grep modalias)
1632 </pre
></blockquote
>
1634 <p
>To learn more about the isenkram system, please check out
1635 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1636 blog posts tagged isenkram
</a
>.
</p
>
1641 <title>The GNU General Public License is not magic pixie dust
</title>
1642 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1643 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1644 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1645 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1646 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1647 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1648 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1649 I quote the blog post from Paul in full here with his permission:
<p
>
1653 <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
>
1656 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1658 The first step is to choose a
1659 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1662 The next step is, when someone fails to follow that copyleft license,
1663 <b
>it must be enforced
</b
><br/
>
1665 and its a simple fact of our modern society that such type of
1668 is incredibly expensive to do and incredibly difficult to do.
1671 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1672 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1673 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1674 0x57</a
></small
></p
>
1676 <p
>As the Debian Website
1677 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1678 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1679 imply, public domain and permissively licensed software can lead to
1680 the production of more proprietary software as people discover useful
1681 software, extend it and or incorporate it into their hardware or
1682 software products. Copyleft licenses such as the GNU GPL were created
1683 to close off this avenue to the production of proprietary software but
1684 such licenses are not enough. With the ongoing adoption of Free
1685 Software by individuals and groups, inevitably the community
's
1686 expectations of license compliance are violated, usually out of
1687 ignorance of the way Free Software works, but not always. As Karen
1688 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1689 Freedom
">FaiF
</a
>
1690 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1691 copyleft is nothing if no-one is willing and able to stand up in court
1692 to protect it. The reality of today
's world is that legal
1693 representation is expensive, difficult and time consuming. With
1694 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1695 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1696 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1697 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1698 of the Linux project, Debian and other groups against GPL violations.
1699 In March the SFC supported a
1700 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1701 by Christoph Hellwig
</a
> against VMware for refusing to
1702 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1703 with the GPL
</a
> in relation to their use of parts of the Linux
1704 kernel. Since then two of their sponsors pulled corporate funding and
1706 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1707 or cancelled their talks
</a
>. As a result they have decided to rely
1708 less on corporate funding and more on the broad community of
1709 individuals who support Free Software and copyleft. So the SFC has
1710 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1711 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1712 a community of folks who stand up for copyleft and the GPL by
1713 supporting their work on promoting and supporting copyleft and Free
1716 <p
>If you support Free Software,
1717 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1718 what the SFC do, agree with their
1719 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1720 principles
</a
>, are happy about their
1721 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1722 work on a project that is an SFC
1723 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1724 just want to stand up for copyleft, please join
1725 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1726 Allan Webber
</a
>,
1727 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1729 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1730 Bacon
</a
>, myself and
1731 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1733 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1734 next week your donation will be
1735 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1736 by an anonymous donor. Please also consider asking your employer to
1737 match your donation or become a sponsor of SFC. Don
't forget to
1738 spread the word about your support for SFC via email, your blog and or
1739 social media accounts.
</p
>
1743 <p
>I agree with Paul on this topic and just signed up as a Supporter
1744 of Software Freedom Conservancy myself. Perhaps you should be a
1745 supporter too?
</p
>
1750 <title>PGP key transition statement for key EE4E02F9
</title>
1751 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1752 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1753 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1754 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1755 set it up properly. I wanted to generate it offline and have it
1756 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1757 smart card
</a
> for daily use, and learning how to do it and finding
1758 time to sit down with an offline machine almost took forever. But
1759 finally I
've been able to complete the process, and have now moved
1760 from my old GPG key to a new GPG key. See
1761 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1762 full transition statement, signed with both my old and new key
</a
> for
1763 the details. This is my new key:
</p
>
1766 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1767 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1768 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1769 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1770 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1771 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1772 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1775 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1776 my old key.
</p
>
1778 <p
>If you signed my old key
1779 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1780 I
'd very much appreciate a signature on my new key, details and
1781 instructions in the transition statement. I m happy to reciprocate if
1782 you have a similarly signed transition statement to present.
</p
>
1787 <title>The life and death of a laptop battery
</title>
1788 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1789 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1790 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1791 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1792 But this do not last. The last few laptops gave me a feeling that
1793 within a year, the life time is just a fraction of what it used to be,
1794 and it slowly become painful to use the laptop without power connected
1795 all the time. Because of this, when I got a new Thinkpad X230 laptop
1796 about two years ago, I decided to monitor its battery state to have
1797 more hard facts when the battery started to fail.
</p
>
1799 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1801 <p
>First I tried to find a sensible Debian package to record the
1802 battery status, assuming that this must be a problem already handled
1803 by someone else. I found
1804 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1805 which collects statistics from the battery, but it was completely
1806 broken. I sent a few suggestions to the maintainer, but decided to
1807 write my own collector as a shell script while I waited for feedback
1809 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1810 blog post about the battery development on a MacBook Air
</a
> I also
1812 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1813 available in Debian.
</p
>
1815 <p
>I started my collector
2013-
07-
15, and it has been collecting
1816 battery stats ever since. Now my
1817 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1818 measurements, from the time the battery was working great until now,
1819 when it is unable to charge above
7% of original capacity. My
1820 collector shell script is quite simple and look like this:
</p
>
1825 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1827 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1828 logfile=/var/log/hjemmenett-battery-status.log
1830 files=
"manufacturer model_name technology serial_number \
1831 energy_full energy_full_design energy_now cycle_count status
"
1833 if [ ! -e
"$logfile
" ] ; then
1835 printf
"timestamp,
"
1837 printf
"%s,
" $f
1840 )
> "$logfile
"
1844 # Print complete message in one echo call, to avoid race condition
1845 # when several log processes run in parallel.
1846 msg=$(printf
"%s,
" $(date +%s); \
1847 for f in $files; do \
1848 printf
"%s,
" $(cat $f); \
1850 echo
"$msg
"
1853 cd /sys/class/power_supply
1856 (cd $bat
&& log_battery
>> "$logfile
")
1860 <p
>The script is called when the power management system detect a
1861 change in the power status (power plug in or out), and when going into
1862 and out of hibernation and suspend. In addition, it collect a value
1863 every
10 minutes. This make it possible for me know when the battery
1864 is discharging, charging and how the maximum charge change over time.
1865 The code for the Debian package
1866 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1867 available on github
</a
>.
</p
>
1869 <p
>The collected log file look like this:
</p
>
1872 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1873 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1875 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1876 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1879 <p
>I wrote a small script to create a graph of the charge development
1880 over time. This graph depicted above show the slow death of my laptop
1883 <p
>But why is this happening? Why are my laptop batteries always
1884 dying in a year or two, while the batteries of space probes and
1885 satellites keep working year after year. If we are to believe
1886 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1887 University
</a
>, the cause is me charging the battery whenever I have a
1888 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1889 all the time, but to stay below
90% of full charge most of the time.
1890 I
've been told that the Tesla electric cars
1891 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1892 the charge of their batteries to
80%
</a
>, with the option to charge to
1893 100% when preparing for a longer trip (not that I would want a car
1894 like Tesla where rights to privacy is abandoned, but that is another
1895 story), which I guess is the option we should have for laptops on
1896 Linux too.
</p
>
1898 <p
>Is there a good and generic way with Linux to tell the battery to
1899 stop charging at
80%, unless requested to charge to
100% once in
1900 preparation for a longer trip? I found
1901 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1902 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1903 80%
</a
>, but could not get it to work (kernel module refused to
1906 <p
>I wonder why the battery capacity was reported to be more than
100%
1907 at the start. I also wonder why the
"full capacity
" increases some
1908 times, and if it is possible to repeat the process to get the battery
1909 back to design capacity. And I wonder if the discharge and charge
1910 speed change over time, or if this stay the same. I did not yet try
1911 to write a tool to calculate the derivative values of the battery
1912 level, but suspect some interesting insights might be learned from
1915 <p
>Update
2015-
09-
24: I got a tip to install the packages
1916 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1917 packages instead of the tp-smapi-dkms package I had tried to use
1918 initially, and use
'tlp setcharge
40 80' to change when charging start
1919 and stop. I
've done so now, but expect my existing battery is toast
1920 and need to be replaced. The proposal is unfortunately Thinkpad
1926 <title>New laptop - some more clues and ideas based on feedback
</title>
1927 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1928 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1929 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1930 <description><p
>Several people contacted me after my previous blog post about my
1931 need for a new laptop, and provided very useful feedback. I wish to
1932 thank every one of these. Several pointed me to the possibility of
1933 fixing my X230, and I am already in the process of getting Lenovo to
1934 do so thanks to the on site, next day support contract covering the
1935 machine. But the battery is almost useless (I expect to replace it
1936 with a non-official battery) and I do not expect the machine to live
1937 for many more years, so it is time to plan its replacement. If I did
1938 not have a support contract, it was suggested to find replacement parts
1939 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1940 might present a language barrier as I do not understand French.
</p
>
1942 <p
>One tip I got was to use the
1943 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1944 compare laptop models. It seem to have more models available than
1945 prisjakt.no. Another tip I got from someone I know have similar
1946 keyboard preferences was that the HP EliteBook
840 keyboard is not
1947 very good, and this matches my experience with earlier EliteBook
1948 keyboards I tested. Because of this, I will not consider it any further.
1950 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1951 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1952 (which is missing from the X240), and is working fairly well with
1953 Debian Sid/Unstable according to
1954 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1955 got on the keyboard quality are not consistent. Some say the keyboard
1956 is good, others say it is ok, while others say it is not very good.
1957 Those with experience from X41 and and X60 agree that the X250
1958 keyboard is not as good as those trusty old laptops, and suggest I
1959 keep and fix my X230 instead of upgrading, or get a used X230 to
1960 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1961 activity and battery status, which is very convenient on my X230. I
'm
1962 also told that the CPU fan is running very often, making it a bit
1963 noisy. In any case, the X250 do not work out of the box with Debian
1964 Stable/Jessie, one of my requirements.
</p
>
1966 <p
>I have also gotten a few vendor proposals, one was
1967 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1968 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1969 The latter look very attractive to me.
</p
>
1971 <p
>Again, thank you all for the very useful feedback. It help a lot
1972 as I keep looking for a replacement.
</p
>
1974 <p
>Update
2015-
07-
06: I was recommended to check out the
1975 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1977 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1978 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1983 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1984 <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>
1985 <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>
1986 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1987 <description><p
>My primary work horse laptop is failing, and will need a
1988 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1989 started flickering yesterday, and I suspect the cause is a broken
1990 cable, as changing the angle of the screen some times get rid of the
1991 flickering.
</p
>
1993 <p
>My requirements have not really changed since I bought it, and is
1995 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1996 described them in
2013</a
>. The last time I bought a laptop, I had
1998 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1999 where I could select at least a few of the requirements (mouse pin,
2000 wifi, weight) and go through the rest manually. Three button mouse
2001 and a good keyboard is not available as an option, and all the three
2002 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2003 G2) lack three mouse buttons). It is also unclear to me how good the
2004 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2005 the keyboard, even if the quality and robustness in the X series have
2006 deteriorated since X41.
</p
>
2008 <p
>I wonder how I can find a sensible laptop when none of the options
2009 seem sensible to me? Are there better services around to search the
2010 set of available laptops for features? Please send me an email if you
2011 have suggestions.
</p
>
2013 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2014 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2015 of endorsed hardware
</a
>, which is useful background information.
</p
>
2020 <title>How to stay with sysvinit in Debian Jessie
</title>
2021 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2022 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2023 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2024 <description><p
>By now, it is well known that Debian Jessie will not be using
2025 sysvinit as its boot system by default. But how can one keep using
2026 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2028 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2029 Schubert
</a
> and
2030 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2033 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2034 keep sysvinit as your boot system, create a file
2035 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2036 you upgrade:
</p
>
2038 <p
><blockquote
><pre
>
2039 Package: systemd-sysv
2040 Pin: release o=Debian
2042 </pre
></blockquote
><p
>
2044 <p
>This file content will tell apt and aptitude to not consider
2045 installing systemd-sysv as part of any installation and upgrade
2046 solution when resolving dependencies, and thus tell it to avoid
2047 systemd as a default boot system. The end result should be that the
2048 upgraded system keep using sysvinit.
</p
>
2050 <p
>If you are installing Jessie for the first time, there is no way to
2051 get sysvinit installed by default (debootstrap used by
2052 debian-installer have no option for this), but one can tell the
2053 installer to switch to sysvinit before the first boot. Either by
2054 using a kernel argument to the installer, or by adding a line to the
2055 preseed file used. First, the kernel command line argument:
2057 <p
><blockquote
><pre
>
2058 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2059 </pre
></blockquote
><p
>
2061 <p
>Next, the line to use in a preseed file:
</p
>
2063 <p
><blockquote
><pre
>
2064 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2065 </pre
></blockquote
><p
>
2067 <p
>One can of course also do this after the first boot by installing
2068 the sysvinit-core package.
</p
>
2070 <p
>I recommend only using sysvinit if you really need it, as the
2071 sysvinit boot sequence in Debian have several hardware specific bugs
2072 on Linux caused by the fact that it is unpredictable when hardware
2073 devices show up during boot. But on the other hand, the new default
2074 boot system still have a few rough edges I hope will be fixed before
2075 Jessie is released.
</p
>
2077 <p
>Update
2014-
11-
26: Inspired by
2078 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2079 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2085 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2086 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2087 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2088 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2089 <description><p
>The right to communicate with your friends and family in private,
2090 without anyone snooping, is a right every citicen have in a liberal
2091 democracy. But this right is under serious attack these days.
</p
>
2093 <p
>A while back it occurred to me that one way to make the dragnet
2094 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2095 the whisleblower Snowden) more expensive for Internet email,
2096 is to deliver all email using SMTP via Tor. Such SMTP option would be
2097 a nice addition to the FreedomBox project if we could send email
2098 between FreedomBox machines without leaking metadata about the emails
2099 to the people peeking on the wire. I
2100 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2101 this on the FreedomBox project mailing list in October
</a
> and got a
2102 lot of useful feedback and suggestions. It also became obvious to me
2103 that this was not a novel idea, as the same idea was tested and
2104 documented by Johannes Berg as early as
2006, and both
2105 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2106 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2107 propose a similar method / protocol to pass emails between users.
</p
>
2109 <p
>To implement such system one need to set up a Tor hidden service
2110 providing the SMTP protocol on port
25, and use email addresses
2111 looking like username@hidden-service-name.onion. With such addresses
2112 the connections to port
25 on hidden-service-name.onion using Tor will
2113 go to the correct SMTP server. To do this, one need to configure the
2114 Tor daemon to provide the hidden service and the mail server to accept
2115 emails for this .onion domain. To learn more about Exim configuration
2116 in Debian and test the design provided by Johannes Berg in his FAQ, I
2117 set out yesterday to create a Debian package for making it trivial to
2118 set up such SMTP over Tor service based on Debian. Getting it to work
2119 were fairly easy, and
2120 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2121 source code for the Debian package
</a
> is available from github. I
2122 plan to move it into Debian if further testing prove this to be a
2123 useful approach.
</p
>
2125 <p
>If you want to test this, set up a blank Debian machine without any
2126 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2127 get rid of exim4). Install tor, clone the git repository mentioned
2128 above, build the deb and install it on the machine. Next, run
2129 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2130 the instructions to get the service up and running. Restart tor and
2131 exim when it is done, and test mail delivery using swaks like
2134 <p
><blockquote
><pre
>
2135 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2136 --to fbx@dutlqrrmjhtfa3vp.onion
2137 </pre
></blockquote
></p
>
2139 <p
>This will test the SMTP delivery using tor. Replace the email
2140 address with your own address to test your server. :)
</p
>
2142 <p
>The setup procedure is still to complex, and I hope it can be made
2143 easier and more automatic. Especially the tor setup need more work.
2144 Also, the package include a tor-smtp tool written in C, but its task
2145 should probably be rewritten in some script language to make the deb
2146 architecture independent. It would probably also make the code easier
2147 to review. The tor-smtp tool currently need to listen on a socket for
2148 exim to talk to it and is started using xinetd. It would be better if
2149 no daemon and no socket is needed. I suspect it is possible to get
2150 exim to run a command line tool for delivery instead of talking to a
2151 socket, and hope to figure out how in a future version of this
2154 <p
>Until I wipe my test machine, I can be reached using the
2155 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2156 SMTorP. :)
</p
>
2161 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2162 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2163 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2164 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2165 <description><p
>If you ever had to moderate a mailman list, like the ones on
2166 alioth.debian.org, you know the web interface is fairly slow to
2167 operate. First you visit one web page, enter the moderation password
2168 and get a new page shown with a list of all the messages to moderate
2169 and various options for each email address. This take a while for
2170 every list you moderate, and you need to do it regularly to do a good
2171 job as a list moderator. But there is a quick alternative,
2172 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2173 listadmin program
</a
>. It allow you to check lists for new messages
2174 to moderate in a fraction of a second. Here is a test run on two
2175 lists I recently took over:
</p
>
2177 <p
><blockquote
><pre
>
2178 % time listadmin xiph
2179 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2180 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2186 </pre
></blockquote
></p
>
2188 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2189 there are no message in the moderation queue. Every morning I
2190 currently moderate
68 mailman lists, and it normally take around two
2191 minutes. When I took over the two pkg-xiph lists above a few days
2192 ago, there were
400 emails waiting in the moderator queue. It took me
2193 less than
15 minutes to process them all using the listadmin
2196 <p
>If you install
2197 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2198 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2199 with content like this, the moderation task is a breeze:
</p
>
2201 <p
><blockquote
><pre
>
2202 username username@example.org
2205 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2208 adminurl https://{domain}/mailman/admindb/{list}
2209 mailman-list@lists.example.com
2212 other-list@otherserver.example.org
2213 </pre
></blockquote
></p
>
2215 <p
>There are other options to set as well. Check the manual page to
2216 learn the details.
</p
>
2218 <p
>If you are forced to moderate lists on a mailman installation where
2219 the SSL certificate is self signed or not properly signed by a
2220 generally accepted signing authority, you can set a environment
2221 variable when calling listadmin to disable SSL verification:
</p
>
2223 <p
><blockquote
><pre
>
2224 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2225 </pre
></blockquote
></p
>
2227 <p
>If you want to moderate a subset of the lists you take care of, you
2228 can provide an argument to the listadmin script like I do in the
2229 initial screen dump (the xiph argument). Using an argument, only
2230 lists matching the argument string will be processed. This make it
2231 quick to accept messages if you notice the moderation request in your
2234 <p
>Without the listadmin program, I would never be the moderator of
68
2235 mailing lists, as I simply do not have time to spend on that if the
2236 process was any slower. The listadmin program have saved me hours of
2237 time I could spend elsewhere over the years. It truly is nice free
2240 <p
>As usual, if you use Bitcoin and want to show your support of my
2241 activities, please send Bitcoin donations to my address
2242 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2244 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2245 configuration example. Also, I
've been told that the
2246 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2252 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2253 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2254 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2255 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2256 <description><p
>When PXE installing laptops with Debian, I often run into the
2257 problem that the WiFi card require some firmware to work properly.
2258 And it has been a pain to fix this using preseeding in Debian.
2259 Normally something more is needed. But thanks to
2260 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2261 package
</a
> and its recent tasksel extension, it has now become easy
2262 to do this using simple preseeding.
</p
>
2264 <p
>The isenkram-cli package provide tasksel tasks which will install
2265 firmware for the hardware found in the machine (actually, requested by
2266 the kernel modules for the hardware). (It can also install user space
2267 programs supporting the hardware detected, but that is not the focus
2268 of this story.)
</p
>
2270 <p
>To get this working in the default installation, two preeseding
2271 values are needed. First, the isenkram-cli package must be installed
2272 into the target chroot (aka the hard drive) before tasksel is executed
2273 in the pkgsel step of the debian-installer system. This is done by
2274 preseeding the base-installer/includes debconf value to include the
2275 isenkram-cli package. The package name is next passed to debootstrap
2276 for installation. With the isenkram-cli package in place, tasksel
2277 will automatically use the isenkram tasks to detect hardware specific
2278 packages for the machine being installed and install them, because
2279 isenkram-cli contain tasksel tasks.
</p
>
2281 <p
>Second, one need to enable the non-free APT repository, because
2282 most firmware unfortunately is non-free. This is done by preseeding
2283 the apt-mirror-setup step. This is unfortunate, but for a lot of
2284 hardware it is the only option in Debian.
</p
>
2286 <p
>The end result is two lines needed in your preseeding file to get
2287 firmware installed automatically by the installer:
</p
>
2289 <p
><blockquote
><pre
>
2290 base-installer base-installer/includes string isenkram-cli
2291 apt-mirror-setup apt-setup/non-free boolean true
2292 </pre
></blockquote
></p
>
2294 <p
>The current version of isenkram-cli in testing/jessie will install
2295 both firmware and user space packages when using this method. It also
2296 do not work well, so use version
0.15 or later. Installing both
2297 firmware and user space packages might give you a bit more than you
2298 want, so I decided to split the tasksel task in two, one for firmware
2299 and one for user space programs. The firmware task is enabled by
2300 default, while the one for user space programs is not. This split is
2301 implemented in the package currently in unstable.
</p
>
2303 <p
>If you decide to give this a go, please let me know (via email) how
2304 this recipe work for you. :)
</p
>
2306 <p
>So, I bet you are wondering, how can this work. First and
2307 foremost, it work because tasksel is modular, and driven by whatever
2308 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2309 isenkram-cli package place two files for tasksel to find. First there
2310 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2312 <p
><blockquote
><pre
>
2313 Task: isenkram-packages
2315 Description: Hardware specific packages (autodetected by isenkram)
2316 Based on the detected hardware various hardware specific packages are
2318 Test-new-install: show show
2320 Packages: for-current-hardware
2322 Task: isenkram-firmware
2324 Description: Hardware specific firmware packages (autodetected by isenkram)
2325 Based on the detected hardware various hardware specific firmware
2326 packages are proposed.
2327 Test-new-install: mark show
2329 Packages: for-current-hardware-firmware
2330 </pre
></blockquote
></p
>
2332 <p
>The key parts are Test-new-install which indicate how the task
2333 should be handled and the Packages line referencing to a script in
2334 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2335 list of packages to install. The for-current-hardware-firmware script
2336 look like this to list relevant firmware for the machine:
2338 <p
><blockquote
><pre
>
2341 PATH=/usr/sbin:$PATH
2343 isenkram-autoinstall-firmware -l
2344 </pre
></blockquote
></p
>
2346 <p
>With those two pieces in place, the firmware is installed by
2347 tasksel during the normal d-i run. :)
</p
>
2349 <p
>If you want to test what tasksel will install when isenkram-cli is
2350 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2351 --new-install
</tt
> to get the list of packages that tasksel would
2354 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2355 pilots in testing this feature, as isenkram is used there now to
2356 install firmware, replacing the earlier scripts.
</p
>
2361 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2362 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2364 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2365 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2366 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2367 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2368 on a screen normally showing the bread types and prizes:
</p
>
2370 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2372 <p
>If it had booted as it was supposed to, I would never had known
2373 about this hidden Linux installation. It is interesting what
2374 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2379 <title>New lsdvd release version
0.17 is ready
</title>
2380 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2382 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2383 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2384 got a new set of developers a few weeks ago, after the original
2385 developer decided to step down and pass the project to fresh blood.
2386 This project is now maintained by Petter Reinholdtsen and Steve
2389 <p
>I just wrapped up
2390 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2391 new lsdvd release
</a
>, available in git or from
2392 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2393 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2398 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2399 <li
>Check for garbage in the program chains, which indicate that a track is
2400 non-existant, to work around additional copy protection
</li
>
2401 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2402 <li
>Fix pallete display of first entry
</li
>
2403 <li
>Fix include orders
</li
>
2404 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2405 <li
>Fix the chapter count
</li
>
2406 <li
>Make sure the array size and the array limit used when initialising
2407 the palette size is the same.
</li
>
2408 <li
>Fix array printing.
</li
>
2409 <li
>Correct subsecond calculations.
</li
>
2410 <li
>Add sector information to the output format.
</li
>
2411 <li
>Clean up code to be closer to ANSI C and compile without warnings
2412 with more GCC compiler warnings.
</li
>
2416 <p
>This change bring together patches for lsdvd in use in various
2417 Linux and Unix distributions, as well as patches submitted to the
2418 project the last nine years. Please check it out. :)
</p
>
2423 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2424 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2425 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2426 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2427 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2428 project
</a
> provide a Linux solution for schools, including a
2429 powerful desktop with education software, a central server providing
2430 web pages, user database, user home directories, central login and PXE
2431 boot of both clients without disk and the installation to install Debian
2432 Edu on machines with disk (and a few other services perhaps to small
2433 to mention here). We in the Debian Edu team are currently working on
2434 the Jessie based version, trying to get everything in shape before the
2435 freeze, to avoid having to maintain our own package repository in the
2437 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2438 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2439 work left. Some fatal problems block testing, breaking the installer,
2440 but it is possible to work around these to get anyway. Here is a
2441 recipe on how to get the installation limping along.
</p
>
2443 <p
>First, download the test ISO via
2444 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2445 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2447 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2448 The ISO build was broken on Tuesday, so we do not get a new ISO every
2449 12 hours or so, but thankfully the ISO we already got we are able to
2450 install with some tweaking.
</p
>
2452 <p
>When you get to the Debian Edu profile question, go to tty2
2453 (use Alt-Ctrl-F2), run
</p
>
2455 <p
><blockquote
><pre
>
2456 nano /usr/bin/edu-eatmydata-install
2457 </pre
></blockquote
></p
>
2459 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2460 optimization. Return to the installation, select the profile you want
2461 and continue. Without this change, exim4-config will fail to install
2462 due to a known bug in eatmydata.
</p
>
2464 <p
>When you get the grub question at the end, answer /dev/sda (or if
2465 this do not work, figure out what your correct value would be. All my
2466 test machines need /dev/sda, so I have no advice if it do not fit
2467 your need.
</p
>
2469 <p
>If you installed a profile including a graphical desktop, log in as
2470 root after the initial boot from hard drive, and install the
2471 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2472 or mate. If you want several desktop options, install more than one
2473 metapackage. Once this is done, reboot and you should have a working
2474 graphical login screen. This workaround should no longer be needed
2475 once the education-tasks package version
1.801 enter testing in two
2478 <p
>I believe the ISO build will start working on two days when the new
2479 tasksel package enter testing and Steve McIntyre get a chance to
2480 update the debian-cd git repository. The eatmydata, grub and desktop
2481 issues are already fixed in unstable and testing, and should show up
2482 on the ISO as soon as the ISO build start working again. Well the
2483 eatmydata optimization is really just disabled. The proper fix
2484 require an upload by the eatmydata maintainer applying the patch
2485 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2486 The rest have proper fixes in unstable.
</p
>
2488 <p
>I hope this get you going with the installation testing, as we are
2489 quickly running out of time trying to get our Jessie based
2490 installation ready before the distribution freeze in a month.
</p
>
2495 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2496 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2498 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2499 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2500 to handle my fairly large DVD collection. It is a nice command line
2501 tool to get details about a DVD, like title, tracks, track length,
2502 etc, in XML, Perl or human readable format. But lsdvd have not seen
2503 any new development since
2006 and had a few irritating bugs affecting
2504 its use with some DVDs. Upstream seemed to be dead, and in January I
2505 sent a small probe asking for a version control repository for the
2506 project, without any reply. But I use it regularly and would like to
2507 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2508 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2509 the project admin, and after getting a reply from him explaining that
2510 he was no longer interested in the project, I asked if I could take
2511 over. And yesterday, I became project admin.
</p
>
2513 <p
>I
've been in touch with a Gentoo developer and the Debian
2514 maintainer interested in joining forces to maintain the upstream
2515 project, and I hope we can get a new release out fairly quickly,
2516 collecting the patches spread around on the internet into on place.
2517 I
've added the relevant Debian patches to the freshly created git
2518 repository, and expect the Gentoo patches to make it too. If you got
2519 a DVD collection and care about command line tools, check out
2520 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2521 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2522 list
</a
>. :)
</p
>
2527 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2528 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2529 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2530 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2531 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2532 a lot quicker. When we install more than
2000 packages in
2533 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2534 tasksel in the installer, unpacking the binary packages take forever.
2535 A part of the slow I/O issue was discussed in
2536 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2537 much file system sync-ing done by dpkg, which is the package
2538 responsible for unpacking the binary packages. Other parts (like code
2539 executed by postinst scripts) might also sync to disk during
2540 installation. All this sync-ing to disk do not really make sense to
2541 me. If the machine crash half-way through, I start over, I do not try
2542 to salvage the half installed system. So the failure sync-ing is
2543 supposed to protect against, hardware or system crash, is not really
2544 relevant while the installer is running.
</p
>
2546 <p
>A few days ago, I thought of a way to get rid of all the file
2547 system sync()-ing in a fairly non-intrusive way, without the need to
2548 change the code in several packages. The idea is not new, but I have
2549 not heard anyone propose the approach using dpkg-divert before. It
2550 depend on the small and clever package
2551 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2552 uses LD_PRELOAD to replace the system functions for syncing data to
2553 disk with functions doing nothing, thus allowing programs to live
2554 dangerous while speeding up disk I/O significantly. Instead of
2555 modifying the implementation of dpkg, apt and tasksel (which are the
2556 packages responsible for selecting, fetching and installing packages),
2557 it occurred to me that we could just divert the programs away, replace
2558 them with a simple shell wrapper calling
2559 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2560 Two days ago I decided to test the idea, and wrapped up a simple
2561 implementation for the Debian Edu udeb.
</p
>
2563 <p
>The effect was stunning. In my first test it reduced the running
2564 time of the pkgsel step (installing tasks) from
64 to less than
44
2565 minutes (
20 minutes shaved off the installation) on an old Dell
2566 Latitude D505 machine. I am not quite sure what the optimised time
2567 would have been, as I messed up the testing a bit, causing the debconf
2568 priority to get low enough for two questions to pop up during
2569 installation. As soon as I saw the questions I moved the installation
2570 along, but do not know how long the question were holding up the
2571 installation. I did some more measurements using Debian Edu Jessie,
2572 and got these results. The time measured is the time stamp in
2573 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2574 "pkgsel: finishing up
" lines, if you want to do the same measurement
2575 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2576 timing thus do not depend on how quickly the user handle the tasksel
2579 <p
><table
>
2582 <th
>Machine/setup
</th
>
2583 <th
>Original tasksel
</th
>
2584 <th
>Optimised tasksel
</th
>
2585 <th
>Reduction
</th
>
2589 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2590 <td
>64 min (
07:
46-
08:
50)
</td
>
2591 <td
><44 min (
11:
27-
12:
11)
</td
>
2592 <td
>>20 min
18%
</td
>
2596 <td
>Latitude D505 Roaming LXDE
</td
>
2597 <td
>57 min (
08:
48-
09:
45)
</td
>
2598 <td
>34 min (
07:
43-
08:
17)
</td
>
2599 <td
>23 min
40%
</td
>
2603 <td
>Latitude D505 Minimal
</td
>
2604 <td
>22 min (
10:
37-
10:
59)
</td
>
2605 <td
>11 min (
11:
16-
11:
27)
</td
>
2606 <td
>11 min
50%
</td
>
2610 <td
>Thinkpad X200 Minimal
</td
>
2611 <td
>6 min (
08:
19-
08:
25)
</td
>
2612 <td
>4 min (
08:
04-
08:
08)
</td
>
2613 <td
>2 min
33%
</td
>
2617 <td
>Thinkpad X200 Roaming KDE
</td
>
2618 <td
>19 min (
09:
21-
09:
40)
</td
>
2619 <td
>15 min (
10:
25-
10:
40)
</td
>
2620 <td
>4 min
21%
</td
>
2623 </table
></p
>
2625 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2626 time is spent downloading packages. The connection to the Internet
2627 was
100Mbit/s during testing, so downloading should not be a
2628 significant factor in the measurement. Download typically took a few
2629 seconds to a few minutes, depending on the amount of packages being
2630 installed.
</p
>
2632 <p
>The speedup is implemented by using two hooks in
2633 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2634 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2635 finish-install.d hook to remove the divert at the end of the
2636 installation. I picked the pre-pkgsel.d hook instead of the
2637 post-base-installer.d hook because I test using an ISO without the
2638 eatmydata package included, and the post-base-installer.d hook in
2639 Debian Edu can only operate on packages included in the ISO. The
2640 negative effect of this is that I am unable to activate this
2641 optimization for the kernel installation step in d-i. If the code is
2642 moved to the post-base-installer.d hook, the speedup would be larger
2643 for the entire installation.
</p
>
2645 <p
>I
've implemented this in the
2646 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2647 git repository, and plan to provide the optimization as part of the
2648 Debian Edu installation. If you want to test this yourself, you can
2649 create two files in the installer (or in an udeb). One shell script
2650 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2652 <p
><blockquote
><pre
>
2655 . /usr/share/debconf/confmodule
2657 logger -t my-pkgsel
"info: $*
"
2660 logger -t my-pkgsel
"error: $*
"
2662 override_install() {
2663 apt-install eatmydata || true
2664 if [ -x /target/usr/bin/eatmydata ] ; then
2665 for bin in dpkg apt-get aptitude tasksel ; do
2667 # Test that the file exist and have not been diverted already.
2668 if [ -f /target$file ] ; then
2669 info
"diverting $file using eatmydata
"
2670 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2671 > /target$file.edu
2672 chmod
755 /target$file.edu
2673 in-target dpkg-divert --package debian-edu-config \
2674 --rename --quiet --add $file
2675 ln -sf ./$bin.edu /target$file
2677 error
"unable to divert $file, as it is missing.
"
2681 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2686 </pre
></blockquote
></p
>
2688 <p
>To clean up, another shell script should go into
2689 /usr/lib/finish-install.d/ with code like this:
2691 <p
><blockquote
><pre
>
2693 . /usr/share/debconf/confmodule
2695 logger -t my-finish-install
"error: $@
"
2697 remove_install_override() {
2698 for bin in dpkg apt-get aptitude tasksel ; do
2700 if [ -x /target$file.edu ] ; then
2702 in-target dpkg-divert --package debian-edu-config \
2703 --rename --quiet --remove $file
2706 error
"Missing divert for $file.
"
2709 sync # Flush file buffers before continuing
2712 remove_install_override
2713 </pre
></blockquote
></p
>
2715 <p
>In Debian Edu, I placed both code fragments in a separate script
2716 edu-eatmydata-install and call it from the pre-pkgsel.d and
2717 finish-install.d scripts.
</p
>
2719 <p
>By now you might ask if this change should get into the normal
2720 Debian installer too? I suspect it should, but am not sure the
2721 current debian-installer coordinators find it useful enough. It also
2722 depend on the side effects of the change. I
'm not aware of any, but I
2723 guess we will see if the change is safe after some more testing.
2724 Perhaps there is some package in Debian depending on sync() and
2725 fsync() having effect? Perhaps it should go into its own udeb, to
2726 allow those of us wanting to enable it to do so without affecting
2729 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2730 will break installation of all programs using gnutls because of
2731 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2732 eatmydata package in Debian will solve it.
</p
>
2734 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2735 the optimization work again. And I have discovered that the
2736 dpkg-divert trick is not really needed and implemented a slightly
2737 simpler approach as part of the debian-edu-install package. See
2738 tools/edu-eatmydata-install in the source package.
</p
>
2740 <p
>Update
2014-
11-
11: Unfortunately, a new
2741 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2742 triggering on i386 made it into testing, and broke this installation
2743 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2744 request
768893</a
> is accepted, it should be working again.
</p
>
2749 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2750 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2752 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2753 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2754 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2755 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2756 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2757 learn that there is a large set of publicly available key servers to
2758 use when looking for peoples public key. So far I have used
2759 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2760 were misbehaving, but those days are ended. The servers I have used
2761 up until yesterday have been slow and some times unavailable. I hope
2762 those problems are gone now.
</p
>
2764 <p
>Behind the round robin DNS entry of the
2765 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2766 there is a pool of more than
100 keyservers which are checked every
2767 day to ensure they are well connected and up to date. It must be
2768 better than what I have used so far. :)
</p
>
2770 <p
>Yesterdays speaker told me that the service is the default
2771 keyserver provided by the default configuration in GnuPG, but this do
2772 not seem to be used in Debian. Perhaps it should?
</p
>
2774 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2777 <p
><blockquote
><pre
>
2778 keyserver pool.sks-keyservers.net
2779 </pre
></blockquote
></p
>
2781 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2782 entries in DNS. Just for fun, I did just that at work, so now every
2783 user of GnuPG at the University of Oslo should find a OpenGPG
2784 keyserver automatically should their need it:
</p
>
2786 <p
><blockquote
><pre
>
2787 % host -t srv _pgpkey-http._tcp.uio.no
2788 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2790 </pre
></blockquote
></p
>
2792 <p
>Now if only
2793 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2794 HKP lookup protocol
</a
> supported finding signature paths, I would be
2795 very happy. It can look up a given key or search for a user ID, but I
2796 normally do not want that, but to find a trust path from my key to
2797 another key. Given a user ID or key ID, I would like to find (and
2798 download) the keys representing a signature path from my key to the
2799 key in question, to be able to get a trust path between the two keys.
2800 This is as far as I can tell not possible today. Perhaps something
2801 for a future version of the protocol?
</p
>
2806 <title>From English wiki to translated PDF and epub via Docbook
</title>
2807 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2808 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2809 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2810 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2811 project
</a
> provide an instruction manual for teachers, system
2812 administrators and other users that contain useful tips for setting up
2813 and maintaining a Debian Edu installation. This text is about how the
2814 text processing of this manual is handled in the project.
</p
>
2816 <p
>One goal of the project is to provide information in the native
2817 language of its users, and for this we need to handle translations.
2818 But we also want to make sure each language contain the same
2819 information, so for this we need a good way to keep the translations
2820 in sync. And we want it to be easy for our users to improve the
2821 documentation, avoiding the need to learn special formats or tools to
2822 contribute, and the obvious way to do this is to make it possible to
2823 edit the documentation using a web browser. We also want it to be
2824 easy for translators to keep the translation up to date, and give them
2825 help in figuring out what need to be translated. Here is the list of
2826 tools and the process we have found trying to reach all these
2829 <p
>We maintain the authoritative source of our manual in the
2830 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2831 wiki
</a
>, as several wiki pages written in English. It consist of one
2832 front page with references to the different chapters, several pages
2833 for each chapter, and finally one
"collection page
" gluing all the
2834 chapters together into one large web page (aka
2835 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2836 AllInOne page
</a
>). The AllInOne page is the one used for further
2837 processing and translations. Thanks to the fact that the
2838 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2839 wiki.debian.org support exporting pages in
2840 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2841 the list of pages to export using the raw version of the AllInOne
2842 page, loop over each of them to generate a Docbook XML version of the
2843 manual. This process also download images and transform image
2844 references to use the locally downloaded images. The generated
2845 Docbook XML files are slightly broken, so some post-processing is done
2846 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2847 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2848 a handfull of images. The XML file can now be used to generate PDF, HTML
2849 and epub versions of the English manual. This is the basic step of
2850 our process, making PDF (using dblatex), HTML (using xsltproc) and
2851 epub (using dbtoepub) version from Docbook XML, and the resulting files
2852 are placed in the debian-edu-doc-en binary package.
</p
>
2854 <p
>But English documentation is not enough for us. We want translated
2855 documentation too, and we want to make it easy for translators to
2856 track the English original. For this we use the
2857 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2858 which allow us to transform the English Docbook XML file into a
2859 translation file (a .pot file), usable with the normal gettext based
2860 translation tools used by those translating free software. The pot
2861 file is used to create and maintain translation files (several .po
2862 files), which the translations update with the native language
2863 translations of all titles, paragraphs and blocks of text in the
2864 original. The next step is combining the original English Docbook XML
2865 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2866 create a translated Docbook XML file (in this case
2867 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2868 translated, if the translation is not complete) Docbook XML file can
2869 then be used like the original to create a PDF, HTML and epub version
2870 of the documentation.
</p
>
2872 <p
>The translators use different tools to edit the .po files. We
2874 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2875 while some use emacs and vi, others can use web based editors like
2876 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2877 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2878 is where the .po file end up, in our git repository. Updated
2879 translations can either be committed directly to git, or submitted as
2880 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2881 against the debian-edu-doc package
</a
>.
</p
>
2883 <p
>One challenge is images, which both might need to be translated (if
2884 they show translated user applications), and are needed in different
2885 formats when creating PDF and HTML versions (epub is a HTML version in
2886 this regard). For this we transform the original PNG images to the
2887 needed density and format during build, and have a way to provide
2888 translated images by storing translated versions in
2889 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2890 package maintainers know more.
</p
>
2892 <p
>If you wonder what the result look like, we provide
2893 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2894 of the documentation packages on the web
</a
>. See for example the
2895 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2896 PDF version
</a
> or the
2897 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2898 HTML version
</a
>. We do not yet build the epub version by default,
2899 but perhaps it will be done in the future.
</p
>
2901 <p
>To learn more, check out
2902 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2903 debian-edu-doc package
</a
>,
2904 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2905 manual on the wiki
</a
> and
2906 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2907 translation instructions
</a
> in the manual.
</p
>
2912 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2913 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2915 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2916 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2917 related packages relevant for the computer installed automatically.
2918 So I implemented one, using
2919 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2920 package
</a
>. To use it, install the tasksel and isenkram packages and
2921 run tasksel as user root. You should be presented with a new option,
2922 "Hardware specific packages (autodetected by isenkram)
". When you
2923 select it, tasksel will install the packages isenkram claim is fit for
2924 the current hardware, hot pluggable or not.
<p
>
2926 <p
>The implementation is in two files, one is the tasksel menu entry
2927 description, and the other is the script used to extract the list of
2928 packages to install. The first part is in
2929 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2932 <p
><blockquote
><pre
>
2935 Description: Hardware specific packages (autodetected by isenkram)
2936 Based on the detected hardware various hardware specific packages are
2938 Test-new-install: mark show
2940 Packages: for-current-hardware
2941 </pre
></blockquote
></p
>
2943 <p
>The second part is in
2944 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2947 <p
><blockquote
><pre
>
2952 isenkram-autoinstall-firmware -l
2954 </pre
></blockquote
></p
>
2956 <p
>All in all, a very short and simple implementation making it
2957 trivial to install the hardware dependent package we all may want to
2958 have installed on our machines. I
've not been able to find a way to
2959 get tasksel to tell you exactly which packages it plan to install
2960 before doing the installation. So if you are curious or careful,
2961 check the output from the isenkram-* command line tools first.
</p
>
2963 <p
>The information about which packages are handling which hardware is
2964 fetched either from the isenkram package itself in
2965 /usr/share/isenkram/, from git.debian.org or from the APT package
2966 database (using the Modaliases header). The APT package database
2967 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2968 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2969 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2970 the python-apt code (bug
2971 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2972 workaround I was able to get rid of the file descriptor leak and
2973 reduce the memory leak from ~
30 MiB per hardware detection down to
2974 around
2 MiB per hardware detection. It should make the desktop
2975 daemon a lot more useful. The fix is in version
0.7 uploaded to
2976 unstable today.
</p
>
2978 <p
>I believe the current way of mapping hardware to packages in
2979 Isenkram is is a good draft, but in the future I expect isenkram to
2980 use the AppStream data source for this. A proposal for getting proper
2981 AppStream support into Debian is floating around as
2982 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2983 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2984 project
</a
> will take place this summer to improve the situation. I
2985 look forward to seeing the result, and welcome patches for isenkram to
2986 start using the information when it is ready.
</p
>
2988 <p
>If you want your package to map to some specific hardware, either
2989 add a
"Xb-Modaliases
" header to your control file like I did in
2990 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2991 package
</a
> or submit a bug report with the details to the isenkram
2993 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2994 blog posts tagged isenkram
</a
> for details on the notation. I expect
2995 the information will be migrated to AppStream eventually, but for the
2996 moment I got no better place to store it.
</p
>
3001 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3002 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3004 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3005 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3006 project
</a
> is working on providing the software and hardware to make
3007 it easy for non-technical people to host their data and communication
3008 at home, and being able to communicate with their friends and family
3009 encrypted and away from prying eyes. It is still going strong, and
3010 today a major mile stone was reached.
</p
>
3012 <p
>Today, the last of the packages currently used by the project to
3013 created the system images were accepted into Debian Unstable. It was
3014 the freedombox-setup package, which is used to configure the images
3015 during build and on the first boot. Now all one need to get going is
3016 the build code from the freedom-maker git repository and packages from
3017 Debian. And once the freedombox-setup package enter testing, we can
3018 build everything directly from Debian. :)
</p
>
3020 <p
>Some key packages used by Freedombox are
3021 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3022 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3023 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3024 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3025 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3026 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3027 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3028 are plans to integrate more packages into the setup. User
3029 documentation is maintained on the Debian wiki. Please
3030 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3031 the manual
</a
> and help us improve it.
</p
>
3033 <p
>To test for yourself and create boot images with the FreedomBox
3034 setup, run this on a Debian machine using a user with sudo rights to
3035 become root:
</p
>
3037 <p
><pre
>
3038 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3039 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3041 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3043 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3044 </pre
></p
>
3046 <p
>Root access is needed to run debootstrap and mount loopback
3047 devices. See the README in the freedom-maker git repo for more
3048 details on the build. If you do not want all three images, trim the
3049 make line. Note that the virtualbox-image target is not really
3050 virtualbox specific. It create a x86 image usable in kvm, qemu,
3051 vmware and any other x86 virtual machine environment. You might need
3052 the version of vmdebootstrap in Jessie to get the build working, as it
3053 include fixes for a race condition with kpartx.
</p
>
3055 <p
>If you instead want to install using a Debian CD and the preseed
3056 method, boot a Debian Wheezy ISO and use this boot argument to load
3057 the preseed values:
</p
>
3059 <p
><pre
>
3060 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3061 </pre
></p
>
3063 <p
>I have not tested it myself the last few weeks, so I do not know if
3064 it still work.
</p
>
3066 <p
>If you wonder how to help, one task you could look at is using
3067 systemd as the boot system. It will become the default for Linux in
3068 Jessie, so we need to make sure it is usable on the Freedombox. I did
3069 a simple test a few weeks ago, and noticed dnsmasq failed to start
3070 during boot when using systemd. I suspect there are other problems
3071 too. :) To detect problems, there is a test suite included, which can
3072 be run from the plinth web interface.
</p
>
3074 <p
>Give it a go and let us know how it goes on the mailing list, and help
3075 us get the new release published. :) Please join us on
3076 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3077 irc.debian.org)
</a
> and
3078 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3079 mailing list
</a
> if you want to help make this vision come true.
</p
>
3084 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3085 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3086 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3087 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3088 <description><p
>For a while now, I have been looking for a sensible offsite backup
3089 solution for use at home. My requirements are simple, it must be
3090 cheap and locally encrypted (in other words, I keep the encryption
3091 keys, the storage provider do not have access to my private files).
3092 One idea me and my friends had many years ago, before the cloud
3093 storage providers showed up, was to use Google mail as storage,
3094 writing a Linux block device storing blocks as emails in the mail
3095 service provided by Google, and thus get heaps of free space. On top
3096 of this one can add encryption, RAID and volume management to have
3097 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3098 I never found time to implement such system. But the last few weeks I
3099 have looked at a system called
3100 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3101 mounted network backed file system with the features I need.
</p
>
3103 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3104 handling several different storage providers, any with Amazon S3,
3105 Google Drive or OpenStack API. There are heaps of such storage
3106 providers. S3QL can also use a local directory as storage, which
3107 combined with sshfs allow for file storage on any ssh server. S3QL
3108 include support for encryption, compression, de-duplication, snapshots
3109 and immutable file systems, allowing me to mount the remote storage as
3110 a local mount point, look at and use the files as if they were local,
3111 while the content is stored in the cloud as well. This allow me to
3112 have a backup that should survive fire. The file system can not be
3113 shared between several machines at the same time, as only one can
3114 mount it at the time, but any machine with the encryption key and
3115 access to the storage service can mount it if it is unmounted.
</p
>
3117 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3118 package is included already. So to get started, run
<tt
>apt-get
3119 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3120 Greenqloud, after reading their nice recipe on
3121 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3122 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3123 in Iceland more than those in USA when it come to keeping my personal
3124 data safe and private, and thus would rather spend money on a company
3125 in Iceland. Another nice recipe is available from the article
3126 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3127 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3128 Admin magazine. When the provider is picked, figure out how to get
3129 the API key needed to connect to the storage API. With Greencloud,
3130 the key did not show up until I had added payment details to my
3133 <p
>Armed with the API access details, it is time to create the file
3134 system. First, create a new bucket in the cloud. This bucket is the
3135 file system storage area. I picked a bucket name reflecting the
3136 machine that was going to store data there, but any name will do.
3137 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3138 the API login and password, and a locally created password. Store it
3139 all in ~root/.s3ql/authinfo2 like this:
3141 <p
><blockquote
><pre
>
3143 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3144 backend-login: API-login
3145 backend-password: API-password
3146 fs-passphrase: local-password
3147 </pre
></blockquote
></p
>
3149 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3150 but any sensible way to create a fairly random password should do it.
3151 Armed with these details, it is now time to run mkfs, entering the API
3152 details and password to create it:
</p
>
3154 <p
><blockquote
><pre
>
3155 # mkdir -m
700 /var/lib/s3ql-cache
3156 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3157 --ssl s3c://s.greenqloud.com:
443/bucket-name
3158 Enter backend login:
3159 Enter backend password:
3160 Before using S3QL, make sure to read the user
's guide, especially
3161 the
'Important Rules to Avoid Loosing Data
' section.
3162 Enter encryption password:
3163 Confirm encryption password:
3164 Generating random encryption key...
3165 Creating metadata tables...
3175 Compressing and uploading metadata...
3176 Wrote
0.00 MB of compressed metadata.
3177 #
</pre
></blockquote
></p
>
3179 <p
>The next step is mounting the file system to make the storage available.
3181 <p
><blockquote
><pre
>
3182 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3183 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3184 Using
4 upload threads.
3185 Downloading and decompressing metadata...
3195 Mounting filesystem...
3197 Filesystem Size Used Avail Use% Mounted on
3198 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3200 </pre
></blockquote
></p
>
3202 <p
>The file system is now ready for use. I use rsync to store my
3203 backups in it, and as the metadata used by rsync is downloaded at
3204 mount time, no network traffic (and storage cost) is triggered by
3205 running rsync. To unmount, one should not use the normal umount
3206 command, as this will not flush the cache to the cloud storage, but
3207 instead running the umount.s3ql command like this:
3209 <p
><blockquote
><pre
>
3212 </pre
></blockquote
></p
>
3214 <p
>There is a fsck command available to check the file system and
3215 correct any problems detected. This can be used if the local server
3216 crashes while the file system is mounted, to reset the
"already
3217 mounted
" flag. This is what it look like when processing a working
3218 file system:
</p
>
3220 <p
><blockquote
><pre
>
3221 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3222 Using cached metadata.
3223 File system seems clean, checking anyway.
3224 Checking DB integrity...
3225 Creating temporary extra indices...
3226 Checking lost+found...
3227 Checking cached objects...
3228 Checking names (refcounts)...
3229 Checking contents (names)...
3230 Checking contents (inodes)...
3231 Checking contents (parent inodes)...
3232 Checking objects (reference counts)...
3233 Checking objects (backend)...
3234 ..processed
5000 objects so far..
3235 ..processed
10000 objects so far..
3236 ..processed
15000 objects so far..
3237 Checking objects (sizes)...
3238 Checking blocks (referenced objects)...
3239 Checking blocks (refcounts)...
3240 Checking inode-block mapping (blocks)...
3241 Checking inode-block mapping (inodes)...
3242 Checking inodes (refcounts)...
3243 Checking inodes (sizes)...
3244 Checking extended attributes (names)...
3245 Checking extended attributes (inodes)...
3246 Checking symlinks (inodes)...
3247 Checking directory reachability...
3248 Checking unix conventions...
3249 Checking referential integrity...
3250 Dropping temporary indices...
3251 Backing up old metadata...
3261 Compressing and uploading metadata...
3262 Wrote
0.89 MB of compressed metadata.
3264 </pre
></blockquote
></p
>
3266 <p
>Thanks to the cache, working on files that fit in the cache is very
3267 quick, about the same speed as local file access. Uploading large
3268 amount of data is to me limited by the bandwidth out of and into my
3269 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3270 which is very close to my upload speed, and downloading the same
3271 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3272 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3273 network, not the file system code. I do not know what a good cache
3274 size would be, but suspect that the cache should e larger than your
3275 working set.
</p
>
3277 <p
>I mentioned that only one machine can mount the file system at the
3278 time. If another machine try, it is told that the file system is
3281 <p
><blockquote
><pre
>
3282 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3283 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3284 Using
8 upload threads.
3285 Backend reports that fs is still mounted elsewhere, aborting.
3287 </pre
></blockquote
></p
>
3289 <p
>The file content is uploaded when the cache is full, while the
3290 metadata is uploaded once every
24 hour by default. To ensure the
3291 file system content is flushed to the cloud, one can either umount the
3292 file system, or ask S3QL to flush the cache and metadata using
3295 <p
><blockquote
><pre
>
3296 # s3qlctrl upload-meta /s3ql
3297 # s3qlctrl flushcache /s3ql
3299 </pre
></blockquote
></p
>
3301 <p
>If you are curious about how much space your data uses in the
3302 cloud, and how much compression and deduplication cut down on the
3303 storage usage, you can use s3qlstat on the mounted file system to get
3306 <p
><blockquote
><pre
>
3308 Directory entries:
9141
3311 Total data size:
22049.38 MB
3312 After de-duplication:
21955.46 MB (
99.57% of total)
3313 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3314 Database size:
2.39 MB (uncompressed)
3315 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3317 </pre
></blockquote
></p
>
3319 <p
>I mentioned earlier that there are several possible suppliers of
3320 storage. I did not try to locate them all, but am aware of at least
3321 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3322 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3323 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3324 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3325 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3326 accept payment in Bitcoin. Pick one that suit your need. Some of
3327 them provide several GiB of free storage, but the prize models are
3328 quite different and you will have to figure out what suits you
3331 <p
>While researching this blog post, I had a look at research papers
3332 and posters discussing the S3QL file system. There are several, which
3333 told me that the file system is getting a critical check by the
3334 science community and increased my confidence in using it. One nice
3336 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3337 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3338 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3339 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3340 and Pamela Smith. Please have a look.
</p
>
3342 <p
>Given my problems with different file systems earlier, I decided to
3343 check out the mounted S3QL file system to see if it would be usable as
3344 a home directory (in other word, that it provided POSIX semantics when
3345 it come to locking and umask handling etc). Running
3346 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3347 test code to check file system semantics
</a
>, I was happy to discover that
3348 no error was found. So the file system can be used for home
3349 directories, if one chooses to do so.
</p
>
3351 <p
>If you do not want a locally file system, and want something that
3352 work without the Linux fuse file system, I would like to mention the
3353 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3354 provide locally encrypted backup using a command line client. It have
3355 a nicer access control system, where one can split out read and write
3356 access, allowing some systems to write to the backup and others to
3357 only read from it.
</p
>
3359 <p
>As usual, if you use Bitcoin and want to show your support of my
3360 activities, please send Bitcoin donations to my address
3361 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3366 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3367 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3369 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3370 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3371 project
</a
> is working on providing the software and hardware for
3372 making it easy for non-technical people to host their data and
3373 communication at home, and being able to communicate with their
3374 friends and family encrypted and away from prying eyes. It has been
3375 going on for a while, and is slowly progressing towards a new test
3376 release (
0.2).
</p
>
3378 <p
>And what day could be better than the Pi day to announce that the
3379 new version will provide
"hard drive
" / SD card / USB stick images for
3380 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3381 system), and can also be installed using a Debian installer preseed
3382 file. The Debian based Freedombox is now based on Debian Jessie,
3383 where most of the needed packages used are already present. Only one,
3384 the freedombox-setup package, is missing. To try to build your own
3385 boot image to test the current status, fetch the freedom-maker scripts
3387 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3388 with a user with sudo access to become root:
3391 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3393 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3394 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3396 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3399 <p
>Root access is needed to run debootstrap and mount loopback
3400 devices. See the README for more details on the build. If you do not
3401 want all three images, trim the make line. But note that thanks to
<a
3402 href=
"https://bugs.debian.org/
741407">a race condition in
3403 vmdebootstrap
</a
>, the build might fail without the patch to the
3404 kpartx call.
</p
>
3406 <p
>If you instead want to install using a Debian CD and the preseed
3407 method, boot a Debian Wheezy ISO and use this boot argument to load
3408 the preseed values:
</p
>
3411 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3414 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3415 recently introduced bug in apt in Jessie
</a
>, the installer will
3416 currently hang while setting up APT sources. Killing the
3417 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3418 installation will get the installation going. This affect all
3419 installations in Jessie, and I expect it will be fixed soon.
</p
>
3421 <p
>Give it a go and let us know how it goes on the mailing list, and help
3422 us get the new release published. :) Please join us on
3423 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3424 irc.debian.org)
</a
> and
3425 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3426 mailing list
</a
> if you want to help make this vision come true.
</p
>
3431 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3432 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3434 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3435 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3436 innetgr tools, because I needed them in
3437 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3438 ng-utils, and it has served me well. I placed the project under the
3439 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3440 repository. But many years ago, the CVS repository was dropped (lost,
3441 not migrated to new hardware, not sure), and the project have lacked a
3442 proper home since then.
</p
>
3444 <p
>Last summer, I had a look at the package and made a new release
3445 fixing a irritating crash bug, but was unable to store the changes in
3446 a proper source control system. I applied for a project on
3447 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3448 to follow up on it. Until today. :)
</p
>
3450 <p
>After many hours of cleaning and migration, the ng-utils project
3451 now have a new home, and a git repository with the highlight of the
3452 history of the project. I published all release tarballs and imported
3453 them into the git repository. As the project is really stable and not
3454 expected to gain new features any time soon, I decided to make a new
3455 release and call it
1.0. Visit the new project home on
3456 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3457 if you want to check it out. The new version is also uploaded into
3458 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3463 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3464 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3465 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3466 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3467 <description><p
>A few days ago I decided to try to help the Hurd people to get
3468 their changes into sysvinit, to allow them to use the normal sysvinit
3469 boot system instead of their old one. This follow up on the
3470 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3471 Google Summer of Code work
</a
> done last summer by Justus Winter to
3472 get Debian on Hurd working more like Debian on Linux. To get started,
3473 I downloaded a prebuilt hard disk image from
3474 <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
>,
3475 and started it using virt-manager.
</p
>
3477 <p
>The first think I had to do after logging in (root without any
3478 password) was to get the network operational. I followed
3479 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3480 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3481 commands as root to get the machine to accept a IP address from the
3482 kvm internal DHCP server:
</p
>
3484 <p
><blockquote
><pre
>
3485 settrans -fgap /dev/netdde /hurd/netdde
3486 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3487 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3489 </pre
></blockquote
></p
>
3491 <p
>After this, the machine had internet connectivity, and I could
3492 upgrade it and install the sysvinit packages from experimental and
3493 enable it as the default boot system in Hurd.
</p
>
3495 <p
>But before I did that, I set a password on the root user, as ssh is
3496 running on the machine it for ssh login to work a password need to be
3497 set. Also, note that a bug somewhere in openssh on Hurd block
3498 compression from working. Remember to turn that off on the client
3501 <p
>Run these commands as root to upgrade and test the new sysvinit
3504 <p
><blockquote
><pre
>
3505 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3506 deb http://http.debian.net/debian/ experimental main
3509 apt-get dist-upgrade
3510 apt-get install -t experimental initscripts sysv-rc sysvinit \
3511 sysvinit-core sysvinit-utils
3512 update-alternatives --config runsystem
3513 </pre
></blockquote
></p
>
3515 <p
>To reboot after switching boot system, you have to use
3516 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3517 yet a sysvinit process able to receive the signals from the normal
3518 'reboot
' command. After switching to sysvinit as the boot system,
3519 upgrading every package and rebooting, the network come up with DHCP
3520 after boot as it should, and the settrans/pkill hack mentioned at the
3521 start is no longer needed. But for some strange reason, there are no
3522 longer any login prompt in the virtual console, so I logged in using
3525 <p
>Note that there are some race conditions in Hurd making the boot
3526 fail some times. No idea what the cause is, but hope the Hurd porters
3527 figure it out. At least Justus said on IRC (#debian-hurd on
3528 irc.debian.org) that they are aware of the problem. A way to reduce
3529 the impact is to upgrade to the Hurd packages built by Justus by
3530 adding this repository to the machine:
</p
>
3532 <p
><blockquote
><pre
>
3533 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3534 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3536 </pre
></blockquote
></p
>
3538 <p
>At the moment the prebuilt virtual machine get some packages from
3539 http://ftp.debian-ports.org/debian, because some of the packages in
3540 unstable do not yet include the required patches that are lingering in
3541 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3543 <p
><blockquote
><pre
>
3544 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3545 i emacs - GNU Emacs editor (metapackage)
3546 i gdb - GNU Debugger
3547 i hurd-recommended - Miscellaneous translators
3548 i isc-dhcp-client - ISC DHCP client
3549 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3550 i libc-bin - Embedded GNU C Library: Binaries
3551 i libc-dev-bin - Embedded GNU C Library: Development binaries
3552 i libc0.3 - Embedded GNU C Library: Shared libraries
3553 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3554 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3555 i multiarch-support - Transitional package to ensure multiarch compatibilit
3556 i A x11-common - X Window System (X.Org) infrastructure
3557 i xorg - X.Org X Window System
3558 i A xserver-xorg - X.Org X server
3559 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3561 </pre
></blockquote
></p
>
3563 <p
>All in all, testing hurd has been an interesting experience. :)
3564 X.org did not work out of the box and I never took the time to follow
3565 the porters instructions to fix it. This time I was interested in the
3566 command line stuff.
<p
>
3571 <title>New chrpath release
0.16</title>
3572 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3573 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3574 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3575 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3576 find problems in C, C++ and Java code using static source code
3577 analysis. It can detect a lot of different problems, and is very
3578 useful to find memory and locking bugs in the error handling part of
3579 the source. The company behind it provide
3580 <a href=
"https://scan.coverity.com/
">check of free software projects as
3581 a community service
</a
>, and many hundred free software projects are
3582 already checked. A few days ago I decided to have a closer look at
3583 the Coverity system, and discovered that the
3584 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3585 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3586 projects I am involved with was already registered. But these are
3587 fairly big, and I would also like to have a small and easy project to
3588 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3589 checking of the chrpath project
</a
>. It was
3590 added to the checker and discovered seven potential defects. Six of
3591 these were real, mostly resource
"leak
" when the program detected an
3592 error. Nothing serious, as the resources would be released a fraction
3593 of a second later when the program exited because of the error, but it
3594 is nice to do it right in case the source of the program some time in
3595 the future end up in a library. Having fixed all defects and added
3596 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3597 mailing list for the chrpath developers
</a
>, I decided it was time to
3598 publish a new release. These are the release notes:
</p
>
3600 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3604 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3605 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3606 <li
>Mention new project mailing list in the documentation.
</li
>
3611 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3612 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3613 project if something is wrong with the new release. The test suite
3614 did not discover any old errors, so if you find a new one, please also
3615 include a test suite check.
</p
>
3620 <title>New chrpath release
0.15</title>
3621 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3623 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3624 <description><p
>After many years break from the package and a vain hope that
3625 development would be continued by someone else, I finally pulled my
3626 acts together this morning and wrapped up a new release of chrpath,
3627 the command line tool to modify the rpath and runpath of already
3628 compiled ELF programs. The update was triggered by the persistence of
3629 Isha Vishnoi at IBM, which needed a new config.guess file to get
3630 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3631 is working on. I checked the
3632 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3633 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3634 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3635 packages for interesting patches (failed to find the source from
3636 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3637 These are the release notes:
</p
>
3639 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3643 <li
>Updated config.sub and config.guess from the GNU project to work
3644 with newer architectures. Thanks to isha vishnoi for the heads
3647 <li
>Updated README with current URLs.
</li
>
3649 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3650 Matthias Klose.
</li
>
3652 <li
>Added missing help for -k|--keepgoing option, using patch by
3653 Petr Machata found in Fedora.
</li
>
3655 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3656 .dynamic is a NULL terminated string. Based on patch found in
3657 Fedora credited Axel Thimm and Christian Krause.
</li
>
3662 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3663 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3664 project if something is wrong with the new release. The test suite
3665 did not discover any old errors, so if you find a new one, please also
3666 include a testsuite check.
</p
>
3671 <title>Debian init.d boot script example for rsyslog
</title>
3672 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3673 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3674 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3675 <description><p
>If one of the points of switching to a new init system in Debian is
3676 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3677 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3678 init.d scripts at all. Here is an example init.d script, ie a rewrite
3679 of /etc/init.d/rsyslog:
</p
>
3681 <p
><pre
>
3682 #!/lib/init/init-d-script
3685 # Required-Start: $remote_fs $time
3686 # Required-Stop: umountnfs $time
3687 # X-Stop-After: sendsigs
3688 # Default-Start:
2 3 4 5
3689 # Default-Stop:
0 1 6
3690 # Short-Description: enhanced syslogd
3691 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3692 # It is quite compatible to stock sysklogd and can be
3693 # used as a drop-in replacement.
3695 DESC=
"enhanced syslogd
"
3696 DAEMON=/usr/sbin/rsyslogd
3697 </pre
></p
>
3699 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3700 script was
137 lines, and the above is just
15 lines, most of it meta
3701 info/comments.
</p
>
3703 <p
>How to do this, you ask? Well, one create a new script
3704 /lib/init/init-d-script looking something like this:
3706 <p
><pre
>
3709 # Define LSB log_* functions.
3710 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3711 # and status_of_proc is working.
3712 . /lib/lsb/init-functions
3715 # Function that starts the daemon/service
3721 #
0 if daemon has been started
3722 #
1 if daemon was already running
3723 #
2 if daemon could not be started
3724 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3726 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3729 # Add code here, if necessary, that waits for the process to be ready
3730 # to handle requests from services started subsequently which depend
3731 # on this one. As a last resort, sleep for some time.
3735 # Function that stops the daemon/service
3740 #
0 if daemon has been stopped
3741 #
1 if daemon was already stopped
3742 #
2 if daemon could not be stopped
3743 # other if a failure occurred
3744 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3745 RETVAL=
"$?
"
3746 [
"$RETVAL
" =
2 ]
&& return
2
3747 # Wait for children to finish too if this is a daemon that forks
3748 # and if the daemon is only ever run from this initscript.
3749 # If the above conditions are not satisfied then add some other code
3750 # that waits for the process to drop all resources that could be
3751 # needed by services started subsequently. A last resort is to
3752 # sleep for some time.
3753 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3754 [
"$?
" =
2 ]
&& return
2
3755 # Many daemons don
't delete their pidfiles when they exit.
3757 return
"$RETVAL
"
3761 # Function that sends a SIGHUP to the daemon/service
3765 # If the daemon can reload its configuration without
3766 # restarting (for example, when it is sent a SIGHUP),
3767 # then implement that here.
3769 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3774 scriptbasename=
"$(basename $
1)
"
3775 echo
"SN: $scriptbasename
"
3776 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3777 script=
"$
1"
3784 NAME=$(basename $DAEMON)
3785 PIDFILE=/var/run/$NAME.pid
3787 # Exit if the package is not installed
3788 #[ -x
"$DAEMON
" ] || exit
0
3790 # Read configuration variable file if it is present
3791 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3793 # Load the VERBOSE setting and other rcS variables
3796 case
"$
1" in
3798 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3800 case
"$?
" in
3801 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3802 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3806 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3808 case
"$?
" in
3809 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3810 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3814 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3816 #reload|force-reload)
3818 # If do_reload() is not implemented then leave this commented out
3819 # and leave
'force-reload
' as an alias for
'restart
'.
3821 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3825 restart|force-reload)
3827 # If the
"reload
" option is implemented then remove the
3828 #
'force-reload
' alias
3830 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3832 case
"$?
" in
3835 case
"$?
" in
3837 1) log_end_msg
1 ;; # Old process is still running
3838 *) log_end_msg
1 ;; # Failed to start
3848 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3854 </pre
></p
>
3856 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3857 lot. I did not really polish the approach, so it might not always
3858 work out of the box, but you get the idea. I did not try very hard to
3859 optimize it nor make it more robust either.
</p
>
3861 <p
>A better argument for switching init system in Debian than reducing
3862 the size of init scripts (which is a good thing to do anyway), is to
3863 get boot system that is able to handle the kernel events sensibly and
3864 robustly, and do not depend on the boot to run sequentially. The boot
3865 and the kernel have not behaved sequentially in years.
</p
>
3870 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3871 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3872 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3873 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3874 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3875 remote display access is the preferred solution with oVirt and RedHat
3876 Enterprise Virtualization, and I was sad to discover the other day
3877 that the browser plugin needed to use these systems seamlessly was
3878 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3879 for a package
</a
> was from
2012-
04-
10 with no progress since
3880 2013-
04-
01, so I decided to wrap up a package based on the great work
3881 from Cajus Pollmeier and put it in a collab-maint maintained git
3882 repository to get a package I could use. I would very much like
3883 others to help me maintain the package (or just take over, I do not
3884 mind), but as no-one had volunteered so far, I just uploaded it to
3885 NEW. I hope it will be available in Debian in a few days.
</p
>
3887 <p
>The source is now available from
3888 <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
>
3893 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3894 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3896 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3897 <description><p
>The
3898 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3899 program is a a very nice system to create virtual machine images. It
3900 create a image file, add a partition table, mount it and run
3901 debootstrap in the mounted directory to create a Debian system on a
3902 stick. Yesterday, I decided to try to teach it how to make images for
3903 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3904 of a plan to simplify the build system for
3905 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3906 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3907 the virtualbox images, but its current build system made multistrap
3908 based system for Dreamplug images, and it is lacking support for
3909 Raspberry Pi.
</p
>
3911 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3912 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3913 code and adjusted it to be able to build armel images on my amd64
3914 Debian laptop. I ended up giving vmdebootstrap five new options,
3915 allowing me to replicate the image creation process I use to make
3916 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3917 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3918 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3919 call debootstrap with --foreign and to copy the handler into the
3920 generated chroot before running the second stage. This allow
3921 vmdebootstrap to create armel images on an amd64 host. Next I added
3922 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3923 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3924 given file system type, allowing me to create an image with a vfat
3925 partition for the /boot/ stuff. I also added a
<tt
>--variant
3926 variant
</tt
> option to allow me to create smaller images without the
3927 Debian base system packages installed. Finally, I added an option
3928 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3929 as a boot loader. It is not needed on the Raspberry Pi and probably
3930 most other non-x86 architectures. The changes were accepted by the
3931 upstream author of vmdebootstrap yesterday and today, and is now
3933 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3934 upstream project page
</a
>.
</p
>
3936 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3937 create a small script (the customize script) to add the non-free
3938 binary blob needed to boot the Raspberry Pi and the APT source
3941 <p
><pre
>
3943 set -e # Exit on first error
3944 rootdir=
"$
1"
3945 cd
"$rootdir
"
3946 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3947 deb http://http.debian.net/debian/ jessie main contrib non-free
3949 # Install non-free binary blob needed to boot Raspberry Pi. This
3950 # install a kernel somewhere too.
3951 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3952 -O $rootdir/usr/bin/rpi-update
3953 chmod a+x $rootdir/usr/bin/rpi-update
3954 mkdir -p $rootdir/lib/modules
3955 touch $rootdir/boot/start.elf
3956 chroot $rootdir rpi-update
3957 </pre
></p
>
3959 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3960 to build the image:
</p
>
3963 sudo ./vmdebootstrap \
3966 --distribution jessie \
3967 --mirror http://http.debian.net/debian \
3976 --root-password raspberry \
3977 --hostname raspberrypi \
3978 --foreign /usr/bin/qemu-arm-static \
3979 --customize `pwd`/customize \
3981 --package git-core \
3982 --package binutils \
3983 --package ca-certificates \
3986 </pre
></p
>
3988 <p
>The list of packages being installed are the ones needed by
3989 rpi-update to make the image bootable on the Raspberry Pi, with the
3990 exception of netbase, which is needed by debootstrap to find
3991 /etc/hosts with the minbase variant. I really wish there was a way to
3992 set up an Raspberry Pi using only packages in the Debian archive, but
3993 that is not possible as far as I know, because it boots from the GPU
3994 using a non-free binary blob.
</p
>
3996 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3997 probably a few others installed. I have not checked the complete
3998 build dependency list.
</p
>
4000 <p
>The resulting image will not use the hardware floating point unit
4001 on the Raspberry PI, because the armel architecture in Debian is not
4002 optimized for that use. So the images created will be a bit slower
4003 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4008 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4009 <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>
4010 <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>
4011 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4012 <description><p
>The last few days I came across a few good causes that should get
4013 wider attention. I recommend signing and donating to each one of
4016 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4017 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4018 Women program which is a Google Summer of Code like initiative to get
4019 more women involved in free software. One debian sponsor has offered
4020 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4021 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4022 hope you will to. :)
</p
>
4024 <p
>And the Electronic Frontier Foundation just announced plans to
4025 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4026 documentaries about the excessive spying
</a
> on every Internet user that
4027 take place these days, and their need to fund the work. I
've already
4028 donated. Are you next?
</p
>
4030 <p
>For my Norwegian audience, the organisation Studentenes og
4031 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4032 statement under the heading
4033 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4034 Access
</a
> for those of us asking for more focus on open access in the
4035 Norwegian government. So far
499 signatures. I hope you will sign it
4041 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4042 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4043 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4044 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4045 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4046 project
</a
> have been going on for a while, and have presented the
4047 vision, ideas and solution several places. Here is a little
4048 collection of videos of talks and presentation of the project.
</p
>
4052 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4053 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4055 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4056 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4058 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4059 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4060 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4061 (Youtube)
</li
>
4063 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4064 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4066 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4067 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4069 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4070 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4071 York City in
2012</a
> (Youtube)
</li
>
4073 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4074 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4075 (Youtube)
</li
>
4077 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4078 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4080 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4081 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4083 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4084 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4085 2013</a
> (Youtube)
</li
>
4089 <p
>A larger list is available from
4090 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4091 Freedombox Wiki
</a
>.
</p
>
4093 <p
>On other news, I am happy to report that Freedombox based on Debian
4094 Jessie is coming along quite well, and soon both Owncloud and using
4095 Tor should be available for testers of the Freedombox solution. :) In
4096 a few weeks I hope everything needed to test it is included in Debian.
4097 The withsqlite package is already in Debian, and the plinth package is
4098 pending in NEW. The third and vital part of that puzzle is the
4099 metapackage/setup framework, which is still pending an upload. Join
4100 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4101 (#freedombox on irc.debian.org)
</a
> and
4102 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4103 mailing list
</a
> if you want to help make this vision come true.
</p
>
4108 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4109 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4111 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4112 <description><p
>I was introduced to the
4113 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4114 in
2010, when Eben Moglen presented his vision about serving the need
4115 of non-technical people to keep their personal information private and
4116 within the legal protection of their own homes. The idea is to give
4117 people back the power over their network and machines, and return
4118 Internet back to its intended peer-to-peer architecture. Instead of
4119 depending on a central service, the Freedombox will give everyone
4120 control over their own basic infrastructure.
</p
>
4122 <p
>I
've intended to join the effort since then, but other tasks have
4123 taken priority. But this summers nasty news about the misuse of trust
4124 and privilege exercised by the
"western
" intelligence gathering
4125 communities increased my eagerness to contribute to a point where I
4126 actually started working on the project a while back.
</p
>
4128 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4129 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4130 create a simple and cheap Debian based appliance that anyone can hook
4131 up in their home and get access to secure and private services and
4132 communication. The initial deployment platform have been the
4133 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4134 which is a piece of hardware I do not own. So to be able to test what
4135 the current Freedombox setup look like, I had to come up with a way to install
4136 it on some hardware I do have access to. I have rewritten the
4137 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4138 image build framework to use .deb packages instead of only copying
4139 setup into the boot images, and thanks to this rewrite I am able to
4140 set up any machine supported by Debian Wheezy as a Freedombox, using
4141 the previously mentioned deb (and a few support debs for packages
4142 missing in Debian).
</p
>
4144 <p
>The current Freedombox setup consist of a set of bootstrapping
4146 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4147 and a administrative web interface
4148 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4149 withsqlite), as well as a privacy enhancing proxy based on
4150 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4151 (freedombox-privoxy). There is also a web/javascript based XMPP
4152 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4153 trying (unsuccessfully so far) to talk to the XMPP server
4154 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4155 web interface is pluggable, and the goal is to use it to enable OpenID
4156 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4157 this is really working yet, see
4158 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4159 project TODO
</a
> for links to GIT repositories. Most of the code is
4160 on github at the moment. The HTTP proxy is operational out of the
4161 box, and the admin web interface can be used to add/remove plinth
4162 users. I
've not been able to do anything else with it so far, but
4163 know there are several branches spread around github and other places
4164 with lots of half baked features.
</p
>
4166 <p
>Anyway, if you want to have a look at the current state, the
4167 following recipes should work to give you a test machine to poke
4170 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4174 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4175 <li
>Boot from it, either as CD or USB stick.
</li
>
4176 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4177 to the Debian installer:
<p
>
4178 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4180 <li
>Answer the few language/region/password questions and pick disk to
4181 install on.
</li
>
4183 <li
>When the installation is finished and the machine have rebooted a
4184 few times, your Freedombox is ready for testing.
</li
>
4188 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4192 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4193 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4194 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4196 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4197 </pre
></li
>
4198 <li
><p
>Run this as root:
</p
>
4200 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4203 apt-get install freedombox-setup
4204 /usr/lib/freedombox/setup
4205 </pre
></li
>
4206 <li
>Reboot into your freshly created Freedombox.
</li
>
4210 <p
>You can test it on other architectures too, but because the
4211 freedombox-privoxy package is binary, it will only work as intended on
4212 the architectures where I have had time to build the binary and put it
4213 in my APT repository. But do not let this stop you. It is only a
4214 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4216 <p
>Note that by default Freedombox is a DHCP server on the
4217 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4218 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4219 disable
</tt
>" as root.
</p
>
4221 <p
>Please let me know if this works for you, or if you have any
4222 problems. We gather on the IRC channel
4223 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4224 irc.debian.org and the
4225 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4226 mailing list
</a
>.
</p
>
4228 <p
>Once you get your freedombox operational, you can visit
4229 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4230 welcome screen (dead end - do not be surprised if you are unable to
4231 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4232 to look at the rest of plinth. The default user is
'admin
' and the
4233 default password is
'secret
'.
</p
>
4238 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4239 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4241 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4242 <description><p
>Earlier, I reported about
4243 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4244 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4245 told by IBM that the original disk should be thrown away. And as
4246 there no longer was a problem if I bricked the firmware, I decided
4247 today to try to install Intel firmware to replace the Lenovo firmware
4248 currently on the disk.
</p
>
4250 <p
>I searched the Intel site for firmware, and found
4251 <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
>
4252 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4253 according to the site should contain the latest firmware for SSD
4254 disks. I inserted the broken disk in one of my spare laptops and
4255 booted the ISO from a USB stick. The disk was recognized, but the
4256 program claimed the newest firmware already were installed and refused
4257 to insert any Intel firmware. So no change, and the disk is still
4258 unable to handle write load. :( I guess the only way to get them
4259 working would be if Lenovo releases new firmware. No idea how likely
4260 that is. Anyway, just blogging about this test for completeness. I
4261 got a working Samsung disk, and see no point in spending more time on
4262 the broken disks.
</p
>
4267 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4268 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4270 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4271 <description><p
>Today I switched to
4272 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4273 new laptop
</a
>. I
've previously written about the problems I had with
4274 my new Thinkpad X230, which was delivered with an
4275 <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
4276 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4277 sustained writes. My hardware supplier have been very forthcoming in
4278 trying to find a solution, and after first trying with another
4279 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4280 disk instead to fix it once and for all. The Samsung disk survived
4281 the installation of Debian with encrypted disks (filling the disk with
4282 random data during installation killed the first two), and I thus
4283 decided to trust it with my data. I have installed it as a Debian Edu
4284 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4285 server at home using Kerberos and LDAP, and will use it as my work
4286 station from now on.
</p
>
4288 <p
>As this is a solid state disk with no moving parts, I believe the
4289 Debian Wheezy default installation need to be tuned a bit to increase
4290 performance and increase life time of the disk. The Linux kernel and
4291 user space applications do not yet adjust automatically to such
4292 environment. To make it easier for my self, I created a draft Debian
4293 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4294 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4295 for the ssd-setup package
</a
> is available from collab-maint, and it
4296 is set up to adjust the setup of the machine by just installing the
4297 package. If there is any non-SSD disk in the machine, the package
4298 will refuse to install, as I did not try to write any logic to sort
4299 file systems in SSD and non-SSD file systems.
</p
>
4301 <p
>I consider the package a draft, as I am a bit unsure how to best
4302 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4303 where I set up the machine with one large encrypted partition (in
4304 addition to /boot), put LVM on top of this and set up partitions on
4305 top of this again. See the README file in the package source for the
4306 references I used to pick the settings. At the moment these
4307 parameters are tuned:
</p
>
4311 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4312 (adding discard to /etc/crypttab)
</li
>
4314 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4315 this case a cryptsetup partition) by changing issue_discards from
4316 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4318 <li
>Set relatime as a file system option for ext3 and ext4 file
4321 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4322 /etc/fstab.
</li
>
4324 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4326 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4327 cron.daily).
</li
>
4329 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4330 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4334 <p
>During installation, I cancelled the part where the installer fill
4335 the disk with random data, as this would kill the SSD performance for
4336 little gain. My goal with the encrypted file system is to ensure
4337 those stealing my laptop end up with a brick and not a working
4338 computer. I have no hope in keeping the really resourceful people
4339 from getting the data on the disk (see
4340 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4341 Thus I concluded that adding the discard option to crypttab is the
4342 right thing to do.
</p
>
4344 <p
>I considered using the noop I/O scheduler, as several recommended
4345 it for SSD, but others recommended deadline and a benchmark I found
4346 indicated that deadline might be better for interactive use.
</p
>
4348 <p
>I also considered using the
'discard
' file system option for ext3
4349 and ext4, but read that it would give a performance hit ever time a
4350 file is removed, and thought it best to that that slowdown once a day
4351 instead of during my work.
</p
>
4353 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4354 this is already done by Debian Edu.
</p
>
4356 <p
>I have not yet started on the user space tuning. I expect
4357 iceweasel need some tuning, and perhaps other applications too, but
4358 have not yet had time to investigate those parts.
</p
>
4360 <p
>The package should work on Ubuntu too, but I have not yet tested it
4363 <p
>As for the answer to the question in the title of this blog post,
4364 as far as I know, the only solution I know about is to replace the
4365 disk. It might be possible to flash it with Intel firmware instead of
4366 the Lenovo firmware. But I have not tried and did not want to do so
4367 without approval from Lenovo as I wanted to keep the warranty on the
4368 disk until a solution was found and they wanted the broken disks
4374 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4375 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4376 <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>
4377 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4378 <description><p
>A few days ago, I wrote about
4379 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4380 problems I experienced with my new X230 and its SSD disk
</a
>, which
4381 was dying during installation because it is unable to cope with
4382 sustained write. My supplier is in contact with
4383 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4384 replacement disk to try to fix the problem. They decided to send an
4385 identical model, so my hopes for a permanent fix was slim.
</p
>
4387 <p
>Anyway, today I got the replacement disk and tried to install
4388 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4389 same firmware version as the original. This time my hope raised
4390 slightly as the installation progressed, as the original disk used to
4391 die after
4-
7% of the disk was written to, while this time it kept
4392 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4393 died again and I was back on square one. I still do not have a new
4394 laptop with a disk I can trust. I can not live with a disk that might
4395 lock up when I download a new
4396 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4397 other large files. I look forward to hearing from my supplier with
4398 the next proposal from Lenovo.
</p
>
4400 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4401 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4402 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4403 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4404 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4405 P/N
45N8295, P0C38732.
</p
>
4407 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4408 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4409 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4410 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4411 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4412 P/N
45N8295, P0C38732.
</p
>
4414 <p
>The only difference is in the first number (serial number?), ISN,
4415 SA, date and WNPP values. Mentioning all the details here in case
4416 someone is able to use the information to find a way to identify the
4417 failing disk among working ones (if any such working disk actually
4423 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4424 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4425 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4426 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4427 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4428 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4429 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4430 member assosiation NUUG
</a
> and
4431 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4432 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4433 Bitraf
</a
>.
</p
>
4435 <p
>It starts
10:
00 and continue until late evening. Everyone is
4436 welcome, and there is no fee to participate. There is on the other
4437 hand limited space, and only room for
30 people. Please put your name
4438 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4439 wiki page
</a
> if you plan to join us.
</p
>
4444 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4445 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4446 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4447 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4448 <description><p
>Half a year ago, I reported that I had to find a
4449 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4450 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4451 time to spend on it, and it took a while to find a model I believe
4452 will do the job, but two days ago the replacement finally arrived. I
4454 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4455 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4456 a roaming workstation, and it seemed to work flawlessly. But my
4457 second installation with encrypted disk was not as successful. More
4458 on that below.
</p
>
4460 <p
>I had a hard time trying to track down a good laptop, as my most
4461 important requirements (robust and with a good keyboard) are never
4462 listed in the feature list. But I did get good help from the search
4463 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4464 allowed me to limit the list of interesting laptops based on my other
4465 requirements. A bit surprising that SSD disk are not disks according
4466 to that search interface, so I had to drop specifying the number of
4467 disks from my search parameters. I also asked around among friends to
4468 get their impression on keyboards and robustness.
</p
>
4470 <p
>So the new laptop arrived, and it is quite a lot wider than the
4471 X41. I am not quite convinced about the keyboard, as it is
4472 significantly wider than my old keyboard, and I have to stretch my
4473 hand a lot more to reach the edges. But the key response is fairly
4474 good and the individual key shape is fairly easy to handle, so I hope
4475 I will get used to it. My old X40 was starting to fail, and I really
4476 needed a new laptop now. :)
</p
>
4478 <p
>Turning off the touch pad was simple. All it took was a quick
4479 visit to the BIOS during boot it disable it.
</p
>
4481 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4482 lock up during load. And this happen when installing Debian Wheezy
4483 with encrypted disk, while the disk is being filled with random data.
4484 I also tested to install Ubuntu Raring, and it happen there too if I
4485 reenable the code to fill the disk with random data (it is disabled by
4486 default in Ubuntu). And the bug with is already known. It was
4487 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4488 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4489 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4490 kernel developers as
4491 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4492 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4493 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4494 Lenovo forums, both for
4495 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4496 2012-
11-
10</a
> and for
4497 <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
4498 03-
20-
2013</a
>. The problem do not only affect installation. The
4499 reports state that the disk lock up during use if many writes are done
4500 on the disk, so it is much no use to work around the installation
4501 problem and end up with a computer that can lock up at any moment.
4503 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4504 available
</a
> that will lock up the hard drive after running a few
4505 minutes by writing to a file.
</p
>
4507 <p
>I
've contacted my supplier and asked how to handle this, and after
4508 contacting PCHELP Norway (request
01D1FDP) which handle support
4509 requests for Lenovo, his first suggestion was to upgrade the disk
4510 firmware. Unfortunately there is no newer firmware available from
4511 Lenovo, as my disk already have the most recent one (version LF1i). I
4512 hope to hear more from him today and hope the problem can be
4518 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4519 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4520 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4521 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4522 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4523 trusty old Thinkpad X41. Unfortunately I did not have much time to
4524 spend on it, but today the replacement finally arrived. I ended up
4525 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4526 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4527 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4528 this, it is installing what I hope will be a more final installation,
4529 with a encrypted hard drive to ensure any dope head stealing it end up
4530 with an expencive door stop.
</p
>
4532 <p
>I had a hard time trying to track down a good laptop, as my most
4533 important requirements (robust and with a good keyboard) are never
4534 listed in the feature list. But I did get good help from the search
4535 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4536 allowed me to limit the list of interesting laptops based on my other
4537 requirements. A bit surprising that SSD disk are not disks, so I had
4538 to drop number of disks from my search parameters.
</p
>
4540 <p
>I am not quite convinced about the keyboard, as it is significantly
4541 wider than my old keyboard, and I have to stretch my hand a lot more
4542 to reach the edges. But the key response is fairly good and the
4543 individual key shape is fairly easy to handle, so I hope I will get
4544 used to it. My old X40 was starting to fail, and I really needed a
4545 new laptop now. :)
</p
>
4547 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4552 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4553 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4554 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4555 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4556 <description><p
>It annoys me when the computer fail to do automatically what it is
4557 perfectly capable of, and I have to do it manually to get things
4558 working. One such task is to find out what firmware packages are
4559 needed to get the hardware on my computer working. Most often this
4560 affect the wifi card, but some times it even affect the RAID
4561 controller or the ethernet card. Today I pushed version
0.4 of the
4562 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4563 including a new script isenkram-autoinstall-firmware handling the
4564 process of asking all the loaded kernel modules what firmware files
4565 they want, find debian packages providing these files and install the
4566 debian packages. Here is a test run on my laptop:
</p
>
4568 <p
><pre
>
4569 # isenkram-autoinstall-firmware
4570 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4571 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4572 info: locating packages with the requested firmware files
4573 info: Updating APT sources after adding non-free APT source
4574 info: trying to install firmware-ipw2x00
4577 Preconfiguring packages ...
4578 Selecting previously deselected package firmware-ipw2x00.
4579 (Reading database ...
259727 files and directories currently installed.)
4580 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4581 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4583 </pre
></p
>
4585 <p
>When all the requested firmware is present, a simple message is
4586 printed instead:
</p
>
4588 <p
><pre
>
4589 # isenkram-autoinstall-firmware
4590 info: did not find any firmware files requested by loaded kernel modules. exiting
4592 </pre
></p
>
4594 <p
>It could use some polish, but it is already working well and saving
4595 me some time when setting up new machines. :)
</p
>
4597 <p
>So, how does it work? It look at the set of currently loaded
4598 kernel modules, and look up each one of them using modinfo, to find
4599 the firmware files listed in the module meta-information. Next, it
4600 download the Contents file from a nearby APT mirror, and search for
4601 the firmware files in this file to locate the package with the
4602 requested firmware file. If the package is in the non-free section, a
4603 non-free APT source is added and the package is installed using
4604 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4607 <p
>I hope someone find time to implement a more polished version of
4608 this script as part of the hw-detect debian-installer module, to
4609 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4610 #
655507</a
>. There really is no need to insert USB sticks with
4611 firmware during a PXE install when the packages already are available
4612 from the nearby Debian mirror.
</p
>
4617 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4618 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4620 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4621 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4622 the screen just turn black when Linux boot, either during installation
4623 or on first boot from the hard disk. I
've seen it once in a while the
4624 last few years, but only recently understood the cause. I
've seen it
4625 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4626 The reason seem to be in the wiring of some laptops. The system to
4627 control the screen background light is inverted, so when Linux try to
4628 turn the brightness fully on, it end up turning it off instead. I do
4629 not know which Linux drivers are affected, but this post is about the
4630 i915 driver used by the
4631 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4632 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4634 <p
>The problem can be worked around two ways. Either by adding
4635 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4636 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4637 option when it load the i915 kernel module. On Debian and Ubuntu, it
4638 can be done by running these commands as root:
</p
>
4641 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4642 update-initramfs -u -k all
4645 <p
>Since March
2012 there is
4646 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4647 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4648 hardware have this problem, and get the driver to invert the
4649 brightness setting automatically. To use it, one need to add a row in
4650 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4651 intel_quirks array
</a
> in the driver source
4652 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4653 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4654 number (vendor number
8086 is assumed) and subdevice vendor and device
4657 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4658 -vvnn
</tt
> for the video card in question:
</p
>
4660 <p
><pre
>
4661 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4662 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4663 (rev
09) (prog-if
00 [VGA controller])
4664 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4665 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4666 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4667 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4668 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4670 Interrupt: pin A routed to IRQ
42
4671 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4672 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4673 Region
4: I/O ports at
4000 [size=
64]
4674 Expansion ROM at
<unassigned
> [disabled]
4675 Capabilities:
<access denied
>
4676 Kernel driver in use: i915
4677 </pre
></p
>
4679 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4681 <p
><pre
>
4682 struct intel_quirk intel_quirks[] = {
4684 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4685 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4688 </pre
></p
>
4690 <p
>According to the kernel module instructions (as seen using
4691 <tt
>modinfo i915
</tt
>), information about hardware needing the
4692 invert_brightness flag should be sent to the
4693 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4694 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4695 developers. But my email about the laptop sent
2013-
06-
03 have not
4697 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4698 web archive for the mailing list
</a
>, so I suspect they do not accept
4699 emails from non-subscribers. Because of this, I sent my patch also to
4700 the Debian bug tracking system instead as
4701 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4702 sure the patch is not lost.
</p
>
4704 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4705 with this problem working properly with Linux. If you use Gnome, your
4706 worries should be over at this point. But if you use KDE, there is
4707 something in KDE ignoring the invert_brightness setting and turning on
4708 the screen during login. I
've reported it to Debian as
4709 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4710 have no idea yet how to figure out exactly what subsystem is doing
4711 this. Perhaps you can help? Perhaps you know what the Gnome
4712 developers did to handle this, and this can give a clue to the KDE
4713 developers? Or you know where in KDE the screen brightness is changed
4714 during login? If so, please update the BTS report (or get in touch if
4715 you do not know how to update BTS).
</p
>
4717 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4718 acpi_backlight=vendor, to disable ACPI backlight support completely,
4719 as the ACPI information on the machine is trash and it is better to
4720 leave it to the intel video driver to control the screen
4721 backlight.
</p
>
4726 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4727 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4728 <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>
4729 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4730 <description><p
>Two days ago, I asked
4731 <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
4732 I could install Linux on a Packard Bell EasyNote LV computer
4733 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4734 with the obstacles put in the way of Linux users on a laptop with UEFI
4735 and Windows
8.
</p
>
4737 <p
>I never found out if the cause of my problems were the use of UEFI
4738 secure booting or fast boot. I suspect fast boot was the problem,
4739 causing the firmware to boot directly from HD without considering any
4740 key presses and alternative devices, but do not know UEFI settings
4741 enough to tell.
</p
>
4743 <p
>There is no way to install Linux on the machine in question without
4744 opening the box and disconnecting the hard drive! This is as far as I
4745 can tell, the only way to get access to the firmware setup menu
4746 without accepting the Windows
8 license agreement. I am told (and
4747 found description on how to) that it is possible to configure the
4748 firmware setup once booted into Windows
8. But as I believe the terms
4749 of that agreement are completely unacceptable, accepting the license
4750 was never an alternative. I do not enter agreements I do not intend
4751 to follow.
</p
>
4753 <p
>I feared I had to return the laptops and ask for a refund, and
4754 waste many hours on this, but luckily there was a way to get it to
4755 work. But I would not recommend it to anyone planning to run Linux on
4756 it, and I have become sceptical to Windows
8 certified laptops. Is
4757 this the way Linux will be forced out of the market place, by making
4758 it close to impossible for
"normal
" users to install Linux without
4759 accepting the Microsoft Windows license terms? Or at least not
4760 without risking to loose the warranty?
</p
>
4762 <p
>I
've updated the
4763 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4764 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4765 do not have to struggle as much as I did to get Linux into the
4768 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4769 Michael Tokarev and others for feedback and ideas.
</p
>
4774 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4775 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4776 <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>
4777 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4778 <description><p
>I
've run into quite a problem the last few days. I bought three
4779 new laptops for my parents and a few others. I bought Packard Bell
4780 Easynote LV to run Kubuntu on and use as their home computer. But I
4781 am completely unable to figure out how to install Linux on it. The
4782 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4783 instead of a BIOS to boot.
</p
>
4785 <p
>The problem is that I am unable to get it to PXE boot, and unable
4786 to get it to boot the Linux installer from my USB stick. I have yet
4787 to try the DVD install, and still hope it will work. when I turn on
4788 the computer, there is no information on what buttons to press to get
4789 the normal boot menu. I expect to get some boot menu to select PXE or
4790 USB stick booting. When booting, it first ask for the language to
4791 use, then for some regional settings, and finally if I will accept the
4792 Windows
8 terms of use. As these terms are completely unacceptable to
4793 me, I have no other choice but to turn off the computer and try again
4794 to get it to boot the Linux installer.
</p
>
4796 <p
>I have gathered my findings so far on a Linlap page about the
4797 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4798 EasyNote LV
</a
> model. If you have any idea how to get Linux
4799 installed on this machine, please get in touch or update that wiki
4800 page. If I can
't find a way to install Linux, I will have to return
4801 the laptop to the seller and find another machine for my parents.
</p
>
4803 <p
>I wonder, is this the way Linux will be forced out of the market
4804 using UEFI and
"secure boot
" by making it impossible to install Linux
4805 on new Laptops?
</p
>
4810 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4811 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4813 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4814 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4815 an operating system based on Debian intended for use in schools. It
4816 contain a turn-key solution for the computer network provided to
4817 pupils in the primary schools. It provide both the central server,
4818 network boot servers and desktop environments with heaps of
4819 educational software. The project was founded almost
12 years ago,
4820 2001-
07-
02. If you want to support the project, which is in need for
4821 cash to fund developer gatherings and other project related activity,
4822 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4823 donate some money
</a
>.
4825 <p
>A topic that come up again and again on the Debian Edu mailing
4826 lists and elsewhere, is the question on how to transform a Debian or
4827 Ubuntu installation into a Debian Edu installation. It isn
't very
4828 hard, and last week I wrote a script to replicate the steps done by
4829 the Debian Edu installer.
</p
>
4831 <p
>The script,
4832 <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/
>
4833 in the debian-edu-config package, will go through these six steps and
4834 transform an existing Debian Wheezy or Ubuntu (untested) installation
4835 into a Debian Edu Workstation:
</p
>
4839 <li
>Add skolelinux related APT sources.
</li
>
4840 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4841 <li
>Install debian-edu-install to load preseeding values and pull in
4842 our configuration.
</li
>
4843 <li
>Preseed debconf database with profile setup in
4844 /etc/debian-edu/config, and run tasksel to install packages
4845 according to the profile specified in the config above,
4846 overriding some of the Debian automation machinery.
</li
>
4847 <li
>Run debian-edu-cfengine-D installation to configure everything
4848 that could not be done using preseeding.
</li
>
4849 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4853 <p
>There are some steps in the Debian Edu installation that can not be
4854 replicated like this. Disk partitioning and LVM setup, for example.
4855 So this script just assume there is enough disk space to install all
4856 the needed packages.
</p
>
4858 <p
>The script was created to help a Debian Edu student working on
4859 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4860 Debian Edu client, and using it he can take the existing
4861 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4862 transform it into a fully functioning Debian Edu Workstation (or
4863 Roaming Workstation, or whatever :).
</p
>
4865 <p
>The default setting in the script is to create a KDE Workstation.
4866 If a LXDE based Roaming workstation is wanted instead, modify the
4867 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4869 <p
><pre
>
4870 PROFILE=
"Roaming-Workstation
"
4871 DESKTOP=
"lxde
"
4872 </pre
></p
>
4874 <p
>The script could even become useful to set up Debian Edu servers in
4875 the cloud, by starting with a virtual Debian installation at some
4876 virtual hosting service and setting up all the services on first
4882 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4883 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4884 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4885 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4886 <description><P
>In January,
4887 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4888 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4889 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4890 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4891 marvellous construction system from Denmark. We also created
4892 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4893 a place to take notes and write down our plans and hopes. And several
4894 people showed up to help. I was very happy to see the effect of my
4895 call. Since the small start, we have a debtags tag
4896 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4897 tag for LEGO related packages, and now count
10 packages related to
4898 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4900 <p
><table
>
4901 <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
>
4902 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4903 <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
>
4904 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4905 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4906 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4907 <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
>
4908 <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
>
4909 <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
>
4910 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4911 </table
></p
>
4913 <p
>Some of these are available in Wheezy, and all but one are
4914 currently available in Jessie/testing. leocad is so far only
4915 available in experimental.
</p
>
4917 <p
>If you care about LEGO in Debian, please join us on IRC and help
4918 adding the rest of the great free software tools available on Linux
4919 for LEGO designers.
</p
>
4924 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4925 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4926 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4927 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4928 <description><p
>When I woke up this morning, I was very happy to see that the
4929 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4930 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4931 Debian release, and I expect to move my machines at home over to it fairly
4934 <p
>The new debian release contain heaps of new stuff, and one program
4935 in particular make me very happy to see included. The
4936 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4937 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4938 included for the first time. Alongside similar programs like
4939 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4940 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4941 it allow for visual programming where syntax errors can not happen,
4942 and a friendly programming environment for learning to control the
4943 computer. Scratch will also be included in the next release of Debian
4946 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4947 Edu/Skolelinux release too. The
4948 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4949 alpha release
</a
> went out last week, and the next should soon
4955 <title>Isenkram
0.2 finally in the Debian archive
</title>
4956 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4958 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4959 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4960 package
</a
> finally made it into the archive, after lingering in NEW
4961 for many months. I uploaded it to the Debian experimental suite
4962 2013-
01-
27, and today it was accepted into the archive.
</p
>
4964 <p
>Isenkram is a system for suggesting to users what packages to
4965 install to work with a pluggable hardware device. The suggestion pop
4966 up when the device is plugged in. For example if a Lego Mindstorm NXT
4967 is inserted, it will suggest to install the program needed to program
4968 the NXT controller. Give it a go, and report bugs and suggestions to
4974 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4975 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4976 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4977 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4978 <description><p
>My
4979 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4980 bitcoin related blog post
</a
> mentioned that the new
4981 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4982 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4983 2013-
01-
19, and have been available in unstable since then. It was
4984 automatically copied to Ubuntu, and is available in their Raring
4985 version too.
</p
>
4987 <p
>But there is a strange problem with the build that block this new
4988 version from being available on the i386 and kfreebsd-i386
4989 architectures. For some strange reason, the autobuilders in Debian
4990 for these architectures fail to run the test suite on these
4991 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4992 We are so far unable to reproduce it when building it manually, and
4993 no-one have been able to propose a fix. If you got an idea what is
4994 failing, please let us know via the BTS.
</p
>
4996 <p
>One feature that is annoying me with of the bitcoin client, because
4997 I often run low on disk space, is the fact that the client will exit
4998 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4999 #
696715</a
>). So make sure you have enough disk space when you run
5002 <p
>As usual, if you use bitcoin and want to show your support of my
5003 activities, please send Bitcoin donations to my address
5004 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5009 <title>Welcome to the world, Isenkram!
</title>
5010 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5011 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5012 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5013 <description><p
>Yesterday, I
5014 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5015 for testers
</a
> for my prototype for making Debian better at handling
5016 pluggable hardware devices, which I
5017 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5018 out to create
</a
> earlier this month. Several valuable testers showed
5019 up, and caused me to really want to to open up the development to more
5020 people. But before I did this, I want to come up with a sensible name
5021 for this project. Today I finally decided on a new name, and I have
5022 renamed the project from hw-support-handler to this new name. In the
5023 process, I moved the source to git and made it available as a
5024 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5025 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5026 To fetch and build the latest version of the source, use
</p
>
5029 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5030 cd isenkram
&& git-buildpackage -us -uc
5033 <p
>I have not yet adjusted all files to use the new name yet. If you
5034 want to hack on the source or improve the package, please go ahead.
5035 But please talk to me first on IRC or via email before you do major
5036 changes, to make sure we do not step on each others toes. :)
</p
>
5038 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5039 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5040 stuff, in other words. I
've been told it is the Norwegian variant of
5041 the German word eisenkram, for those that are familiar with that
5044 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5045 instructions, to avoid confusing people with an error from the signing
5048 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5049 clone argument to avoid the need for authentication.
</p
>
5054 <title>First prototype ready making hardware easier to use in Debian
</title>
5055 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5056 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5057 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5058 <description><p
>Early this month I set out to try to
5059 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5060 the Debian support for pluggable hardware devices
</a
>. Now my
5061 prototype is working, and it is ready for a larger audience. To test
5063 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5064 from the Debian Edu subversion repository
</a
>, build and install the
5065 package. You might have to log out and in again activate the
5066 autostart script.
</p
>
5068 <p
>The design is simple:
</p
>
5072 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5073 hw-support-handlerd to start when the user log in.
</li
>
5075 <li
>This program listen for kernel events about new hardware (directly
5076 from the kernel like udev does), not using HAL dbus events as I
5077 initially did.
</li
>
5079 <li
>When new hardware is inserted, look up the hardware modalias in
5080 the APT database, a database
5081 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5082 via HTTP
</a
> and a database available as part of the package.
</li
>
5084 <li
>If a package is mapped to the hardware in question, the package
5085 isn
't installed yet and this is the first time the hardware was
5086 plugged in, show a desktop notification suggesting to install the
5087 package or packages.
</li
>
5089 <li
>If the user click on the
'install package now
' button, ask
5090 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5092 <li
>aptdaemon ask for root password or sudo password, and install the
5093 package while showing progress information in a window.
</li
>
5097 <p
>I still need to come up with a better name for the system. Here
5098 are some screen shots showing the prototype in action. First the
5099 notification, then the password request, and finally the request to
5100 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5102 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5103 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5104 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5105 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5106 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5108 <p
>The prototype still need to be improved with longer timeouts, but
5109 is already useful. The database of hardware to package mappings also
5110 need more work. It is currently compatible with the Ubuntu way of
5111 storing such information in the package control file, but could be
5112 changed to use other formats instead or in addition to the current
5113 method. I
've dropped the use of discover for this mapping, as the
5114 modalias approach is more flexible and easier to use on Linux as long
5115 as the Linux kernel expose its modalias strings directly.
</p
>
5117 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5118 here is the command required to check out and build the source: Use
5119 '<tt
>svn checkout
5120 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5121 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5122 devscripts package.
</p
>
5124 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5125 renamed to Isenkram and the source moved from the Debian Edu
5126 subversion repository to a Debian collab-maint git repository. See
5127 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5128 instructions
</a
> for details.
</p
>
5133 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5134 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5135 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5136 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5137 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5138 suddenly in bed. With a quiet whimper, it went completely quiet and
5139 black. The power button was no longer able to turn it on. It was a
5140 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5141 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5142 Compaq I had before that. Now I need to find a replacement. To keep
5143 going during Christmas, I moved the one year old SSD disk to my old
5144 X40 where it fitted (only one I had left that could use it), but it is
5145 not a durable solution.
5147 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5148 got a new one more than
10 years ago. It still holds true.:)
</p
>
5152 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5153 than A4).
</li
>
5154 <li
>Robust, it will be in my backpack every day.
</li
>
5155 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5156 <li
>Long battery life time. Preferable a week.
</li
>
5157 <li
>Internal WIFI network card.
</li
>
5158 <li
>Internal Twisted Pair network card.
</li
>
5159 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5160 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5161 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5163 <li
>Hardware supported by Debian Stable, ie the default kernel and
5164 X.org packages.
</li
>
5165 <li
>Quiet, preferably fan free (or at least not using the fan most of
5170 <p
>You will notice that there are no RAM and CPU requirements in the
5171 list. The reason is simply that the specifications on laptops the
5172 last
10-
15 years have been sufficient for my needs, and I have to look
5173 at other features to choose my laptop. But are there still made as
5174 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5175 robust, and Thinkpads seem to be heading in the wrong direction since
5176 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5177 still be useful.
</p
>
5179 <p
>Perhaps I should rethink my needs, and look for a pad with an
5180 external keyboard? I
'll have to check the
5181 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5182 well-supported laptops, or perhaps just buy one preinstalled from one
5183 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5184 Pre-loaded site
</a
>.
</p
>
5189 <title>How to find a browser plugin supporting a given MIME type
</title>
5190 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5192 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5193 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5194 install to get support for a given MIME type. Thanks to
5195 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5196 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5197 Unfortunately, not very many packages provide the needed meta
5198 information, Anyway, here is a small script to look up all browser
5199 plugin packages announcing ther MIME support using this specification:
</p
>
5205 def pkgs_handling_mimetype(mimetype):
5210 version = pkg.candidate
5212 version = pkg.installed
5215 record = version.record
5216 if not record.has_key(
'Npp-MimeType
'):
5218 mime_types = record[
'Npp-MimeType
'].split(
',
')
5219 for t in mime_types:
5220 t = t.rstrip().strip()
5222 thepkgs.append(pkg.name)
5224 mimetype =
"audio/ogg
"
5225 if
1 < len(sys.argv):
5226 mimetype = sys.argv[
1]
5227 print
"Browser plugin packages supporting %s:
" % mimetype
5228 for pkg in pkgs_handling_mimetype(mimetype):
5229 print
" %s
" %pkg
5232 <p
>It can be used like this to look up a given MIME type:
</p
>
5235 % ./apt-find-browserplug-for-mimetype
5236 Browser plugin packages supporting audio/ogg:
5238 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5239 Browser plugin packages supporting application/x-shockwave-flash:
5240 browser-plugin-gnash
5244 <p
>In Ubuntu this mechanism is combined with support in the browser
5245 itself to query for plugins and propose to install the needed
5246 packages. It would be great if Debian supported such feature too. Is
5247 anyone working on adding it?
</p
>
5249 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5250 request for icweasel support for this feature is
5251 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5252 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5253 of manpower and wish for a different design is the reason thus feature
5254 is not yet in iceweasel from Debian.
</p
>
5259 <title>What is the most supported MIME type in Debian?
</title>
5260 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5261 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5262 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5263 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5264 proposal to add AppStream information to the Debian archive
</a
>, is a
5265 proposal to make it possible for a Desktop application to propose to
5266 the user some package to install to gain support for a given MIME
5267 type, font, library etc. that is currently missing. With such
5268 mechanism in place, it would be possible for the desktop to
5269 automatically propose and install leocad if some LDraw file is
5270 downloaded by the browser.
</p
>
5272 <p
>To get some idea about the current content of the archive, I decided
5273 to write a simple program to extract all .desktop files from the
5274 Debian archive and look up the claimed MIME support there. The result
5276 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5277 site
</a
>. Using the collected information, it become possible to
5278 answer the question in the title. Here are the
20 most supported MIME
5279 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5280 The complete list is available from the link above.
</p
>
5282 <p
><strong
>Debian Stable:
</strong
></p
>
5286 ----- -----------------------
5302 18 application/x-ogg
5309 <p
><strong
>Debian Testing:
</strong
></p
>
5313 ----- -----------------------
5329 18 application/x-ogg
5336 <p
><strong
>Debian Unstable:
</strong
></p
>
5340 ----- -----------------------
5357 18 application/x-ogg
5363 <p
>I am told that PackageKit can provide an API to access the kind of
5364 information mentioned in DEP-
11. I have not yet had time to look at
5365 it, but hope the PackageKit people in Debian are on top of these
5368 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5369 discovering a typo in my script.
</p
>
5374 <title>Using modalias info to find packages handling my hardware
</title>
5375 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5376 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5377 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5378 <description><p
>Yesterday, I wrote about the
5379 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5380 values provided by the Linux kernel
</a
> following my hope for
5381 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5382 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5383 modalias values attached to package names can be used to map packages
5384 to hardware. This allow the system to look up and suggest relevant
5385 packages when I plug in some new hardware into my machine, and replace
5386 discover and discover-data as the database used to map hardware to
5389 <p
>I create a modaliases file with entries like the following,
5390 containing package name, kernel module name (if relevant, otherwise
5391 the package name) and globs matching the relevant hardware
5394 <p
><blockquote
>
5395 Package: package-name
5396 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5397 </blockquote
></p
>
5399 <p
>It is fairly trivial to write code to find the relevant packages
5400 for a given modalias value using this file.
</p
>
5402 <p
>An entry like this would suggest the video and picture application
5403 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5405 <p
><blockquote
>
5407 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5408 </blockquote
></p
>
5410 <p
>An entry like this would suggest the pcmciautils package when a
5411 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5413 <p
><blockquote
>
5414 Package: pcmciautils
5415 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5416 </blockquote
></p
>
5418 <p
>An entry like this would suggest the package colorhug-client when
5419 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5421 <p
><blockquote
>
5422 Package: colorhug-client
5423 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5424 </blockquote
></p
>
5426 <p
>I believe the format is compatible with the format of the Packages
5427 file in the Debian archive. Ubuntu already uses their Packages file
5428 to store their mappings from packages to hardware.
</p
>
5430 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5431 announce the hardware it support in a way my prototype understand.
5432 This allow those publishing packages in an APT source outside the
5433 Debian archive as well as those backporting packages to make sure the
5434 hardware mapping are included in the package meta information. I
've
5435 tested such header in the pymissile package, and its modalias mapping
5436 is working as it should with my prototype. It even made it to Ubuntu
5439 <p
>To test if it was possible to look up supported hardware using only
5440 the shell tools available in the Debian installer, I wrote a shell
5441 implementation of the lookup code. The idea is to create files for
5442 each modalias and let the shell do the matching. Please check out and
5444 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5445 shell script. It run without any extra dependencies and fetch the
5446 hardware mappings from the Debian archive and the subversion
5447 repository where I currently work on my prototype.
</p
>
5449 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5450 install yubikey-personalization:
</p
>
5452 <p
><blockquote
>
5453 % ./hw-support-lookup
5454 <br
>yubikey-personalization
5456 </blockquote
></p
>
5458 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5459 propose to install the pcmciautils package:
</p
>
5461 <p
><blockquote
>
5462 % ./hw-support-lookup
5463 <br
>pcmciautils
5465 </blockquote
></p
>
5467 <p
>If you know of any hardware-package mapping that should be added to
5468 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5469 database
</a
>, please tell me about it.
</p
>
5471 <p
>It could be possible to generate several of the mappings between
5472 packages and hardware. One source would be to look at packages with
5473 kernel modules, ie packages with *.ko files in /lib/modules/, and
5474 extract their modalias information. Another would be to look at
5475 packages with udev rules, ie packages with files in
5476 /lib/udev/rules.d/, and extract their vendor/model information to
5477 generate a modalias matching rule. I have not tested any of these to
5478 see if it work.
</p
>
5480 <p
>If you want to help implementing a system to let us propose what
5481 packages to install when new hardware is plugged into a Debian
5482 machine, please send me an email or talk to me on
5483 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5488 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5489 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5491 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5492 <description><p
>While looking into how to look up Debian packages based on hardware
5493 information, to find the packages that support a given piece of
5494 hardware, I refreshed my memory regarding modalias values, and decided
5495 to document the details. Here are my findings so far, also available
5497 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5498 Debian Edu subversion repository
</a
>:
5500 <p
><strong
>Modalias decoded
</strong
></p
>
5502 <p
>This document try to explain what the different types of modalias
5503 values stands for. It is in part based on information from
5504 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5505 &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;,
5506 &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
5507 &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;.
5509 <p
>The modalias entries for a given Linux machine can be found using
5510 this shell script:
</p
>
5513 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5516 <p
>The supported modalias globs for a given kernel module can be found
5517 using modinfo:
</p
>
5520 % /sbin/modinfo psmouse | grep alias:
5521 alias: serio:ty05pr*id*ex*
5522 alias: serio:ty01pr*id*ex*
5526 <p
><strong
>PCI subtype
</strong
></p
>
5528 <p
>A typical PCI entry can look like this. This is an Intel Host
5529 Bridge memory controller:
</p
>
5531 <p
><blockquote
>
5532 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5533 </blockquote
></p
>
5535 <p
>This represent these values:
</p
>
5540 sv
00001028 (subvendor)
5541 sd
000001AD (subdevice)
5543 sc
00 (bus subclass)
5547 <p
>The vendor/device values are the same values outputted from
'lspci
5548 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5549 0600. The
0600 class is a host bridge. Other useful bus values are
5550 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5552 <p
>Not sure how to figure out the interface value, nor what it
5555 <p
><strong
>USB subtype
</strong
></p
>
5557 <p
>Some typical USB entries can look like this. This is an internal
5558 USB hub in a laptop:
</p
>
5560 <p
><blockquote
>
5561 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5562 </blockquote
></p
>
5564 <p
>Here is the values included in this alias:
</p
>
5567 v
1D6B (device vendor)
5568 p
0001 (device product)
5570 dc
09 (device class)
5571 dsc
00 (device subclass)
5572 dp
00 (device protocol)
5573 ic
09 (interface class)
5574 isc
00 (interface subclass)
5575 ip
00 (interface protocol)
5578 <p
>The
0900 device class/subclass means hub. Some times the relevant
5579 class is in the interface class section. For a simple USB web camera,
5580 these alias entries show up:
</p
>
5582 <p
><blockquote
>
5583 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5584 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5585 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5586 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5587 </blockquote
></p
>
5589 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5590 camera),
0101 is audio control device and
0102 is audio streaming (aka
5591 microphone). Thus this is a camera with microphone included.
</p
>
5593 <p
><strong
>ACPI subtype
</strong
></p
>
5595 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5596 receiver in a Thinkpad X40:
</p
>
5598 <p
><blockquote
>
5599 acpi:IBM0071:PNP0511:
5600 </blockquote
></p
>
5602 <p
>The values between the colons are IDs.
</p
>
5604 <p
><strong
>DMI subtype
</strong
></p
>
5606 <p
>The DMI table contain lots of information about the computer case
5607 and model. This is an entry for a IBM Thinkpad X40, fetched from
5608 /sys/devices/virtual/dmi/id/modalias:
</p
>
5610 <p
><blockquote
>
5611 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5612 </blockquote
></p
>
5614 <p
>The values present are
</p
>
5617 bvn IBM (BIOS vendor)
5618 bvr
1UETB
6WW(
1.66) (BIOS version)
5619 bd
06/
15/
2005 (BIOS date)
5620 svn IBM (system vendor)
5621 pn
2371H4G (product name)
5622 pvr ThinkPadX40 (product version)
5623 rvn IBM (board vendor)
5624 rn
2371H4G (board name)
5625 rvr NotAvailable (board version)
5626 cvn IBM (chassis vendor)
5627 ct
10 (chassis type)
5628 cvr NotAvailable (chassis version)
5631 <p
>The chassis type
10 is Notebook. Other interesting values can be
5632 found in the dmidecode source:
</p
>
5636 4 Low Profile Desktop
5649 17 Main Server Chassis
5650 18 Expansion Chassis
5652 20 Bus Expansion Chassis
5653 21 Peripheral Chassis
5655 23 Rack Mount Chassis
5664 <p
>The chassis type values are not always accurately set in the DMI
5665 table. For example my home server is a tower, but the DMI modalias
5666 claim it is a desktop.
</p
>
5668 <p
><strong
>SerIO subtype
</strong
></p
>
5670 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5671 test machine:
</p
>
5673 <p
><blockquote
>
5674 serio:ty01pr00id00ex00
5675 </blockquote
></p
>
5677 <p
>The values present are
</p
>
5686 <p
>This type is supported by the psmouse driver. I am not sure what
5687 the valid values are.
</p
>
5689 <p
><strong
>Other subtypes
</strong
></p
>
5691 <p
>There are heaps of other modalias subtypes according to
5692 file2alias.c. There is the rest of the list from that source: amba,
5693 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5694 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5695 vmbus, x86cpu and zorro. I did not spend time documenting all of
5696 these, as they do not seem relevant for my intended use with mapping
5697 hardware to packages when new stuff is inserted during run time.
</p
>
5699 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5701 <p
>To check which kernel modules provide support for a given modalias,
5702 one can use the following shell script:
</p
>
5705 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5706 echo
"$id
" ; \
5707 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5711 <p
>The output can look like this (only the first few entries as the
5712 list is very long on my test machine):
</p
>
5716 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5718 FATAL: Module acpi:device: not found.
5720 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5721 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5722 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5723 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5724 acpi:IBM0071:PNP0511:
5725 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5726 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5727 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5731 <p
>If you want to help implementing a system to let us propose what
5732 packages to install when new hardware is plugged into a Debian
5733 machine, please send me an email or talk to me on
5734 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5736 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5737 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5738 in /sys/ with space in them.
</p
>
5743 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5744 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5745 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5746 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5747 <description><p
>As part of my investigation on how to improve the support in Debian
5748 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5749 Launcher and updated the Debian package
5750 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5751 sure udev will fix the device permissions when it is plugged in. I
5752 also added a
"Modaliases
" header to test it in the Debian archive and
5753 hopefully make the package be proposed by jockey in Ubuntu when a user
5754 plug in his rocket launcher. In the process I moved the source to a
5755 git repository under collab-maint, to make it easier for any DD to
5756 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5757 is not very active, but the software still work for me even after five
5758 years of relative silence. The new git repository is not listed in
5759 the uploaded package yet, because I want to test the other changes a
5760 bit more before I upload the new version. If you want to check out
5761 the new version with a .desktop file included, visit the
5762 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5763 view
</a
> or use
"<tt
>git clone
5764 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5769 <title>Lets make hardware dongles easier to use in Debian
</title>
5770 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5772 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5773 <description><p
>One thing that annoys me with Debian and Linux distributions in
5774 general, is that there is a great package management system with the
5775 ability to automatically install software packages by downloading them
5776 from the distribution mirrors, but no way to get it to automatically
5777 install the packages I need to use the hardware I plug into my
5778 machine. Even if the package to use it is easily available from the
5779 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5780 suggest to automatically install the python-nxt, nbc and t2n packages
5781 I need to talk to it. When I plug in a Yubikey, it could propose the
5782 yubikey-personalization package. The information required to do this
5783 is available, but no-one have pulled all the pieces together.
</p
>
5785 <p
>Some years ago, I proposed to
5786 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5787 the discover subsystem to implement this
</a
>. The idea is fairly
5792 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5793 starting when a user log in.
</li
>
5795 <li
>Set this program up to listen for kernel events emitted when new
5796 hardware is inserted into the computer.
</li
>
5798 <li
>When new hardware is inserted, look up the hardware ID in a
5799 database mapping to packages, and take note of any non-installed
5800 packages.
</li
>
5802 <li
>Show a message to the user proposing to install the discovered
5803 package, and make it easy to install it.
</li
>
5807 <p
>I am not sure what the best way to implement this is, but my
5808 initial idea was to use dbus events to discover new hardware, the
5809 discover database to find packages and
5810 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5813 <p
>Yesterday, I found time to try to implement this idea, and the
5814 draft package is now checked into
5815 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5816 Debian Edu subversion repository
</a
>. In the process, I updated the
5817 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5818 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5819 the relevant packages in Debian, and uploaded a new version
5820 2.2013.01.09 to unstable. I also discovered that the current
5821 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5822 package in Debian no longer discovered any USB devices, because
5823 /proc/bus/usb/devices is no longer present. I ported it to use
5824 libusb as a fall back option to get it working. The fixed package
5825 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5826 because of the freeze).
</p
>
5828 <p
>With this prototype in place, I can insert my Yubikey, and get this
5829 desktop notification to show up (only once, the first time it is
5830 inserted):
</p
>
5832 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5834 <p
>For this prototype to be really useful, some way to automatically
5835 install the proposed packages by pressing the
"Please install
5836 program(s)
" button should to be implemented.
</p
>
5838 <p
>If this idea seem useful to you, and you want to help make it
5839 happen, please help me update the discover-data database with mappings
5840 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5841 list the package you would like to have installed when a given
5842 hardware device is inserted into your computer, and report bugs using
5843 reportbug if it isn
't. Or, if you know of a better way to provide
5844 such mapping, please let me know.
</p
>
5846 <p
>This prototype need more work, and there are several questions that
5847 should be considered before it is ready for production use. Is dbus
5848 the correct way to detect new hardware? At the moment I look for HAL
5849 dbus events on the system bus, because that is the events I could see
5850 on my Debian Squeeze KDE desktop. Are there better events to use?
5851 How should the user be notified? Is the desktop notification
5852 mechanism the best option, or should the background daemon raise a
5853 popup instead? How should packages be installed? When should they
5854 not be installed?
</p
>
5856 <p
>If you want to help getting such feature implemented in Debian,
5857 please send me an email. :)
</p
>
5862 <title>New IRC channel for LEGO designers using Debian
</title>
5863 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5864 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5865 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5866 <description><p
>During Christmas, I have worked a bit on the Debian support for
5867 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5868 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5869 discovered I had to build all the tools myself because none were
5870 already in Debian Squeeze. If Debian support for LEGO is something
5871 you care about, please join me on the IRC channel
5872 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5873 irc.debian.org). There is a lot that could be done to improve the
5874 Debian support for LEGO designers. For example both CAD software
5875 and Mindstorm compilers are missing. :)
</p
>
5877 <p
>Update
2012-
01-
03: A
5878 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5879 including links to Lego related packages is now available.
</p
>
5884 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5885 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5887 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5888 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5889 year! I hope next year will prove to be a good year.
</p
>
5891 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5892 decentralised
"currency
" that allow people to transfer bitcoins
5893 between each other with minimal overhead, is a very interesting
5894 experiment. And as I wrote a few days ago, the bitcoin situation in
5895 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5896 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5897 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5898 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5899 for one of the ftpmasters to approve the new bitcoin-qt package
5902 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5903 team in Debian, you can easily test the package in Debian Squeeze
5904 using the following steps to get a set of working packages:
</p
>
5906 <blockquote
><pre
>
5907 git clone git://git.debian.org/git/collab-maint/bitcoin
5909 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5910 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5911 </pre
></blockquote
>
5913 <p
>You might have to install some build dependencies as well. The
5914 list of commands should give you two packages, bitcoind and
5915 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5916 client will download the complete set of bitcoin
"blocks
", which need
5917 around
5.6 GiB of data on my machine at the moment. Make sure your
5918 ~/.bitcoin/ directory have lots of spare room if you want to download
5919 all the blocks. The client will warn if the disk is getting full, so
5920 there is not really a problem if you got too little room, but you will
5921 not be able to get all the features out of the client.
</p
>
5923 <p
>As usual, if you use bitcoin and want to show your support of my
5924 activities, please send Bitcoin donations to my address
5925 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5930 <title>A word on bitcoin support in Debian
</title>
5931 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5932 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5933 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5934 <description><p
>It has been a while since I wrote about
5935 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5936 peer-to-peer based crypto-currency, and the reason is simply that I
5937 have been busy elsewhere. But two days ago, I started looking at the
5938 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5939 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5940 is now maintained by a
5941 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5942 people
</a
>, and the grunt work had already been done by this team. We
5943 owe a huge thank you to all these team members. :)
5944 But I was sad to discover that the bitcoin client is missing in
5945 Wheezy. It is only available in Sid (and an outdated client from
5946 backports). The client had several RC bugs registered in BTS blocking
5947 it from entering testing. To try to help the team and improve the
5948 situation, I spent some time providing patches and triaging the bug
5949 reports. I also had a look at the bitcoin package available from Matt
5951 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5952 Ubuntu
</a
>, and moved the useful pieces from that version into the
5953 Debian package.
</p
>
5955 <p
>After checking with the main package maintainer Jonas Smedegaard on
5956 IRC, I pushed several patches into the collab-maint git repository to
5957 improve the package. It now contains fixes for the RC issues (not from
5958 me, but fixed by Scott Howard), build rules for a Qt GUI client
5959 package, konqueror support for the bitcoin: URI and bash completion
5960 setup. As I work on Debian Squeeze, I also created
5961 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5962 patch to backport
</a
> the latest version. Jonas is going to look at
5963 it and try to integrate it into the git repository before uploading a
5964 new version to unstable.
5966 <p
>I would very much like bitcoin to succeed, to get rid of the
5967 centralized control currently exercised in the monetary system. I
5968 find it completely unacceptable that the USA government is collecting
5969 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5970 that the major credit card companies can block legal money
5971 transactions to Wikileaks. But for bitcoin to succeed, more people
5972 need to use bitcoins, and more people need to accept bitcoins when
5973 they sell products and services. Improving the bitcoin support in
5974 Debian is a small step in the right direction, but not enough.
5975 Unfortunately the user experience when browsing the web and wanting to
5976 pay with bitcoin is still not very good. The bitcoin: URI is a step
5977 in the right direction, but need to work in most or every browser in
5978 use. Also the bitcoin-qt client is too heavy to fire up to do a
5979 quick transaction. I believe there are other clients available, but
5980 have not tested them.
</p
>
5983 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5984 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5985 I received
20.15 BTC so far on the address I provided in my blog two
5986 years ago, as can be
5987 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5988 on the blockexplorer service
</a
>. Thank you everyone for your
5989 donation. The blockexplorer service demonstrates quite well that
5990 bitcoin is not quite anonymous and untracked. :) I wonder if the
5991 number of users have gone up since then. If you use bitcoin and want
5992 to show your support of my activity, please send Bitcoin donations to
5993 the same address as last time,
5994 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5999 <title>Git repository for song book for Computer Scientists
</title>
6000 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6001 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6002 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6003 <description><p
>As I
6004 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6005 this summer
</a
>, I have created a Computer Science song book a few
6006 years ago, and today I finally found time to create a public
6007 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6008 repository for the project
</a
>.
</p
>
6010 <p
>If you want to help out, please clone the source and submit patches
6011 to the HTML version. To generate the PDF and PostScript version,
6012 please use prince XML, or let me know about a useful free software
6013 processor capable of creating a good looking PDF from the HTML.
</p
>
6015 <p
>Want to sing? You can still find the song book in HTML, PDF and
6016 PostScript formats at
6017 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6018 Science Songbook
</a
>.
</p
>
6023 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6024 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6026 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6027 <description><p
>I dag fyller
6028 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6029 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6030 si gratulerer med dagen, Debian!
</p
>
6035 <title>Song book for Computer Scientists
</title>
6036 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6037 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6038 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6039 <description><p
>Many years ago, while studying Computer Science at the
6040 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6041 collecting computer related songs for use at parties. The original
6042 version was written in LaTeX, but a few years ago I got help from
6043 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6044 while keeping the ability to create a nice book in PDF format. I have
6045 not had time to maintain the book for a while now, and guess I should
6046 put it up on some public version control repository where others can
6047 help me extend and update the book. If anyone is volunteering to help
6048 me with this, send me an email. Also let me know if there are songs
6049 missing in my book.
</p
>
6051 <p
>I have not mentioned the book on my blog so far, and it occured to
6052 me today that I really should let all my readers share the joys of
6053 singing out load about programming, computers and computer networks.
6054 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6055 12</a
> is about to start (and I am not going). Want to sing? Check
6056 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6057 Computer Science Songbook
</a
>.
6062 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6063 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6065 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6066 <description><p
>At work we have heaps of servers. I believe the total count is
6067 around
1000 at the moment. To be able to get help from the vendors
6068 when something go wrong, we want to keep the firmware on the servers
6069 up to date. If the firmware isn
't the latest and greatest, the
6070 vendors typically refuse to start debugging any problems until the
6071 firmware is upgraded. So before every reboot, we want to upgrade the
6072 firmware, and we would really like everyone handling servers at the
6073 university to do this themselves when they plan to reboot a machine.
6074 For that to happen we at the unix server admin group need to provide
6075 the tools to do so.
</p
>
6077 <p
>To make firmware upgrading easier, I am working on a script to
6078 fetch and install the latest firmware for the servers we got. Most of
6079 our hardware are from Dell and HP, so I have focused on these servers
6080 so far. This blog post is about the Dell part.
</P
>
6082 <p
>On the Dell FTP site I was lucky enough to find
6083 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6084 with firmware information for all
11th generation servers, listing
6085 which firmware should be used on a given model and where on the FTP
6086 site I can find it. Using a simple perl XML parser I can then
6087 download the shell scripts Dell provides to do firmware upgrades from
6088 within Linux and reboot when all the firmware is primed and ready to
6089 be activated on the first reboot.
</p
>
6091 <p
>This is the Dell related fragment of the perl code I am working on.
6092 Are there anyone working on similar tools for firmware upgrading all
6093 servers at a site? Please get in touch and lets share resources.
</p
>
6095 <p
><pre
>
6099 use File::Temp qw(tempdir);
6101 # Install needed RHEL packages if missing
6103 'XML::Simple
' =
> 'perl-XML-Simple
',
6105 for my $module (keys %rhelmodules) {
6106 eval
"use $module;
";
6108 my $pkg = $rhelmodules{$module};
6109 system(
"yum install -y $pkg
");
6110 eval
"use $module;
";
6114 my $errorsto =
'pere@hungry.com
';
6120 sub run_firmware_script {
6121 my ($opts, $script) = @_;
6123 print STDERR
"fail: missing script name\n
";
6126 print STDERR
"Running $script\n\n
";
6128 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6129 print STDERR
"success: firmware script ran succcessfully\n
";
6131 print STDERR
"fail: firmware script returned error\n
";
6135 sub run_firmware_scripts {
6136 my ($opts, @dirs) = @_;
6137 # Run firmware packages
6138 for my $dir (@dirs) {
6139 print STDERR
"info: Running scripts in $dir\n
";
6140 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6141 while (my $s = readdir $dh) {
6142 next if $s =~ m/^\.\.?/;
6143 run_firmware_script($opts,
"$dir/$s
");
6151 print STDERR
"info: Downloading $url\n
";
6152 system(
"wget --quiet \
"$url\
"");
6157 my $product = `dmidecode -s system-product-name`;
6160 if ($product =~ m/PowerEdge/) {
6162 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6163 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6165 my $tmpdir = tempdir(
6169 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6170 system(
'gunzip Catalog.xml.gz
');
6171 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6172 # -q is quiet, disabling interactivity and reducing console output
6173 my $fwopts =
"-q
";
6175 for my $url (@paths) {
6176 fetch_dell_fw($url);
6178 run_firmware_scripts($fwopts, $tmpdir);
6180 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6181 print STDERR
"error: Please report to $errorsto.\n
";
6185 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6186 print STDERR
"error: Please report to $errorsto.\n
";
6192 my $url =
"ftp://ftp.us.dell.com/$path
";
6196 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6197 # firmware packages to download from Dell. Only work for Linux
6198 # machines and
11th generation Dell servers.
6199 sub fetch_dell_fw_list {
6200 my $filename = shift;
6202 my $product = `dmidecode -s system-product-name`;
6204 my ($mybrand, $mymodel) = split(/\s+/, $product);
6206 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6208 my $xml = XMLin($filename);
6210 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6211 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6212 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6214 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6215 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6217 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6219 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6221 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6224 for my $component (@{$xml-
>{SoftwareComponent}}) {
6225 my $componenttype = $component-
>{ComponentType}-
>{value};
6227 # Drop application packages, only firmware and BIOS
6228 next if
'APAC
' eq $componenttype;
6230 my $cpath = $component-
>{path};
6231 for my $path (@paths) {
6232 if ($cpath =~ m%/$path$%) {
6233 push(@paths, $cpath);
6241 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6242 it could work on other platforms with some tweaking. Anyone know a
6243 index like Catalog.xml is available from HP for HP servers? At the
6244 moment I maintain a similar list manually and it is quickly getting
6250 <title>How is booting into runlevel
1 different from single user boots?
</title>
6251 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6252 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6253 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6254 <description><p
>Wouter Verhelst have some
6255 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6256 comments and opinions
</a
> on my blog post on
6257 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6258 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6259 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6260 default KDE desktop in Debian
</a
>. I only have time to address one
6261 small piece of his comment now, and though it best to address the
6262 misunderstanding he bring forward:
</p
>
6264 <p
><blockquote
>
6265 Currently, a system admin has four options: [...] boot to a
6266 single-user system (by adding
'single
' to the kernel command line;
6267 this runs rcS and rc1 scripts)
6268 </blockquote
></p
>
6270 <p
>This make me believe Wouter believe booting into single user mode
6271 and booting into runlevel
1 is the same. I am not surprised he
6272 believe this, because it would make sense and is a quite sensible
6273 thing to believe. But because the boot in Debian is slightly broken,
6274 runlevel
1 do not work properly and it isn
't the same as single user
6275 mode. I
'll try to explain what is actually happing, but it is a bit
6276 hard to explain.
</p
>
6278 <p
>Single user mode is defined like this in /etc/inittab:
6279 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6280 executed in single user mode is sulogin. Single user mode is a boot
6281 state
"between
" the runlevels, and when booting into single user mode,
6282 only the scripts in /etc/rcS.d/ are executed before the init process
6283 enters the single user state. When switching to runlevel
1, the state
6284 is in fact not ending in runlevel
1, but it passes through runlevel
1
6285 and end up in the single user mode (see /etc/rc1.d/S03single, which
6286 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6287 1. It is confusing that the
'S
' (single user) init mode is not the
6288 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6291 <p
>This summary might make it clearer. When booting for the first
6292 time into single user mode, the following commands are executed:
6293 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6294 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6295 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6296 trying to continue after visiting single user mode. Not all services
6297 are started again as they should, causing the machine to end up in an
6298 unpredicatble state. This is why Debian admins recommend rebooting
6299 after visiting single user mode.
</p
>
6301 <p
>A similar problem with runlevel
1 is caused by the amount of
6302 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6303 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6304 stopped when passing through the scripts in /etc/rc1.d/, and not
6305 started again when switching away from runlevel
1 to the runlevels
6306 2-
5. I believe the problem is best fixed by moving all the scripts
6307 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6308 functioning single user mode during boot.
</p
>
6310 <p
>I have spent several years investigating the Debian boot system,
6311 and discovered this problem a few years ago. I suspect it originates
6312 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6317 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6318 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6320 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6321 <description><p
>In the Debian boot system, several packages include scripts that
6322 are started from /etc/rcS.d/. In fact, there is a bite more of them
6323 than make sense, and this causes a few problems. What kind of
6324 problems, you might ask. There are at least two problems. The first
6325 is that it is not possible to recover a machine after switching to
6326 runlevel
1. One need to actually reboot to get the machine back to
6327 the expected state. The other is that single user boot will sometimes
6328 run into problems because some of the subsystems are activated before
6329 the root login is presented, causing problems when trying to recover a
6330 machine from a problem in that subsystem. A minor additional point is
6331 that moving more scripts out of rcS.d/ and into the other rc#.d/
6332 directories will increase the amount of scripts that can run in
6333 parallel during boot, and thus decrease the boot time.
</p
>
6335 <p
>So, which scripts should start from rcS.d/. In short, only the
6336 scripts that _have_ to execute before the root login prompt is
6337 presented during a single user boot should go there. Everything else
6338 should go into the numeric runlevels. This means things like
6339 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6340 the numeric runlevels. Today in Debian, there are around
115 init.d
6341 scripts that are started from rcS.d/, and most of them should be moved
6342 out. Do your package have one of them? Please help us make single
6343 user and runlevel
1 better by moving it.
</p
>
6345 <p
>Scripts setting up the screen, keyboard, system partitions
6346 etc. should still be started from rcS.d/, but there is for example no
6347 need to have the network enabled before the single user login prompt
6348 is presented.
</p
>
6350 <p
>As always, things are not so easy to fix as they sound. To keep
6351 Debian systems working while scripts migrate and during upgrades, the
6352 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6353 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6354 and the next ones can only be moved when their dependencies have been
6355 moved first. This migration must be done sequentially while we ensure
6356 that the package system upgrade packages in the right order to keep
6357 the system state correct. This will require some coordination when it
6358 comes to network related packages, but most of the packages with
6359 scripts that should migrate do not have anything in rcS.d/ depending
6360 on them. Some packages have already been updated, like the sudo
6361 package, while others are still left to do. I wish I had time to work
6362 on this myself, but real live constrains make it unlikely that I will
6363 find time to push this forward.
</p
>
6368 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6369 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6370 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6371 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6372 <description><p
>While at Debconf11, I have several times during discussions
6373 mentioned the issues I believe should be improved in Debian for its
6374 desktop to be useful for more people. The use case for this is my
6375 parents, which are currently running Kubuntu which solve the
6378 <p
>I suspect these four missing features are not very hard to
6379 implement. After all, they are present in Ubuntu, so if we wanted to
6380 do this in Debian we would have a source.
</p
>
6384 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6385 are new packages available for upgrades, a icon in the KDE status bar
6386 indicate this, and clicking on it will activate the simple upgrade
6387 tool to handle it. I have no problem guiding both of my parents
6388 through the process over the phone. If a kernel reboot is required,
6389 this too is indicated by the status bars and the upgrade tool. Last
6390 time I checked, nothing with the same features was working in KDE in
6393 <li
><strong
>Simple handling of missing Firefox browser
6394 plugins.
</strong
> When the browser encounter a MIME type it do not
6395 currently have a handler for, it will ask the user if the system
6396 should search for a package that would add support for this MIME type,
6397 and if the user say yes, the APT sources will be searched for packages
6398 advertising the MIME type in their control file (visible in the
6399 Packages file in the APT archive). If one or more packages are found,
6400 it is a simple click of the mouse to add support for the missing mime
6401 type. If the package require the user to accept some non-free
6402 license, this is explained to the user. The entire process make it
6403 more clear to the user why something do not work in the browser, and
6404 make the chances higher for the user to blame the web page authors and
6405 not the browser for any missing features.
</li
>
6407 <li
><strong
>Simple handling of missing multimedia codec/format
6408 handlers.
</strong
> When the media players encounter a format or codec
6409 it is not supporting, a dialog pop up asking the user if the system
6410 should search for a package that would add support for it. This
6411 happen with things like MP3, Windows Media or H
.264. The selection
6412 and installation procedure is very similar to the Firefox browser
6413 plugin handling. This is as far as I know implemented using a
6414 gstreamer hook. The end result is that the user easily get access to
6415 the codecs that are present from the APT archives available, while
6416 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6418 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6419 displaying a text/plain file in my Debian browser, it will propose to
6420 start emacs to show it. If I remember correctly, when doing the same
6421 in Kunbutu it show the file as a text file in the browser. At least I
6422 know Opera will show text files within the browser. I much prefer the
6423 latter behaviour.
</li
>
6427 <p
>There are other nice features as well, like the simplified suite
6428 upgrader, but given that I am the one mostly doing the dist-upgrade,
6429 it do not matter much.
</p
>
6431 <p
>I really hope we could get these features in place for the next
6432 Debian release. It would require the coordinated effort of several
6433 maintainers, but would make the end user experience a lot better.
</p
>
6438 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6439 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6441 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6442 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6443 site is build on Debian/Squeeze, and this platform was chosen because
6444 I am most familiar with Debian (being a Debian Developer for around
10
6445 years) because it is the latest stable Debian release which should get
6446 security support for a few years.
</p
>
6448 <p
>The web service is written in Perl, and depend on some perl modules
6449 that are missing in Debian at the moment. It would be great if these
6450 modules were added to the Debian archive, allowing anyone to set up
6451 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6452 in their own country using only Debian packages. The list of modules
6453 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6454 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6455 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6456 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6457 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6458 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6459 easier in the future.
</p
>
6461 <p
>Thanks to the great tools in Debian, getting the missing modules
6462 installed on my server was a simple call to
'cpan2deb Module::Name
'
6463 and
'dpkg -i
' to install the resulting package. But this leave me
6464 with the responsibility of tracking security problems, which I really
6465 do not have time for.
</p
>
6470 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6471 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6472 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6473 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6474 <description><p
>Here is a small update for my English readers. Most of my blog
6475 posts have been in Norwegian the last few weeks, so here is a short
6476 update in English.
</p
>
6478 <p
>The kids still keep me too busy to get much free software work
6479 done, but I did manage to organise a project to get a Norwegian port
6480 of the British service
6481 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6482 and it has been running for a month now. The entire project has been
6483 organised by me and two others. Around Christmas we gathered sponsors
6484 to fund the development work. In January I drafted a contract with
6485 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6486 and in February the development took place. Most of it involved
6487 converting the source to use GPS coordinates instead of British
6488 easting/northing, and the resulting code should be a lot easier to get
6489 running in any country by now. The Norwegian
6490 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6491 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6492 source and the source for administrative borders in Norway, and
6493 support for this had to be added/fixed.
</p
>
6495 <p
>The Norwegian version went live March
3th, and we spent the weekend
6496 polishing the system before we announced it March
7th. The system is
6497 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6498 problem reports in a few weeks. Soon we hope to announce the Android
6499 and iPhone versions making it even easier to report problems with the
6500 public infrastructure.
</p
>
6502 <p
>Perhaps something to consider for those of you in countries without
6503 such service?
</p
>
6508 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6509 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6510 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6511 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6512 <description><p
>The last few days I have looked at ways to track open security
6513 issues here at my work with the University of Oslo. My idea is that
6514 it should be possible to use the information about security issues
6515 available on the Internet, and check our locally
6516 maintained/distributed software against this information. It should
6517 allow us to verify that no known security issues are forgotten. The
6518 CVE database listing vulnerabilities seem like a great central point,
6519 and by using the package lists from Debian mapped to CVEs provided by
6520 the testing security team, I believed it should be possible to figure
6521 out which security holes were present in our free software
6522 collection.
</p
>
6524 <p
>After reading up on the topic, it became obvious that the first
6525 building block is to be able to name software packages in a unique and
6526 consistent way across data sources. I considered several ways to do
6527 this, for example coming up with my own naming scheme like using URLs
6528 to project home pages or URLs to the Freshmeat entries, or using some
6529 existing naming scheme. And it seem like I am not the first one to
6530 come across this problem, as MITRE already proposed and implemented a
6531 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6532 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6533 software, hardware and other platform components. The CPE ids are
6534 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6535 Vulnerability Database
</a
>, allowing me to look up know security
6536 issues for any CPE name. With this in place, all I need to do is to
6537 locate the CPE id for the software packages we use at the university.
6538 This is fairly trivial (I google for
'cve cpe $package
' and check the
6539 NVD entry if a CVE for the package exist).
</p
>
6541 <p
>To give you an example. The GNU gzip source package have the CPE
6542 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6543 check out, one could look up
6544 <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
6545 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6546 The most recent one is
6547 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6548 and at the bottom of the NVD page for this vulnerability the complete
6549 list of affected versions is provided.
</p
>
6551 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6552 for offline processing of issues. Using this dump, I
've written a
6553 small script taking a list of CPEs as input and list all CVEs
6554 affecting the packages represented by these CPEs. One give it CPEs
6555 with version numbers as specified above and get a list of open
6556 security issues out.
</p
>
6558 <p
>Of course for this approach to be useful, the quality of the NVD
6559 information need to be high. For that to happen, I believe as many as
6560 possible need to use and contribute to the NVD database. I notice
6562 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6563 map from CVE to CPE
</a
>, indicating that they are using the CPE
6564 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6566 <p
>To get an idea about the quality for free software, I spent some
6567 time making it possible to compare the CVE database from Debian with
6568 the CVE database in NVD. The result look fairly good, but there are
6569 some inconsistencies in NVD (same software package having several
6570 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6571 Debian believe are affected by a CVE). Hope to find time to improve
6572 the quality of NVD, but that require being able to get in touch with
6573 someone maintaining it. So far my three emails with questions and
6574 corrections have not seen any reply, but I hope contact can be
6575 established soon.
</p
>
6577 <p
>An interesting application for CPEs is cross platform package
6578 mapping. It would be useful to know which packages in for example
6579 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6580 this would be trivial if all linux distributions provided CPE entries
6581 for their packages.
</p
>
6586 <title>Which module is loaded for a given PCI and USB device?
</title>
6587 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6588 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6589 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6590 <description><p
>In the
6591 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6592 package in Debian, there is a script to report useful information
6593 about the running hardware for use when people report missing
6594 information. One part of this script that I find very useful when
6595 debugging hardware problems, is the part mapping loaded kernel module
6596 to the PCI device it claims. It allow me to quickly see if the kernel
6597 module I expect is driving the hardware I am struggling with. To see
6598 the output, make sure discover-data is installed and run
6599 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6600 one of my machines like this:
</p
>
6604 10de:
03eb i2c_nforce2
6607 10de:
03f0 snd_hda_intel
6616 <p
>The code in question look like this, slightly modified for
6617 readability and to drop the output to file descriptor
3:
</p
>
6620 if [ -d /sys/bus/pci/devices/ ] ; then
6621 echo loaded pci modules:
6623 cd /sys/bus/pci/devices/
6624 for address in * ; do
6625 if [ -d
"$address/driver/module
" ] ; then
6626 module=`cd $address/driver/module ; pwd -P | xargs basename`
6627 if grep -q
"^$module
" /proc/modules ; then
6628 address=$(echo $address |sed s/
0000://)
6629 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6630 echo
"$id $module
"
6639 <p
>Similar code could be used to extract USB device module
6643 if [ -d /sys/bus/usb/devices/ ] ; then
6644 echo loaded usb modules:
6646 cd /sys/bus/usb/devices/
6647 for address in * ; do
6648 if [ -d
"$address/driver/module
" ] ; then
6649 module=`cd $address/driver/module ; pwd -P | xargs basename`
6650 if grep -q
"^$module
" /proc/modules ; then
6651 address=$(echo $address |sed s/
0000://)
6652 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6653 if [
"$id
" ] ; then
6654 echo
"$id $module
"
6664 <p
>This might perhaps be something to include in other tools as
6670 <title>How to test if a laptop is working with Linux
</title>
6671 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6673 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6674 <description><p
>The last few days I have spent at work here at the
<a
6675 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6676 batch of computers will work with Linux. Every year for the last few
6677 years the university have organised shared bid of a few thousand
6678 computers, and this year HP won the bid. Two different desktops and
6679 five different laptops are on the list this year. We in the UNIX
6680 group want to know which one of these computers work well with RHEL
6681 and Ubuntu, the two Linux distributions we currently handle at the
6682 university.
</p
>
6684 <p
>My test method is simple, and I share it here to get feedback and
6685 perhaps inspire others to test hardware as well. To test, I PXE
6686 install the OS version of choice, and log in as my normal user and run
6687 a few applications and plug in selected pieces of hardware. When
6688 something fail, I make a note about this in the test matrix and move
6689 on. If I have some spare time I try to report the bug to the OS
6690 vendor, but as I only have the machines for a short time, I rarely
6691 have the time to do this for all the problems I find.
</p
>
6693 <p
>Anyway, to get to the point of this post. Here is the simple tests
6694 I perform on a new model.
</p
>
6698 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6699 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6700 RHEL5 and Debian Edu/Squeeze.
</li
>
6702 <li
>Is X.org working? If the graphical login screen show up after
6703 installation, X.org is working.
</li
>
6705 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6706 package mesa-utils on Ubuntu) and writing down the frames per second
6707 reported by the program.
</li
>
6709 <li
>Is sound working? With Gnome and KDE, a sound is played when
6710 logging in, and if I can hear this the test is successful. If there
6711 are several audio exits on the machine, I try them all and check if
6712 the Gnome/KDE audio mixer can control where to send the sound. I
6713 normally test this by playing
6714 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6715 video
</a
> in Firefox/Iceweasel.
</li
>
6717 <li
>Is the USB subsystem working? I test this by plugging in a USB
6718 memory stick and see if Gnome/KDE notices this.
</li
>
6720 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6721 I have lying around, and see if Gnome/KDE notices this.
</li
>
6723 <li
>Is any built in camera working? Test using cheese, and see if a
6724 picture from the v4l device show up.
</li
>
6726 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6727 any bluetooth devices are discovered. In my office, I normally see a
6730 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6731 memory modules lying around, and stick them in and see if Gnome/KDE
6732 notice this.
</li
>
6734 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6735 special button work, and if the laptop continue to work after
6738 <li
>For laptops, is the extra buttons working, like audio level,
6739 adjusting background light, switching on/off external video output,
6740 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6741 laptop to laptop, so I just write down which are working and which are
6744 <li
>Some laptops have smart card readers, finger print readers,
6745 acceleration sensors etc. I rarely test these, as I do not know how
6746 to quickly test if they are working or not, so I only document their
6747 existence.
</li
>
6751 <p
>By now I suspect you are really curious what the test results are
6752 for the HP machines I am testing. I
'm not done yet, so I will report
6753 the test results later. For now I can report that HP
8100 Elite work
6754 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6755 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6756 can see, I have most machines left to test. One interesting
6757 observation is that Ubuntu Lucid has almost twice the frame rate than
6758 RHEL6 with glxgears. No idea why.
</p
>
6763 <title>Some thoughts on BitCoins
</title>
6764 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6766 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6767 <description><p
>As I continue to explore
6768 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6769 what properties the system have, and how it will be affected by laws
6770 and regulations here in Norway. Here are some random notes.
</p
>
6772 <p
>One interesting thing to note is that since the transactions are
6773 verified using a peer to peer network, all details about a transaction
6774 is known to everyone. This means that if a BitCoin address has been
6775 published like I did with mine in my initial post about BitCoin, it is
6776 possible for everyone to see how many BitCoins have been transfered to
6777 that address. There is even a web service to look at the details for
6778 all transactions. There I can see that my address
6779 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6780 have received
16.06 Bitcoin, the
6781 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6782 address of Simon Phipps have received
181.97 BitCoin and the address
6783 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6784 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6785 every one of you that donated bitcoins to support my activity. The
6786 fact that anyone can see how much money was transfered to a given
6787 address make it more obvious why the BitCoin community recommend to
6788 generate and hand out a new address for each transaction. I
'm told
6789 there is no way to track which addresses belong to a given person or
6790 organisation without the person or organisation revealing it
6791 themselves, as Simon, EFF and I have done.
</p
>
6793 <p
>In Norway, and in most other countries, there are laws and
6794 regulations limiting how much money one can transfer across the border
6795 without declaring it. There are money laundering, tax and accounting
6796 laws and regulations I would expect to apply to the use of BitCoin.
6797 If the Skolelinux foundation
6798 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6799 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6800 normal bank transfers like EFF is doing, how should this be accounted?
6801 Given that it is impossible to know if money can cross the border or
6802 not, should everything or nothing be declared? What exchange rate
6803 should be used when calculating taxes? Would receivers have to pay
6804 income tax if the foundation were to pay Skolelinux contributors in
6805 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6807 <p
>For a currency to be useful and successful, it must be trusted and
6808 accepted by a lot of users. It must be possible to get easy access to
6809 the currency (as a wage or using currency exchanges), and it must be
6810 easy to spend it. At the moment BitCoin seem fairly easy to get
6811 access to, but there are very few places to spend it. I am not really
6812 a regular user of any of the vendor types currently accepting BitCoin,
6813 so I wonder when my kind of shop would start accepting BitCoins. I
6814 would like to buy electronics, travels and subway tickets, not herbs
6815 and books. :) The currency is young, and this will improve over time
6816 if it become popular, but I suspect regular banks will start to lobby
6817 to get BitCoin declared illegal if it become popular. I
'm sure they
6818 will claim it is helping fund terrorism and money laundering (which
6819 probably would be true, as is any currency in existence), but I
6820 believe the problems should be solved elsewhere and not by blaming
6821 currencies.
</p
>
6823 <p
>The process of creating new BitCoins is called mining, and it is
6824 CPU intensive process that depend on a bit of luck as well (as one is
6825 competing against all the other miners currently spending CPU cycles
6826 to see which one get the next lump of cash). The
"winner
" get
50
6827 BitCoin when this happen. Yesterday I came across the obvious way to
6828 join forces to increase ones changes of getting at least some coins,
6829 by coordinating the work on mining BitCoins across several machines
6830 and people, and sharing the result if one is lucky and get the
50
6832 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6833 if this sounds interesting. I have not had time to try to set up a
6834 machine to participate there yet, but have seen that running on ones
6835 own for a few days have not yield any BitCoins througth mining
6838 <p
>Update
2010-
12-
15: Found an
<a
6839 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6840 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6841 it was interesting to read. The arguments presented seem to be
6842 equally valid for gold, which was used as a currency for many years.
</p
>
6847 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6848 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6849 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6850 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6851 <description><p
>With this weeks lawless
6852 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6853 attacks
</a
> on Wikileak and
6854 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6855 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6856 not be trusted to handle money transactions.
6858 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6859 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6860 mine mentioned earlier. I decided to follow Simon
's example, and get
6861 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6862 some help from my friend to get it all running, and he even handed me
6863 some bitcoins to get started. I even donated a few bitcoins to Simon
6864 for helping me remember BitCoin.
</p
>
6866 <p
>So, what is bitcoins, you probably wonder? It is a digital
6867 crypto-currency, decentralised and handled using peer-to-peer
6868 networks. It allows anonymous transactions and prohibits central
6869 control over the transactions, making it impossible for governments
6870 and companies alike to block donations and other transactions. The
6871 source is free software, and while the key dependency wxWidgets
2.9
6872 for the graphical user interface is missing in Debian, the command
6873 line client builds just fine. Hopefully Jonas
6874 <a href=
"http://bugs.debian.org/
578157">will get the package into
6875 Debian
</a
> soon.
</p
>
6877 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6878 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6879 bitcoins
</a
> when selling services and goods, and there are even
6880 currency
"stock
" markets where the exchange rate is decided. There
6881 are not many users so far, but the concept seems promising. If you
6882 want to get started and lack a friend with any bitcoins to spare,
6884 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6885 bitcoin at the time of writing). Use
6886 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6887 on the current exchange rates.
</p
>
6889 <p
>As an experiment, I have decided to set up bitcoind on one of my
6890 machines. If you want to support my activity, please send Bitcoin
6891 donations to the address
6892 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6897 <title>Why isn
't Debian Edu using VLC?
</title>
6898 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6900 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6901 <description><p
>In the latest issue of Linux Journal, the readers choices were
6902 presented, and the winner among the multimedia player were VLC.
6903 Personally, I like VLC, and it is my player of choice when I first try
6904 to play a video file or stream. Only if VLC fail will I drag out
6905 gmplayer to see if it can do better. The reason is mostly the failure
6906 model and trust. When VLC fail, it normally pop up a error message
6907 reporting the problem. When mplayer fail, it normally segfault or
6908 just hangs. The latter failure mode drain my trust in the program.
<p
>
6910 <p
>But even if VLC is my player of choice, we have choosen to use
6911 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6912 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6913 plugin to play web videos seamlessly, and the VLC browser plugin is
6914 not very good. For example, it lack in-line control buttons, so there
6915 is no way for the user to pause the video. Also, when I
6916 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6917 tested the browser plugins
</a
> available in Debian, the VLC plugin
6918 failed on several video pages where mplayer based plugins worked. If
6919 the browser plugin for VLC was as good as the gecko-mediaplayer
6920 package (which uses mplayer), we would switch.
</P
>
6922 <p
>While VLC is a good player, its user interface is slightly
6923 annoying. The most annoying feature is its inconsistent use of
6924 keyboard shortcuts. When the player is in full screen mode, its
6925 shortcuts are different from when it is playing the video in a window.
6926 For example, space only work as pause when in full screen mode. I
6927 wish it had consisten shortcuts and that space also would work when in
6928 window mode. Another nice shortcut in gmplayer is [enter] to restart
6929 the current video. It is very nice when playing short videos from the
6930 web and want to restart it when new people arrive to have a look at
6931 what is going on.
</p
>
6936 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6937 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6938 <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>
6939 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6940 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6941 upgrade testing of the
6942 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6943 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6944 This seem like a very good idea, so I adjusted by test scripts and
6945 can now present the updated result from today:
</p
>
6947 <p
>This is for Gnome:
</p
>
6949 <p
>Installed using apt-get, missing with aptitude
</p
>
6951 <blockquote
><p
>
6956 browser-plugin-gnash
6963 freedesktop-sound-theme
6965 gconf-defaults-service
6980 gnome-desktop-environment
6984 gnome-session-canberra
6989 gstreamer0.10-fluendo-mp3
6995 libapache2-mod-dnssd
6998 libaprutil1-dbd-sqlite3
7001 libboost-date-time1.42
.0
7002 libboost-python1.42
.0
7003 libboost-thread1.42
.0
7005 libchamplain-gtk-
0.4-
0
7007 libclutter-gtk-
0.10-
0
7014 libfreerdp-plugins-standard
7029 libgnomepanel2.24-cil
7034 libgtksourceview2.0-common
7035 libmono-addins-gui0.2-cil
7036 libmono-addins0.2-cil
7037 libmono-cairo2.0-cil
7038 libmono-corlib2.0-cil
7039 libmono-i18n-west2.0-cil
7040 libmono-posix2.0-cil
7041 libmono-security2.0-cil
7042 libmono-sharpzip2.84-cil
7043 libmono-system2.0-cil
7046 libndesk-dbus-glib1.0-cil
7047 libndesk-dbus1.0-cil
7057 libtelepathy-farsight0
7066 nautilus-sendto-empathy
7070 python-aptdaemon-gtk
7072 python-beautifulsoup
7087 python-gtksourceview2
7098 python-pkg-resources
7105 python-twisted-conch
7111 python-zope.interface
7116 rhythmbox-plugin-cdrecorder
7123 system-config-printer-udev
7125 telepathy-mission-control-
5
7136 </p
></blockquote
>
7138 <p
>Installed using apt-get, removed with aptitude
</p
>
7140 <blockquote
><p
>
7146 fast-user-switch-applet
7165 libgtksourceview2.0-
0
7167 libsdl1.2debian-alsa
7173 system-config-printer
7178 </p
></blockquote
>
7180 <p
>Installed using aptitude, missing with apt-get
</p
>
7182 <blockquote
><p
>
7183 gstreamer0.10-gnomevfs
7184 </p
></blockquote
>
7186 <p
>Installed using aptitude, removed with apt-get
</p
>
7188 <blockquote
><p
>
7190 </p
></blockquote
>
7192 <p
>This is for KDE:
</p
>
7194 <p
>Installed using apt-get, missing with aptitude
</p
>
7196 <blockquote
><p
>
7198 </p
></blockquote
>
7200 <p
>Installed using apt-get, removed with aptitude
</p
>
7202 <blockquote
><p
>
7205 </p
></blockquote
>
7207 <p
>Installed using aptitude, missing with apt-get
</p
>
7209 <blockquote
><p
>
7223 kdeartwork-emoticons
7225 kdeartwork-theme-icon
7229 kdebase-workspace-bin
7230 kdebase-workspace-data
7244 kscreensaver-xsavers
7259 plasma-dataengines-workspace
7261 plasma-desktopthemes-artwork
7262 plasma-runners-addons
7263 plasma-scriptengine-googlegadgets
7264 plasma-scriptengine-python
7265 plasma-scriptengine-qedje
7266 plasma-scriptengine-ruby
7267 plasma-scriptengine-webkit
7268 plasma-scriptengines
7269 plasma-wallpapers-addons
7270 plasma-widget-folderview
7271 plasma-widget-networkmanagement
7275 xscreensaver-data-extra
7277 xscreensaver-gl-extra
7278 xscreensaver-screensaver-bsod
7279 </p
></blockquote
>
7281 <p
>Installed using aptitude, removed with apt-get
</p
>
7283 <blockquote
><p
>
7285 google-gadgets-common
7303 libggadget-qt-
1.0-
0b
7308 libkonqsidebarplugin4a
7317 libplasma-geolocation-interface4
7319 libplasmagenericshell4
7333 libsmokeknewstuff2-
3
7334 libsmokeknewstuff3-
3
7336 libsmokektexteditor3
7344 libsmokeqtnetwork4-
3
7350 libsmokeqtuitools4-
3
7362 plasma-dataengines-addons
7363 plasma-scriptengine-superkaramba
7364 plasma-widget-lancelot
7365 plasma-widgets-addons
7366 plasma-widgets-workspace
7370 update-notifier-common
7371 </p
></blockquote
>
7373 <p
>Running apt-get autoremove made the results using apt-get and
7374 aptitude a bit more similar, but there are still quite a lott of
7375 differences. I have no idea what packages should be installed after
7376 the upgrade, but hope those that do can have a look.
</p
>
7381 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7382 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7383 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7384 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7385 <description><p
>Most of the computers in use by the
7386 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7387 are virtual machines. And they have been Xen machines running on a
7388 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7389 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7390 bit harder that it could have been, because we set up the Xen virtual
7391 machines to get the virtual partitions from LVM, which as far as I
7392 know is not supported by KVM. So to migrate, we had to convert
7393 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7396 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7397 nice recipe
</a
> to do this, and wrote the following script to do the
7398 migration. It uses qemu-img from the qemu package to make the disk
7399 image, parted to partition it, losetup and kpartx to present the disk
7400 image partions as devices, and dd to copy the data. I NFS mounted the
7401 new servers storage area on the old server to do the migration.
</p
>
7407 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7412 if [ -z
"$
1" ] ; then
7413 echo
"Usage: $
0 &lt;hostname
&gt;
"
7419 if [ ! -e /dev/vg_data/$host-disk ] ; then
7420 echo
"error: unable to find LVM volume for $host
"
7424 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7425 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7426 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7427 totalsize=$(( ( $disksize + $swapsize ) ))
7430 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7431 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7433 parted $img mklabel msdos
7434 parted $img mkpart primary linux-swap
0 $disksize
7435 parted $img mkpart primary ext2 $disksize $totalsize
7436 parted $img set
1 boot on
7439 losetup /dev/loop0 $img
7440 kpartx -a /dev/loop0
7442 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7443 fsck.ext3 -f /dev/mapper/loop0p1 || true
7444 mkswap /dev/mapper/loop0p2
7446 kpartx -d /dev/loop0
7447 losetup -d /dev/loop0
7450 <p
>The script is perhaps so simple that it is not copyrightable, but
7451 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7453 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7454 the new disk image attached, installed grub-pc and linux-image-
686 and
7455 set up grub to boot from the disk image. After this, the KVM machines
7456 seem to work just fine.
</p
>
7461 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7462 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7463 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7464 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7465 <description><p
>I
'm still running upgrade testing of the
7466 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7467 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7468 status. Here is a short update based on a test I ran
20101118.
</p
>
7470 <p
>I still do not know what a correct migration should look like, so I
7471 report any differences between apt and aptitude and hope someone else
7472 can see if anything should be changed.
</p
>
7474 <p
>This is for Gnome:
</p
>
7476 <p
>Installed using apt-get, missing with aptitude
</p
>
7478 <blockquote
><p
>
7479 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7480 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7481 dmz-cursor-theme empathy empathy-common finger
7482 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7483 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7484 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7485 gnome-cards-data gnome-codec-install gnome-core
7486 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7487 gnome-search-tool gnome-session-canberra gnome-spell
7488 gnome-system-log gnome-themes-extras gnome-themes-more
7489 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7490 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7491 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7492 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7493 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7494 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7495 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7496 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7497 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7498 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7499 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7500 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7501 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7502 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7503 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7504 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7505 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7506 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7507 libmono-security2.0-cil libmono-sharpzip2.84-cil
7508 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7509 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7510 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7511 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7512 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7513 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7514 libxalan2-java libxerces2-java media-player-info mesa-utils
7515 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7516 nautilus-sendto-empathy openoffice.org-writer2latex
7517 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7518 python-aptdaemon python-aptdaemon-gtk python-axiom
7519 python-beautifulsoup python-bugbuddy python-clientform
7520 python-coherence python-configobj python-crypto python-cupshelpers
7521 python-cupsutils python-eggtrayicon python-elementtree
7522 python-epsilon python-evolution python-feedparser python-gdata
7523 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7524 python-gtksourceview2 python-httplib2 python-louie python-mako
7525 python-markupsafe python-mechanize python-nevow python-notify
7526 python-opengl python-openssl python-pam python-pkg-resources
7527 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7528 python-tagpy python-twisted-bin python-twisted-conch
7529 python-twisted-core python-twisted-web python-utidylib python-webkit
7530 python-xdg python-zope.interface remmina remmina-plugin-data
7531 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7532 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7533 software-center svgalibg1 system-config-printer-udev
7534 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7535 totem totem-coherence totem-mozilla totem-plugins
7536 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7538 </p
></blockquote
>
7540 Installed using apt-get, removed with aptitude
7542 <blockquote
><p
>
7543 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7544 epiphany-extensions epiphany-gecko evolution-exchange
7545 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7546 gedit-common gnome-app-install gnome-games gnome-games-data
7547 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7548 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7549 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7550 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7551 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7552 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7553 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7554 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7555 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7556 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7557 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7558 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7559 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7560 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7561 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7562 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7563 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7564 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7565 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7566 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7567 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7568 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7569 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7570 sound-juicer swfdec-gnome system-config-printer totem-common
7571 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7572 </p
></blockquote
>
7574 <p
>Installed using aptitude, missing with apt-get
</p
>
7576 <blockquote
><p
>
7577 gstreamer0.10-gnomevfs
7578 </p
></blockquote
>
7580 <p
>Installed using aptitude, removed with apt-get
</p
>
7582 <blockquote
><p
>
7584 </p
></blockquote
>
7586 <p
>This is for KDE:
</p
>
7588 <p
>Installed using apt-get, missing with aptitude
</p
>
7590 <blockquote
><p
>
7591 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7592 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7593 ghostscript-x git gnome-audio gnugo granatier gs-common
7594 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7595 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7596 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7597 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7598 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7599 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7600 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7601 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7602 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7603 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7604 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7605 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7606 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7607 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7608 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7609 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7610 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7611 libkrossui4 libmailtools-perl libmime-tools-perl
7612 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7613 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7614 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7615 lirc luatex marble networkstatus noatun-plugins
7616 openoffice.org-writer2latex palapeli palapeli-data parley
7617 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7618 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7619 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7621 </p
></blockquote
>
7623 <p
>Installed using apt-get, removed with aptitude
</p
>
7625 <blockquote
><p
>
7626 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7627 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7628 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7629 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7630 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7631 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7632 kitchensync kiten kjumpingcube klatin klettres klickety klines
7633 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7634 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7635 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7636 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7637 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7638 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7639 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7640 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7641 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7642 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7643 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7644 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7645 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7646 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7647 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7648 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7649 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7650 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7651 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7652 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7653 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7654 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7655 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7656 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7657 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7658 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7659 </p
></blockquote
>
7661 <p
>Installed using aptitude, missing with apt-get
</p
>
7663 <blockquote
><p
>
7664 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7665 kdeartwork kdebase kdebase-apps kdebase-workspace
7666 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7667 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7668 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7669 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7670 xscreensaver-screensaver-bsod
7671 </p
></blockquote
>
7673 <p
>Installed using aptitude, removed with apt-get
</p
>
7675 <blockquote
><p
>
7676 kdebase-bin konq-plugins konqueror
7677 </p
></blockquote
>
7682 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7683 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7685 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7686 <description><p
>Answering
7687 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7688 call from the Gnash project
</a
> for
7689 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7690 current source, I have set up a virtual KVM machine on the Debian
7691 Edu/Skolelinux virtualization host to test the git source on
7692 Debian/Squeeze. I hope this can help the developers in getting new
7693 releases out more often.
</p
>
7695 <p
>As the developers want less main-stream build platforms tested to,
7696 I have considered setting up a
<a
7697 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7698 machine as well. I have also considered using the kfreebsd
7699 architecture in Debian as a file server in NUUG to get access to the
5
7700 TB zfs volume we currently use to store DV video. Because of this, I
7701 finally got around to do a test installation of Debian/Squeeze with
7702 kfreebsd. Installation went fairly smooth, thought I noticed some
7703 visual glitches in the cdebconf dialogs (black cursor left on the
7704 screen at random locations). Have not gotten very far with the
7705 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7706 fatal problem. Have to spend some more time on it to see if it is
7707 useful as a file server for NUUG. Will try to find time to set up a
7708 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7713 <title>Debian in
3D
</title>
7714 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7715 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7716 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7717 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7719 <p
>3D printing is just great. I just came across this Debian logo in
7721 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7722 thingiverse blog
</a
>.
</p
>
7727 <title>Software updates
2010-
10-
24</title>
7728 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7730 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7731 <description><p
>Some updates.
</p
>
7733 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7734 raise money for the project is going well. The lower limit of
10
7735 signers was reached in
24 hours, and so far
13 people have signed it.
7736 More signers and more funding is most welcome, and I am really curious
7737 how far we can get before the time limit of December
24 is reached.
7740 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7741 about what appear to be a great code coverage tool capable of
7742 generating code coverage stats without any changes to the source code.
7744 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7745 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7746 It is missing in Debian, but the git source built just fine in Squeeze
7747 after I installed libelf-dev, libdwarf-dev, pkg-config and
7748 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7749 solvable. I hope kcov make it into Debian soon.
</p
>
7751 <p
>Finally found time to wrap up the release notes for
<a
7752 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7753 new alpha release of Debian Edu
</a
>, and just published the second
7754 alpha test release of the Squeeze based Debian Edu /
7755 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7756 release. Give it a try if you need a complete linux solution for your
7757 school, including central infrastructure server, workstations, thin
7758 client servers and diskless workstations. A nice touch added
7759 yesterday is RDP support on the thin client servers, for windows
7760 clients to get a Linux desktop on request.
</p
>
7765 <title>Some notes on Flash in Debian and Debian Edu
</title>
7766 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7767 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7768 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7769 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7770 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7771 second most popular used package that is missing in Debian. The sixth
7772 most popular is flashplayer-mozilla. This is a clear indication that
7773 working flash is important for Debian users. Around
10 percent of the
7774 users submitting data to popcon.debian.org have this package
7775 installed.
</p
>
7777 <p
>In the report written by Lars Risan in August
2008
7778 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7779 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7780 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7781 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7782 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7783 web sites require Flash to work, and lacking working Flash support in
7784 the web browser and the problems with installing it was perceived as a
7785 good reason to stay with Windows.
</p
>
7787 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7788 said to be the retarded cousin that did not really understand
7789 everything you told him but could work fairly well. This was a
7790 comment regarding the problems Linux have with proprietary formats and
7791 non-standard web pages, and is sad because it exposes a fairly common
7792 understanding of whose fault it is if web pages that only work in for
7793 example Internet Explorer
6 fail to work on Firefox, and funny because
7794 it explain very well how annoying it is for users when Linux
7795 distributions do not work with the documents they receive or the web
7796 pages they want to visit.
</p
>
7798 <p
>This is part of the reason why I believe it is important for Debian
7799 and Debian Edu to have a well working Flash implementation in the
7800 distribution, to get at least popular sites as Youtube and Google
7801 Video to working out of the box. For Squeeze, Debian have the chance
7802 to include the latest version of Gnash that will make this happen, as
7803 the new release
0.8.8 was published a few weeks ago and is resting in
7804 unstable. The new version work with more sites that version
0.8.7.
7805 The Gnash maintainers have asked for a freeze exception, but the
7806 release team have not had time to reply to it yet. I hope they agree
7807 with me that Flash is important for the Debian desktop users, and thus
7808 accept the new package into Squeeze.
</p
>
7813 <title>Circular package dependencies harms apt recovery
</title>
7814 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7815 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7816 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7817 <description><p
>I discovered this while doing
7818 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7819 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7820 in Debian still got circular dependencies, and it is often claimed
7821 that apt and aptitude should be able to handle this just fine, but
7822 some times these dependency loops causes apt to fail.
</p
>
7824 <p
>An example is from todays
7825 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7826 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7827 causes perl-modules to fail to upgrade. The cause is simple. If a
7828 package fail to unpack, then only part of packages with the circular
7829 dependency might end up being unpacked when unpacking aborts, and the
7830 ones already unpacked will fail to configure in the recovery phase
7831 because its dependencies are unavailable.
</p
>
7833 <p
>In this log, the problem manifest itself with this error:
</p
>
7835 <blockquote
><pre
>
7836 dpkg: dependency problems prevent configuration of perl-modules:
7837 perl-modules depends on perl (
>=
5.10.1-
1); however:
7838 Version of perl on system is
5.10.0-
19lenny
2.
7839 dpkg: error processing perl-modules (--configure):
7840 dependency problems - leaving unconfigured
7841 </pre
></blockquote
>
7843 <p
>The perl/perl-modules circular dependency is already
7844 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7845 hopefully be solved as soon as possible, but it is not the only one,
7846 and each one of these loops in the dependency tree can cause similar
7847 failures. Of course, they only occur when there are bugs in other
7848 packages causing the unpacking to fail, but it is rather nasty when
7849 the failure of one package causes the problem to become worse because
7850 of dependency loops.
</p
>
7853 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7854 tireless effort by Bill Allombert
</a
>, the number of circular
7856 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7857 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7859 <p
>Todays testing also exposed a bug in
7860 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7861 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7862 apt-get and aptitude, the latter possibly caused by some circular
7863 dependency. Reported both to BTS to try to get someone to look at
7869 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7870 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7872 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7873 <description><p
>This is a
7874 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7876 <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
7878 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7879 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7881 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7882 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7883 and dhcp3-server-ldap in Debian use the LDAP server. The two
7884 implementations are quite different in how they use LDAP.
</p
>
7886 To get this information, I started slapd with debugging enabled and
7887 dumped the debug output to a file to get the LDAP searches performed
7888 on a Debian Edu main-server. Here is a summary.
7890 <p
><strong
>powerdns
</strong
></p
>
7892 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7893 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7896 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7897 One
"strict
" mode where the forward and reverse DNS lookups are done
7898 using the same LDAP objects, and a
"tree
" mode where the forward and
7899 reverse entries are in two different subtrees in LDAP with a structure
7900 based on the DNS names, as in tjener.intern and
7901 2.2.0.10.in-addr.arpa.
</p
>
7903 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7904 base, and uses a
"base
" scoped search for the DNS name by adding
7905 "dc=tjener,dc=intern,
" to the base with a filter for
7906 "(associateddomain=tjener.intern)
" for the forward entry and
7907 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7908 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7909 forward entries, it is looking for attributes named dnsttl, arecord,
7910 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7911 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7912 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7913 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7914 spfrecord and modifytimestamp. For reverse entries it is looking for
7915 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7916 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7917 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7918 ldapsearch commands could look like this:
</p
>
7920 <blockquote
><pre
>
7921 ldapsearch -h ldap \
7922 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7923 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7924 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7925 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7926 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7927 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7929 ldapsearch -h ldap \
7930 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7931 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7932 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7933 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7934 srvrecord naptrrecord modifytimestamp
7935 </pre
></blockquote
>
7937 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7938 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7939 example LDAP objects used there. In addition to these objects, the
7940 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7941 also exist.
</p
>
7943 <blockquote
><pre
>
7944 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7946 objectclass: dnsdomain
7947 objectclass: domainrelatedobject
7950 associateddomain: tjener.intern
7952 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7954 objectclass: dnsdomain2
7955 objectclass: domainrelatedobject
7957 ptrrecord: tjener.intern
7958 associateddomain:
2.2.0.10.in-addr.arpa
7959 </pre
></blockquote
>
7961 <p
>In strict mode, the server behaves differently. When looking for
7962 forward DNS entries, it is doing a
"subtree
" scoped search with the
7963 same base as in the tree mode for a object with filter
7964 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7965 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7966 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7967 naptrrecord and modifytimestamp. For reverse entires it also do a
7968 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7969 and the requested attributes are associateddomain, dnsttl and
7970 modifytimestamp. In short, in strict mode the objects with ptrrecord
7971 go away, and the arecord attribute in the forward object is used
7974 <p
>The forward and reverse searches can be simulated using ldapsearch
7975 like this:
</p
>
7977 <blockquote
><pre
>
7978 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7979 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7980 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7981 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7982 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7983 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7985 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7986 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7987 </pre
></blockquote
>
7989 <p
>In addition to the forward and reverse searches , there is also a
7990 search for SOA records, which behave similar to the forward and
7991 reverse lookups.
</p
>
7993 <p
>A thing to note with the PowerDNS behaviour is that it do not
7994 specify any objectclass names, and instead look for the attributes it
7995 need to generate a DNS reply. This make it able to work with any
7996 objectclass that provide the needed attributes.
</p
>
7998 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7999 dnsdomain2 schemas. The latter is used for reverse entries like
8000 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8002 <p
>In Debian Edu, we have created DNS objects using the object classes
8003 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8004 attributes) and domainrelatedobject (for associatedDomain). The use
8005 of structural object classes make it impossible to combine these
8006 classes with the object classes used by DHCP.
</p
>
8008 <p
>There are other schemas that could be used too, for example the
8009 dnszone structural object class used by Gosa and bind-sdb for the DNS
8010 attributes combined with the domainrelatedobject object class, but in
8011 this case some unused attributes would have to be included as well
8012 (zonename and relativedomainname).
</p
>
8014 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8015 mode and not use any of the existing objectclasses (dnsdomain,
8016 dnsdomain2 and dnszone) when one want to combine the DNS information
8017 with DHCP information, and instead create a auxiliary object class
8018 defined something like this (using the attributes defined for
8019 dnsdomain and dnsdomain2 or dnszone):
</p
>
8021 <blockquote
><pre
>
8022 objectclass ( some-oid NAME
'dnsDomainAux
'
8025 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8026 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8027 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8028 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8029 A6Record $ DNAMERecord
8031 </pre
></blockquote
>
8033 <p
>This will allow any object to become a DNS entry when combined with
8034 the domainrelatedobject object class, and allow any entity to include
8035 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8036 developers asking for their view on this schema and if they are
8037 interested in providing such schema with PowerDNS, and I hope my
8038 message will be accepted into their mailing list soon.
</p
>
8040 <p
><strong
>ISC dhcp
</strong
></p
>
8042 <p
>The DHCP server searches for specific objectclass and requests all
8043 the object attributes, and then uses the attributes it want. This
8044 make it harder to figure out exactly what attributes are used, but
8045 thanks to the working example in Debian Edu I can at least get an idea
8046 what is needed without having to read the source code.
</p
>
8048 <p
>In the DHCP server configuration, the LDAP base to use and the
8049 search filter to use to locate the correct dhcpServer entity is
8050 stored. These are the relevant entries from
8051 /etc/dhcp3/dhcpd.conf:
</p
>
8053 <blockquote
><pre
>
8054 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8055 ldap-dhcp-server-cn
"dhcp
";
8056 </pre
></blockquote
>
8058 <p
>The DHCP server uses this information to nest all the DHCP
8059 configuration it need. The cn
"dhcp
" is located using the given LDAP
8060 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8061 search result is this entry:
</p
>
8063 <blockquote
><pre
>
8064 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8067 objectClass: dhcpServer
8068 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8069 </pre
></blockquote
>
8071 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8072 subtree with DHCP configuration. The DHCP configuration subtree base
8073 is located using a base scope search with base
"cn=DHCP
8074 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8075 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8076 The search result is this entry:
</p
>
8078 <blockquote
><pre
>
8079 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8082 objectClass: dhcpService
8083 objectClass: dhcpOptions
8084 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8085 dhcpStatements: ddns-update-style none
8086 dhcpStatements: authoritative
8087 dhcpOption: smtp-server code
69 = array of ip-address
8088 dhcpOption: www-server code
72 = array of ip-address
8089 dhcpOption: wpad-url code
252 = text
8090 </pre
></blockquote
>
8092 <p
>Next, the entire subtree is processed, one level at the time. When
8093 all the DHCP configuration is loaded, it is ready to receive requests.
8094 The subtree in Debian Edu contain objects with object classes
8095 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8096 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8097 and information about netmasks, dynamic range etc. Leaving out the
8098 details here because it is not relevant for the focus of my
8099 investigation, which is to see if it is possible to merge dns and dhcp
8100 related computer objects.
</p
>
8102 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8103 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8104 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8105 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8106 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8109 <blockquote
><pre
>
8110 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8113 objectClass: dhcpHost
8114 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8115 dhcpStatements: fixed-address hostname
8116 </pre
></blockquote
>
8118 <p
>There is less flexiblity in the way LDAP searches are done here.
8119 The object classes need to have fixed names, and the configuration
8120 need to be stored in a fairly specific LDAP structure. On the
8121 positive side, the invidiual dhcpHost entires can be anywhere without
8122 the DN pointed to by the dhcpServer entries. The latter should make
8123 it possible to group all host entries in a subtree next to the
8124 configuration entries, and this subtree can also be shared with the
8125 DNS server if the schema proposed above is combined with the dhcpHost
8126 structural object class.
8128 <p
><strong
>Conclusion
</strong
></p
>
8130 <p
>The PowerDNS implementation seem to be very flexible when it come
8131 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8132 come to the the LDAP structure, the
"strict
" mode is very flexible,
8133 allowing DNS objects to be stored anywhere under the base cn specified
8134 in the configuration.
</p
>
8136 <p
>The DHCP implementation on the other hand is very inflexible, both
8137 regarding which LDAP schemas to use and which LDAP structure to use.
8138 I guess one could implement ones own schema, as long as the
8139 objectclasses and attributes have the names used, but this do not
8140 really help when the DHCP subtree need to have a fairly fixed
8141 structure.
</p
>
8143 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8144 this might work for Debian Edu:
</p
>
8146 <blockquote
><pre
>
8148 cn=machine-info (dhcpService) - dhcpServiceDN points here
8149 cn=dhcp (dhcpServer)
8150 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8151 cn=
10.0.2.0 (dhcpSubnet)
8152 cn=group1 (dhcpGroup/dhcpOptions)
8153 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8154 cn=
192.168.0.0 (dhcpSubnet)
8155 cn=group1 (dhcpGroup/dhcpOptions)
8156 ou=machines - PowerDNS base points here
8157 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8158 </pre
></blockquote
>
8160 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8161 entries to be in the dhcpGroup subtrees, the entries can be stored
8162 there instead of a common machines subtree, and the PowerDNS base
8163 would have to be moved one level up to the machine-info subtree.
</p
>
8165 <p
>The combined object under the machines subtree would look something
8166 like this:
</p
>
8168 <blockquote
><pre
>
8169 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8172 objectClass: dhcpHost
8173 objectclass: domainrelatedobject
8174 objectclass: dnsDomainAux
8175 associateddomain: hostname.intern
8176 arecord:
10.11.12.13
8177 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8178 dhcpStatements: fixed-address hostname.intern
8179 </pre
></blockquote
>
8181 </p
>One could even add the LTSP configuration associated with a given
8182 machine, as long as the required attributes are available in a
8183 auxiliary object class.
</p
>
8188 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8189 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8190 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8191 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8192 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8193 DHCP services in Debian Edu to use the same LDAP objects for a given
8194 computer, to avoid the possibility of having a inconsistent state for
8195 a computer in LDAP (as in DHCP but no DNS entry or the other way
8196 around) and make it easier to add computers to LDAP.
</p
>
8198 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8199 information finally found a solution that seem to work.
</p
>
8201 <p
>The old setup required three LDAP objects for a given computer.
8202 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8203 we switch powerdns to use its strict LDAP method (ldap-method=strict
8204 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8205 merged into one while making it impossible to transfer the reverse map
8206 to a slave DNS server.
</p
>
8208 <p
>If we also replace the object class used to get the DNS related
8209 attributes to one allowing these attributes to be combined with the
8210 dhcphost object class, we can merge the DNS and DHCP entries into one.
8211 I
've written such object class in the dnsdomainaux.schema file (need
8212 proper OIDs, but that is a minor issue), and tested the setup. It
8213 seem to work.
</p
>
8215 <p
>With this test setup in place, we can get away with one LDAP object
8216 for both DNS and DHCP, and even the LTSP configuration I suggested in
8217 an earlier email. The combined LDAP object will look something like
8220 <blockquote
><pre
>
8221 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8223 objectClass: dhcphost
8224 objectclass: domainrelatedobject
8225 objectclass: dnsdomainaux
8226 associateddomain: hostname.intern
8227 arecord:
10.11.12.13
8228 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8229 dhcpstatements: fixed-address hostname
8231 </pre
></blockquote
>
8233 <p
>The DNS server uses the associateddomain and arecord entries, while
8234 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8235 before asking DNS to resolve the fixed-adddress. LTSP will use
8236 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8238 <p
>I am not yet sure if I can get the DHCP server to look for its
8239 dhcphost in a different location, to allow us to put the objects
8240 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8241 that. If I can
't figure out a way to do that, we can still get rid of
8242 the hosts subtree and move all its content into the DHCP Config tree
8243 (which probably should be renamed to be more related to the new
8244 content. I suspect cn=dnsdhcp,ou=services or something like that
8245 might be a good place to put it.
</p
>
8247 <p
>If you want to help out with implementing this for Debian Edu,
8248 please contact us on debian-edu@lists.debian.org.
</p
>
8253 <title>Idea for storing LTSP configuration in LDAP
</title>
8254 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8256 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8257 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8258 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8259 clients, and that this can be used to fetch configuration from LDAP if
8260 Debian Edu choose to store configuration there.
</p
>
8262 <p
>Armed with this information, I got inspired and wrote a test module
8263 to get configuration from LDAP. The idea is to look up the MAC
8264 address of the client in LDAP, and look for attributes on the form
8265 ltspconfigsetting=value, and use this to export SETTING=value to the
8266 LTSP clients.
</p
>
8268 <p
>The goal is to be able to store the LTSP configuration attributes
8269 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8270 allowing us to store all information about a computer in one place.
</p
>
8272 <p
>This is a untested draft implementation, and I welcome feedback on
8273 this approach. A real LDAP schema for the ltspClientAux objectclass
8274 need to be written. Comments, suggestions, etc?
</p
>
8276 <blockquote
><pre
>
8277 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8279 # Fetch LTSP client settings from LDAP based on MAC address
8281 # Uses ethernet address as stored in the dhcpHost objectclass using
8282 # the dhcpHWAddress attribute or ethernet address stored in the
8283 # ieee802Device objectclass with the macAddress attribute.
8285 # This module is written to be schema agnostic, and only depend on the
8286 # existence of attribute names.
8288 # The LTSP configuration variables are saved directly using a
8289 # ltspConfig prefix and uppercasing the rest of the attribute name.
8290 # To set the SERVER variable, set the ltspConfigServer attribute.
8292 # Some LDAP schema should be created with all the relevant
8293 # configuration settings. Something like this should work:
8295 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8298 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8300 LDAPSERVER=$(debian-edu-ldapserver)
8301 if [
"$LDAPSERVER
" ] ; then
8302 LDAPBASE=$(debian-edu-ldapserver -b)
8303 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8304 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8305 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8306 grep
'^ltspConfig
' | while read attr value ; do
8307 # Remove prefix and convert to upper case
8308 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8309 # bass value on to clients
8310 eval
"$attr=$value; export $attr
"
8314 </pre
></blockquote
>
8316 <p
>I
'm not sure this shell construction will work, because I suspect
8317 the while block might end up in a subshell causing the variables set
8318 there to not show up in ltsp-config, but if that is the case I am sure
8319 the code can be restructured to make sure the variables are passed on.
8320 I expect that can be solved with some testing. :)
</p
>
8322 <p
>If you want to help out with implementing this for Debian Edu,
8323 please contact us on debian-edu@lists.debian.org.
</p
>
8325 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8326 configuration in LDAP that was created around year
2000 by
8327 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8328 Xperience, Inc.,
2000</a
>. I found its
8329 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8330 personal home page over at redhat.com.
</p
>
8335 <title>jXplorer, a very nice LDAP GUI
</title>
8336 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8338 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8339 <description><p
>Since
8340 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8341 last post
</a
> about available LDAP tools in Debian, I was told about a
8342 LDAP GUI that is even better than luma. The java application
8343 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8344 moving LDAP objects and subtrees using drag-and-drop, and can
8345 authenticate using Kerberos. I have only tested the Kerberos
8346 authentication, but do not have a LDAP setup allowing me to rewrite
8347 LDAP with my test user yet. It is
8348 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8349 Debian
</a
> testing and unstable at the moment. The only problem I
8350 have with it is how it handle errors. If something go wrong, its
8351 non-intuitive behaviour require me to go through some query work list
8352 and remove the failing query. Nothing big, but very annoying.
</p
>
8357 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8358 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8360 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8361 <description><p
>Here is a short update on my
<a
8362 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8363 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8364 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8365 not reporting the status for KDE, because the upgrade crashes when
8366 aptitude try because of missing conflicts
8367 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8368 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8370 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8371 complete list of the installed packages. Based on this I see these
8372 differences when I did a test run today. As usual, I do not really
8373 know what the correct set of packages would be, but thought it best to
8374 publish the difference.
</p
>
8376 <p
>Installed using apt-get, missing with aptitude
</p
>
8378 <blockquote
><p
>
8379 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8380 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8381 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8382 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8383 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8384 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8385 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8386 python-gtkmozembed svgalibg1 xserver-xephyr zip
8387 </p
></blockquote
>
8389 <p
>Installed using apt-get, removed with aptitude
</p
>
8391 <blockquote
><p
>
8392 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8393 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8394 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8395 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8396 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8397 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8398 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8399 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8400 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8401 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8402 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8403 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8404 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8405 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8406 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8407 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8408 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8409 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8410 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8411 mysql-common swfdec-gnome totem-gstreamer wodim
8412 </p
></blockquote
>
8414 <p
>Installed using aptitude, missing with apt-get
</p
>
8416 <blockquote
><p
>
8417 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8418 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8419 xserver-xorg-input-all xserver-xorg-input-evdev
8420 xserver-xorg-input-kbd xserver-xorg-input-mouse
8421 xserver-xorg-input-synaptics xserver-xorg-video-all
8422 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8423 xserver-xorg-video-chips xserver-xorg-video-cirrus
8424 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8425 xserver-xorg-video-glint xserver-xorg-video-i128
8426 xserver-xorg-video-i740 xserver-xorg-video-mach64
8427 xserver-xorg-video-mga xserver-xorg-video-neomagic
8428 xserver-xorg-video-nouveau xserver-xorg-video-nv
8429 xserver-xorg-video-r128 xserver-xorg-video-radeon
8430 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8431 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8432 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8433 xserver-xorg-video-sis xserver-xorg-video-sisusb
8434 xserver-xorg-video-tdfx xserver-xorg-video-tga
8435 xserver-xorg-video-trident xserver-xorg-video-tseng
8436 xserver-xorg-video-vesa xserver-xorg-video-vmware
8437 xserver-xorg-video-voodoo
8438 </p
></blockquote
>
8440 <p
>Installed using aptitude, removed with apt-get
</p
>
8442 <blockquote
><p
>
8443 deskbar-applet xserver-xorg xserver-xorg-core
8444 xserver-xorg-input-wacom xserver-xorg-video-intel
8445 xserver-xorg-video-openchrome
8446 </p
></blockquote
>
8448 <p
>I was told on IRC that the xorg-xserver package was
8449 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8450 in git
</a
> today to try to get apt-get to not remove xorg completely.
8451 No idea when it hits Squeeze, but when it does I hope it will reduce
8452 the difference somewhat.
8457 <title>LUMA, a very nice LDAP GUI
</title>
8458 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8460 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8461 <description><p
>The last few days I have been looking into the status of the LDAP
8462 directory in Debian Edu, and in the process I started to miss a GUI
8463 tool to browse the LDAP tree. The only one I was able to find in
8464 Debian/Squeeze and Lenny is
8465 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8466 be a great tool to get a overview of the current LDAP directory
8467 populated by default in Skolelinux. Thanks to it, I have been able to
8468 find empty and obsolete subtrees, misplaced objects and duplicate
8469 objects. It will be installed by default in Debian/Squeeze. If you
8470 are working with LDAP, give it a go. :)
</p
>
8472 <p
>I did notice one problem with it I have not had time to report to
8473 the BTS yet. There is no .desktop file in the package, so the tool do
8474 not show up in the Gnome and KDE menus, but only deep down in in the
8475 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8478 <p
>I have not yet been able to get it to modify the tree yet. I would
8479 like to move objects and remove subtrees directly in the GUI, but have
8480 not found a way to do that with LUMA yet. So in the mean time, I use
8481 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8483 <p
>If you have tips on other GUI tools for LDAP that might be useful
8484 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8486 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8487 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8488 useful GUI alternative. It seem like a good tool, but is unmaintained
8489 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8490 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8495 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8496 <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>
8497 <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>
8498 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8499 <description><p
>A while back, I
8500 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8501 about the fact
</a
> that it is not possible with the provided schemas
8502 for storing DNS and DHCP information in LDAP to combine the two sets
8503 of information into one LDAP object representing a computer.
</p
>
8505 <p
>In the mean time, I discovered that a simple fix would be to make
8506 the dhcpHost object class auxiliary, to allow it to be combined with
8507 the dNSDomain object class, and thus forming one object for one
8508 computer when storing both DHCP and DNS information in LDAP.
</p
>
8510 <p
>If I understand this correctly, it is not safe to do this change
8511 without also changing the assigned number for the object class, and I
8512 do not know enough about LDAP schema design to do that properly for
8513 Debian Edu.
</p
>
8515 <p
>Anyway, for future reference, this is how I believe we could change
8517 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8518 schema
</a
> to solve at least part of the problem with the LDAP schemas
8519 available today from IETF.
</p
>
8522 --- dhcp.schema (revision
65192)
8523 +++ dhcp.schema (working copy)
8525 objectclass (
2.16.840.1.113719.1.203.6.6
8526 NAME
'dhcpHost
'
8527 DESC
'This represents information about a particular client
'
8531 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8532 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8535 <p
>I very much welcome clues on how to do this properly for Debian
8536 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8537 package, and should thus be free to rewrite it as we see fit.
</p
>
8539 <p
>If you want to help out with implementing this for Debian Edu,
8540 please contact us on debian-edu@lists.debian.org.
</p
>
8545 <title>Calling tasksel like the installer, while still getting useful output
</title>
8546 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8547 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8548 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8549 <description><p
>A few times I have had the need to simulate the way tasksel
8550 installs packages during the normal debian-installer run. Until now,
8551 I have ended up letting tasksel do the work, with the annoying problem
8552 of not getting any feedback at all when something fails (like a
8553 conffile question from dpkg or a download that fails), using code like
8556 <blockquote
><pre
>
8557 export DEBIAN_FRONTEND=noninteractive
8558 tasksel --new-install
8559 </pre
></blockquote
>
8561 This would invoke tasksel, let its automatic task selection pick the
8562 tasks to install, and continue to install the requested tasks without
8563 any output what so ever.
8565 Recently I revisited this problem while working on the automatic
8566 package upgrade testing, because tasksel would some times hang without
8567 any useful feedback, and I want to see what is going on when it
8568 happen. Then it occured to me, I can parse the output from tasksel
8569 when asked to run in test mode, and use that aptitude command line
8570 printed by tasksel then to simulate the tasksel run. I ended up using
8573 <blockquote
><pre
>
8574 export DEBIAN_FRONTEND=noninteractive
8575 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8577 </pre
></blockquote
>
8579 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8580 --without-recommends -o APT::Install-Recommends=no -y install
8581 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8582 ~pimportant
</tt
>", which will install the gnome desktop task, the
8583 laptop task and all packages with priority standard , required and
8584 important, just like tasksel would have done it during
8585 installation.
</p
>
8587 <p
>A better approach is probably to extend tasksel to be able to
8588 install packages without using debconf-apt-progress, for use cases
8589 like this.
</p
>
8594 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8595 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8596 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8597 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8598 <description><p
>My
8599 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8600 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8601 finally made the upgrade logs available from
8602 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8603 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8604 apt and aptitude, and found their differences interesting. This time
8605 I will only focus on their removal plans.
</p
>
8607 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8608 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8609 surprising part is that it want to remove xorg and all
8610 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8611 sure why. When asking aptitude to do the same, it want to remove
129
8612 packages, but most of them are library packages I suspect are no
8613 longer needed. Both of them want to remove bluetooth packages, which
8614 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8616 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8617 which seem like a bad idea and xorg the same way as with Gnome. Asking
8618 aptitude for the same, it wants to remove
192 packages, none which are
8619 too surprising.
</p
>
8621 <p
>I guess the removal of xorg during upgrades should be investigated
8622 and avoided, and perhaps others as well. Here are the complete list
8623 of planned removals. The complete logs is available from the URL
8624 above. Note if you want to repeat these tests, that the upgrade test
8625 for kde+apt-get hung in the tasksel setup because of dpkg asking
8626 conffile questions. No idea why. I worked around it by using
8627 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8630 <p
><b
>apt-get gnome
72</b
>
8631 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8632 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8633 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8634 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8635 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8636 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8637 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8638 xserver-xorg-input-kbd xserver-xorg-input-mouse
8639 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8640 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8641 xserver-xorg-video-ati xserver-xorg-video-chips
8642 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8643 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8644 xserver-xorg-video-glint xserver-xorg-video-i128
8645 xserver-xorg-video-i740 xserver-xorg-video-imstt
8646 xserver-xorg-video-intel xserver-xorg-video-mach64
8647 xserver-xorg-video-mga xserver-xorg-video-neomagic
8648 xserver-xorg-video-nsc xserver-xorg-video-nv
8649 xserver-xorg-video-openchrome xserver-xorg-video-r128
8650 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8651 xserver-xorg-video-rendition xserver-xorg-video-s3
8652 xserver-xorg-video-s3virge xserver-xorg-video-savage
8653 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8654 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8655 xserver-xorg-video-tga xserver-xorg-video-trident
8656 xserver-xorg-video-tseng xserver-xorg-video-v4l
8657 xserver-xorg-video-vesa xserver-xorg-video-vga
8658 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8659 xulrunner-
1.9-gnome-support
</p
>
8661 <p
><b
>aptitude gnome
129</b
>
8663 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8664 djvulibre-desktop finger gnome-app-install gnome-mount
8665 gnome-network-admin gnome-spell gnome-vfs-obexftp
8666 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8667 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8668 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8669 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8670 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8671 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8672 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8673 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8674 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8675 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8676 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8677 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8678 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8679 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8680 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8681 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8682 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8683 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8684 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8685 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8686 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8687 openoffice.org-writer2latex openssl-blacklist p7zip
8688 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8689 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8690 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8691 swfdec-mozilla totem-gstreamer update-manager wodim
8692 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8693 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8696 <p
><b
>apt-get kde
82</b
>
8698 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8699 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8700 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8701 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8702 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8703 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8704 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8705 xserver-xorg-input-kbd xserver-xorg-input-mouse
8706 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8707 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8708 xserver-xorg-video-ati xserver-xorg-video-chips
8709 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8710 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8711 xserver-xorg-video-glint xserver-xorg-video-i128
8712 xserver-xorg-video-i740 xserver-xorg-video-imstt
8713 xserver-xorg-video-intel xserver-xorg-video-mach64
8714 xserver-xorg-video-mga xserver-xorg-video-neomagic
8715 xserver-xorg-video-nsc xserver-xorg-video-nv
8716 xserver-xorg-video-openchrome xserver-xorg-video-r128
8717 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8718 xserver-xorg-video-rendition xserver-xorg-video-s3
8719 xserver-xorg-video-s3virge xserver-xorg-video-savage
8720 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8721 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8722 xserver-xorg-video-tga xserver-xorg-video-trident
8723 xserver-xorg-video-tseng xserver-xorg-video-v4l
8724 xserver-xorg-video-vesa xserver-xorg-video-vga
8725 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8727 <p
><b
>aptitude kde
192</b
>
8728 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8729 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8730 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8731 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8732 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8733 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8734 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8735 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8736 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8737 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8738 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8739 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8740 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8741 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8742 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8743 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8744 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8745 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8746 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8747 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8748 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8749 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8750 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8751 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8752 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8753 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8754 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8755 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8756 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8757 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8758 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8759 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8760 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8761 texlive-common texlive-doc-base texlive-fonts-recommended
8762 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8763 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8764 xulrunner-
1.9</p
>
8770 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8771 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8773 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8774 <description><p
>The last few days I have done some upgrade testing in Debian, to
8775 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8776 have been discovered and reported in the process
8777 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8778 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8779 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8780 kdebase-workspace-data), and to get a more regular testing going on, I
8781 am working on a script to automate the test.
</p
>
8783 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8784 Gnome or KDE desktop installation inside the chroot before upgrading
8785 it. To ensure no services are started in the chroot, a policy-rc.d
8786 script is inserted. To make sure tasksel believe it is to install a
8787 desktop on a laptop, the tasksel tests are replaced in the chroot
8788 (only acceptable because this is a throw-away chroot).
</p
>
8790 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8791 currently always fail because udev refuses to upgrade with the kernel
8792 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8793 is created. The bug report
8794 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8795 this problem do not trigger in a chroot, but I touch the file anyway
8796 to make sure the upgrade go well. Testing on virtual and real
8797 hardware have failed me because of udev so far, and creating this file
8798 do the trick in such settings anyway. This is a
8799 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8800 issue
</a
> and the current udev behaviour is intended by the udev
8801 maintainer because he lack the resources to rewrite udev to keep
8802 working with old kernels or something like that. I really wish the
8803 udev upstream would keep udev backwards compatible, to avoid such
8804 upgrade problem, but given that they fail to do so, I guess
8805 documenting the way out of this mess is the best option we got for
8806 Debian Squeeze.
</p
>
8808 <p
>Anyway, back to the task at hand, testing upgrades. This test
8809 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8812 <blockquote
><pre
>
8816 if [
"$
1" ] ; then
8825 exec
&lt; /dev/null
8827 mirror=http://ftp.skolelinux.org/debian
8828 tmpdir=chroot-$from-upgrade-$to-$desktop
8830 debootstrap $from $tmpdir $mirror
8831 chroot $tmpdir aptitude update
8832 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8836 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8840 mount -t proc proc $tmpdir/proc
8841 # Make sure proc is unmounted also on failure
8842 trap exit_cleanup EXIT INT
8844 chroot $tmpdir aptitude -y install debconf-utils
8846 # Make sure tasksel autoselection trigger. It need the test scripts
8847 # to return the correct answers.
8848 echo tasksel tasksel/desktop multiselect $desktop | \
8849 chroot $tmpdir debconf-set-selections
8851 # Include the desktop and laptop task
8852 for test in desktop laptop ; do
8853 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8857 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8860 DEBIAN_FRONTEND=noninteractive
8861 DEBIAN_PRIORITY=critical
8862 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8863 chroot $tmpdir tasksel --new-install
8865 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8866 chroot $tmpdir aptitude update
8867 touch $tmpdir/etc/udev/kernel-upgrade
8868 chroot $tmpdir aptitude -y dist-upgrade
8870 </pre
></blockquote
>
8872 <p
>I suspect it would be useful to test upgrades with both apt-get and
8873 with aptitude, but I have not had time to look at how they behave
8874 differently so far. I hope to get a cron job running to do the test
8875 regularly and post the result on the web. The Gnome upgrade currently
8876 work, while the KDE upgrade fail because of the bug in
8877 kdebase-workspace-data
</p
>
8879 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8880 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8881 post, so I will refrain from trying. I can report that for Gnome,
8882 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8883 remove and
1 not upgraded and
1024MB need to be downloaded while for
8884 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8885 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8887 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8888 is able to migrate to dependency based boot sequencing and parallel
8889 booting without a hitch. Was unsure if there were still bugs with
8890 packages failing to clean up their obsolete init.d script during
8891 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8897 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8898 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8900 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8901 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8902 scripts to migrate (some of) their operations to upstart job while
8903 keeping the init.d for hurd and kfreebsd. The packages with such
8904 needs will need a way to get their init.d scripts to behave
8905 differently when used with sysvinit and with upstart. Because of
8906 this, I had a look at the environment variables set when a init.d
8907 script is running under upstart, and when it is not.
</p
>
8909 <p
>With upstart, I notice these environment variables are set when a
8910 script is started from rcS.d/ (ignoring some irrelevant ones like
8913 <blockquote
><pre
>
8919 UPSTART_EVENTS=startup
8921 UPSTART_JOB=rc-sysinit
8922 </pre
></blockquote
>
8924 <p
>With sysvinit, these environment variables are set for the same
8927 <blockquote
><pre
>
8928 INIT_VERSION=sysvinit-
2.88
8933 </pre
></blockquote
>
8935 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8936 sysvinit are not set by upstart. Not sure if it is intentional or not
8937 to not be compatible with sysvinit in this regard.
</p
>
8939 <p
>For scripts needing to behave differently when upstart is used,
8940 looking for the UPSTART_JOB environment variable seem to be a good
8946 <title>A manual for standards wars...
</title>
8947 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8949 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8950 <description><p
>Via the
8951 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8952 of Rob Weir
</a
> I came across the very interesting essay named
8953 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8954 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8955 following the standards wars of today.
</p
>
8960 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8961 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8962 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8963 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8964 <description><p
>When using sitesummary at a site to track machines, it is possible
8965 to get a list of the machine types in use thanks to the DMI
8966 information extracted from each machine. The script to do so is
8967 included in the sitesummary package, and here is example output from
8968 the Skolelinux build servers:
</p
>
8970 <blockquote
><pre
>
8971 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8973 Dell Computer Corporation
1
8976 eserver xSeries
345 -[
8670M1X]-
1
8980 </pre
></blockquote
>
8982 <p
>The quality of the report depend on the quality of the DMI tables
8983 provided in each machine. Here there are Intel machines without model
8984 information listed with Intel as vendor and no model, and virtual Xen
8985 machines listed as [no-dmi-info]. One can add -l as a command line
8986 option to list the individual machines.
</p
>
8988 <p
>A larger list is
8989 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8990 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8991 provide the basic sitesummary report publicly. In their report there
8992 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8993 their machines, and as sitesummary is available in both distributions,
8994 it is trivial to get all of them to report to the same central
8995 collector.
</p
>
9000 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9001 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9002 <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>
9003 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9004 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9005 start at boot when an NVidia video card is used is handled. The
9006 problem seem to be that the nvidia X.org driver uses a long time to
9007 initialize, and this duration is longer than kdm is configured to
9010 <p
>I came across two bugs related to this issue,
9011 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9012 against initscripts and passed on to nvidia-glx when it became obvious
9013 that the nvidia drivers were involved, and
9014 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9015 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9017 <p
>To me, it seem that no-one is interested in actually solving the
9018 problem nvidia video card owners experience and make sure the Debian
9019 distribution work out of the box for these users. The nvidia driver
9020 maintainers expect kdm to be set up to wait longer, while kdm expect
9021 the nvidia driver maintainers to fix the driver to start faster, and
9022 while they wait for each other I guess the users end up switching to a
9023 distribution that work for them. I have no idea what the solution is,
9024 but I am pretty sure that waiting for each other is not it.
</p
>
9026 <p
>I wonder why we end up handling bugs this way.
</p
>
9031 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9032 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9034 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9035 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9036 The feature seem to hold up pretty well, but three fairly serious
9037 issues are known and should be solved:
9041 <li
>The wicd package seen to
9042 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9043 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9044 parallel booting is enabled. No idea why, but the wicd maintainer
9045 seem to be on the case.
</li
>
9047 <li
>The nvidia X driver seem to
9048 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9049 triggered more easily when parallel booting is in effect. The
9050 maintainer is on the case.
</li
>
9052 <li
>The sysv-rc package fail to properly enable dependency based boot
9053 sequencing (the shutdown is broken) when old file-rc users
9054 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9055 sysv-rc. One way to solve it would be for file-rc to create
9056 /etc/init.d/.legacy-bootordering, and another is to try to make
9057 sysv-rc more robust. Will investigate some more and probably upload a
9058 workaround in sysv-rc to help those trying to move from file-rc to
9059 sysv-rc get a working shutdown.
</li
>
9061 </ul
></p
>
9063 <p
>All in all not many surprising issues, and all of them seem
9064 solvable before Squeeze is released. In addition to these there are
9065 some packages with bugs in their dependencies and run level settings,
9066 which I expect will be fixed in a reasonable time span.
</p
>
9068 <p
>If you report any problems with dependencies in init.d scripts to
9069 the BTS, please usertag the report to get it to show up at
9070 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9071 list of usertagged bugs related to this
</a
>.
</p
>
9073 <p
>Update: Correct bug number to file-rc issue.
</p
>
9078 <title>More flexible firmware handling in debian-installer
</title>
9079 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9080 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9081 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9082 <description><p
>After a long break from debian-installer development, I finally
9083 found time today to return to the project. Having to spend less time
9084 working dependency based boot in debian, as it is almost complete now,
9085 definitely helped freeing some time.
</p
>
9087 <p
>A while back, I ran into a problem while working on Debian Edu. We
9088 include some firmware packages on the Debian Edu CDs, those needed to
9089 get disk and network controllers working. Without having these
9090 firmware packages available during installation, it is impossible to
9091 install Debian Edu on the given machine, and because our target group
9092 are non-technical people, asking them to provide firmware packages on
9093 an external medium is a support pain. Initially, I expected it to be
9094 enough to include the firmware packages on the CD to get
9095 debian-installer to find and use them. This proved to be wrong.
9096 Next, I hoped it was enough to symlink the relevant firmware packages
9097 to some useful location on the CD (tried /cdrom/ and
9098 /cdrom/firmware/). This also proved to not work, and at this point I
9099 found time to look at the debian-installer code to figure out what was
9100 going to work.
</p
>
9102 <p
>The firmware loading code is in the hw-detect package, and a closer
9103 look revealed that it would only look for firmware packages outside
9104 the installation media, so the CD was never checked for firmware
9105 packages. It would only check USB sticks, floppies and other
9106 "external
" media devices. Today I changed it to also look in the
9107 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9108 solve the problem I ran into with Debian edu. I also changed it to
9109 look in /firmware/, to make sure the installer also find firmware
9110 provided in the initrd when booting the installer via PXE, to allow us
9111 to provide the same feature in the PXE setup included in Debian
9114 <p
>To make sure firmware deb packages with a license questions are not
9115 activated without asking if the license is accepted, I extended
9116 hw-detect to look for preinst scripts in the firmware packages, and
9117 run these before activating the firmware during installation. The
9118 license question is asked using debconf in the preinst, so this should
9119 solve the issue for the firmware packages I have looked at so far.
</p
>
9121 <p
>If you want to discuss the details of these features, please
9122 contact us on debian-boot@lists.debian.org.
</p
>
9127 <title>Parallellized boot is now the default in Debian/unstable
</title>
9128 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9130 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9131 <description><p
>Since this evening, parallel booting is the default in
9132 Debian/unstable for machines using dependency based boot sequencing.
9133 Apparently the testing of concurrent booting has been wider than
9134 expected, if I am to believe the
9135 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9136 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9137 with the feature this weekend, to give us some time to detect any
9138 remaining problems before Squeeze is frozen. If serious problems are
9139 detected, it is simple to change the default back to sequential boot.
9140 The upload of the new sysvinit package also activate a new upstream
9143 More information about
9144 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9145 based boot sequencing
</a
> is available from the Debian wiki. It is
9146 currently possible to disable parallel booting when one run into
9147 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9149 <blockquote
><pre
>
9151 </pre
></blockquote
>
9153 <p
>If you report any problems with dependencies in init.d scripts to
9154 the BTS, please usertag the report to get it to show up at
9155 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9156 list of usertagged bugs related to this
</a
>.
</p
>
9161 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9162 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9163 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9164 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9165 <description><p
>In the recent Debian Edu versions, the
9166 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9167 system
</a
> is used to keep track of the machines in the school
9168 network. Each machine will automatically report its status to the
9169 central server after boot and once per night. The network setup is
9170 also reported, and using this information it is possible to get the
9171 MAC address of all network interfaces in the machines. This is useful
9172 to update the DHCP configuration.
</p
>
9174 <p
>To give some idea how to use sitesummary, here is a one-liner to
9175 ist all MAC addresses of all machines reporting to sitesummary. Run
9176 this on the collector host:
</p
>
9178 <blockquote
><pre
>
9179 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9180 </pre
></blockquote
>
9182 <p
>This will list all MAC addresses assosiated with all machine, one
9183 line per machine and with space between the MAC addresses.
</p
>
9185 <p
>To allow system administrators easier job at adding static DHCP
9186 addresses for hosts, it would be possible to extend this to fetch
9187 machine information from sitesummary and update the DHCP and DNS
9188 tables in LDAP using this information. Such tool is unfortunately not
9189 written yet.
</p
>
9194 <title>systemd, an interesting alternative to upstart
</title>
9195 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9197 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9198 <description><p
>The last few days a new boot system called
9199 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9201 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9203 to the free software world. I have not yet had time to play around
9204 with it, but it seem to be a very interesting alternative to
9205 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9206 a good alternative for Debian when we are able to switch to an event
9207 based boot system. Tollef is
9208 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9209 systemd into Debian, and I look forward to seeing how well it work. I
9210 like the fact that systemd handles init.d scripts with dependency
9211 information natively, allowing them to run in parallel where upstart
9212 at the moment do not.
</p
>
9214 <p
>Unfortunately do systemd have the same problem as upstart regarding
9215 platform support. It only work on recent Linux kernels, and also need
9216 some new kernel features enabled to function properly. This means
9217 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9218 system. Not sure how that will be handled if systemd proves to be the
9219 way forward.
</p
>
9221 <p
>In the mean time, based on the
9222 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9223 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9224 decided to enable full parallel booting as the default in Debian as
9225 soon as possible (probably this weekend or early next week), to see if
9226 there are any remaining serious bugs in the init.d dependencies. A
9227 new version of the sysvinit package implementing this change is
9228 already in experimental. If all go well, Squeeze will be released
9229 with parallel booting enabled by default.
</p
>
9234 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9235 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9237 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9238 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9239 complete, so complete that it is actually possible to run all the
9240 init.d scripts in parallell based on these dependencies. If you want
9241 to test your Squeeze system, make sure
9242 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9243 based boot sequencing
</a
> is enabled, and add this line to
9244 /etc/default/rcS:
</p
>
9246 <blockquote
><pre
>
9247 CONCURRENCY=makefile
9248 </pre
></blockquote
>
9250 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9251 scripts in parallel using the dependency information stored in
9252 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9253 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9254 to try to start the kdm and gdm scripts as early as possible, and will
9255 start the facilities required by kdm or gdm as early as possible to
9256 make this happen.
</p
>
9258 <p
>Give it a try, and see if you like the result. If some services
9259 fail to start properly, it is most likely because they have incomplete
9260 init.d script dependencies in their startup script (or some of their
9261 dependent scripts have incomplete dependencies). Report bugs and get
9262 the package maintainers to fix it. :)
</p
>
9264 <p
>Running scripts in parallel could be the default in Debian when we
9265 manage to get the init.d script dependencies complete and correct. I
9266 expect we will get there in Squeeze+
1, if we get manage to test and
9267 fix the remaining issues.
</p
>
9269 <p
>If you report any problems with dependencies in init.d scripts to
9270 the BTS, please usertag the report to get it to show up at
9271 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9272 list of usertagged bugs related to this
</a
>.
</p
>
9277 <title>Debian has switched to dependency based boot sequencing
</title>
9278 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9280 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9281 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9282 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9283 have been migrated to using dependency based boot sequencing. This
9284 conclude work me and others have been doing for the last three days.
9285 It feels great to see this finally part of the default Debian
9286 installation. Now we just need to weed out the last few problems that
9287 are bound to show up, to get everything ready for Squeeze.
</p
>
9289 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9290 fixing the more fundamental problem of handing the event based
9291 non-predictable kernel in the early boot.
</p
>
9296 <title>Taking over sysvinit development
</title>
9297 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9298 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9299 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9300 <description><p
>After several years of frustration with the lack of activity from
9301 the existing sysvinit upstream developer, I decided a few weeks ago to
9302 take over the package and become the new upstream. The number of
9303 patches to track for the Debian package was becoming a burden, and the
9304 lack of synchronization between the distribution made it hard to keep
9305 the package up to date.
</p
>
9307 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9308 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9309 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9310 and Fedora), based on the patches currently in use in these
9311 distributions. We Debian maintainers plan to move to this tarball as
9312 the new upstream as soon as we find time to do the merge. Since the
9313 new tarball was created, we agreed with Werner at SuSe to make a new
9314 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9315 development there. The project is registered and currently waiting
9316 for approval by the Savannah administrators, and as soon as it is
9317 approved, we will import the old versions from svn and continue
9318 working on the future release.
</p
>
9320 <p
>It is a bit ironic that this is done now, when some of the involved
9321 distributions are moving to upstart as a syvinit replacement.
</p
>
9326 <title>Debian boots quicker and quicker
</title>
9327 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9329 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9330 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9331 people involved in the boot system on Debian and Ubuntu, to see if we
9332 could find more ways to speed up the boot system. This was an Ubuntu
9334 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9335 gathering
</a
>. It was quite productive. We also discussed the future
9336 of boot systems, and ways to handle the increasing number of boot
9337 issues introduced by the Linux kernel becoming more and more
9338 asynchronous and event base. The Ubuntu approach using udev and
9339 upstart might be a good way forward. Time will show.
</p
>
9341 <p
>Anyway, there are a few ways at the moment to speed up the boot
9342 process in Debian. All of these should be applied to get a quick
9347 <li
>Use dash as /bin/sh.
</li
>
9349 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9350 clock is in UTC.
</li
>
9352 <li
>Install and activate the insserv package to enable
9353 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9354 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9358 These points are based on the Google summer of code work done by
9359 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9362 <p
>Support for makefile-style concurrency during boot was uploaded to
9363 unstable yesterday. When we tested it, we were able to cut
6 seconds
9364 from the boot sequence. It depend on very correct dependency
9365 declaration in all init.d scripts, so I expect us to find edge cases
9366 where the dependences in some scripts are slightly wrong when we start
9367 using this.
</p
>
9369 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9370 introduced by Raphael Geissert today, one that could affect the
9371 startup speed as well. Instead of starting some scripts concurrently
9372 from rcS.d/ and another set of scripts from rc2.d/, it would be
9373 possible to run a of them in the same process. A quick way to test
9374 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9375 insserv
'. Will need to test if that work. :)
</p
>
9380 <title>BSAs påstander om piratkopiering møter motstand
</title>
9381 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9383 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9384 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9385 programvareselskapene som Microsoft og Apple, publisert en rapport der
9386 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9387 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9389 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9390 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9391 dagene. Et spesielt interessant kommentar fra Sverige,
9392 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9393 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9396 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9397 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9398 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9399 exakta
", säger BSAs Sverigechef John Hugosson.
9402 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9403 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9404 piracy figures need a shot of reality
</a
> og
<a
9405 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9406 Copyright Treaty Work?
</a
></p
>
9408 <p
>Fant lenkene via
<a
9409 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9410 på Slashdot
</a
>.
</p
>
9415 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9416 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9418 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9419 <description><p
>Kom over
9420 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9421 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9422 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9423 jobber til daglig. En rask opptelling forteller meg at vi har
490
9424 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9425 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9426 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9431 <title>Kryptert harddisk - naturligvis
</title>
9432 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9434 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9435 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9436 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9437 når en tar tap av arbeidstid, fortrolige dokumenter,
9438 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9439 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9440 til at jeg har kryptert harddisken på både kontormaskinen og min
9441 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9442 komme på avveie, den første informasjon relatert til jobben min ved
9443 Universitetet i Oslo, og den andre relatert til blant annet
9444 foreningsarbeide. Kryptering av diskene gjør at det er lite
9445 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9446 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9447 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9448 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9449 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9450 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9451 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9452 det er gjort slik jeg gjør det er minimale, og gevinstene er
9453 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9454 maskinen reinstalleres og alt er tapt.
</p
>
9456 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9457 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9458 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9459 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9460 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9461 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9462 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9463 betydelige.
</p
>
9468 <title>Two projects that have improved the quality of free software a lot
</title>
9469 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9471 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9472 <description><p
>There are two software projects that have had huge influence on the
9473 quality of free software, and I wanted to mention both in case someone
9474 do not yet know them.
</p
>
9476 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9477 tool to detect and expose errors in the memory handling of programs.
9478 It is easy to use, all one need to do is to run
'valgrind program
',
9479 and it will report any problems on stdout. It is even better if the
9480 program include debug information. With debug information, it is able
9481 to report the source file name and line number where the problem
9482 occurs. It can report things like
'reading past memory block in file
9483 X line N, the memory block was allocated in file Y, line M
', and
9484 'using uninitialised value in control logic
'. This tool has made it
9485 trivial to investigate reproducible crash bugs in programs, and have
9486 reduced the number of this kind of bugs in free software a lot.
9488 <p
>The second one is
9489 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9490 a source code checker. It is able to process the source of a program
9491 and find problems in the logic without running the program. It
9492 started out as the Stanford Checker and became well known when it was
9493 used to find bugs in the Linux kernel. It is now a commercial tool
9494 and the company behind it is running
9495 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9496 free software community, where a lot of free software projects get
9497 their source checked for free. Several thousand defects have been
9498 found and fixed so far. It can find errors like
'lock L taken in file
9499 X line N is never released if exiting in line M
', or
'the code in file
9500 Y lines O to P can never be executed
'. The projects included in the
9501 community service project have managed to get rid of a lot of
9502 reliability problems thanks to Coverity.
</p
>
9504 <p
>I believe tools like this, that are able to automatically find
9505 errors in the source, are vital to improve the quality of software and
9506 make sure we can get rid of the crashing and failing software we are
9507 surrounded by today.
</p
>
9512 <title>No patch is not better than a useless patch
</title>
9513 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9514 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9515 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9516 <description><p
>Julien Blache
9517 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9518 patch is better than a useless patch
</a
>. I completely disagree, as a
9519 patch allow one to discuss a concrete and proposed solution, and also
9520 prove that the issue at hand is important enough for someone to spent
9521 time on fixing it. No patch do not provide any of these positive
9522 properties.
</p
>
9527 <title>Standardize on protocols and formats, not vendors and applications
</title>
9528 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9529 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9530 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9531 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9532 very good one to form a long lived computer infrastructure. It is the
9533 simple one, lost by many in todays computer industry: Standardize on
9534 open network protocols and open exchange/storage formats, not applications.
9535 Applications come and go, while protocols and files tend to stay, and
9536 thus one want to make it easy to change application and vendor, while
9537 avoiding conversion costs and locking users to a specific platform or
9538 application.
</p
>
9540 <p
>This approach make it possible to replace the client applications
9541 independently of the server applications. One can even allow users to
9542 use several different applications as long as they handle the selected
9543 protocol and format. In the normal case, only one client application
9544 is recommended and users only get help if they choose to use this
9545 application, but those that want to deviate from the easy path are not
9546 blocked from doing so.
</p
>
9548 <p
>It also allow us to replace the server side without forcing the
9549 users to replace their applications, and thus allow us to select the
9550 best server implementation at any moment, when scale and resouce
9551 requirements change.
</p
>
9553 <p
>I strongly recommend standardizing - on open network protocols and
9554 open formats, but I would never recommend standardizing on a single
9555 application that do not use open network protocol or open formats.
</p
>
9560 <title>Returning from Skolelinux developer gathering
</title>
9561 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9562 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9563 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9564 <description><p
>I
'm sitting on the train going home from this weekends Debian
9565 Edu/Skolelinux development gathering. I got a bit done tuning the
9566 desktop, and looked into the dynamic service location protocol
9567 implementation avahi. It look like it could be useful for us. Almost
9568 30 people participated, and I believe it was a great environment to
9569 get to know the Skolelinux system. Walter Bender, involved in the
9570 development of the Sugar educational platform, presented his stuff and
9571 also helped me improve my OLPC installation. He also showed me that
9572 his Turtle Art application can be used in standalone mode, and we
9573 agreed that I would help getting it packaged for Debian. As a
9574 standalone application it would be great for Debian Edu. We also
9575 tried to get the video conferencing working with two OLPCs, but that
9576 proved to be too hard for us. The application seem to need more work
9577 before it is ready for me. I look forward to getting home and relax
9583 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9584 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9585 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9586 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9587 <description><p
>The state of standardized LDAP schemas on Linux is far from
9588 optimal. There is RFC
2307 documenting one way to store NIS maps in
9589 LDAP, and a modified version of this normally called RFC
2307bis, with
9590 some modifications to be compatible with Active Directory. The RFC
9591 specification handle the content of a lot of system databases, but do
9592 not handle DNS zones and DHCP configuration.
</p
>
9594 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9595 we would like to store information about users, SMB clients/hosts,
9596 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9597 and LTSP configuration in LDAP. These objects have a lot in common,
9598 but with the current LDAP schemas it is not possible to have one
9599 object per entity. For example, one need to have at least three LDAP
9600 objects for a given computer, one with the SMB related stuff, one with
9601 DNS information and another with DHCP information. The schemas
9602 provided for DNS and DHCP are impossible to combine into one LDAP
9603 object. In addition, it is impossible to implement quick queries for
9604 netgroup membership, because of the way NIS triples are implemented.
9605 It just do not scale. I believe it is time for a few RFC
9606 specifications to cleam up this mess.
</p
>
9608 <p
>I would like to have one LDAP object representing each computer in
9609 the network, and this object can then keep the SMB (ie host key), DHCP
9610 (mac address/name) and DNS (name/IP address) settings in one place.
9611 It need to be efficently stored to make sure it scale well.
</p
>
9613 <p
>I would also like to have a quick way to map from a user or
9614 computer and to the net group this user or computer is a member.
</p
>
9616 <p
>Active Directory have done a better job than unix heads like myself
9617 in this regard, and the unix side need to catch up. Time to start a
9618 new IETF work group?
</p
>
9623 <title>Endelig er Debian Lenny gitt ut
</title>
9624 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9625 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9626 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9627 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9628 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9629 Et langt steg videre for Debian-prosjektet, og en rekke nye
9630 programpakker blir nå tilgjengelig for de av oss som bruker den
9631 stabile utgaven av Debian. Neste steg er nå å få
9632 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9633 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9634 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9635 slippes løs på skolene. Takk til alle debian-utviklerne som har
9636 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9637 bootsekvens tilgjengelig i stabil utgave, vha pakken
9638 <tt
>insserv
</tt
>.
</p
>
9643 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9644 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9645 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9646 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9647 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9648 Oslo. Most of Saturday was used for the general assemly for the
9649 member organization, but the rest of the weekend I used to tune the
9650 LTSP installation. LTSP now work out of the box on the
10-network.
9651 Acer Aspire One proved to be a very nice thin client, with both
9652 screen, mouse and keybard in a small box. Was working on getting the
9653 diskless workstation setup configured out of the box, but did not
9654 finish it before the weekend was up.
</p
>
9656 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9657 the Brazilian group, so that will have to wait for the next
9658 development gathering. Would love to have the Debian Edu installer
9659 automatically detect and configure a multiseat setup when it find one
9660 of these cards.
</p
>
9665 <title>The sorry state of multimedia browser plugins in Debian
</title>
9666 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9667 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9668 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9669 <description><p
>Recently I have spent some time evaluating the multimedia browser
9670 plugins available in Debian Lenny, to see which one we should use by
9671 default in Debian Edu. We need an embedded video playing plugin with
9672 control buttons to pause or stop the video, and capable of streaming
9673 all the multimedia content available on the web. The test results and
9674 notes are available on
9675 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9676 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9677 fill this need. My personal video player favorite, VLC, has a really
9678 bad plugin which fail on a lot of the test pages. A lot of the MIME
9679 types I would expect to work with any free software player (like
9680 video/ogg), just do not work. And simple formats like the
9681 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9682 totem and vlc plugins. I hope the situation will improve soon. No
9683 wonder sites use the proprietary Adobe flash to play video.
</p
>
9685 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9686 be the only one fitting our needs. :/
</p
>