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>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
11 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
12 <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>
13 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
14 <description><p
>In April we
15 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
16 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
17 how to set up and administrate a Debian system. Today I am happy to
18 report that the first draft is now publicly available. You can find
19 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
20 Administrator
's Handbook page
</a
> (under Other languages). The first
21 eight chapters have a first draft translation, and we are working on
22 proofreading the content. If you want to help out, please start
24 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
25 hosted weblate project page
</a
>, and get in touch using
26 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
27 translators mailing list
</a
>. Please also check out
28 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
29 contributors
</a
>. A good way to contribute is to proofread the text
30 and update weblate if you find errors.
</p
>
32 <p
>Our goal is still to make the Norwegian book available on paper as well as
33 electronic form.
</p
>
38 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
39 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
40 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
41 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
42 <description><p
>This summer, I read a great article
43 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
44 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
45 how to profile multi-threaded programs. It presented a system for
46 profiling software by running experiences in the running program,
47 testing how run time performance is affected by
"speeding up
" parts of
48 the code to various degrees compared to a normal run. It does this by
49 slowing down parallel threads while the
"faster up
" code is running
50 and measure how this affect processing time. The processing time is
51 measured using probes inserted into the code, either using progress
52 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
53 can also measure unmodified code by measuring complete the program
54 runtime and running the program several times instead.
</p
>
56 <p
>The project and presentation was so inspiring that I would like to
57 get the system into Debian. I
58 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
59 a WNPP request for it
</a
> and contacted upstream to try to make the
60 system ready for Debian by sending patches. The build process need to
61 be changed a bit to avoid running
'git clone
' to get dependencies, and
62 to include the JavaScript web page used to visualize the collected
63 profiling information included in the source package.
64 But I expect that should work out fairly soon.
</p
>
66 <p
>The way the system work is fairly simple. To run an coz experiment
67 on a binary with debug symbols available, start the program like this:
69 <p
><blockquote
><pre
>
70 coz run --- program-to-run
71 </pre
></blockquote
></p
>
73 <p
>This will create a text file profile.coz with the instrumentation
74 information. To show what part of the code affect the performance
75 most, use a web browser and either point it to
76 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
77 or use the copy from git (in the gh-pages branch). Check out this web
78 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
79 profiling more useful you include
&lt;coz.h
&gt; and insert the
80 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
81 code, rebuild and run the profiler. This allow coz to do more
82 targeted experiments.
</p
>
84 <p
>A video published by ACM
85 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
86 Coz profiler
</a
> is available from Youtube. There is also a paper
87 from the
25th Symposium on Operating Systems Principles available
89 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
90 finding code that counts with causal profiling
</a
>.
</p
>
92 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
93 for Coz is available from github. It will only build with clang
95 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
96 feature missing in GCC
</a
>, but I
've submitted
97 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
98 it
</a
> and hope it will be included in the upstream source soon.
</p
>
100 <p
>Please get in touch if you, like me, would like to see this piece
101 of software in Debian. I would very much like some help with the
102 packaging effort, as I lack the in depth knowledge on how to package
103 C++ libraries.
</p
>
108 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
109 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
111 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
112 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
113 to be a slight challenge. Here is the recipe if I ever need to do it
114 again. It all started by me wanting to try the recipe to set up
115 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
116 hardened Android installation
</a
> from the Tor project blog on a
117 device I had access to. It is a old mobile phone with a broken
118 microphone The initial idea had been to just
119 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
120 CyanogenMod on it
</a
>, but did not quite find time to start on it
121 until a few days ago.
</p
>
123 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
124 loader (press volume down and power at the same time), (
2) select
125 'fastboot
' before (
3) connecting the device via USB to a Linux
126 machine, (
4) request the device identifier token by running
'fastboot
127 oem get_identifier_token
', (
5) request the device unlocking key using
128 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
129 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
131 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
132 or newer, and the device I was working on had
2.00.0027. This
133 apparently can be easily fixed by downloading a Windows program and
134 running it on your Windows machine, if you accept the terms Microsoft
135 require you to accept to use Windows - which I do not. So I had to
136 come up with a different approach. I got a lot of help from AndyCap
137 on #nuug, and would not have been able to get this working without
140 <p
>First I needed to extract the hboot firmware from
141 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
142 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
143 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
144 project named unruu
</a
> using libunshield. The unshield tool did not
145 recognise the file format, but unruu worked and extracted rom.zip,
146 containing the new hboot firmware and a text file describing which
147 devices it would work for.
</p
>
149 <p
>Next, I needed to get the new firmware into the device. For this I
150 followed some instructions
151 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
152 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
153 machine with Debian testing:
</p
>
156 adb reboot-bootloader
157 fastboot oem rebootRUU
158 fastboot flash zip rom.zip
159 fastboot flash zip rom.zip
161 </pre
></p
>
163 <p
>The flash command apparently need to be done twice to take effect,
164 as the first is just preparations and the second one do the flashing.
165 The adb command is just to get to the boot loader menu, so turning the
166 device on while holding volume down and the power button should work
169 <p
>With the new hboot version in place I could start following the
170 instructions on the HTC developer web site. I got the device token
174 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
177 <p
>And once I got the unlock code via email, I could use it like
181 fastboot flash unlocktoken Unlock_code.bin
182 </pre
></p
>
184 <p
>And with that final step in place, the phone was unlocked and I
185 could start stuffing the software of my own choosing into the device.
186 So far I only inserted a replacement recovery image to wipe the phone
187 before I start. We will see what happen next. Perhaps I should
188 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
193 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
194 <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>
195 <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>
196 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
197 <description><p
>For a while now, I have wanted to test
198 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
199 said to provide end to end encrypted communication and several of my
200 friends and family are already using it. As I by choice do not own a
201 mobile phone, this proved to be harder than expected. And I wanted to
202 have the source of the client and know that it was the code used on my
203 machine. But yesterday I managed to get it working. I used the
204 Github source, compared it to the source in
205 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
206 Signal Chrome app
</a
> available from the Chrome web store, applied
207 patches to use the production Signal servers, started the app and
208 asked for the hidden
"register without a smart phone
" form. Here is
209 the recipe how I did it.
</p
>
211 <p
>First, I fetched the Signal desktop source from Github, using
214 git clone https://github.com/WhisperSystems/Signal-Desktop.git
217 <p
>Next, I patched the source to use the production servers, to be
218 able to talk to other Signal users:
</p
>
221 cat
&lt;
&lt;EOF | patch -p0
222 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
223 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
224 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
229 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
230 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
231 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
232 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
234 window.getSocketStatus = function() {
235 if (messageReceiver) {
236 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
237 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
238 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
241 'use strict
';
242 - var BUILD_EXPIRATION =
0;
243 + var BUILD_EXPIRATION =
1474492690000;
245 window.extension = window.extension || {};
250 <p
>The first part is changing the servers, and the second is updating
251 an expiration timestamp. This timestamp need to be updated regularly.
252 It is set
90 days in the future by the build process (Gruntfile.js).
253 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
255 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
256 script to launch Signal in Chromium.
</p
>
263 --proxy-server=
"socks://localhost:
9050" \
264 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
267 <p
> The script start the app and configure Chromium to use the Tor
268 SOCKS5 proxy to make sure those controlling the Signal servers (today
269 Amazon and Whisper Systems) as well as those listening on the lines
270 will have a harder time location my laptop based on the Signal
271 connections if they use source IP address.
</p
>
273 <p
>When the script starts, one need to follow the instructions under
274 "Standalone Registration
" in the CONTRIBUTING.md file in the git
275 repository. I right clicked on the Signal window to get up the
276 Chromium debugging tool, visited the
'Console
' tab and wrote
277 'extension.install(
"standalone
")
' on the console prompt to get the
278 registration form. Then I entered by land line phone number and
279 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
280 repeated the verification code three times. After entering the number
281 into the verification code field in the form, I could start using
282 Signal from my laptop.
284 <p
>As far as I can tell, The Signal app will leak who is talking to
285 whom and thus who know who to those controlling the central server,
286 but such leakage is hard to avoid with a centrally controlled server
287 setup. It is something to keep in mind when using Signal - the
288 content of your chats are harder to intercept, but the meta data
289 exposing your contact network is available to people you do not know.
290 So better than many options, but not great. And sadly the usage is
291 connected to my land line, thus allowing those controlling the server
292 to associate it to my home and person. I would prefer it if only
293 those I knew could tell who I was on Signal. There are options
294 avoiding such information leakage, but most of my friends are not
295 using them, so I am stuck with Signal for now.
</p
>
300 <title>The new
"best
" multimedia player in Debian?
</title>
301 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
303 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
304 <description><p
>When I set out a few weeks ago to figure out
305 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
306 multimedia player in Debian claimed to support most file formats /
307 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
308 the various players claimed support for. The range was from
55 to
130
309 MIME types. I suspect most media formats are supported by all
310 players, but this is not really reflected in the MimeTypes values in
311 their desktop files. There are probably also some bogus MIME types
312 listed, but it is hard to identify which one this is.
</p
>
314 <p
>Anyway, in the mean time I got in touch with upstream for some of
315 the players suggesting to add more MIME types to their desktop files,
316 and decided to spend some time myself improving the situation for my
317 favorite media player VLC. The fixes for VLC entered Debian unstable
318 yesterday. The complete list of MIME types can be seen on the
319 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
320 player MIME type support status
</a
> Debian wiki page.
</p
>
322 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
323 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
324 kmplayer. I am sure some of the other players desktop files support
325 several of the formats currently listed as working only with vlc,
326 toten and parole.
</p
>
328 <p
>A sad observation is that only
14 MIME types are listed as
329 supported by all the tested multimedia players in Debian in their
330 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
331 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
332 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
333 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
334 it sad that video/ogg and video/webm is not supported by all the media
335 players in Debian. As far as I can tell, all of them can handle both
341 <title>A program should be able to open its own files on Linux
</title>
342 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
344 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
345 <description><p
>Many years ago, when koffice was fresh and with few users, I
346 decided to test its presentation tool when making the slides for a
347 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
348 wrote the first draft of the slides, saved the result and went to bed
349 the day before I would give the talk. The next day I took a plane to
350 the location where the meeting should take place, and on the plane I
351 started up koffice again to polish the talk a bit, only to discover
352 that kpresenter refused to load its own data file. I cursed a bit and
353 started making the slides again from memory, to have something to
354 present when I arrived. I tested that the saved files could be
355 loaded, and the day seemed to be rescued. I continued to polish the
356 slides until I suddenly discovered that the saved file could no longer
357 be loaded into kpresenter. In the end I had to rewrite the slides
358 three times, condensing the content until the talk became shorter and
359 shorter. After the talk I was able to pinpoint the problem
&ndash;
360 kpresenter wrote inline images in a way itself could not understand.
361 Eventually that bug was fixed and kpresenter ended up being a great
362 program to make slides. The point I
'm trying to make is that we
363 expect a program to be able to load its own data files, and it is
364 embarrassing to its developers if it can
't.
</p
>
366 <p
>Did you ever experience a program failing to load its own data
367 files from the desktop file browser? It is not a uncommon problem. A
368 while back I discovered that the screencast recorder
369 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
370 browser would refuse to open. No video player claimed to understand
371 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
372 returning the application/ogg MIME type, which no video player I had
373 installed listed as a MIME type they would understand. I asked for
374 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
375 behavour
</a
> and use the MIME type video/ogg instead. I also asked
376 several video players to add video/ogg to their desktop files, to give
377 the file browser an idea what to do about Ogg Theora files. After a
378 while, the desktop file browsers in Debian started to handle the
379 output from gtk-recordmydesktop properly.
</p
>
381 <p
>But history repeats itself. A few days ago I tested the music
382 system Rosegarden again, and I discovered that the KDE and xfce file
383 browsers did not know what to do with the Rosegarden project files
384 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
385 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
386 included in the next upload. To increase the chance of me remembering
387 how to fix the problem next time some program fail to load its files
388 from the file browser, here are some notes on how to fix it.
</p
>
390 <p
>The file browsers in Debian in general operates on MIME types.
391 There are two sources for the MIME type of a given file. The output from
392 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
393 shared MIME type registry (under /usr/share/mime/). The file MIME
394 type is mapped to programs supporting the MIME type, and this
395 information is collected from
396 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
397 desktop files
</a
> available in /usr/share/applications/. If there is
398 one desktop file claiming support for the MIME type of the file, it is
399 activated when asking to open a given file. If there are more, one
400 can normally select which one to use by right-clicking on the file and
401 selecting the wanted one using
'Open with
' or similar. In general
402 this work well. But it depend on each program picking a good MIME
404 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
405 MIME type registered with IANA
</a
>), file and/or the shared MIME
406 registry recognizing the file and the desktop file to list the MIME
407 type in its list of supported MIME types.
</p
>
409 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
410 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
411 Shared MIME database
</a
> look like this:
</p
>
413 <p
><blockquote
><pre
>
414 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
415 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
416 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
417 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
418 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
419 &lt;glob pattern=
"*.rg
"/
&gt;
420 &lt;/mime-type
&gt;
421 &lt;/mime-info
&gt;
422 </pre
></blockquote
></p
>
424 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
425 (it is a gzipped XML file). Note, it is much better to use an
426 official MIME type registered with IANA than it is to make up ones own
427 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
429 <p
>The desktop file of the rosegarden program failed to list
430 audio/x-rosegarden in its list of supported MIME types, causing the
431 file browsers to have no idea what to do with *.rg files:
</p
>
433 <p
><blockquote
><pre
>
434 % grep Mime /usr/share/applications/rosegarden.desktop
435 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
436 X-KDE-NativeMimeType=audio/x-rosegarden-composition
438 </pre
></blockquote
></p
>
440 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
441 MimeType= line.
</p
>
443 <p
>If you run into a file which fail to open the correct program when
444 selected from the file browser, please check out the output from
445 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
446 MIME type is registered somewhere under /usr/share/mime/ and check
447 that some desktop file under /usr/share/applications/ is claiming
448 support for this MIME type. If not, please report a bug to have it
454 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
455 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
457 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
458 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
459 system
</a
> is a user-focused solution in Debian for handling hardware
460 related packages. The idea is to have a database of mappings between
461 hardware and packages, and pop up a dialog suggesting for the user to
462 install the packages to use a given hardware dongle. Some use cases
463 are when you insert a Yubikey, it proposes to install the software
464 needed to control it; when you insert a braille reader list it
465 proposes to install the packages needed to send text to the reader;
466 and when you insert a ColorHug screen calibrator it suggests to
467 install the driver for it. The system work well, and even have a few
468 command line tools to install firmware packages and packages for the
469 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
471 <p
>The system was initially written using aptdaemon, because I found
472 good documentation and example code on how to use it. But aptdaemon
473 is going away and is generally being replaced by
474 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
475 so Isenkram needed a rewrite. And today, thanks to the great patch
476 from my college Sunil Mohan Adapa in the FreedomBox project, the
477 rewrite finally took place. I
've just uploaded a new version of
478 Isenkram into Debian Unstable with the patch included, and the default
479 for the background daemon is now to use PackageKit. To check it out,
480 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
481 and see if it is recognised.
</p
>
483 <p
>If you want to know what kind of packages isenkram would propose for
484 the machine it is running on, you can check out the isenkram-lookup
485 program. This is what it look like on a Thinkpad X230:
</p
>
487 <p
><blockquote
><pre
>
503 </pre
></blockquote
></p
>
505 <p
>The hardware mappings come from several places. The preferred way
506 is for packages to announce their hardware support using
507 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
508 cross distribution appstream system
</a
>.
510 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
511 blog posts about isenkram
</a
> to learn how to do that.
</p
>
516 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
517 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
519 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
520 <description><p
>Yesterday I updated the
521 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
522 package in Debian
</a
> with a few patches sent to me by skilled and
523 enterprising users. There were some nice user and visible changes.
524 First of all, both desktop menu entries now work. A design flaw in
525 one of the script made the history graph fail to show up (its PNG was
526 dumped in ~/.xsession-errors) if no controlling TTY was available.
527 The script worked when called from the command line, but not when
528 called from the desktop menu. I changed this to look for a DISPLAY
529 variable or a TTY before deciding where to draw the graph, and now the
530 graph window pop up as expected.
</p
>
532 <p
>The next new feature is a discharge rate estimator in one of the
533 graphs (the one showing the last few hours). New is also the user of
534 colours showing charging in blue and discharge in red. The percentages
535 of this graph is relative to last full charge, not battery design
538 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
540 <p
>The other graph show the entire history of the collected battery
541 statistics, comparing it to the design capacity of the battery to
542 visualise how the battery life time get shorter over time. The red
543 line in this graph is what the previous graph considers
100 percent:
545 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
547 <p
>In this graph you can see that I only charge the battery to
80
548 percent of last full capacity, and how the capacity of the battery is
549 shrinking. :(
</p
>
551 <p
>The last new feature is in the collector, which now will handle
552 more hardware models. On some hardware, Linux power supply
553 information is stored in /sys/class/power_supply/ACAD/, while the
554 collector previously only looked in /sys/class/power_supply/AC/. Now
555 both are checked to figure if there is power connected to the
558 <p
>If you are interested in how your laptop battery is doing, please
560 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
561 in Debian unstable, or rebuild it on Jessie to get it working on
562 Debian stable. :) The upstream source is available from
<a
563 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
564 Patches are very welcome.
</p
>
566 <p
>As usual, if you use Bitcoin and want to show your support of my
567 activities, please send Bitcoin donations to my address
568 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
573 <title>Debian now with ZFS on Linux included
</title>
574 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
576 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
577 <description><p
>Today, after many years of hard work from many people,
578 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
579 Debian. The package status can be seen on
580 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
581 for zfs-linux
</a
>. and
582 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
583 team status page
</a
>. If you want to help out, please join us.
584 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
585 source code
</a
> is available via git on Alioth. It would also be
586 great if you could help out with
587 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
588 it is an important piece of the puzzle to get ZFS working.
</p
>
593 <title>What is the best multimedia player in Debian?
</title>
594 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
596 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
597 <description><p
><strong
>Where I set out to figure out which multimedia player in
598 Debian claim support for most file formats.
</strong
></p
>
600 <p
>A few years ago, I had a look at the media support for Browser
601 plugins in Debian, to get an idea which plugins to include in Debian
602 Edu. I created a script to extract the set of supported MIME types
603 for each plugin, and used this to find out which multimedia browser
604 plugin supported most file formats / media types.
605 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
606 result
</a
> can still be seen on the Debian wiki, even though it have
607 not been updated for a while. But browser plugins are less relevant
608 these days, so I thought it was time to look at standalone
611 <p
>A few days ago I was tired of VLC not being listed as a viable
612 player when I wanted to play videos from the Norwegian National
613 Broadcasting Company, and decided to investigate why. The cause is a
614 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
615 desktop file
</a
>. In the process I wrote a script to compare the set
616 of MIME types announced in the desktop file and the browser plugin,
617 only to discover that there is quite a large difference between the
618 two for VLC. This discovery made me dig up the script I used to
619 compare browser plugins, and adjust it to compare desktop files
620 instead, to try to figure out which multimedia player in Debian
621 support most file formats.
</p
>
623 <p
>The result can be seen on the Debian Wiki, as
624 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
625 table listing all MIME types supported by one of the packages included
626 in the table
</a
>, with the package supporting most MIME types being
627 listed first in the table.
</p
>
629 </p
>The best multimedia player in Debian? It is totem, followed by
630 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
631 kmplayer. Time for the other players to update their announced MIME
637 <title>The Pyra - handheld computer with Debian preinstalled
</title>
638 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
639 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
640 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
641 <description>A friend of mine made me aware of
642 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
643 handheld computer which will be delivered with Debian preinstalled. I
644 would love to get one of those for my birthday. :)
</p
>
646 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
647 plugs and many others connectors, and include a full keyboard and a
5"
648 LCD touch screen. The
6000mAh battery is claimed to provide a whole
649 day of battery life time, but I have not seen any independent tests
650 confirming this. The vendor is still collecting preorders, and the
651 last I heard last night was that
22 more orders were needed before
652 production started.
</p
>
654 <p
>As far as I know, this is the first handheld preinstalled with
655 Debian. Please let me know if you know of any others. Is it the
656 first computer being sold with Debian preinstalled?
</p
>
661 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
662 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
663 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
664 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
665 <description><p
>During this weekends
666 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
667 squashing party and developer gathering
</a
>, we decided to do our part
668 to make sure there are good books about Debian available in Norwegian
669 Bokmål, and got in touch with the people behind the
670 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
671 project
</a
> to get started. If you want to help out, please start
673 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
674 hosted weblate project page
</a
>, and get in touch using
675 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
676 translators mailing list
</a
>. Please also check out
677 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
678 contributors
</a
>.
</p
>
680 <p
>The book is already available on paper in English, French and
681 Japanese, and our goal is to get it available on paper in Norwegian
682 Bokmål too. In addition to the paper edition, there are also EPUB and
683 Mobi versions available. And there are incomplete translations
684 available for many more languages.
</p
>
689 <title>One in two hundred Debian users using ZFS on Linux?
</title>
690 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
691 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
692 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
693 <description><p
>Just for fun I had a look at the popcon number of ZFS related
694 packages in Debian, and was quite surprised with what I found. I use
695 ZFS myself at home, but did not really expect many others to do so.
696 But I might be wrong.
</p
>
698 <p
>According to
699 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
700 results for spl-linux
</a
>, there are
1019 Debian installations, or
701 0.53% of the population, with the package installed. As far as I know
702 the only use of the spl-linux package is as a support library for ZFS
703 on Linux, so I use it here as proxy for measuring the number of ZFS
704 installation on Linux in Debian. In the kFreeBSD variant of Debian
705 the ZFS feature is already available, and there
706 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
707 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
708 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
710 <p
>But even though the Debian project leader Lucas Nussbaum
711 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
712 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
713 cleared, the package is still not in Debian. The package is again in
714 the NEW queue. Several uploads have been rejected so far because the
715 debian/copyright file was incomplete or wrong, but there is no reason
716 to give up. The current status can be seen on
717 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
718 team status page
</a
>, and
719 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
720 source code
</a
> is available on Alioth.
</p
>
722 <p
>As I want ZFS to be included in next version of Debian to make sure
723 my home server can function in the future using only official Debian
724 packages, and the current blocker is to get the debian/copyright file
725 accepted by the FTP masters in Debian, I decided a while back to try
726 to help out the team. This was the background for my blog post about
727 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
728 updating and checking debian/copyright semi-automatically
</a
>, and I
729 used the techniques I explored there to try to find any errors in the
730 copyright file. It is not very easy to check every one of the around
731 2000 files in the source package, but I hope we this time got it
732 right. If you want to help out, check out the git source and try to
733 find missing entries in the debian/copyright file.
</p
>
738 <title>Full battery stats collector is now available in Debian
</title>
739 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
740 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
741 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
742 <description><p
>Since this morning, the battery-stats package in Debian include an
743 extended collector that will collect the complete battery history for
744 later processing and graphing. The original collector store the
745 battery level as percentage of last full level, while the new
746 collector also record battery vendor, model, serial number, design
747 full level, last full level and current battery level. This make it
748 possible to predict the lifetime of the battery as well as visualise
749 the energy flow when the battery is charging or discharging.
</p
>
751 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
752 in the version
0.5.1 package in unstable. Get the new battery level graph
753 and lifetime prediction by running:
756 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
757 </pre
></p
>
759 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
761 <p
>The flow in/out of the battery can be seen by running (no menu
762 entry yet):
</p
>
765 /usr/share/battery-stats/battery-stats-graph-flow
766 </pre
></p
>
768 <p
>I
'm not quite happy with the way the data is visualised, at least
769 when there are few data points. The graphs look a bit better with a
770 few years of data.
</p
>
772 <p
>A while back one important feature I use in the battery stats
773 collector broke in Debian. The scripts in
774 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
775 suspect it happened when Jessie started using systemd, but I do not
776 know. The issue is reported as
777 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
778 pm-utils. I managed to work around it by adding an udev rule to call
779 the collector script every time the power connector is connected and
780 disconnected. With this fix in place it was finally time to make a
781 new release of the package, and get it into Debian.
</p
>
783 <p
>If you are interested in how your laptop battery is doing, please
785 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
786 in Debian unstable, or rebuild it on Jessie to get it working on
787 Debian stable. :) The upstream source is available from
788 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
789 As always, patches are very welcome.
</p
>
794 <title>Making battery measurements a little easier in Debian
</title>
795 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
796 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
797 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
798 <description><p
>Back in September, I blogged about
799 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
800 system I wrote to collect statistics about my laptop battery
</a
>, and
801 how it showed the decay and death of this battery (now replaced). I
802 created a simple deb package to handle the collection and graphing,
803 but did not want to upload it to Debian as there were already
804 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
805 package in Debian
</a
> that should do the same thing, and I did not see
806 a point of uploading a competing package when battery-stats could be
807 fixed instead. I reported a few bugs about its non-function, and
808 hoped someone would step in and fix it. But no-one did.
</p
>
810 <p
>I got tired of waiting a few days ago, and took matters in my own
811 hands. The end result is that I am now the new upstream developer of
812 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
813 battery-stats in Debian, and the package in Debian unstable is finally
814 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
815 information provided by the Linux kernel. If you install the
816 battery-stats package from unstable now, you will be able to get a
817 graph of the current battery fill level, to get some idea about the
818 status of the battery. The source package build and work just fine in
819 Debian testing and stable (and probably oldstable too, but I have not
820 tested). The default graph you get for that system look like this:
</p
>
822 <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
>
824 <p
>My plans for the future is to merge my old scripts into the
825 battery-stats package, as my old scripts collected a lot more details
826 about the battery. The scripts are merged into the upstream
827 battery-stats git repository already, but I am not convinced they work
828 yet, as I changed a lot of paths along the way. Will have to test a
829 bit more before I make a new release.
</p
>
831 <p
>I will also consider changing the file format slightly, as I
832 suspect the way I combine several values into one field might make it
833 impossible to know the type of the value when using it for processing
834 and graphing.
</p
>
836 <p
>If you would like I would like to keep an close eye on your laptop
837 battery, check out the battery-stats package in
838 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
840 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
841 I would love some help to improve the system further.
</p
>
846 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
847 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
849 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
850 <description><p
>Making packages for Debian requires quite a lot of attention to
851 details. And one of the details is the content of the
852 debian/copyright file, which should list all relevant licenses used by
853 the code in the package in question, preferably in
854 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
855 readable DEP5 format
</a
>.
</p
>
857 <p
>For large packages with lots of contributors it is hard to write
858 and update this file manually, and if you get some detail wrong, the
859 package is normally rejected by the ftpmasters. So getting it right
860 the first time around get the package into Debian faster, and save
861 both you and the ftpmasters some work.. Today, while trying to figure
862 out what was wrong with
863 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
864 zfsonlinux copyright file
</a
>, I decided to spend some time on
865 figuring out the options for doing this job automatically, or at least
866 semi-automatically.
</p
>
868 <p
>Lucikly, there are at least two tools available for generating the
869 file based on the code in the source package,
870 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
871 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
872 not sure which one of them came first, but both seem to be able to
873 create a sensible draft file. As far as I can tell, none of them can
874 be trusted to get the result just right, so the content need to be
875 polished a bit before the file is OK to upload. I found the debmake
877 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
878 blog posts from
2014</a
>.
880 <p
>To generate using debmake, use the -cc option:
883 debmake -cc
> debian/copyright
884 </pre
></p
>
886 <p
>Note there are some problems with python and non-ASCII names, so
887 this might not be the best option.
</p
>
889 <p
>The cme option is based on a config parsing library, and I found
891 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
892 blog post from
2015</a
>. To generate using cme, use the
'update
893 dpkg-copyright
' option:
896 cme update dpkg-copyright
897 </pre
></p
>
899 <p
>This will create or update debian/copyright. The cme tool seem to
900 handle UTF-
8 names better than debmake.
</p
>
902 <p
>When the copyright file is created, I would also like some help to
903 check if the file is correct. For this I found two good options,
904 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
905 to focus on license types and file matching, and is able to detect
906 ineffective blocks in the copyright file. The latter reports missing
907 copyright holders and years, but was confused by inconsistent license
908 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
909 fix all issues reported by them before uploading. But I do not know
910 if the tools and the ftpmasters agree on what is important to fix in a
911 copyright file, so the package might still be rejected.
</p
>
913 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
914 will read through the source and try to find all copyright statements.
915 It is not comparing the result to the content of debian/copyright, but
916 can be useful when verifying the content of the copyright file.
</p
>
918 <p
>Are you aware of better tools in Debian to create and update
919 debian/copyright file. Please let me know, or blog about it on
920 planet.debian.org.
</p
>
922 <p
>As usual, if you use Bitcoin and want to show your support of my
923 activities, please send Bitcoin donations to my address
924 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
926 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
927 on how to use licensecheck and cdbs to create a draft copyright file
930 licensecheck --copyright -r `find * -type f` | \
931 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
932 </pre
></p
>
934 <p
>He mentioned that he normally check the generated file into the
935 version control system to make it easier to discover license and
936 copyright changes in the upstream source. I will try to do the same
937 with my packages in the future.
</p
>
939 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
940 against using -quiet for new users, so I removed it from the proposed
941 command line.
</p
>
946 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
947 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
949 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
950 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
951 is taking shape in Debian, and one provided feature is a very
952 convenient way to tell you which package to install to make a given
953 firmware file available when the kernel is looking for it. This can
954 be done using apt-file too, but that is for someone else to blog
957 <p
>Here is a small recipe to find the package with a given firmware
958 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
959 picked from the set of firmware announced using appstream in Debian
960 unstable. In general you would be looking for the firmware requested
961 by the kernel during kernel module loading. To find the package
962 providing the example file, do like this:
</p
>
964 <blockquote
><pre
>
965 % apt install appstream
969 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
970 awk
'/Package:/ {print $
2}
'
973 </pre
></blockquote
>
975 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
976 appstream wiki
</a
> page to learn how to embed the package metadata in
977 a way appstream can use.
</p
>
979 <p
>This same approach can be used to find any package supporting a
980 given MIME type. This is very useful when you get a file you do not
981 know how to handle. First find the mime type using
<tt
>file
982 --mime-type
</tt
>, and next look up the package providing support for
983 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
984 and you can find all packages handling this type like this:
</p
>
986 <blockquote
><pre
>
987 % apt install appstream
991 % appstreamcli what-provides mimetype image/svg+xml | \
992 awk
'/Package:/ {print $
2}
'
1014 </pre
></blockquote
>
1016 <p
>I believe the MIME types are fetched from the desktop file for
1017 packages providing appstream metadata.
</p
>
1022 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1023 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1025 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1026 <description><p
>Most people seem not to realise that every time they walk around
1027 with the computerised radio beacon known as a mobile phone their
1028 position is tracked by the phone company and often stored for a long
1029 time (like every time a SMS is received or sent). And if their
1030 computerised radio beacon is capable of running programs (often called
1031 mobile apps) downloaded from the Internet, these programs are often
1032 also capable of tracking their location (if the app requested access
1033 during installation). And when these programs send out information to
1034 central collection points, the location is often included, unless
1035 extra care is taken to not send the location. The provided
1036 information is used by several entities, for good and bad (what is
1037 good and bad, depend on your point of view). What is certain, is that
1038 the private sphere and the right to free movement is challenged and
1039 perhaps even eradicated for those announcing their location this way,
1040 when they share their whereabouts with private and public
1043 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1045 <p
>The phone company logs provide a register of locations to check out
1046 when one want to figure out what the tracked person was doing. It is
1047 unavailable for most of us, but provided to selected government
1048 officials, company staff, those illegally buying information from
1049 unfaithful servants and crackers stealing the information. But the
1050 public information can be collected and analysed, and a free software
1051 tool to do so is called
1052 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1053 discovered it when I read
1054 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1055 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1056 November
2014, and decided to check if it was available in Debian.
1057 The python program was in Debian, but
1058 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1059 Debian
</a
> was completely broken and practically unmaintained. I
1060 uploaded a new version which did not work quite right, but did not
1061 have time to fix it then. This Christmas I decided to finally try to
1062 get Creepy operational in Debian. Now a fixed version is available in
1063 Debian unstable and testing, and almost all Debian specific patches
1065 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1067 <p
>The Creepy program visualises geolocation information fetched from
1068 Twitter, Instagram, Flickr and Google+, and allow one to get a
1069 complete picture of every social media message posted recently in a
1070 given area, or track the movement of a given individual across all
1071 these services. Earlier it was possible to use the search API of at
1072 least some of these services without identifying oneself, but these
1073 days it is impossible. This mean that to use Creepy, you need to
1074 configure it to log in as yourself on these services, and provide
1075 information to them about your search interests. This should be taken
1076 into account when using Creepy, as it will also share information
1077 about yourself with the services.
</p
>
1079 <p
>The picture above show the twitter messages sent from (or at least
1080 geotagged with a position from) the city centre of Oslo, the capital
1081 of Norway. One useful way to use Creepy is to first look at
1082 information tagged with an area of interest, and next look at all the
1083 information provided by one or more individuals who was in the area.
1084 I tested it by checking out which celebrity provide their location in
1085 twitter messages by checkout out who sent twitter messages near a
1086 Norwegian TV station, and next could track their position over time,
1087 making it possible to locate their home and work place, among other
1088 things. A similar technique have been
1089 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1090 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1091 tool to discover lying governments, and a useful tool to help people
1092 understand the value of the private information they provide to the
1095 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1096 it depend on several python modules currently missing in Jessie (at
1097 least python-instagram, python-flickrapi and
1098 python-requests-toolbelt).
</p
>
1100 <p
>(I have uploaded
1101 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1102 screenshots.debian.net
</a
> and licensed it under the same terms as the
1103 Creepy program in Debian.)
</p
>
1108 <title>Always download Debian packages using Tor - the simple recipe
</title>
1109 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1111 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1112 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1113 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1114 that those listening on the Internet lines would have good reason to
1115 believe a computer have a given security hole
</a
> if it download a
1116 security fix from a Debian mirror. This is a good reason to always
1117 use encrypted connections to the Debian mirror, to make sure those
1118 listening do not know which IP address to attack. In August, Richard
1119 Hartmann observed that encryption was not enough, when it was possible
1120 to interfere download size to security patches or the fact that
1121 download took place shortly after a security fix was released, and
1122 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1123 to always use Tor to download packages from the Debian mirror
</a
>. He
1124 was not the first to propose this, as the
1125 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1126 package by Tim Retout already existed to make it easy to convince apt
1127 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1128 aware of that package when I read the blog post from Richard.
</p
>
1130 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1131 sysadmins, and he set up a Tor hidden service on one of the central
1132 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1133 it possible to download packages directly between two tor nodes,
1134 making sure the network traffic always were encrypted.
</p
>
1136 <p
>Here is a short recipe for enabling this on your machine, by
1137 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1138 urls with tor+http and tor+https, and using the hidden service instead
1139 of the official Debian mirror site. I recommend installing
1140 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1141 done in /etc/.
</p
>
1143 <blockquote
><pre
>
1144 apt install apt-transport-tor
1145 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1146 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1147 </pre
></blockquote
>
1149 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1150 the sed commands for these too. The sed command is assuming your are
1151 using the ftp.debian.org Debian mirror. Adjust the command (or just
1152 edit the file manually) to match your mirror.
</p
>
1154 <p
>This work in Debian Jessie and later. Note that tools like
1155 <tt
>apt-file
</tt
> only recently started using the apt transport
1156 system, and do not work with these tor+http URLs. For
1157 <tt
>apt-file
</tt
> you need the version currently in experimental,
1158 which need a recent apt version currently only in unstable. So if you
1159 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1161 <p
>Another advantage from this change is that your machine will start
1162 using Tor regularly and at fairly random intervals (every time you
1163 update the package lists or upgrade or install a new package), thus
1164 masking other Tor traffic done from the same machine. Using Tor will
1165 become normal for the machine in question.
</p
>
1167 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1168 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1169 enabled. It would be great if it was the default on any Debian
1175 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1176 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1177 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1178 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1179 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1180 call the car license plate numbers in those days. I would write the
1181 numbers down in my little book and compare notes with the other kids
1182 to see how many region codes we had seen and if we had seen some
1183 exotic or special region codes and numbers. It was a fun game to pass
1184 time, as we kids have plenty of it.
</p
>
1186 <p
>A few days I came across
1187 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1188 project
</a
>, a free software project to automatically discover and
1189 report license plates in images and video streams, and provide the
1190 "car numbers
" in a machine readable format. I
've been looking for
1191 such system for a while now, because I believe it is a bad idea that the
1192 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1193 number plate recognition
</a
> tool only is available in the hands of
1194 the powerful, and want it to be available also for the powerless to
1195 even the score when it comes to surveillance and sousveillance. I
1196 discovered the developer
1197 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1198 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1199 help him get it into shape to get the package uploaded into the Debian
1202 <p
>Today we finally managed to get the package into shape and uploaded
1203 it into Debian, where it currently
1204 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1205 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1207 <p
>I guess you are wondering why on earth such tool would be useful
1208 for the common folks, ie those not running a large government
1209 surveillance system? Well, I plan to put it in a computer on my bike
1210 and in my car, tracking the cars nearby and allowing me to be notified
1211 when number plates on my watch list are discovered. Another use case
1212 was suggested by a friend of mine, who wanted to set it up at his home
1213 to open the car port automatically when it discovered the plate on his
1214 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1215 capable of placing his license plate number of a piece of cardboard to
1216 open his car port, men replied that it was always unlocked anyway. I
1217 guess for such use case it make sense. I am sure there are other use
1218 cases too, for those with imagination and a vision.
</p
>
1220 <p
>If you want to build your own version of the Debian package, check
1221 out the upstream git source and symlink ./distros/debian to ./debian/
1222 before running
"debuild
" to build the source. Or wait a bit until the
1223 package show up in unstable.
</p
>
1228 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1229 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1231 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1232 <description><p
>Around three years ago, I created
1233 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1234 system
</a
> to get a more practical solution in Debian for handing
1235 hardware related packages. A GUI system in the isenkram package will
1236 present a pop-up dialog when some hardware dongle supported by
1237 relevant packages in Debian is inserted into the machine. The same
1238 lookup mechanism to detect packages is available as command line
1239 tools in the isenkram-cli package. In addition to mapping hardware,
1240 it will also map kernel firmware files to packages and make it easy to
1241 install needed firmware packages automatically. The key for this
1242 system to work is a good way to map hardware to packages, in other
1243 words, allow packages to announce what hardware they will work
1246 <p
>I started by providing data files in the isenkram source, and
1247 adding code to download the latest version of these data files at run
1248 time, to ensure every user had the most up to date mapping available.
1249 I also added support for storing the mapping in the Packages file in
1250 the apt repositories, but did not push this approach because while I
1251 was trying to figure out how to best store hardware/package mappings,
1252 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1253 appstream system
</a
> was announced. I got in touch and suggested to
1254 add the hardware mapping into that data set to be able to use
1255 appstream as a data source, and this was accepted at least for the
1256 Debian version of appstream.
</p
>
1258 <p
>A few days ago using appstream in Debian for this became possible,
1259 and today I uploaded a new version
0.20 of isenkram adding support for
1260 appstream as a data source for mapping hardware to packages. The only
1261 package so far using appstream to announce its hardware support is my
1262 pymissile package. I got help from Matthias Klumpp with figuring out
1263 how do add the required
1264 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1265 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1266 this content:
</p
>
1268 <blockquote
><pre
>
1269 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1270 &lt;component
&gt;
1271 &lt;id
&gt;pymissile
&lt;/id
&gt;
1272 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1273 &lt;name
&gt;pymissile
&lt;/name
&gt;
1274 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1275 &lt;description
&gt;
1277 Pymissile provides a curses interface to control an original
1278 Marks and Spencer / Striker USB Missile Launcher, as well as a
1279 motion control script to allow a webcamera to control the
1282 &lt;/description
&gt;
1283 &lt;provides
&gt;
1284 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1285 &lt;/provides
&gt;
1286 &lt;/component
&gt;
1287 </pre
></blockquote
>
1289 <p
>The key for isenkram is the component/provides/modalias value,
1290 which is a glob style match rule for hardware specific strings
1291 (modalias strings) provided by the Linux kernel. In this case, it
1292 will map to all USB devices with vendor code
1130 and product code
1295 <p
>Note, it is important that the license of all the metadata files
1296 are compatible to have permissions to aggregate them into archive wide
1297 appstream files. Matthias suggested to use MIT or BSD licenses for
1298 these files. A challenge is figuring out a good id for the data, as
1299 it is supposed to be globally unique and shared across distributions
1300 (in other words, best to coordinate with upstream what to use). But
1301 it can be changed later or, so we went with the package name as
1302 upstream for this project is dormant.
</p
>
1304 <p
>To get the metadata file installed in the correct location for the
1305 mirror update scripts to pick it up and include its content the
1306 appstream data source, the file must be installed in the binary
1307 package under /usr/share/appdata/. I did this by adding the following
1308 line to debian/pymissile.install:
</p
>
1310 <blockquote
><pre
>
1311 debian/pymissile.metainfo.xml usr/share/appdata
1312 </pre
></blockquote
>
1314 <p
>With that in place, the command line tool isenkram-lookup will list
1315 all packages useful on the current computer automatically, and the GUI
1316 pop-up handler will propose to install the package not already
1317 installed if a hardware dongle is inserted into the machine in
1320 <p
>Details of the modalias field in appstream is available from the
1321 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1323 <p
>To locate the modalias values of all hardware present in a machine,
1324 try running this command on the command line:
</p
>
1326 <blockquote
><pre
>
1327 cat $(find /sys/devices/|grep modalias)
1328 </pre
></blockquote
>
1330 <p
>To learn more about the isenkram system, please check out
1331 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1332 blog posts tagged isenkram
</a
>.
</p
>
1337 <title>The GNU General Public License is not magic pixie dust
</title>
1338 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1339 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1340 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1341 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1342 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1343 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1344 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1345 I quote the blog post from Paul in full here with his permission:
<p
>
1349 <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
>
1352 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1354 The first step is to choose a
1355 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1358 The next step is, when someone fails to follow that copyleft license,
1359 <b
>it must be enforced
</b
><br/
>
1361 and its a simple fact of our modern society that such type of
1364 is incredibly expensive to do and incredibly difficult to do.
1367 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1368 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1369 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1370 0x57</a
></small
></p
>
1372 <p
>As the Debian Website
1373 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1374 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1375 imply, public domain and permissively licensed software can lead to
1376 the production of more proprietary software as people discover useful
1377 software, extend it and or incorporate it into their hardware or
1378 software products. Copyleft licenses such as the GNU GPL were created
1379 to close off this avenue to the production of proprietary software but
1380 such licenses are not enough. With the ongoing adoption of Free
1381 Software by individuals and groups, inevitably the community
's
1382 expectations of license compliance are violated, usually out of
1383 ignorance of the way Free Software works, but not always. As Karen
1384 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1385 Freedom
">FaiF
</a
>
1386 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1387 copyleft is nothing if no-one is willing and able to stand up in court
1388 to protect it. The reality of today
's world is that legal
1389 representation is expensive, difficult and time consuming. With
1390 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1391 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1392 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1393 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1394 of the Linux project, Debian and other groups against GPL violations.
1395 In March the SFC supported a
1396 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1397 by Christoph Hellwig
</a
> against VMware for refusing to
1398 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1399 with the GPL
</a
> in relation to their use of parts of the Linux
1400 kernel. Since then two of their sponsors pulled corporate funding and
1402 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1403 or cancelled their talks
</a
>. As a result they have decided to rely
1404 less on corporate funding and more on the broad community of
1405 individuals who support Free Software and copyleft. So the SFC has
1406 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1407 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1408 a community of folks who stand up for copyleft and the GPL by
1409 supporting their work on promoting and supporting copyleft and Free
1412 <p
>If you support Free Software,
1413 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1414 what the SFC do, agree with their
1415 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1416 principles
</a
>, are happy about their
1417 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1418 work on a project that is an SFC
1419 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1420 just want to stand up for copyleft, please join
1421 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1422 Allan Webber
</a
>,
1423 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1425 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1426 Bacon
</a
>, myself and
1427 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1429 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1430 next week your donation will be
1431 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1432 by an anonymous donor. Please also consider asking your employer to
1433 match your donation or become a sponsor of SFC. Don
't forget to
1434 spread the word about your support for SFC via email, your blog and or
1435 social media accounts.
</p
>
1439 <p
>I agree with Paul on this topic and just signed up as a Supporter
1440 of Software Freedom Conservancy myself. Perhaps you should be a
1441 supporter too?
</p
>
1446 <title>PGP key transition statement for key EE4E02F9
</title>
1447 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1449 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1450 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1451 set it up properly. I wanted to generate it offline and have it
1452 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1453 smart card
</a
> for daily use, and learning how to do it and finding
1454 time to sit down with an offline machine almost took forever. But
1455 finally I
've been able to complete the process, and have now moved
1456 from my old GPG key to a new GPG key. See
1457 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1458 full transition statement, signed with both my old and new key
</a
> for
1459 the details. This is my new key:
</p
>
1462 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1463 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1464 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1465 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1466 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1467 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1468 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1471 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1472 my old key.
</p
>
1474 <p
>If you signed my old key
1475 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1476 I
'd very much appreciate a signature on my new key, details and
1477 instructions in the transition statement. I m happy to reciprocate if
1478 you have a similarly signed transition statement to present.
</p
>
1483 <title>The life and death of a laptop battery
</title>
1484 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1485 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1486 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1487 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1488 But this do not last. The last few laptops gave me a feeling that
1489 within a year, the life time is just a fraction of what it used to be,
1490 and it slowly become painful to use the laptop without power connected
1491 all the time. Because of this, when I got a new Thinkpad X230 laptop
1492 about two years ago, I decided to monitor its battery state to have
1493 more hard facts when the battery started to fail.
</p
>
1495 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1497 <p
>First I tried to find a sensible Debian package to record the
1498 battery status, assuming that this must be a problem already handled
1499 by someone else. I found
1500 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1501 which collects statistics from the battery, but it was completely
1502 broken. I sent a few suggestions to the maintainer, but decided to
1503 write my own collector as a shell script while I waited for feedback
1505 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1506 blog post about the battery development on a MacBook Air
</a
> I also
1508 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1509 available in Debian.
</p
>
1511 <p
>I started my collector
2013-
07-
15, and it has been collecting
1512 battery stats ever since. Now my
1513 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1514 measurements, from the time the battery was working great until now,
1515 when it is unable to charge above
7% of original capacity. My
1516 collector shell script is quite simple and look like this:
</p
>
1521 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1523 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1524 logfile=/var/log/hjemmenett-battery-status.log
1526 files=
"manufacturer model_name technology serial_number \
1527 energy_full energy_full_design energy_now cycle_count status
"
1529 if [ ! -e
"$logfile
" ] ; then
1531 printf
"timestamp,
"
1533 printf
"%s,
" $f
1536 )
> "$logfile
"
1540 # Print complete message in one echo call, to avoid race condition
1541 # when several log processes run in parallel.
1542 msg=$(printf
"%s,
" $(date +%s); \
1543 for f in $files; do \
1544 printf
"%s,
" $(cat $f); \
1546 echo
"$msg
"
1549 cd /sys/class/power_supply
1552 (cd $bat
&& log_battery
>> "$logfile
")
1556 <p
>The script is called when the power management system detect a
1557 change in the power status (power plug in or out), and when going into
1558 and out of hibernation and suspend. In addition, it collect a value
1559 every
10 minutes. This make it possible for me know when the battery
1560 is discharging, charging and how the maximum charge change over time.
1561 The code for the Debian package
1562 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1563 available on github
</a
>.
</p
>
1565 <p
>The collected log file look like this:
</p
>
1568 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1569 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1571 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1572 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1575 <p
>I wrote a small script to create a graph of the charge development
1576 over time. This graph depicted above show the slow death of my laptop
1579 <p
>But why is this happening? Why are my laptop batteries always
1580 dying in a year or two, while the batteries of space probes and
1581 satellites keep working year after year. If we are to believe
1582 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1583 University
</a
>, the cause is me charging the battery whenever I have a
1584 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1585 all the time, but to stay below
90% of full charge most of the time.
1586 I
've been told that the Tesla electric cars
1587 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1588 the charge of their batteries to
80%
</a
>, with the option to charge to
1589 100% when preparing for a longer trip (not that I would want a car
1590 like Tesla where rights to privacy is abandoned, but that is another
1591 story), which I guess is the option we should have for laptops on
1592 Linux too.
</p
>
1594 <p
>Is there a good and generic way with Linux to tell the battery to
1595 stop charging at
80%, unless requested to charge to
100% once in
1596 preparation for a longer trip? I found
1597 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1598 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1599 80%
</a
>, but could not get it to work (kernel module refused to
1602 <p
>I wonder why the battery capacity was reported to be more than
100%
1603 at the start. I also wonder why the
"full capacity
" increases some
1604 times, and if it is possible to repeat the process to get the battery
1605 back to design capacity. And I wonder if the discharge and charge
1606 speed change over time, or if this stay the same. I did not yet try
1607 to write a tool to calculate the derivative values of the battery
1608 level, but suspect some interesting insights might be learned from
1611 <p
>Update
2015-
09-
24: I got a tip to install the packages
1612 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1613 packages instead of the tp-smapi-dkms package I had tried to use
1614 initially, and use
'tlp setcharge
40 80' to change when charging start
1615 and stop. I
've done so now, but expect my existing battery is toast
1616 and need to be replaced. The proposal is unfortunately Thinkpad
1622 <title>New laptop - some more clues and ideas based on feedback
</title>
1623 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1624 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1625 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1626 <description><p
>Several people contacted me after my previous blog post about my
1627 need for a new laptop, and provided very useful feedback. I wish to
1628 thank every one of these. Several pointed me to the possibility of
1629 fixing my X230, and I am already in the process of getting Lenovo to
1630 do so thanks to the on site, next day support contract covering the
1631 machine. But the battery is almost useless (I expect to replace it
1632 with a non-official battery) and I do not expect the machine to live
1633 for many more years, so it is time to plan its replacement. If I did
1634 not have a support contract, it was suggested to find replacement parts
1635 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1636 might present a language barrier as I do not understand French.
</p
>
1638 <p
>One tip I got was to use the
1639 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1640 compare laptop models. It seem to have more models available than
1641 prisjakt.no. Another tip I got from someone I know have similar
1642 keyboard preferences was that the HP EliteBook
840 keyboard is not
1643 very good, and this matches my experience with earlier EliteBook
1644 keyboards I tested. Because of this, I will not consider it any further.
1646 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1647 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1648 (which is missing from the X240), and is working fairly well with
1649 Debian Sid/Unstable according to
1650 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1651 got on the keyboard quality are not consistent. Some say the keyboard
1652 is good, others say it is ok, while others say it is not very good.
1653 Those with experience from X41 and and X60 agree that the X250
1654 keyboard is not as good as those trusty old laptops, and suggest I
1655 keep and fix my X230 instead of upgrading, or get a used X230 to
1656 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1657 activity and battery status, which is very convenient on my X230. I
'm
1658 also told that the CPU fan is running very often, making it a bit
1659 noisy. In any case, the X250 do not work out of the box with Debian
1660 Stable/Jessie, one of my requirements.
</p
>
1662 <p
>I have also gotten a few vendor proposals, one was
1663 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1664 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1665 The latter look very attractive to me.
</p
>
1667 <p
>Again, thank you all for the very useful feedback. It help a lot
1668 as I keep looking for a replacement.
</p
>
1670 <p
>Update
2015-
07-
06: I was recommended to check out the
1671 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1673 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1674 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1679 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1680 <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>
1681 <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>
1682 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1683 <description><p
>My primary work horse laptop is failing, and will need a
1684 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1685 started flickering yesterday, and I suspect the cause is a broken
1686 cable, as changing the angle of the screen some times get rid of the
1687 flickering.
</p
>
1689 <p
>My requirements have not really changed since I bought it, and is
1691 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1692 described them in
2013</a
>. The last time I bought a laptop, I had
1694 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1695 where I could select at least a few of the requirements (mouse pin,
1696 wifi, weight) and go through the rest manually. Three button mouse
1697 and a good keyboard is not available as an option, and all the three
1698 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1699 G2) lack three mouse buttons). It is also unclear to me how good the
1700 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1701 the keyboard, even if the quality and robustness in the X series have
1702 deteriorated since X41.
</p
>
1704 <p
>I wonder how I can find a sensible laptop when none of the options
1705 seem sensible to me? Are there better services around to search the
1706 set of available laptops for features? Please send me an email if you
1707 have suggestions.
</p
>
1709 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1710 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1711 of endorsed hardware
</a
>, which is useful background information.
</p
>
1716 <title>How to stay with sysvinit in Debian Jessie
</title>
1717 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1718 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1719 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1720 <description><p
>By now, it is well known that Debian Jessie will not be using
1721 sysvinit as its boot system by default. But how can one keep using
1722 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1724 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1725 Schubert
</a
> and
1726 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1729 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1730 keep sysvinit as your boot system, create a file
1731 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1732 you upgrade:
</p
>
1734 <p
><blockquote
><pre
>
1735 Package: systemd-sysv
1736 Pin: release o=Debian
1738 </pre
></blockquote
><p
>
1740 <p
>This file content will tell apt and aptitude to not consider
1741 installing systemd-sysv as part of any installation and upgrade
1742 solution when resolving dependencies, and thus tell it to avoid
1743 systemd as a default boot system. The end result should be that the
1744 upgraded system keep using sysvinit.
</p
>
1746 <p
>If you are installing Jessie for the first time, there is no way to
1747 get sysvinit installed by default (debootstrap used by
1748 debian-installer have no option for this), but one can tell the
1749 installer to switch to sysvinit before the first boot. Either by
1750 using a kernel argument to the installer, or by adding a line to the
1751 preseed file used. First, the kernel command line argument:
1753 <p
><blockquote
><pre
>
1754 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1755 </pre
></blockquote
><p
>
1757 <p
>Next, the line to use in a preseed file:
</p
>
1759 <p
><blockquote
><pre
>
1760 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1761 </pre
></blockquote
><p
>
1763 <p
>One can of course also do this after the first boot by installing
1764 the sysvinit-core package.
</p
>
1766 <p
>I recommend only using sysvinit if you really need it, as the
1767 sysvinit boot sequence in Debian have several hardware specific bugs
1768 on Linux caused by the fact that it is unpredictable when hardware
1769 devices show up during boot. But on the other hand, the new default
1770 boot system still have a few rough edges I hope will be fixed before
1771 Jessie is released.
</p
>
1773 <p
>Update
2014-
11-
26: Inspired by
1774 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1775 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1781 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1782 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1783 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1784 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1785 <description><p
>The right to communicate with your friends and family in private,
1786 without anyone snooping, is a right every citicen have in a liberal
1787 democracy. But this right is under serious attack these days.
</p
>
1789 <p
>A while back it occurred to me that one way to make the dragnet
1790 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1791 the whisleblower Snowden) more expensive for Internet email,
1792 is to deliver all email using SMTP via Tor. Such SMTP option would be
1793 a nice addition to the FreedomBox project if we could send email
1794 between FreedomBox machines without leaking metadata about the emails
1795 to the people peeking on the wire. I
1796 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1797 this on the FreedomBox project mailing list in October
</a
> and got a
1798 lot of useful feedback and suggestions. It also became obvious to me
1799 that this was not a novel idea, as the same idea was tested and
1800 documented by Johannes Berg as early as
2006, and both
1801 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1802 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1803 propose a similar method / protocol to pass emails between users.
</p
>
1805 <p
>To implement such system one need to set up a Tor hidden service
1806 providing the SMTP protocol on port
25, and use email addresses
1807 looking like username@hidden-service-name.onion. With such addresses
1808 the connections to port
25 on hidden-service-name.onion using Tor will
1809 go to the correct SMTP server. To do this, one need to configure the
1810 Tor daemon to provide the hidden service and the mail server to accept
1811 emails for this .onion domain. To learn more about Exim configuration
1812 in Debian and test the design provided by Johannes Berg in his FAQ, I
1813 set out yesterday to create a Debian package for making it trivial to
1814 set up such SMTP over Tor service based on Debian. Getting it to work
1815 were fairly easy, and
1816 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1817 source code for the Debian package
</a
> is available from github. I
1818 plan to move it into Debian if further testing prove this to be a
1819 useful approach.
</p
>
1821 <p
>If you want to test this, set up a blank Debian machine without any
1822 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1823 get rid of exim4). Install tor, clone the git repository mentioned
1824 above, build the deb and install it on the machine. Next, run
1825 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1826 the instructions to get the service up and running. Restart tor and
1827 exim when it is done, and test mail delivery using swaks like
1830 <p
><blockquote
><pre
>
1831 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1832 --to fbx@dutlqrrmjhtfa3vp.onion
1833 </pre
></blockquote
></p
>
1835 <p
>This will test the SMTP delivery using tor. Replace the email
1836 address with your own address to test your server. :)
</p
>
1838 <p
>The setup procedure is still to complex, and I hope it can be made
1839 easier and more automatic. Especially the tor setup need more work.
1840 Also, the package include a tor-smtp tool written in C, but its task
1841 should probably be rewritten in some script language to make the deb
1842 architecture independent. It would probably also make the code easier
1843 to review. The tor-smtp tool currently need to listen on a socket for
1844 exim to talk to it and is started using xinetd. It would be better if
1845 no daemon and no socket is needed. I suspect it is possible to get
1846 exim to run a command line tool for delivery instead of talking to a
1847 socket, and hope to figure out how in a future version of this
1850 <p
>Until I wipe my test machine, I can be reached using the
1851 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1852 SMTorP. :)
</p
>
1857 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1858 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1860 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1861 <description><p
>If you ever had to moderate a mailman list, like the ones on
1862 alioth.debian.org, you know the web interface is fairly slow to
1863 operate. First you visit one web page, enter the moderation password
1864 and get a new page shown with a list of all the messages to moderate
1865 and various options for each email address. This take a while for
1866 every list you moderate, and you need to do it regularly to do a good
1867 job as a list moderator. But there is a quick alternative,
1868 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1869 listadmin program
</a
>. It allow you to check lists for new messages
1870 to moderate in a fraction of a second. Here is a test run on two
1871 lists I recently took over:
</p
>
1873 <p
><blockquote
><pre
>
1874 % time listadmin xiph
1875 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1876 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1882 </pre
></blockquote
></p
>
1884 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1885 there are no message in the moderation queue. Every morning I
1886 currently moderate
68 mailman lists, and it normally take around two
1887 minutes. When I took over the two pkg-xiph lists above a few days
1888 ago, there were
400 emails waiting in the moderator queue. It took me
1889 less than
15 minutes to process them all using the listadmin
1892 <p
>If you install
1893 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1894 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1895 with content like this, the moderation task is a breeze:
</p
>
1897 <p
><blockquote
><pre
>
1898 username username@example.org
1901 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1904 adminurl https://{domain}/mailman/admindb/{list}
1905 mailman-list@lists.example.com
1908 other-list@otherserver.example.org
1909 </pre
></blockquote
></p
>
1911 <p
>There are other options to set as well. Check the manual page to
1912 learn the details.
</p
>
1914 <p
>If you are forced to moderate lists on a mailman installation where
1915 the SSL certificate is self signed or not properly signed by a
1916 generally accepted signing authority, you can set a environment
1917 variable when calling listadmin to disable SSL verification:
</p
>
1919 <p
><blockquote
><pre
>
1920 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1921 </pre
></blockquote
></p
>
1923 <p
>If you want to moderate a subset of the lists you take care of, you
1924 can provide an argument to the listadmin script like I do in the
1925 initial screen dump (the xiph argument). Using an argument, only
1926 lists matching the argument string will be processed. This make it
1927 quick to accept messages if you notice the moderation request in your
1930 <p
>Without the listadmin program, I would never be the moderator of
68
1931 mailing lists, as I simply do not have time to spend on that if the
1932 process was any slower. The listadmin program have saved me hours of
1933 time I could spend elsewhere over the years. It truly is nice free
1936 <p
>As usual, if you use Bitcoin and want to show your support of my
1937 activities, please send Bitcoin donations to my address
1938 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1940 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1941 configuration example. Also, I
've been told that the
1942 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1948 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1949 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1951 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1952 <description><p
>When PXE installing laptops with Debian, I often run into the
1953 problem that the WiFi card require some firmware to work properly.
1954 And it has been a pain to fix this using preseeding in Debian.
1955 Normally something more is needed. But thanks to
1956 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1957 package
</a
> and its recent tasksel extension, it has now become easy
1958 to do this using simple preseeding.
</p
>
1960 <p
>The isenkram-cli package provide tasksel tasks which will install
1961 firmware for the hardware found in the machine (actually, requested by
1962 the kernel modules for the hardware). (It can also install user space
1963 programs supporting the hardware detected, but that is not the focus
1964 of this story.)
</p
>
1966 <p
>To get this working in the default installation, two preeseding
1967 values are needed. First, the isenkram-cli package must be installed
1968 into the target chroot (aka the hard drive) before tasksel is executed
1969 in the pkgsel step of the debian-installer system. This is done by
1970 preseeding the base-installer/includes debconf value to include the
1971 isenkram-cli package. The package name is next passed to debootstrap
1972 for installation. With the isenkram-cli package in place, tasksel
1973 will automatically use the isenkram tasks to detect hardware specific
1974 packages for the machine being installed and install them, because
1975 isenkram-cli contain tasksel tasks.
</p
>
1977 <p
>Second, one need to enable the non-free APT repository, because
1978 most firmware unfortunately is non-free. This is done by preseeding
1979 the apt-mirror-setup step. This is unfortunate, but for a lot of
1980 hardware it is the only option in Debian.
</p
>
1982 <p
>The end result is two lines needed in your preseeding file to get
1983 firmware installed automatically by the installer:
</p
>
1985 <p
><blockquote
><pre
>
1986 base-installer base-installer/includes string isenkram-cli
1987 apt-mirror-setup apt-setup/non-free boolean true
1988 </pre
></blockquote
></p
>
1990 <p
>The current version of isenkram-cli in testing/jessie will install
1991 both firmware and user space packages when using this method. It also
1992 do not work well, so use version
0.15 or later. Installing both
1993 firmware and user space packages might give you a bit more than you
1994 want, so I decided to split the tasksel task in two, one for firmware
1995 and one for user space programs. The firmware task is enabled by
1996 default, while the one for user space programs is not. This split is
1997 implemented in the package currently in unstable.
</p
>
1999 <p
>If you decide to give this a go, please let me know (via email) how
2000 this recipe work for you. :)
</p
>
2002 <p
>So, I bet you are wondering, how can this work. First and
2003 foremost, it work because tasksel is modular, and driven by whatever
2004 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2005 isenkram-cli package place two files for tasksel to find. First there
2006 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2008 <p
><blockquote
><pre
>
2009 Task: isenkram-packages
2011 Description: Hardware specific packages (autodetected by isenkram)
2012 Based on the detected hardware various hardware specific packages are
2014 Test-new-install: show show
2016 Packages: for-current-hardware
2018 Task: isenkram-firmware
2020 Description: Hardware specific firmware packages (autodetected by isenkram)
2021 Based on the detected hardware various hardware specific firmware
2022 packages are proposed.
2023 Test-new-install: mark show
2025 Packages: for-current-hardware-firmware
2026 </pre
></blockquote
></p
>
2028 <p
>The key parts are Test-new-install which indicate how the task
2029 should be handled and the Packages line referencing to a script in
2030 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2031 list of packages to install. The for-current-hardware-firmware script
2032 look like this to list relevant firmware for the machine:
2034 <p
><blockquote
><pre
>
2037 PATH=/usr/sbin:$PATH
2039 isenkram-autoinstall-firmware -l
2040 </pre
></blockquote
></p
>
2042 <p
>With those two pieces in place, the firmware is installed by
2043 tasksel during the normal d-i run. :)
</p
>
2045 <p
>If you want to test what tasksel will install when isenkram-cli is
2046 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2047 --new-install
</tt
> to get the list of packages that tasksel would
2050 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2051 pilots in testing this feature, as isenkram is used there now to
2052 install firmware, replacing the earlier scripts.
</p
>
2057 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2058 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2059 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2060 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2061 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2062 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2063 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2064 on a screen normally showing the bread types and prizes:
</p
>
2066 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2068 <p
>If it had booted as it was supposed to, I would never had known
2069 about this hidden Linux installation. It is interesting what
2070 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2075 <title>New lsdvd release version
0.17 is ready
</title>
2076 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2077 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2078 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2079 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2080 got a new set of developers a few weeks ago, after the original
2081 developer decided to step down and pass the project to fresh blood.
2082 This project is now maintained by Petter Reinholdtsen and Steve
2085 <p
>I just wrapped up
2086 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2087 new lsdvd release
</a
>, available in git or from
2088 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2089 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2094 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2095 <li
>Check for garbage in the program chains, which indicate that a track is
2096 non-existant, to work around additional copy protection
</li
>
2097 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2098 <li
>Fix pallete display of first entry
</li
>
2099 <li
>Fix include orders
</li
>
2100 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2101 <li
>Fix the chapter count
</li
>
2102 <li
>Make sure the array size and the array limit used when initialising
2103 the palette size is the same.
</li
>
2104 <li
>Fix array printing.
</li
>
2105 <li
>Correct subsecond calculations.
</li
>
2106 <li
>Add sector information to the output format.
</li
>
2107 <li
>Clean up code to be closer to ANSI C and compile without warnings
2108 with more GCC compiler warnings.
</li
>
2112 <p
>This change bring together patches for lsdvd in use in various
2113 Linux and Unix distributions, as well as patches submitted to the
2114 project the last nine years. Please check it out. :)
</p
>
2119 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2120 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2122 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2123 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2124 project
</a
> provide a Linux solution for schools, including a
2125 powerful desktop with education software, a central server providing
2126 web pages, user database, user home directories, central login and PXE
2127 boot of both clients without disk and the installation to install Debian
2128 Edu on machines with disk (and a few other services perhaps to small
2129 to mention here). We in the Debian Edu team are currently working on
2130 the Jessie based version, trying to get everything in shape before the
2131 freeze, to avoid having to maintain our own package repository in the
2133 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2134 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2135 work left. Some fatal problems block testing, breaking the installer,
2136 but it is possible to work around these to get anyway. Here is a
2137 recipe on how to get the installation limping along.
</p
>
2139 <p
>First, download the test ISO via
2140 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2141 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2143 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2144 The ISO build was broken on Tuesday, so we do not get a new ISO every
2145 12 hours or so, but thankfully the ISO we already got we are able to
2146 install with some tweaking.
</p
>
2148 <p
>When you get to the Debian Edu profile question, go to tty2
2149 (use Alt-Ctrl-F2), run
</p
>
2151 <p
><blockquote
><pre
>
2152 nano /usr/bin/edu-eatmydata-install
2153 </pre
></blockquote
></p
>
2155 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2156 optimization. Return to the installation, select the profile you want
2157 and continue. Without this change, exim4-config will fail to install
2158 due to a known bug in eatmydata.
</p
>
2160 <p
>When you get the grub question at the end, answer /dev/sda (or if
2161 this do not work, figure out what your correct value would be. All my
2162 test machines need /dev/sda, so I have no advice if it do not fit
2163 your need.
</p
>
2165 <p
>If you installed a profile including a graphical desktop, log in as
2166 root after the initial boot from hard drive, and install the
2167 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2168 or mate. If you want several desktop options, install more than one
2169 metapackage. Once this is done, reboot and you should have a working
2170 graphical login screen. This workaround should no longer be needed
2171 once the education-tasks package version
1.801 enter testing in two
2174 <p
>I believe the ISO build will start working on two days when the new
2175 tasksel package enter testing and Steve McIntyre get a chance to
2176 update the debian-cd git repository. The eatmydata, grub and desktop
2177 issues are already fixed in unstable and testing, and should show up
2178 on the ISO as soon as the ISO build start working again. Well the
2179 eatmydata optimization is really just disabled. The proper fix
2180 require an upload by the eatmydata maintainer applying the patch
2181 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2182 The rest have proper fixes in unstable.
</p
>
2184 <p
>I hope this get you going with the installation testing, as we are
2185 quickly running out of time trying to get our Jessie based
2186 installation ready before the distribution freeze in a month.
</p
>
2191 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2192 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2194 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2195 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2196 to handle my fairly large DVD collection. It is a nice command line
2197 tool to get details about a DVD, like title, tracks, track length,
2198 etc, in XML, Perl or human readable format. But lsdvd have not seen
2199 any new development since
2006 and had a few irritating bugs affecting
2200 its use with some DVDs. Upstream seemed to be dead, and in January I
2201 sent a small probe asking for a version control repository for the
2202 project, without any reply. But I use it regularly and would like to
2203 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2204 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2205 the project admin, and after getting a reply from him explaining that
2206 he was no longer interested in the project, I asked if I could take
2207 over. And yesterday, I became project admin.
</p
>
2209 <p
>I
've been in touch with a Gentoo developer and the Debian
2210 maintainer interested in joining forces to maintain the upstream
2211 project, and I hope we can get a new release out fairly quickly,
2212 collecting the patches spread around on the internet into on place.
2213 I
've added the relevant Debian patches to the freshly created git
2214 repository, and expect the Gentoo patches to make it too. If you got
2215 a DVD collection and care about command line tools, check out
2216 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2217 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2218 list
</a
>. :)
</p
>
2223 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2224 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2226 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2227 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2228 a lot quicker. When we install more than
2000 packages in
2229 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2230 tasksel in the installer, unpacking the binary packages take forever.
2231 A part of the slow I/O issue was discussed in
2232 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2233 much file system sync-ing done by dpkg, which is the package
2234 responsible for unpacking the binary packages. Other parts (like code
2235 executed by postinst scripts) might also sync to disk during
2236 installation. All this sync-ing to disk do not really make sense to
2237 me. If the machine crash half-way through, I start over, I do not try
2238 to salvage the half installed system. So the failure sync-ing is
2239 supposed to protect against, hardware or system crash, is not really
2240 relevant while the installer is running.
</p
>
2242 <p
>A few days ago, I thought of a way to get rid of all the file
2243 system sync()-ing in a fairly non-intrusive way, without the need to
2244 change the code in several packages. The idea is not new, but I have
2245 not heard anyone propose the approach using dpkg-divert before. It
2246 depend on the small and clever package
2247 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2248 uses LD_PRELOAD to replace the system functions for syncing data to
2249 disk with functions doing nothing, thus allowing programs to live
2250 dangerous while speeding up disk I/O significantly. Instead of
2251 modifying the implementation of dpkg, apt and tasksel (which are the
2252 packages responsible for selecting, fetching and installing packages),
2253 it occurred to me that we could just divert the programs away, replace
2254 them with a simple shell wrapper calling
2255 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2256 Two days ago I decided to test the idea, and wrapped up a simple
2257 implementation for the Debian Edu udeb.
</p
>
2259 <p
>The effect was stunning. In my first test it reduced the running
2260 time of the pkgsel step (installing tasks) from
64 to less than
44
2261 minutes (
20 minutes shaved off the installation) on an old Dell
2262 Latitude D505 machine. I am not quite sure what the optimised time
2263 would have been, as I messed up the testing a bit, causing the debconf
2264 priority to get low enough for two questions to pop up during
2265 installation. As soon as I saw the questions I moved the installation
2266 along, but do not know how long the question were holding up the
2267 installation. I did some more measurements using Debian Edu Jessie,
2268 and got these results. The time measured is the time stamp in
2269 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2270 "pkgsel: finishing up
" lines, if you want to do the same measurement
2271 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2272 timing thus do not depend on how quickly the user handle the tasksel
2275 <p
><table
>
2278 <th
>Machine/setup
</th
>
2279 <th
>Original tasksel
</th
>
2280 <th
>Optimised tasksel
</th
>
2281 <th
>Reduction
</th
>
2285 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2286 <td
>64 min (
07:
46-
08:
50)
</td
>
2287 <td
><44 min (
11:
27-
12:
11)
</td
>
2288 <td
>>20 min
18%
</td
>
2292 <td
>Latitude D505 Roaming LXDE
</td
>
2293 <td
>57 min (
08:
48-
09:
45)
</td
>
2294 <td
>34 min (
07:
43-
08:
17)
</td
>
2295 <td
>23 min
40%
</td
>
2299 <td
>Latitude D505 Minimal
</td
>
2300 <td
>22 min (
10:
37-
10:
59)
</td
>
2301 <td
>11 min (
11:
16-
11:
27)
</td
>
2302 <td
>11 min
50%
</td
>
2306 <td
>Thinkpad X200 Minimal
</td
>
2307 <td
>6 min (
08:
19-
08:
25)
</td
>
2308 <td
>4 min (
08:
04-
08:
08)
</td
>
2309 <td
>2 min
33%
</td
>
2313 <td
>Thinkpad X200 Roaming KDE
</td
>
2314 <td
>19 min (
09:
21-
09:
40)
</td
>
2315 <td
>15 min (
10:
25-
10:
40)
</td
>
2316 <td
>4 min
21%
</td
>
2319 </table
></p
>
2321 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2322 time is spent downloading packages. The connection to the Internet
2323 was
100Mbit/s during testing, so downloading should not be a
2324 significant factor in the measurement. Download typically took a few
2325 seconds to a few minutes, depending on the amount of packages being
2326 installed.
</p
>
2328 <p
>The speedup is implemented by using two hooks in
2329 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2330 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2331 finish-install.d hook to remove the divert at the end of the
2332 installation. I picked the pre-pkgsel.d hook instead of the
2333 post-base-installer.d hook because I test using an ISO without the
2334 eatmydata package included, and the post-base-installer.d hook in
2335 Debian Edu can only operate on packages included in the ISO. The
2336 negative effect of this is that I am unable to activate this
2337 optimization for the kernel installation step in d-i. If the code is
2338 moved to the post-base-installer.d hook, the speedup would be larger
2339 for the entire installation.
</p
>
2341 <p
>I
've implemented this in the
2342 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2343 git repository, and plan to provide the optimization as part of the
2344 Debian Edu installation. If you want to test this yourself, you can
2345 create two files in the installer (or in an udeb). One shell script
2346 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2348 <p
><blockquote
><pre
>
2351 . /usr/share/debconf/confmodule
2353 logger -t my-pkgsel
"info: $*
"
2356 logger -t my-pkgsel
"error: $*
"
2358 override_install() {
2359 apt-install eatmydata || true
2360 if [ -x /target/usr/bin/eatmydata ] ; then
2361 for bin in dpkg apt-get aptitude tasksel ; do
2363 # Test that the file exist and have not been diverted already.
2364 if [ -f /target$file ] ; then
2365 info
"diverting $file using eatmydata
"
2366 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2367 > /target$file.edu
2368 chmod
755 /target$file.edu
2369 in-target dpkg-divert --package debian-edu-config \
2370 --rename --quiet --add $file
2371 ln -sf ./$bin.edu /target$file
2373 error
"unable to divert $file, as it is missing.
"
2377 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2382 </pre
></blockquote
></p
>
2384 <p
>To clean up, another shell script should go into
2385 /usr/lib/finish-install.d/ with code like this:
2387 <p
><blockquote
><pre
>
2389 . /usr/share/debconf/confmodule
2391 logger -t my-finish-install
"error: $@
"
2393 remove_install_override() {
2394 for bin in dpkg apt-get aptitude tasksel ; do
2396 if [ -x /target$file.edu ] ; then
2398 in-target dpkg-divert --package debian-edu-config \
2399 --rename --quiet --remove $file
2402 error
"Missing divert for $file.
"
2405 sync # Flush file buffers before continuing
2408 remove_install_override
2409 </pre
></blockquote
></p
>
2411 <p
>In Debian Edu, I placed both code fragments in a separate script
2412 edu-eatmydata-install and call it from the pre-pkgsel.d and
2413 finish-install.d scripts.
</p
>
2415 <p
>By now you might ask if this change should get into the normal
2416 Debian installer too? I suspect it should, but am not sure the
2417 current debian-installer coordinators find it useful enough. It also
2418 depend on the side effects of the change. I
'm not aware of any, but I
2419 guess we will see if the change is safe after some more testing.
2420 Perhaps there is some package in Debian depending on sync() and
2421 fsync() having effect? Perhaps it should go into its own udeb, to
2422 allow those of us wanting to enable it to do so without affecting
2425 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2426 will break installation of all programs using gnutls because of
2427 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2428 eatmydata package in Debian will solve it.
</p
>
2430 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2431 the optimization work again. And I have discovered that the
2432 dpkg-divert trick is not really needed and implemented a slightly
2433 simpler approach as part of the debian-edu-install package. See
2434 tools/edu-eatmydata-install in the source package.
</p
>
2436 <p
>Update
2014-
11-
11: Unfortunately, a new
2437 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2438 triggering on i386 made it into testing, and broke this installation
2439 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2440 request
768893</a
> is accepted, it should be working again.
</p
>
2445 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2446 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2447 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2448 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2449 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2450 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2451 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2452 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2453 learn that there is a large set of publicly available key servers to
2454 use when looking for peoples public key. So far I have used
2455 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2456 were misbehaving, but those days are ended. The servers I have used
2457 up until yesterday have been slow and some times unavailable. I hope
2458 those problems are gone now.
</p
>
2460 <p
>Behind the round robin DNS entry of the
2461 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2462 there is a pool of more than
100 keyservers which are checked every
2463 day to ensure they are well connected and up to date. It must be
2464 better than what I have used so far. :)
</p
>
2466 <p
>Yesterdays speaker told me that the service is the default
2467 keyserver provided by the default configuration in GnuPG, but this do
2468 not seem to be used in Debian. Perhaps it should?
</p
>
2470 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2473 <p
><blockquote
><pre
>
2474 keyserver pool.sks-keyservers.net
2475 </pre
></blockquote
></p
>
2477 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2478 entries in DNS. Just for fun, I did just that at work, so now every
2479 user of GnuPG at the University of Oslo should find a OpenGPG
2480 keyserver automatically should their need it:
</p
>
2482 <p
><blockquote
><pre
>
2483 % host -t srv _pgpkey-http._tcp.uio.no
2484 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2486 </pre
></blockquote
></p
>
2488 <p
>Now if only
2489 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2490 HKP lookup protocol
</a
> supported finding signature paths, I would be
2491 very happy. It can look up a given key or search for a user ID, but I
2492 normally do not want that, but to find a trust path from my key to
2493 another key. Given a user ID or key ID, I would like to find (and
2494 download) the keys representing a signature path from my key to the
2495 key in question, to be able to get a trust path between the two keys.
2496 This is as far as I can tell not possible today. Perhaps something
2497 for a future version of the protocol?
</p
>
2502 <title>From English wiki to translated PDF and epub via Docbook
</title>
2503 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2504 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2505 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2506 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2507 project
</a
> provide an instruction manual for teachers, system
2508 administrators and other users that contain useful tips for setting up
2509 and maintaining a Debian Edu installation. This text is about how the
2510 text processing of this manual is handled in the project.
</p
>
2512 <p
>One goal of the project is to provide information in the native
2513 language of its users, and for this we need to handle translations.
2514 But we also want to make sure each language contain the same
2515 information, so for this we need a good way to keep the translations
2516 in sync. And we want it to be easy for our users to improve the
2517 documentation, avoiding the need to learn special formats or tools to
2518 contribute, and the obvious way to do this is to make it possible to
2519 edit the documentation using a web browser. We also want it to be
2520 easy for translators to keep the translation up to date, and give them
2521 help in figuring out what need to be translated. Here is the list of
2522 tools and the process we have found trying to reach all these
2525 <p
>We maintain the authoritative source of our manual in the
2526 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2527 wiki
</a
>, as several wiki pages written in English. It consist of one
2528 front page with references to the different chapters, several pages
2529 for each chapter, and finally one
"collection page
" gluing all the
2530 chapters together into one large web page (aka
2531 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2532 AllInOne page
</a
>). The AllInOne page is the one used for further
2533 processing and translations. Thanks to the fact that the
2534 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2535 wiki.debian.org support exporting pages in
2536 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2537 the list of pages to export using the raw version of the AllInOne
2538 page, loop over each of them to generate a Docbook XML version of the
2539 manual. This process also download images and transform image
2540 references to use the locally downloaded images. The generated
2541 Docbook XML files are slightly broken, so some post-processing is done
2542 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2543 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2544 a handfull of images. The XML file can now be used to generate PDF, HTML
2545 and epub versions of the English manual. This is the basic step of
2546 our process, making PDF (using dblatex), HTML (using xsltproc) and
2547 epub (using dbtoepub) version from Docbook XML, and the resulting files
2548 are placed in the debian-edu-doc-en binary package.
</p
>
2550 <p
>But English documentation is not enough for us. We want translated
2551 documentation too, and we want to make it easy for translators to
2552 track the English original. For this we use the
2553 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2554 which allow us to transform the English Docbook XML file into a
2555 translation file (a .pot file), usable with the normal gettext based
2556 translation tools used by those translating free software. The pot
2557 file is used to create and maintain translation files (several .po
2558 files), which the translations update with the native language
2559 translations of all titles, paragraphs and blocks of text in the
2560 original. The next step is combining the original English Docbook XML
2561 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2562 create a translated Docbook XML file (in this case
2563 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2564 translated, if the translation is not complete) Docbook XML file can
2565 then be used like the original to create a PDF, HTML and epub version
2566 of the documentation.
</p
>
2568 <p
>The translators use different tools to edit the .po files. We
2570 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2571 while some use emacs and vi, others can use web based editors like
2572 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2573 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2574 is where the .po file end up, in our git repository. Updated
2575 translations can either be committed directly to git, or submitted as
2576 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2577 against the debian-edu-doc package
</a
>.
</p
>
2579 <p
>One challenge is images, which both might need to be translated (if
2580 they show translated user applications), and are needed in different
2581 formats when creating PDF and HTML versions (epub is a HTML version in
2582 this regard). For this we transform the original PNG images to the
2583 needed density and format during build, and have a way to provide
2584 translated images by storing translated versions in
2585 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2586 package maintainers know more.
</p
>
2588 <p
>If you wonder what the result look like, we provide
2589 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2590 of the documentation packages on the web
</a
>. See for example the
2591 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2592 PDF version
</a
> or the
2593 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2594 HTML version
</a
>. We do not yet build the epub version by default,
2595 but perhaps it will be done in the future.
</p
>
2597 <p
>To learn more, check out
2598 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2599 debian-edu-doc package
</a
>,
2600 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2601 manual on the wiki
</a
> and
2602 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2603 translation instructions
</a
> in the manual.
</p
>
2608 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2609 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2610 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2611 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2612 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2613 related packages relevant for the computer installed automatically.
2614 So I implemented one, using
2615 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2616 package
</a
>. To use it, install the tasksel and isenkram packages and
2617 run tasksel as user root. You should be presented with a new option,
2618 "Hardware specific packages (autodetected by isenkram)
". When you
2619 select it, tasksel will install the packages isenkram claim is fit for
2620 the current hardware, hot pluggable or not.
<p
>
2622 <p
>The implementation is in two files, one is the tasksel menu entry
2623 description, and the other is the script used to extract the list of
2624 packages to install. The first part is in
2625 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2628 <p
><blockquote
><pre
>
2631 Description: Hardware specific packages (autodetected by isenkram)
2632 Based on the detected hardware various hardware specific packages are
2634 Test-new-install: mark show
2636 Packages: for-current-hardware
2637 </pre
></blockquote
></p
>
2639 <p
>The second part is in
2640 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2643 <p
><blockquote
><pre
>
2648 isenkram-autoinstall-firmware -l
2650 </pre
></blockquote
></p
>
2652 <p
>All in all, a very short and simple implementation making it
2653 trivial to install the hardware dependent package we all may want to
2654 have installed on our machines. I
've not been able to find a way to
2655 get tasksel to tell you exactly which packages it plan to install
2656 before doing the installation. So if you are curious or careful,
2657 check the output from the isenkram-* command line tools first.
</p
>
2659 <p
>The information about which packages are handling which hardware is
2660 fetched either from the isenkram package itself in
2661 /usr/share/isenkram/, from git.debian.org or from the APT package
2662 database (using the Modaliases header). The APT package database
2663 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2664 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2665 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2666 the python-apt code (bug
2667 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2668 workaround I was able to get rid of the file descriptor leak and
2669 reduce the memory leak from ~
30 MiB per hardware detection down to
2670 around
2 MiB per hardware detection. It should make the desktop
2671 daemon a lot more useful. The fix is in version
0.7 uploaded to
2672 unstable today.
</p
>
2674 <p
>I believe the current way of mapping hardware to packages in
2675 Isenkram is is a good draft, but in the future I expect isenkram to
2676 use the AppStream data source for this. A proposal for getting proper
2677 AppStream support into Debian is floating around as
2678 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2679 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2680 project
</a
> will take place this summer to improve the situation. I
2681 look forward to seeing the result, and welcome patches for isenkram to
2682 start using the information when it is ready.
</p
>
2684 <p
>If you want your package to map to some specific hardware, either
2685 add a
"Xb-Modaliases
" header to your control file like I did in
2686 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2687 package
</a
> or submit a bug report with the details to the isenkram
2689 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2690 blog posts tagged isenkram
</a
> for details on the notation. I expect
2691 the information will be migrated to AppStream eventually, but for the
2692 moment I got no better place to store it.
</p
>
2697 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2698 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2700 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2701 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2702 project
</a
> is working on providing the software and hardware to make
2703 it easy for non-technical people to host their data and communication
2704 at home, and being able to communicate with their friends and family
2705 encrypted and away from prying eyes. It is still going strong, and
2706 today a major mile stone was reached.
</p
>
2708 <p
>Today, the last of the packages currently used by the project to
2709 created the system images were accepted into Debian Unstable. It was
2710 the freedombox-setup package, which is used to configure the images
2711 during build and on the first boot. Now all one need to get going is
2712 the build code from the freedom-maker git repository and packages from
2713 Debian. And once the freedombox-setup package enter testing, we can
2714 build everything directly from Debian. :)
</p
>
2716 <p
>Some key packages used by Freedombox are
2717 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2718 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2719 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2720 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2721 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2722 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2723 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2724 are plans to integrate more packages into the setup. User
2725 documentation is maintained on the Debian wiki. Please
2726 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2727 the manual
</a
> and help us improve it.
</p
>
2729 <p
>To test for yourself and create boot images with the FreedomBox
2730 setup, run this on a Debian machine using a user with sudo rights to
2731 become root:
</p
>
2733 <p
><pre
>
2734 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2735 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2737 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2739 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2740 </pre
></p
>
2742 <p
>Root access is needed to run debootstrap and mount loopback
2743 devices. See the README in the freedom-maker git repo for more
2744 details on the build. If you do not want all three images, trim the
2745 make line. Note that the virtualbox-image target is not really
2746 virtualbox specific. It create a x86 image usable in kvm, qemu,
2747 vmware and any other x86 virtual machine environment. You might need
2748 the version of vmdebootstrap in Jessie to get the build working, as it
2749 include fixes for a race condition with kpartx.
</p
>
2751 <p
>If you instead want to install using a Debian CD and the preseed
2752 method, boot a Debian Wheezy ISO and use this boot argument to load
2753 the preseed values:
</p
>
2755 <p
><pre
>
2756 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2757 </pre
></p
>
2759 <p
>I have not tested it myself the last few weeks, so I do not know if
2760 it still work.
</p
>
2762 <p
>If you wonder how to help, one task you could look at is using
2763 systemd as the boot system. It will become the default for Linux in
2764 Jessie, so we need to make sure it is usable on the Freedombox. I did
2765 a simple test a few weeks ago, and noticed dnsmasq failed to start
2766 during boot when using systemd. I suspect there are other problems
2767 too. :) To detect problems, there is a test suite included, which can
2768 be run from the plinth web interface.
</p
>
2770 <p
>Give it a go and let us know how it goes on the mailing list, and help
2771 us get the new release published. :) Please join us on
2772 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2773 irc.debian.org)
</a
> and
2774 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2775 mailing list
</a
> if you want to help make this vision come true.
</p
>
2780 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2781 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2783 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2784 <description><p
>For a while now, I have been looking for a sensible offsite backup
2785 solution for use at home. My requirements are simple, it must be
2786 cheap and locally encrypted (in other words, I keep the encryption
2787 keys, the storage provider do not have access to my private files).
2788 One idea me and my friends had many years ago, before the cloud
2789 storage providers showed up, was to use Google mail as storage,
2790 writing a Linux block device storing blocks as emails in the mail
2791 service provided by Google, and thus get heaps of free space. On top
2792 of this one can add encryption, RAID and volume management to have
2793 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2794 I never found time to implement such system. But the last few weeks I
2795 have looked at a system called
2796 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2797 mounted network backed file system with the features I need.
</p
>
2799 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2800 handling several different storage providers, any with Amazon S3,
2801 Google Drive or OpenStack API. There are heaps of such storage
2802 providers. S3QL can also use a local directory as storage, which
2803 combined with sshfs allow for file storage on any ssh server. S3QL
2804 include support for encryption, compression, de-duplication, snapshots
2805 and immutable file systems, allowing me to mount the remote storage as
2806 a local mount point, look at and use the files as if they were local,
2807 while the content is stored in the cloud as well. This allow me to
2808 have a backup that should survive fire. The file system can not be
2809 shared between several machines at the same time, as only one can
2810 mount it at the time, but any machine with the encryption key and
2811 access to the storage service can mount it if it is unmounted.
</p
>
2813 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2814 package is included already. So to get started, run
<tt
>apt-get
2815 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2816 Greenqloud, after reading their nice recipe on
2817 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2818 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2819 in Iceland more than those in USA when it come to keeping my personal
2820 data safe and private, and thus would rather spend money on a company
2821 in Iceland. Another nice recipe is available from the article
2822 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2823 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2824 Admin magazine. When the provider is picked, figure out how to get
2825 the API key needed to connect to the storage API. With Greencloud,
2826 the key did not show up until I had added payment details to my
2829 <p
>Armed with the API access details, it is time to create the file
2830 system. First, create a new bucket in the cloud. This bucket is the
2831 file system storage area. I picked a bucket name reflecting the
2832 machine that was going to store data there, but any name will do.
2833 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2834 the API login and password, and a locally created password. Store it
2835 all in ~root/.s3ql/authinfo2 like this:
2837 <p
><blockquote
><pre
>
2839 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2840 backend-login: API-login
2841 backend-password: API-password
2842 fs-passphrase: local-password
2843 </pre
></blockquote
></p
>
2845 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2846 but any sensible way to create a fairly random password should do it.
2847 Armed with these details, it is now time to run mkfs, entering the API
2848 details and password to create it:
</p
>
2850 <p
><blockquote
><pre
>
2851 # mkdir -m
700 /var/lib/s3ql-cache
2852 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2853 --ssl s3c://s.greenqloud.com:
443/bucket-name
2854 Enter backend login:
2855 Enter backend password:
2856 Before using S3QL, make sure to read the user
's guide, especially
2857 the
'Important Rules to Avoid Loosing Data
' section.
2858 Enter encryption password:
2859 Confirm encryption password:
2860 Generating random encryption key...
2861 Creating metadata tables...
2871 Compressing and uploading metadata...
2872 Wrote
0.00 MB of compressed metadata.
2873 #
</pre
></blockquote
></p
>
2875 <p
>The next step is mounting the file system to make the storage available.
2877 <p
><blockquote
><pre
>
2878 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2879 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2880 Using
4 upload threads.
2881 Downloading and decompressing metadata...
2891 Mounting filesystem...
2893 Filesystem Size Used Avail Use% Mounted on
2894 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2896 </pre
></blockquote
></p
>
2898 <p
>The file system is now ready for use. I use rsync to store my
2899 backups in it, and as the metadata used by rsync is downloaded at
2900 mount time, no network traffic (and storage cost) is triggered by
2901 running rsync. To unmount, one should not use the normal umount
2902 command, as this will not flush the cache to the cloud storage, but
2903 instead running the umount.s3ql command like this:
2905 <p
><blockquote
><pre
>
2908 </pre
></blockquote
></p
>
2910 <p
>There is a fsck command available to check the file system and
2911 correct any problems detected. This can be used if the local server
2912 crashes while the file system is mounted, to reset the
"already
2913 mounted
" flag. This is what it look like when processing a working
2914 file system:
</p
>
2916 <p
><blockquote
><pre
>
2917 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2918 Using cached metadata.
2919 File system seems clean, checking anyway.
2920 Checking DB integrity...
2921 Creating temporary extra indices...
2922 Checking lost+found...
2923 Checking cached objects...
2924 Checking names (refcounts)...
2925 Checking contents (names)...
2926 Checking contents (inodes)...
2927 Checking contents (parent inodes)...
2928 Checking objects (reference counts)...
2929 Checking objects (backend)...
2930 ..processed
5000 objects so far..
2931 ..processed
10000 objects so far..
2932 ..processed
15000 objects so far..
2933 Checking objects (sizes)...
2934 Checking blocks (referenced objects)...
2935 Checking blocks (refcounts)...
2936 Checking inode-block mapping (blocks)...
2937 Checking inode-block mapping (inodes)...
2938 Checking inodes (refcounts)...
2939 Checking inodes (sizes)...
2940 Checking extended attributes (names)...
2941 Checking extended attributes (inodes)...
2942 Checking symlinks (inodes)...
2943 Checking directory reachability...
2944 Checking unix conventions...
2945 Checking referential integrity...
2946 Dropping temporary indices...
2947 Backing up old metadata...
2957 Compressing and uploading metadata...
2958 Wrote
0.89 MB of compressed metadata.
2960 </pre
></blockquote
></p
>
2962 <p
>Thanks to the cache, working on files that fit in the cache is very
2963 quick, about the same speed as local file access. Uploading large
2964 amount of data is to me limited by the bandwidth out of and into my
2965 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2966 which is very close to my upload speed, and downloading the same
2967 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2968 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2969 network, not the file system code. I do not know what a good cache
2970 size would be, but suspect that the cache should e larger than your
2971 working set.
</p
>
2973 <p
>I mentioned that only one machine can mount the file system at the
2974 time. If another machine try, it is told that the file system is
2977 <p
><blockquote
><pre
>
2978 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2979 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2980 Using
8 upload threads.
2981 Backend reports that fs is still mounted elsewhere, aborting.
2983 </pre
></blockquote
></p
>
2985 <p
>The file content is uploaded when the cache is full, while the
2986 metadata is uploaded once every
24 hour by default. To ensure the
2987 file system content is flushed to the cloud, one can either umount the
2988 file system, or ask S3QL to flush the cache and metadata using
2991 <p
><blockquote
><pre
>
2992 # s3qlctrl upload-meta /s3ql
2993 # s3qlctrl flushcache /s3ql
2995 </pre
></blockquote
></p
>
2997 <p
>If you are curious about how much space your data uses in the
2998 cloud, and how much compression and deduplication cut down on the
2999 storage usage, you can use s3qlstat on the mounted file system to get
3002 <p
><blockquote
><pre
>
3004 Directory entries:
9141
3007 Total data size:
22049.38 MB
3008 After de-duplication:
21955.46 MB (
99.57% of total)
3009 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3010 Database size:
2.39 MB (uncompressed)
3011 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3013 </pre
></blockquote
></p
>
3015 <p
>I mentioned earlier that there are several possible suppliers of
3016 storage. I did not try to locate them all, but am aware of at least
3017 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3018 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3019 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3020 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3021 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3022 accept payment in Bitcoin. Pick one that suit your need. Some of
3023 them provide several GiB of free storage, but the prize models are
3024 quite different and you will have to figure out what suits you
3027 <p
>While researching this blog post, I had a look at research papers
3028 and posters discussing the S3QL file system. There are several, which
3029 told me that the file system is getting a critical check by the
3030 science community and increased my confidence in using it. One nice
3032 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3033 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3034 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3035 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3036 and Pamela Smith. Please have a look.
</p
>
3038 <p
>Given my problems with different file systems earlier, I decided to
3039 check out the mounted S3QL file system to see if it would be usable as
3040 a home directory (in other word, that it provided POSIX semantics when
3041 it come to locking and umask handling etc). Running
3042 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3043 test code to check file system semantics
</a
>, I was happy to discover that
3044 no error was found. So the file system can be used for home
3045 directories, if one chooses to do so.
</p
>
3047 <p
>If you do not want a locally file system, and want something that
3048 work without the Linux fuse file system, I would like to mention the
3049 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3050 provide locally encrypted backup using a command line client. It have
3051 a nicer access control system, where one can split out read and write
3052 access, allowing some systems to write to the backup and others to
3053 only read from it.
</p
>
3055 <p
>As usual, if you use Bitcoin and want to show your support of my
3056 activities, please send Bitcoin donations to my address
3057 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3062 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3063 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3065 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3066 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3067 project
</a
> is working on providing the software and hardware for
3068 making it easy for non-technical people to host their data and
3069 communication at home, and being able to communicate with their
3070 friends and family encrypted and away from prying eyes. It has been
3071 going on for a while, and is slowly progressing towards a new test
3072 release (
0.2).
</p
>
3074 <p
>And what day could be better than the Pi day to announce that the
3075 new version will provide
"hard drive
" / SD card / USB stick images for
3076 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3077 system), and can also be installed using a Debian installer preseed
3078 file. The Debian based Freedombox is now based on Debian Jessie,
3079 where most of the needed packages used are already present. Only one,
3080 the freedombox-setup package, is missing. To try to build your own
3081 boot image to test the current status, fetch the freedom-maker scripts
3083 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3084 with a user with sudo access to become root:
3087 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3089 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3090 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3092 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3095 <p
>Root access is needed to run debootstrap and mount loopback
3096 devices. See the README for more details on the build. If you do not
3097 want all three images, trim the make line. But note that thanks to
<a
3098 href=
"https://bugs.debian.org/
741407">a race condition in
3099 vmdebootstrap
</a
>, the build might fail without the patch to the
3100 kpartx call.
</p
>
3102 <p
>If you instead want to install using a Debian CD and the preseed
3103 method, boot a Debian Wheezy ISO and use this boot argument to load
3104 the preseed values:
</p
>
3107 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3110 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3111 recently introduced bug in apt in Jessie
</a
>, the installer will
3112 currently hang while setting up APT sources. Killing the
3113 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3114 installation will get the installation going. This affect all
3115 installations in Jessie, and I expect it will be fixed soon.
</p
>
3117 <p
>Give it a go and let us know how it goes on the mailing list, and help
3118 us get the new release published. :) Please join us on
3119 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3120 irc.debian.org)
</a
> and
3121 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3122 mailing list
</a
> if you want to help make this vision come true.
</p
>
3127 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3128 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3130 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3131 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3132 innetgr tools, because I needed them in
3133 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3134 ng-utils, and it has served me well. I placed the project under the
3135 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3136 repository. But many years ago, the CVS repository was dropped (lost,
3137 not migrated to new hardware, not sure), and the project have lacked a
3138 proper home since then.
</p
>
3140 <p
>Last summer, I had a look at the package and made a new release
3141 fixing a irritating crash bug, but was unable to store the changes in
3142 a proper source control system. I applied for a project on
3143 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3144 to follow up on it. Until today. :)
</p
>
3146 <p
>After many hours of cleaning and migration, the ng-utils project
3147 now have a new home, and a git repository with the highlight of the
3148 history of the project. I published all release tarballs and imported
3149 them into the git repository. As the project is really stable and not
3150 expected to gain new features any time soon, I decided to make a new
3151 release and call it
1.0. Visit the new project home on
3152 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3153 if you want to check it out. The new version is also uploaded into
3154 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3159 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3160 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3161 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3162 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3163 <description><p
>A few days ago I decided to try to help the Hurd people to get
3164 their changes into sysvinit, to allow them to use the normal sysvinit
3165 boot system instead of their old one. This follow up on the
3166 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3167 Google Summer of Code work
</a
> done last summer by Justus Winter to
3168 get Debian on Hurd working more like Debian on Linux. To get started,
3169 I downloaded a prebuilt hard disk image from
3170 <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
>,
3171 and started it using virt-manager.
</p
>
3173 <p
>The first think I had to do after logging in (root without any
3174 password) was to get the network operational. I followed
3175 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3176 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3177 commands as root to get the machine to accept a IP address from the
3178 kvm internal DHCP server:
</p
>
3180 <p
><blockquote
><pre
>
3181 settrans -fgap /dev/netdde /hurd/netdde
3182 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3183 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3185 </pre
></blockquote
></p
>
3187 <p
>After this, the machine had internet connectivity, and I could
3188 upgrade it and install the sysvinit packages from experimental and
3189 enable it as the default boot system in Hurd.
</p
>
3191 <p
>But before I did that, I set a password on the root user, as ssh is
3192 running on the machine it for ssh login to work a password need to be
3193 set. Also, note that a bug somewhere in openssh on Hurd block
3194 compression from working. Remember to turn that off on the client
3197 <p
>Run these commands as root to upgrade and test the new sysvinit
3200 <p
><blockquote
><pre
>
3201 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3202 deb http://http.debian.net/debian/ experimental main
3205 apt-get dist-upgrade
3206 apt-get install -t experimental initscripts sysv-rc sysvinit \
3207 sysvinit-core sysvinit-utils
3208 update-alternatives --config runsystem
3209 </pre
></blockquote
></p
>
3211 <p
>To reboot after switching boot system, you have to use
3212 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3213 yet a sysvinit process able to receive the signals from the normal
3214 'reboot
' command. After switching to sysvinit as the boot system,
3215 upgrading every package and rebooting, the network come up with DHCP
3216 after boot as it should, and the settrans/pkill hack mentioned at the
3217 start is no longer needed. But for some strange reason, there are no
3218 longer any login prompt in the virtual console, so I logged in using
3221 <p
>Note that there are some race conditions in Hurd making the boot
3222 fail some times. No idea what the cause is, but hope the Hurd porters
3223 figure it out. At least Justus said on IRC (#debian-hurd on
3224 irc.debian.org) that they are aware of the problem. A way to reduce
3225 the impact is to upgrade to the Hurd packages built by Justus by
3226 adding this repository to the machine:
</p
>
3228 <p
><blockquote
><pre
>
3229 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3230 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3232 </pre
></blockquote
></p
>
3234 <p
>At the moment the prebuilt virtual machine get some packages from
3235 http://ftp.debian-ports.org/debian, because some of the packages in
3236 unstable do not yet include the required patches that are lingering in
3237 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3239 <p
><blockquote
><pre
>
3240 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3241 i emacs - GNU Emacs editor (metapackage)
3242 i gdb - GNU Debugger
3243 i hurd-recommended - Miscellaneous translators
3244 i isc-dhcp-client - ISC DHCP client
3245 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3246 i libc-bin - Embedded GNU C Library: Binaries
3247 i libc-dev-bin - Embedded GNU C Library: Development binaries
3248 i libc0.3 - Embedded GNU C Library: Shared libraries
3249 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3250 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3251 i multiarch-support - Transitional package to ensure multiarch compatibilit
3252 i A x11-common - X Window System (X.Org) infrastructure
3253 i xorg - X.Org X Window System
3254 i A xserver-xorg - X.Org X server
3255 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3257 </pre
></blockquote
></p
>
3259 <p
>All in all, testing hurd has been an interesting experience. :)
3260 X.org did not work out of the box and I never took the time to follow
3261 the porters instructions to fix it. This time I was interested in the
3262 command line stuff.
<p
>
3267 <title>New chrpath release
0.16</title>
3268 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3270 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3271 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3272 find problems in C, C++ and Java code using static source code
3273 analysis. It can detect a lot of different problems, and is very
3274 useful to find memory and locking bugs in the error handling part of
3275 the source. The company behind it provide
3276 <a href=
"https://scan.coverity.com/
">check of free software projects as
3277 a community service
</a
>, and many hundred free software projects are
3278 already checked. A few days ago I decided to have a closer look at
3279 the Coverity system, and discovered that the
3280 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3281 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3282 projects I am involved with was already registered. But these are
3283 fairly big, and I would also like to have a small and easy project to
3284 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3285 checking of the chrpath project
</a
>. It was
3286 added to the checker and discovered seven potential defects. Six of
3287 these were real, mostly resource
"leak
" when the program detected an
3288 error. Nothing serious, as the resources would be released a fraction
3289 of a second later when the program exited because of the error, but it
3290 is nice to do it right in case the source of the program some time in
3291 the future end up in a library. Having fixed all defects and added
3292 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3293 mailing list for the chrpath developers
</a
>, I decided it was time to
3294 publish a new release. These are the release notes:
</p
>
3296 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3300 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3301 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3302 <li
>Mention new project mailing list in the documentation.
</li
>
3307 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3308 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3309 project if something is wrong with the new release. The test suite
3310 did not discover any old errors, so if you find a new one, please also
3311 include a test suite check.
</p
>
3316 <title>New chrpath release
0.15</title>
3317 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3318 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3319 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3320 <description><p
>After many years break from the package and a vain hope that
3321 development would be continued by someone else, I finally pulled my
3322 acts together this morning and wrapped up a new release of chrpath,
3323 the command line tool to modify the rpath and runpath of already
3324 compiled ELF programs. The update was triggered by the persistence of
3325 Isha Vishnoi at IBM, which needed a new config.guess file to get
3326 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3327 is working on. I checked the
3328 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3329 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3330 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3331 packages for interesting patches (failed to find the source from
3332 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3333 These are the release notes:
</p
>
3335 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3339 <li
>Updated config.sub and config.guess from the GNU project to work
3340 with newer architectures. Thanks to isha vishnoi for the heads
3343 <li
>Updated README with current URLs.
</li
>
3345 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3346 Matthias Klose.
</li
>
3348 <li
>Added missing help for -k|--keepgoing option, using patch by
3349 Petr Machata found in Fedora.
</li
>
3351 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3352 .dynamic is a NULL terminated string. Based on patch found in
3353 Fedora credited Axel Thimm and Christian Krause.
</li
>
3358 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3359 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3360 project if something is wrong with the new release. The test suite
3361 did not discover any old errors, so if you find a new one, please also
3362 include a testsuite check.
</p
>
3367 <title>Debian init.d boot script example for rsyslog
</title>
3368 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3370 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3371 <description><p
>If one of the points of switching to a new init system in Debian is
3372 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3373 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3374 init.d scripts at all. Here is an example init.d script, ie a rewrite
3375 of /etc/init.d/rsyslog:
</p
>
3377 <p
><pre
>
3378 #!/lib/init/init-d-script
3381 # Required-Start: $remote_fs $time
3382 # Required-Stop: umountnfs $time
3383 # X-Stop-After: sendsigs
3384 # Default-Start:
2 3 4 5
3385 # Default-Stop:
0 1 6
3386 # Short-Description: enhanced syslogd
3387 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3388 # It is quite compatible to stock sysklogd and can be
3389 # used as a drop-in replacement.
3391 DESC=
"enhanced syslogd
"
3392 DAEMON=/usr/sbin/rsyslogd
3393 </pre
></p
>
3395 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3396 script was
137 lines, and the above is just
15 lines, most of it meta
3397 info/comments.
</p
>
3399 <p
>How to do this, you ask? Well, one create a new script
3400 /lib/init/init-d-script looking something like this:
3402 <p
><pre
>
3405 # Define LSB log_* functions.
3406 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3407 # and status_of_proc is working.
3408 . /lib/lsb/init-functions
3411 # Function that starts the daemon/service
3417 #
0 if daemon has been started
3418 #
1 if daemon was already running
3419 #
2 if daemon could not be started
3420 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3422 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3425 # Add code here, if necessary, that waits for the process to be ready
3426 # to handle requests from services started subsequently which depend
3427 # on this one. As a last resort, sleep for some time.
3431 # Function that stops the daemon/service
3436 #
0 if daemon has been stopped
3437 #
1 if daemon was already stopped
3438 #
2 if daemon could not be stopped
3439 # other if a failure occurred
3440 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3441 RETVAL=
"$?
"
3442 [
"$RETVAL
" =
2 ]
&& return
2
3443 # Wait for children to finish too if this is a daemon that forks
3444 # and if the daemon is only ever run from this initscript.
3445 # If the above conditions are not satisfied then add some other code
3446 # that waits for the process to drop all resources that could be
3447 # needed by services started subsequently. A last resort is to
3448 # sleep for some time.
3449 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3450 [
"$?
" =
2 ]
&& return
2
3451 # Many daemons don
't delete their pidfiles when they exit.
3453 return
"$RETVAL
"
3457 # Function that sends a SIGHUP to the daemon/service
3461 # If the daemon can reload its configuration without
3462 # restarting (for example, when it is sent a SIGHUP),
3463 # then implement that here.
3465 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3470 scriptbasename=
"$(basename $
1)
"
3471 echo
"SN: $scriptbasename
"
3472 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3473 script=
"$
1"
3480 NAME=$(basename $DAEMON)
3481 PIDFILE=/var/run/$NAME.pid
3483 # Exit if the package is not installed
3484 #[ -x
"$DAEMON
" ] || exit
0
3486 # Read configuration variable file if it is present
3487 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3489 # Load the VERBOSE setting and other rcS variables
3492 case
"$
1" in
3494 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3496 case
"$?
" in
3497 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3498 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3502 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3504 case
"$?
" in
3505 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3506 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3510 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3512 #reload|force-reload)
3514 # If do_reload() is not implemented then leave this commented out
3515 # and leave
'force-reload
' as an alias for
'restart
'.
3517 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3521 restart|force-reload)
3523 # If the
"reload
" option is implemented then remove the
3524 #
'force-reload
' alias
3526 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3528 case
"$?
" in
3531 case
"$?
" in
3533 1) log_end_msg
1 ;; # Old process is still running
3534 *) log_end_msg
1 ;; # Failed to start
3544 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3550 </pre
></p
>
3552 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3553 lot. I did not really polish the approach, so it might not always
3554 work out of the box, but you get the idea. I did not try very hard to
3555 optimize it nor make it more robust either.
</p
>
3557 <p
>A better argument for switching init system in Debian than reducing
3558 the size of init scripts (which is a good thing to do anyway), is to
3559 get boot system that is able to handle the kernel events sensibly and
3560 robustly, and do not depend on the boot to run sequentially. The boot
3561 and the kernel have not behaved sequentially in years.
</p
>
3566 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3567 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3568 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3569 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3570 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3571 remote display access is the preferred solution with oVirt and RedHat
3572 Enterprise Virtualization, and I was sad to discover the other day
3573 that the browser plugin needed to use these systems seamlessly was
3574 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3575 for a package
</a
> was from
2012-
04-
10 with no progress since
3576 2013-
04-
01, so I decided to wrap up a package based on the great work
3577 from Cajus Pollmeier and put it in a collab-maint maintained git
3578 repository to get a package I could use. I would very much like
3579 others to help me maintain the package (or just take over, I do not
3580 mind), but as no-one had volunteered so far, I just uploaded it to
3581 NEW. I hope it will be available in Debian in a few days.
</p
>
3583 <p
>The source is now available from
3584 <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
>
3589 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3590 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3591 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3592 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3593 <description><p
>The
3594 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3595 program is a a very nice system to create virtual machine images. It
3596 create a image file, add a partition table, mount it and run
3597 debootstrap in the mounted directory to create a Debian system on a
3598 stick. Yesterday, I decided to try to teach it how to make images for
3599 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3600 of a plan to simplify the build system for
3601 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3602 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3603 the virtualbox images, but its current build system made multistrap
3604 based system for Dreamplug images, and it is lacking support for
3605 Raspberry Pi.
</p
>
3607 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3608 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3609 code and adjusted it to be able to build armel images on my amd64
3610 Debian laptop. I ended up giving vmdebootstrap five new options,
3611 allowing me to replicate the image creation process I use to make
3612 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3613 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3614 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3615 call debootstrap with --foreign and to copy the handler into the
3616 generated chroot before running the second stage. This allow
3617 vmdebootstrap to create armel images on an amd64 host. Next I added
3618 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3619 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3620 given file system type, allowing me to create an image with a vfat
3621 partition for the /boot/ stuff. I also added a
<tt
>--variant
3622 variant
</tt
> option to allow me to create smaller images without the
3623 Debian base system packages installed. Finally, I added an option
3624 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3625 as a boot loader. It is not needed on the Raspberry Pi and probably
3626 most other non-x86 architectures. The changes were accepted by the
3627 upstream author of vmdebootstrap yesterday and today, and is now
3629 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3630 upstream project page
</a
>.
</p
>
3632 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3633 create a small script (the customize script) to add the non-free
3634 binary blob needed to boot the Raspberry Pi and the APT source
3637 <p
><pre
>
3639 set -e # Exit on first error
3640 rootdir=
"$
1"
3641 cd
"$rootdir
"
3642 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3643 deb http://http.debian.net/debian/ jessie main contrib non-free
3645 # Install non-free binary blob needed to boot Raspberry Pi. This
3646 # install a kernel somewhere too.
3647 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3648 -O $rootdir/usr/bin/rpi-update
3649 chmod a+x $rootdir/usr/bin/rpi-update
3650 mkdir -p $rootdir/lib/modules
3651 touch $rootdir/boot/start.elf
3652 chroot $rootdir rpi-update
3653 </pre
></p
>
3655 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3656 to build the image:
</p
>
3659 sudo ./vmdebootstrap \
3662 --distribution jessie \
3663 --mirror http://http.debian.net/debian \
3672 --root-password raspberry \
3673 --hostname raspberrypi \
3674 --foreign /usr/bin/qemu-arm-static \
3675 --customize `pwd`/customize \
3677 --package git-core \
3678 --package binutils \
3679 --package ca-certificates \
3682 </pre
></p
>
3684 <p
>The list of packages being installed are the ones needed by
3685 rpi-update to make the image bootable on the Raspberry Pi, with the
3686 exception of netbase, which is needed by debootstrap to find
3687 /etc/hosts with the minbase variant. I really wish there was a way to
3688 set up an Raspberry Pi using only packages in the Debian archive, but
3689 that is not possible as far as I know, because it boots from the GPU
3690 using a non-free binary blob.
</p
>
3692 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3693 probably a few others installed. I have not checked the complete
3694 build dependency list.
</p
>
3696 <p
>The resulting image will not use the hardware floating point unit
3697 on the Raspberry PI, because the armel architecture in Debian is not
3698 optimized for that use. So the images created will be a bit slower
3699 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3704 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3705 <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>
3706 <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>
3707 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3708 <description><p
>The last few days I came across a few good causes that should get
3709 wider attention. I recommend signing and donating to each one of
3712 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3713 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3714 Women program which is a Google Summer of Code like initiative to get
3715 more women involved in free software. One debian sponsor has offered
3716 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3717 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3718 hope you will to. :)
</p
>
3720 <p
>And the Electronic Frontier Foundation just announced plans to
3721 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3722 documentaries about the excessive spying
</a
> on every Internet user that
3723 take place these days, and their need to fund the work. I
've already
3724 donated. Are you next?
</p
>
3726 <p
>For my Norwegian audience, the organisation Studentenes og
3727 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3728 statement under the heading
3729 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3730 Access
</a
> for those of us asking for more focus on open access in the
3731 Norwegian government. So far
499 signatures. I hope you will sign it
3737 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3738 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3739 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3740 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3741 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3742 project
</a
> have been going on for a while, and have presented the
3743 vision, ideas and solution several places. Here is a little
3744 collection of videos of talks and presentation of the project.
</p
>
3748 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3749 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3751 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3752 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3754 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3755 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3756 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3757 (Youtube)
</li
>
3759 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3760 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3762 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3763 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3765 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3766 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3767 York City in
2012</a
> (Youtube)
</li
>
3769 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3770 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3771 (Youtube)
</li
>
3773 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3774 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3776 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3777 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3779 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3780 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3781 2013</a
> (Youtube)
</li
>
3785 <p
>A larger list is available from
3786 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3787 Freedombox Wiki
</a
>.
</p
>
3789 <p
>On other news, I am happy to report that Freedombox based on Debian
3790 Jessie is coming along quite well, and soon both Owncloud and using
3791 Tor should be available for testers of the Freedombox solution. :) In
3792 a few weeks I hope everything needed to test it is included in Debian.
3793 The withsqlite package is already in Debian, and the plinth package is
3794 pending in NEW. The third and vital part of that puzzle is the
3795 metapackage/setup framework, which is still pending an upload. Join
3796 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3797 (#freedombox on irc.debian.org)
</a
> and
3798 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3799 mailing list
</a
> if you want to help make this vision come true.
</p
>
3804 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3805 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3806 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3807 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3808 <description><p
>I was introduced to the
3809 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3810 in
2010, when Eben Moglen presented his vision about serving the need
3811 of non-technical people to keep their personal information private and
3812 within the legal protection of their own homes. The idea is to give
3813 people back the power over their network and machines, and return
3814 Internet back to its intended peer-to-peer architecture. Instead of
3815 depending on a central service, the Freedombox will give everyone
3816 control over their own basic infrastructure.
</p
>
3818 <p
>I
've intended to join the effort since then, but other tasks have
3819 taken priority. But this summers nasty news about the misuse of trust
3820 and privilege exercised by the
"western
" intelligence gathering
3821 communities increased my eagerness to contribute to a point where I
3822 actually started working on the project a while back.
</p
>
3824 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3825 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3826 create a simple and cheap Debian based appliance that anyone can hook
3827 up in their home and get access to secure and private services and
3828 communication. The initial deployment platform have been the
3829 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3830 which is a piece of hardware I do not own. So to be able to test what
3831 the current Freedombox setup look like, I had to come up with a way to install
3832 it on some hardware I do have access to. I have rewritten the
3833 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3834 image build framework to use .deb packages instead of only copying
3835 setup into the boot images, and thanks to this rewrite I am able to
3836 set up any machine supported by Debian Wheezy as a Freedombox, using
3837 the previously mentioned deb (and a few support debs for packages
3838 missing in Debian).
</p
>
3840 <p
>The current Freedombox setup consist of a set of bootstrapping
3842 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3843 and a administrative web interface
3844 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3845 withsqlite), as well as a privacy enhancing proxy based on
3846 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3847 (freedombox-privoxy). There is also a web/javascript based XMPP
3848 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3849 trying (unsuccessfully so far) to talk to the XMPP server
3850 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3851 web interface is pluggable, and the goal is to use it to enable OpenID
3852 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3853 this is really working yet, see
3854 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3855 project TODO
</a
> for links to GIT repositories. Most of the code is
3856 on github at the moment. The HTTP proxy is operational out of the
3857 box, and the admin web interface can be used to add/remove plinth
3858 users. I
've not been able to do anything else with it so far, but
3859 know there are several branches spread around github and other places
3860 with lots of half baked features.
</p
>
3862 <p
>Anyway, if you want to have a look at the current state, the
3863 following recipes should work to give you a test machine to poke
3866 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3870 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3871 <li
>Boot from it, either as CD or USB stick.
</li
>
3872 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3873 to the Debian installer:
<p
>
3874 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3876 <li
>Answer the few language/region/password questions and pick disk to
3877 install on.
</li
>
3879 <li
>When the installation is finished and the machine have rebooted a
3880 few times, your Freedombox is ready for testing.
</li
>
3884 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3888 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3889 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3890 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3892 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3893 </pre
></li
>
3894 <li
><p
>Run this as root:
</p
>
3896 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3899 apt-get install freedombox-setup
3900 /usr/lib/freedombox/setup
3901 </pre
></li
>
3902 <li
>Reboot into your freshly created Freedombox.
</li
>
3906 <p
>You can test it on other architectures too, but because the
3907 freedombox-privoxy package is binary, it will only work as intended on
3908 the architectures where I have had time to build the binary and put it
3909 in my APT repository. But do not let this stop you. It is only a
3910 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3912 <p
>Note that by default Freedombox is a DHCP server on the
3913 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3914 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3915 disable
</tt
>" as root.
</p
>
3917 <p
>Please let me know if this works for you, or if you have any
3918 problems. We gather on the IRC channel
3919 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3920 irc.debian.org and the
3921 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3922 mailing list
</a
>.
</p
>
3924 <p
>Once you get your freedombox operational, you can visit
3925 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3926 welcome screen (dead end - do not be surprised if you are unable to
3927 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3928 to look at the rest of plinth. The default user is
'admin
' and the
3929 default password is
'secret
'.
</p
>
3934 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3935 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3937 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3938 <description><p
>Earlier, I reported about
3939 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3940 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3941 told by IBM that the original disk should be thrown away. And as
3942 there no longer was a problem if I bricked the firmware, I decided
3943 today to try to install Intel firmware to replace the Lenovo firmware
3944 currently on the disk.
</p
>
3946 <p
>I searched the Intel site for firmware, and found
3947 <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
>
3948 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3949 according to the site should contain the latest firmware for SSD
3950 disks. I inserted the broken disk in one of my spare laptops and
3951 booted the ISO from a USB stick. The disk was recognized, but the
3952 program claimed the newest firmware already were installed and refused
3953 to insert any Intel firmware. So no change, and the disk is still
3954 unable to handle write load. :( I guess the only way to get them
3955 working would be if Lenovo releases new firmware. No idea how likely
3956 that is. Anyway, just blogging about this test for completeness. I
3957 got a working Samsung disk, and see no point in spending more time on
3958 the broken disks.
</p
>
3963 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3964 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3965 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3966 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3967 <description><p
>Today I switched to
3968 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3969 new laptop
</a
>. I
've previously written about the problems I had with
3970 my new Thinkpad X230, which was delivered with an
3971 <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
3972 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3973 sustained writes. My hardware supplier have been very forthcoming in
3974 trying to find a solution, and after first trying with another
3975 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3976 disk instead to fix it once and for all. The Samsung disk survived
3977 the installation of Debian with encrypted disks (filling the disk with
3978 random data during installation killed the first two), and I thus
3979 decided to trust it with my data. I have installed it as a Debian Edu
3980 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3981 server at home using Kerberos and LDAP, and will use it as my work
3982 station from now on.
</p
>
3984 <p
>As this is a solid state disk with no moving parts, I believe the
3985 Debian Wheezy default installation need to be tuned a bit to increase
3986 performance and increase life time of the disk. The Linux kernel and
3987 user space applications do not yet adjust automatically to such
3988 environment. To make it easier for my self, I created a draft Debian
3989 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3990 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3991 for the ssd-setup package
</a
> is available from collab-maint, and it
3992 is set up to adjust the setup of the machine by just installing the
3993 package. If there is any non-SSD disk in the machine, the package
3994 will refuse to install, as I did not try to write any logic to sort
3995 file systems in SSD and non-SSD file systems.
</p
>
3997 <p
>I consider the package a draft, as I am a bit unsure how to best
3998 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3999 where I set up the machine with one large encrypted partition (in
4000 addition to /boot), put LVM on top of this and set up partitions on
4001 top of this again. See the README file in the package source for the
4002 references I used to pick the settings. At the moment these
4003 parameters are tuned:
</p
>
4007 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4008 (adding discard to /etc/crypttab)
</li
>
4010 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4011 this case a cryptsetup partition) by changing issue_discards from
4012 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4014 <li
>Set relatime as a file system option for ext3 and ext4 file
4017 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4018 /etc/fstab.
</li
>
4020 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4022 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4023 cron.daily).
</li
>
4025 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4026 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4030 <p
>During installation, I cancelled the part where the installer fill
4031 the disk with random data, as this would kill the SSD performance for
4032 little gain. My goal with the encrypted file system is to ensure
4033 those stealing my laptop end up with a brick and not a working
4034 computer. I have no hope in keeping the really resourceful people
4035 from getting the data on the disk (see
4036 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4037 Thus I concluded that adding the discard option to crypttab is the
4038 right thing to do.
</p
>
4040 <p
>I considered using the noop I/O scheduler, as several recommended
4041 it for SSD, but others recommended deadline and a benchmark I found
4042 indicated that deadline might be better for interactive use.
</p
>
4044 <p
>I also considered using the
'discard
' file system option for ext3
4045 and ext4, but read that it would give a performance hit ever time a
4046 file is removed, and thought it best to that that slowdown once a day
4047 instead of during my work.
</p
>
4049 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4050 this is already done by Debian Edu.
</p
>
4052 <p
>I have not yet started on the user space tuning. I expect
4053 iceweasel need some tuning, and perhaps other applications too, but
4054 have not yet had time to investigate those parts.
</p
>
4056 <p
>The package should work on Ubuntu too, but I have not yet tested it
4059 <p
>As for the answer to the question in the title of this blog post,
4060 as far as I know, the only solution I know about is to replace the
4061 disk. It might be possible to flash it with Intel firmware instead of
4062 the Lenovo firmware. But I have not tried and did not want to do so
4063 without approval from Lenovo as I wanted to keep the warranty on the
4064 disk until a solution was found and they wanted the broken disks
4070 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4071 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4072 <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>
4073 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4074 <description><p
>A few days ago, I wrote about
4075 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4076 problems I experienced with my new X230 and its SSD disk
</a
>, which
4077 was dying during installation because it is unable to cope with
4078 sustained write. My supplier is in contact with
4079 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4080 replacement disk to try to fix the problem. They decided to send an
4081 identical model, so my hopes for a permanent fix was slim.
</p
>
4083 <p
>Anyway, today I got the replacement disk and tried to install
4084 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4085 same firmware version as the original. This time my hope raised
4086 slightly as the installation progressed, as the original disk used to
4087 die after
4-
7% of the disk was written to, while this time it kept
4088 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4089 died again and I was back on square one. I still do not have a new
4090 laptop with a disk I can trust. I can not live with a disk that might
4091 lock up when I download a new
4092 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4093 other large files. I look forward to hearing from my supplier with
4094 the next proposal from Lenovo.
</p
>
4096 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4097 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4098 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4099 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4100 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4101 P/N
45N8295, P0C38732.
</p
>
4103 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4104 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4105 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4106 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4107 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4108 P/N
45N8295, P0C38732.
</p
>
4110 <p
>The only difference is in the first number (serial number?), ISN,
4111 SA, date and WNPP values. Mentioning all the details here in case
4112 someone is able to use the information to find a way to identify the
4113 failing disk among working ones (if any such working disk actually
4119 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4120 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4122 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4123 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4124 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4125 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4126 member assosiation NUUG
</a
> and
4127 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4128 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4129 Bitraf
</a
>.
</p
>
4131 <p
>It starts
10:
00 and continue until late evening. Everyone is
4132 welcome, and there is no fee to participate. There is on the other
4133 hand limited space, and only room for
30 people. Please put your name
4134 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4135 wiki page
</a
> if you plan to join us.
</p
>
4140 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4141 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4143 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4144 <description><p
>Half a year ago, I reported that I had to find a
4145 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4146 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4147 time to spend on it, and it took a while to find a model I believe
4148 will do the job, but two days ago the replacement finally arrived. I
4150 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4151 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4152 a roaming workstation, and it seemed to work flawlessly. But my
4153 second installation with encrypted disk was not as successful. More
4154 on that below.
</p
>
4156 <p
>I had a hard time trying to track down a good laptop, as my most
4157 important requirements (robust and with a good keyboard) are never
4158 listed in the feature list. But I did get good help from the search
4159 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4160 allowed me to limit the list of interesting laptops based on my other
4161 requirements. A bit surprising that SSD disk are not disks according
4162 to that search interface, so I had to drop specifying the number of
4163 disks from my search parameters. I also asked around among friends to
4164 get their impression on keyboards and robustness.
</p
>
4166 <p
>So the new laptop arrived, and it is quite a lot wider than the
4167 X41. I am not quite convinced about the keyboard, as it is
4168 significantly wider than my old keyboard, and I have to stretch my
4169 hand a lot more to reach the edges. But the key response is fairly
4170 good and the individual key shape is fairly easy to handle, so I hope
4171 I will get used to it. My old X40 was starting to fail, and I really
4172 needed a new laptop now. :)
</p
>
4174 <p
>Turning off the touch pad was simple. All it took was a quick
4175 visit to the BIOS during boot it disable it.
</p
>
4177 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4178 lock up during load. And this happen when installing Debian Wheezy
4179 with encrypted disk, while the disk is being filled with random data.
4180 I also tested to install Ubuntu Raring, and it happen there too if I
4181 reenable the code to fill the disk with random data (it is disabled by
4182 default in Ubuntu). And the bug with is already known. It was
4183 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4184 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4185 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4186 kernel developers as
4187 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4188 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4189 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4190 Lenovo forums, both for
4191 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4192 2012-
11-
10</a
> and for
4193 <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
4194 03-
20-
2013</a
>. The problem do not only affect installation. The
4195 reports state that the disk lock up during use if many writes are done
4196 on the disk, so it is much no use to work around the installation
4197 problem and end up with a computer that can lock up at any moment.
4199 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4200 available
</a
> that will lock up the hard drive after running a few
4201 minutes by writing to a file.
</p
>
4203 <p
>I
've contacted my supplier and asked how to handle this, and after
4204 contacting PCHELP Norway (request
01D1FDP) which handle support
4205 requests for Lenovo, his first suggestion was to upgrade the disk
4206 firmware. Unfortunately there is no newer firmware available from
4207 Lenovo, as my disk already have the most recent one (version LF1i). I
4208 hope to hear more from him today and hope the problem can be
4214 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4215 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4217 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4218 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4219 trusty old Thinkpad X41. Unfortunately I did not have much time to
4220 spend on it, but today the replacement finally arrived. I ended up
4221 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4222 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4223 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4224 this, it is installing what I hope will be a more final installation,
4225 with a encrypted hard drive to ensure any dope head stealing it end up
4226 with an expencive door stop.
</p
>
4228 <p
>I had a hard time trying to track down a good laptop, as my most
4229 important requirements (robust and with a good keyboard) are never
4230 listed in the feature list. But I did get good help from the search
4231 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4232 allowed me to limit the list of interesting laptops based on my other
4233 requirements. A bit surprising that SSD disk are not disks, so I had
4234 to drop number of disks from my search parameters.
</p
>
4236 <p
>I am not quite convinced about the keyboard, as it is significantly
4237 wider than my old keyboard, and I have to stretch my hand a lot more
4238 to reach the edges. But the key response is fairly good and the
4239 individual key shape is fairly easy to handle, so I hope I will get
4240 used to it. My old X40 was starting to fail, and I really needed a
4241 new laptop now. :)
</p
>
4243 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4248 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4249 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4251 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4252 <description><p
>It annoys me when the computer fail to do automatically what it is
4253 perfectly capable of, and I have to do it manually to get things
4254 working. One such task is to find out what firmware packages are
4255 needed to get the hardware on my computer working. Most often this
4256 affect the wifi card, but some times it even affect the RAID
4257 controller or the ethernet card. Today I pushed version
0.4 of the
4258 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4259 including a new script isenkram-autoinstall-firmware handling the
4260 process of asking all the loaded kernel modules what firmware files
4261 they want, find debian packages providing these files and install the
4262 debian packages. Here is a test run on my laptop:
</p
>
4264 <p
><pre
>
4265 # isenkram-autoinstall-firmware
4266 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4267 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4268 info: locating packages with the requested firmware files
4269 info: Updating APT sources after adding non-free APT source
4270 info: trying to install firmware-ipw2x00
4273 Preconfiguring packages ...
4274 Selecting previously deselected package firmware-ipw2x00.
4275 (Reading database ...
259727 files and directories currently installed.)
4276 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4277 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4279 </pre
></p
>
4281 <p
>When all the requested firmware is present, a simple message is
4282 printed instead:
</p
>
4284 <p
><pre
>
4285 # isenkram-autoinstall-firmware
4286 info: did not find any firmware files requested by loaded kernel modules. exiting
4288 </pre
></p
>
4290 <p
>It could use some polish, but it is already working well and saving
4291 me some time when setting up new machines. :)
</p
>
4293 <p
>So, how does it work? It look at the set of currently loaded
4294 kernel modules, and look up each one of them using modinfo, to find
4295 the firmware files listed in the module meta-information. Next, it
4296 download the Contents file from a nearby APT mirror, and search for
4297 the firmware files in this file to locate the package with the
4298 requested firmware file. If the package is in the non-free section, a
4299 non-free APT source is added and the package is installed using
4300 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4303 <p
>I hope someone find time to implement a more polished version of
4304 this script as part of the hw-detect debian-installer module, to
4305 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4306 #
655507</a
>. There really is no need to insert USB sticks with
4307 firmware during a PXE install when the packages already are available
4308 from the nearby Debian mirror.
</p
>
4313 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4314 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4315 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4316 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4317 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4318 the screen just turn black when Linux boot, either during installation
4319 or on first boot from the hard disk. I
've seen it once in a while the
4320 last few years, but only recently understood the cause. I
've seen it
4321 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4322 The reason seem to be in the wiring of some laptops. The system to
4323 control the screen background light is inverted, so when Linux try to
4324 turn the brightness fully on, it end up turning it off instead. I do
4325 not know which Linux drivers are affected, but this post is about the
4326 i915 driver used by the
4327 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4328 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4330 <p
>The problem can be worked around two ways. Either by adding
4331 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4332 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4333 option when it load the i915 kernel module. On Debian and Ubuntu, it
4334 can be done by running these commands as root:
</p
>
4337 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4338 update-initramfs -u -k all
4341 <p
>Since March
2012 there is
4342 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4343 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4344 hardware have this problem, and get the driver to invert the
4345 brightness setting automatically. To use it, one need to add a row in
4346 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4347 intel_quirks array
</a
> in the driver source
4348 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4349 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4350 number (vendor number
8086 is assumed) and subdevice vendor and device
4353 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4354 -vvnn
</tt
> for the video card in question:
</p
>
4356 <p
><pre
>
4357 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4358 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4359 (rev
09) (prog-if
00 [VGA controller])
4360 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4361 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4362 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4363 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4364 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4366 Interrupt: pin A routed to IRQ
42
4367 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4368 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4369 Region
4: I/O ports at
4000 [size=
64]
4370 Expansion ROM at
<unassigned
> [disabled]
4371 Capabilities:
<access denied
>
4372 Kernel driver in use: i915
4373 </pre
></p
>
4375 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4377 <p
><pre
>
4378 struct intel_quirk intel_quirks[] = {
4380 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4381 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4384 </pre
></p
>
4386 <p
>According to the kernel module instructions (as seen using
4387 <tt
>modinfo i915
</tt
>), information about hardware needing the
4388 invert_brightness flag should be sent to the
4389 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4390 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4391 developers. But my email about the laptop sent
2013-
06-
03 have not
4393 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4394 web archive for the mailing list
</a
>, so I suspect they do not accept
4395 emails from non-subscribers. Because of this, I sent my patch also to
4396 the Debian bug tracking system instead as
4397 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4398 sure the patch is not lost.
</p
>
4400 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4401 with this problem working properly with Linux. If you use Gnome, your
4402 worries should be over at this point. But if you use KDE, there is
4403 something in KDE ignoring the invert_brightness setting and turning on
4404 the screen during login. I
've reported it to Debian as
4405 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4406 have no idea yet how to figure out exactly what subsystem is doing
4407 this. Perhaps you can help? Perhaps you know what the Gnome
4408 developers did to handle this, and this can give a clue to the KDE
4409 developers? Or you know where in KDE the screen brightness is changed
4410 during login? If so, please update the BTS report (or get in touch if
4411 you do not know how to update BTS).
</p
>
4413 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4414 acpi_backlight=vendor, to disable ACPI backlight support completely,
4415 as the ACPI information on the machine is trash and it is better to
4416 leave it to the intel video driver to control the screen
4417 backlight.
</p
>
4422 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4423 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4424 <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>
4425 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4426 <description><p
>Two days ago, I asked
4427 <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
4428 I could install Linux on a Packard Bell EasyNote LV computer
4429 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4430 with the obstacles put in the way of Linux users on a laptop with UEFI
4431 and Windows
8.
</p
>
4433 <p
>I never found out if the cause of my problems were the use of UEFI
4434 secure booting or fast boot. I suspect fast boot was the problem,
4435 causing the firmware to boot directly from HD without considering any
4436 key presses and alternative devices, but do not know UEFI settings
4437 enough to tell.
</p
>
4439 <p
>There is no way to install Linux on the machine in question without
4440 opening the box and disconnecting the hard drive! This is as far as I
4441 can tell, the only way to get access to the firmware setup menu
4442 without accepting the Windows
8 license agreement. I am told (and
4443 found description on how to) that it is possible to configure the
4444 firmware setup once booted into Windows
8. But as I believe the terms
4445 of that agreement are completely unacceptable, accepting the license
4446 was never an alternative. I do not enter agreements I do not intend
4447 to follow.
</p
>
4449 <p
>I feared I had to return the laptops and ask for a refund, and
4450 waste many hours on this, but luckily there was a way to get it to
4451 work. But I would not recommend it to anyone planning to run Linux on
4452 it, and I have become sceptical to Windows
8 certified laptops. Is
4453 this the way Linux will be forced out of the market place, by making
4454 it close to impossible for
"normal
" users to install Linux without
4455 accepting the Microsoft Windows license terms? Or at least not
4456 without risking to loose the warranty?
</p
>
4458 <p
>I
've updated the
4459 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4460 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4461 do not have to struggle as much as I did to get Linux into the
4464 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4465 Michael Tokarev and others for feedback and ideas.
</p
>
4470 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4471 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4472 <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>
4473 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4474 <description><p
>I
've run into quite a problem the last few days. I bought three
4475 new laptops for my parents and a few others. I bought Packard Bell
4476 Easynote LV to run Kubuntu on and use as their home computer. But I
4477 am completely unable to figure out how to install Linux on it. The
4478 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4479 instead of a BIOS to boot.
</p
>
4481 <p
>The problem is that I am unable to get it to PXE boot, and unable
4482 to get it to boot the Linux installer from my USB stick. I have yet
4483 to try the DVD install, and still hope it will work. when I turn on
4484 the computer, there is no information on what buttons to press to get
4485 the normal boot menu. I expect to get some boot menu to select PXE or
4486 USB stick booting. When booting, it first ask for the language to
4487 use, then for some regional settings, and finally if I will accept the
4488 Windows
8 terms of use. As these terms are completely unacceptable to
4489 me, I have no other choice but to turn off the computer and try again
4490 to get it to boot the Linux installer.
</p
>
4492 <p
>I have gathered my findings so far on a Linlap page about the
4493 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4494 EasyNote LV
</a
> model. If you have any idea how to get Linux
4495 installed on this machine, please get in touch or update that wiki
4496 page. If I can
't find a way to install Linux, I will have to return
4497 the laptop to the seller and find another machine for my parents.
</p
>
4499 <p
>I wonder, is this the way Linux will be forced out of the market
4500 using UEFI and
"secure boot
" by making it impossible to install Linux
4501 on new Laptops?
</p
>
4506 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4507 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4508 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4509 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4510 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4511 an operating system based on Debian intended for use in schools. It
4512 contain a turn-key solution for the computer network provided to
4513 pupils in the primary schools. It provide both the central server,
4514 network boot servers and desktop environments with heaps of
4515 educational software. The project was founded almost
12 years ago,
4516 2001-
07-
02. If you want to support the project, which is in need for
4517 cash to fund developer gatherings and other project related activity,
4518 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4519 donate some money
</a
>.
4521 <p
>A topic that come up again and again on the Debian Edu mailing
4522 lists and elsewhere, is the question on how to transform a Debian or
4523 Ubuntu installation into a Debian Edu installation. It isn
't very
4524 hard, and last week I wrote a script to replicate the steps done by
4525 the Debian Edu installer.
</p
>
4527 <p
>The script,
4528 <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/
>
4529 in the debian-edu-config package, will go through these six steps and
4530 transform an existing Debian Wheezy or Ubuntu (untested) installation
4531 into a Debian Edu Workstation:
</p
>
4535 <li
>Add skolelinux related APT sources.
</li
>
4536 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4537 <li
>Install debian-edu-install to load preseeding values and pull in
4538 our configuration.
</li
>
4539 <li
>Preseed debconf database with profile setup in
4540 /etc/debian-edu/config, and run tasksel to install packages
4541 according to the profile specified in the config above,
4542 overriding some of the Debian automation machinery.
</li
>
4543 <li
>Run debian-edu-cfengine-D installation to configure everything
4544 that could not be done using preseeding.
</li
>
4545 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4549 <p
>There are some steps in the Debian Edu installation that can not be
4550 replicated like this. Disk partitioning and LVM setup, for example.
4551 So this script just assume there is enough disk space to install all
4552 the needed packages.
</p
>
4554 <p
>The script was created to help a Debian Edu student working on
4555 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4556 Debian Edu client, and using it he can take the existing
4557 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4558 transform it into a fully functioning Debian Edu Workstation (or
4559 Roaming Workstation, or whatever :).
</p
>
4561 <p
>The default setting in the script is to create a KDE Workstation.
4562 If a LXDE based Roaming workstation is wanted instead, modify the
4563 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4565 <p
><pre
>
4566 PROFILE=
"Roaming-Workstation
"
4567 DESKTOP=
"lxde
"
4568 </pre
></p
>
4570 <p
>The script could even become useful to set up Debian Edu servers in
4571 the cloud, by starting with a virtual Debian installation at some
4572 virtual hosting service and setting up all the services on first
4578 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4579 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4580 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4581 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4582 <description><P
>In January,
4583 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4584 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4585 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4586 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4587 marvellous construction system from Denmark. We also created
4588 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4589 a place to take notes and write down our plans and hopes. And several
4590 people showed up to help. I was very happy to see the effect of my
4591 call. Since the small start, we have a debtags tag
4592 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4593 tag for LEGO related packages, and now count
10 packages related to
4594 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4596 <p
><table
>
4597 <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
>
4598 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4599 <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
>
4600 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4601 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4602 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4603 <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
>
4604 <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
>
4605 <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
>
4606 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4607 </table
></p
>
4609 <p
>Some of these are available in Wheezy, and all but one are
4610 currently available in Jessie/testing. leocad is so far only
4611 available in experimental.
</p
>
4613 <p
>If you care about LEGO in Debian, please join us on IRC and help
4614 adding the rest of the great free software tools available on Linux
4615 for LEGO designers.
</p
>
4620 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4621 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4623 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4624 <description><p
>When I woke up this morning, I was very happy to see that the
4625 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4626 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4627 Debian release, and I expect to move my machines at home over to it fairly
4630 <p
>The new debian release contain heaps of new stuff, and one program
4631 in particular make me very happy to see included. The
4632 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4633 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4634 included for the first time. Alongside similar programs like
4635 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4636 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4637 it allow for visual programming where syntax errors can not happen,
4638 and a friendly programming environment for learning to control the
4639 computer. Scratch will also be included in the next release of Debian
4642 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4643 Edu/Skolelinux release too. The
4644 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4645 alpha release
</a
> went out last week, and the next should soon
4651 <title>Isenkram
0.2 finally in the Debian archive
</title>
4652 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4654 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4655 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4656 package
</a
> finally made it into the archive, after lingering in NEW
4657 for many months. I uploaded it to the Debian experimental suite
4658 2013-
01-
27, and today it was accepted into the archive.
</p
>
4660 <p
>Isenkram is a system for suggesting to users what packages to
4661 install to work with a pluggable hardware device. The suggestion pop
4662 up when the device is plugged in. For example if a Lego Mindstorm NXT
4663 is inserted, it will suggest to install the program needed to program
4664 the NXT controller. Give it a go, and report bugs and suggestions to
4670 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4671 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4673 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4674 <description><p
>My
4675 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4676 bitcoin related blog post
</a
> mentioned that the new
4677 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4678 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4679 2013-
01-
19, and have been available in unstable since then. It was
4680 automatically copied to Ubuntu, and is available in their Raring
4681 version too.
</p
>
4683 <p
>But there is a strange problem with the build that block this new
4684 version from being available on the i386 and kfreebsd-i386
4685 architectures. For some strange reason, the autobuilders in Debian
4686 for these architectures fail to run the test suite on these
4687 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4688 We are so far unable to reproduce it when building it manually, and
4689 no-one have been able to propose a fix. If you got an idea what is
4690 failing, please let us know via the BTS.
</p
>
4692 <p
>One feature that is annoying me with of the bitcoin client, because
4693 I often run low on disk space, is the fact that the client will exit
4694 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4695 #
696715</a
>). So make sure you have enough disk space when you run
4698 <p
>As usual, if you use bitcoin and want to show your support of my
4699 activities, please send Bitcoin donations to my address
4700 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4705 <title>Welcome to the world, Isenkram!
</title>
4706 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4708 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4709 <description><p
>Yesterday, I
4710 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4711 for testers
</a
> for my prototype for making Debian better at handling
4712 pluggable hardware devices, which I
4713 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4714 out to create
</a
> earlier this month. Several valuable testers showed
4715 up, and caused me to really want to to open up the development to more
4716 people. But before I did this, I want to come up with a sensible name
4717 for this project. Today I finally decided on a new name, and I have
4718 renamed the project from hw-support-handler to this new name. In the
4719 process, I moved the source to git and made it available as a
4720 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4721 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4722 To fetch and build the latest version of the source, use
</p
>
4725 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4726 cd isenkram
&& git-buildpackage -us -uc
4729 <p
>I have not yet adjusted all files to use the new name yet. If you
4730 want to hack on the source or improve the package, please go ahead.
4731 But please talk to me first on IRC or via email before you do major
4732 changes, to make sure we do not step on each others toes. :)
</p
>
4734 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4735 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4736 stuff, in other words. I
've been told it is the Norwegian variant of
4737 the German word eisenkram, for those that are familiar with that
4740 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4741 instructions, to avoid confusing people with an error from the signing
4744 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4745 clone argument to avoid the need for authentication.
</p
>
4750 <title>First prototype ready making hardware easier to use in Debian
</title>
4751 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4752 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4753 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4754 <description><p
>Early this month I set out to try to
4755 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4756 the Debian support for pluggable hardware devices
</a
>. Now my
4757 prototype is working, and it is ready for a larger audience. To test
4759 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4760 from the Debian Edu subversion repository
</a
>, build and install the
4761 package. You might have to log out and in again activate the
4762 autostart script.
</p
>
4764 <p
>The design is simple:
</p
>
4768 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4769 hw-support-handlerd to start when the user log in.
</li
>
4771 <li
>This program listen for kernel events about new hardware (directly
4772 from the kernel like udev does), not using HAL dbus events as I
4773 initially did.
</li
>
4775 <li
>When new hardware is inserted, look up the hardware modalias in
4776 the APT database, a database
4777 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4778 via HTTP
</a
> and a database available as part of the package.
</li
>
4780 <li
>If a package is mapped to the hardware in question, the package
4781 isn
't installed yet and this is the first time the hardware was
4782 plugged in, show a desktop notification suggesting to install the
4783 package or packages.
</li
>
4785 <li
>If the user click on the
'install package now
' button, ask
4786 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4788 <li
>aptdaemon ask for root password or sudo password, and install the
4789 package while showing progress information in a window.
</li
>
4793 <p
>I still need to come up with a better name for the system. Here
4794 are some screen shots showing the prototype in action. First the
4795 notification, then the password request, and finally the request to
4796 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4798 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4799 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4800 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4801 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4802 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4804 <p
>The prototype still need to be improved with longer timeouts, but
4805 is already useful. The database of hardware to package mappings also
4806 need more work. It is currently compatible with the Ubuntu way of
4807 storing such information in the package control file, but could be
4808 changed to use other formats instead or in addition to the current
4809 method. I
've dropped the use of discover for this mapping, as the
4810 modalias approach is more flexible and easier to use on Linux as long
4811 as the Linux kernel expose its modalias strings directly.
</p
>
4813 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4814 here is the command required to check out and build the source: Use
4815 '<tt
>svn checkout
4816 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4817 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4818 devscripts package.
</p
>
4820 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4821 renamed to Isenkram and the source moved from the Debian Edu
4822 subversion repository to a Debian collab-maint git repository. See
4823 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4824 instructions
</a
> for details.
</p
>
4829 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4830 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4832 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4833 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4834 suddenly in bed. With a quiet whimper, it went completely quiet and
4835 black. The power button was no longer able to turn it on. It was a
4836 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4837 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4838 Compaq I had before that. Now I need to find a replacement. To keep
4839 going during Christmas, I moved the one year old SSD disk to my old
4840 X40 where it fitted (only one I had left that could use it), but it is
4841 not a durable solution.
4843 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4844 got a new one more than
10 years ago. It still holds true.:)
</p
>
4848 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4849 than A4).
</li
>
4850 <li
>Robust, it will be in my backpack every day.
</li
>
4851 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4852 <li
>Long battery life time. Preferable a week.
</li
>
4853 <li
>Internal WIFI network card.
</li
>
4854 <li
>Internal Twisted Pair network card.
</li
>
4855 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4856 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4857 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4859 <li
>Hardware supported by Debian Stable, ie the default kernel and
4860 X.org packages.
</li
>
4861 <li
>Quiet, preferably fan free (or at least not using the fan most of
4866 <p
>You will notice that there are no RAM and CPU requirements in the
4867 list. The reason is simply that the specifications on laptops the
4868 last
10-
15 years have been sufficient for my needs, and I have to look
4869 at other features to choose my laptop. But are there still made as
4870 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4871 robust, and Thinkpads seem to be heading in the wrong direction since
4872 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4873 still be useful.
</p
>
4875 <p
>Perhaps I should rethink my needs, and look for a pad with an
4876 external keyboard? I
'll have to check the
4877 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4878 well-supported laptops, or perhaps just buy one preinstalled from one
4879 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4880 Pre-loaded site
</a
>.
</p
>
4885 <title>How to find a browser plugin supporting a given MIME type
</title>
4886 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4887 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4888 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4889 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4890 install to get support for a given MIME type. Thanks to
4891 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4892 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4893 Unfortunately, not very many packages provide the needed meta
4894 information, Anyway, here is a small script to look up all browser
4895 plugin packages announcing ther MIME support using this specification:
</p
>
4901 def pkgs_handling_mimetype(mimetype):
4906 version = pkg.candidate
4908 version = pkg.installed
4911 record = version.record
4912 if not record.has_key(
'Npp-MimeType
'):
4914 mime_types = record[
'Npp-MimeType
'].split(
',
')
4915 for t in mime_types:
4916 t = t.rstrip().strip()
4918 thepkgs.append(pkg.name)
4920 mimetype =
"audio/ogg
"
4921 if
1 < len(sys.argv):
4922 mimetype = sys.argv[
1]
4923 print
"Browser plugin packages supporting %s:
" % mimetype
4924 for pkg in pkgs_handling_mimetype(mimetype):
4925 print
" %s
" %pkg
4928 <p
>It can be used like this to look up a given MIME type:
</p
>
4931 % ./apt-find-browserplug-for-mimetype
4932 Browser plugin packages supporting audio/ogg:
4934 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4935 Browser plugin packages supporting application/x-shockwave-flash:
4936 browser-plugin-gnash
4940 <p
>In Ubuntu this mechanism is combined with support in the browser
4941 itself to query for plugins and propose to install the needed
4942 packages. It would be great if Debian supported such feature too. Is
4943 anyone working on adding it?
</p
>
4945 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4946 request for icweasel support for this feature is
4947 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4948 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4949 of manpower and wish for a different design is the reason thus feature
4950 is not yet in iceweasel from Debian.
</p
>
4955 <title>What is the most supported MIME type in Debian?
</title>
4956 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4958 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4959 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4960 proposal to add AppStream information to the Debian archive
</a
>, is a
4961 proposal to make it possible for a Desktop application to propose to
4962 the user some package to install to gain support for a given MIME
4963 type, font, library etc. that is currently missing. With such
4964 mechanism in place, it would be possible for the desktop to
4965 automatically propose and install leocad if some LDraw file is
4966 downloaded by the browser.
</p
>
4968 <p
>To get some idea about the current content of the archive, I decided
4969 to write a simple program to extract all .desktop files from the
4970 Debian archive and look up the claimed MIME support there. The result
4972 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4973 site
</a
>. Using the collected information, it become possible to
4974 answer the question in the title. Here are the
20 most supported MIME
4975 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4976 The complete list is available from the link above.
</p
>
4978 <p
><strong
>Debian Stable:
</strong
></p
>
4982 ----- -----------------------
4998 18 application/x-ogg
5005 <p
><strong
>Debian Testing:
</strong
></p
>
5009 ----- -----------------------
5025 18 application/x-ogg
5032 <p
><strong
>Debian Unstable:
</strong
></p
>
5036 ----- -----------------------
5053 18 application/x-ogg
5059 <p
>I am told that PackageKit can provide an API to access the kind of
5060 information mentioned in DEP-
11. I have not yet had time to look at
5061 it, but hope the PackageKit people in Debian are on top of these
5064 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5065 discovering a typo in my script.
</p
>
5070 <title>Using modalias info to find packages handling my hardware
</title>
5071 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5072 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5073 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5074 <description><p
>Yesterday, I wrote about the
5075 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5076 values provided by the Linux kernel
</a
> following my hope for
5077 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5078 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5079 modalias values attached to package names can be used to map packages
5080 to hardware. This allow the system to look up and suggest relevant
5081 packages when I plug in some new hardware into my machine, and replace
5082 discover and discover-data as the database used to map hardware to
5085 <p
>I create a modaliases file with entries like the following,
5086 containing package name, kernel module name (if relevant, otherwise
5087 the package name) and globs matching the relevant hardware
5090 <p
><blockquote
>
5091 Package: package-name
5092 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5093 </blockquote
></p
>
5095 <p
>It is fairly trivial to write code to find the relevant packages
5096 for a given modalias value using this file.
</p
>
5098 <p
>An entry like this would suggest the video and picture application
5099 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5101 <p
><blockquote
>
5103 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5104 </blockquote
></p
>
5106 <p
>An entry like this would suggest the pcmciautils package when a
5107 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5109 <p
><blockquote
>
5110 Package: pcmciautils
5111 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5112 </blockquote
></p
>
5114 <p
>An entry like this would suggest the package colorhug-client when
5115 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5117 <p
><blockquote
>
5118 Package: colorhug-client
5119 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5120 </blockquote
></p
>
5122 <p
>I believe the format is compatible with the format of the Packages
5123 file in the Debian archive. Ubuntu already uses their Packages file
5124 to store their mappings from packages to hardware.
</p
>
5126 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5127 announce the hardware it support in a way my prototype understand.
5128 This allow those publishing packages in an APT source outside the
5129 Debian archive as well as those backporting packages to make sure the
5130 hardware mapping are included in the package meta information. I
've
5131 tested such header in the pymissile package, and its modalias mapping
5132 is working as it should with my prototype. It even made it to Ubuntu
5135 <p
>To test if it was possible to look up supported hardware using only
5136 the shell tools available in the Debian installer, I wrote a shell
5137 implementation of the lookup code. The idea is to create files for
5138 each modalias and let the shell do the matching. Please check out and
5140 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5141 shell script. It run without any extra dependencies and fetch the
5142 hardware mappings from the Debian archive and the subversion
5143 repository where I currently work on my prototype.
</p
>
5145 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5146 install yubikey-personalization:
</p
>
5148 <p
><blockquote
>
5149 % ./hw-support-lookup
5150 <br
>yubikey-personalization
5152 </blockquote
></p
>
5154 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5155 propose to install the pcmciautils package:
</p
>
5157 <p
><blockquote
>
5158 % ./hw-support-lookup
5159 <br
>pcmciautils
5161 </blockquote
></p
>
5163 <p
>If you know of any hardware-package mapping that should be added to
5164 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5165 database
</a
>, please tell me about it.
</p
>
5167 <p
>It could be possible to generate several of the mappings between
5168 packages and hardware. One source would be to look at packages with
5169 kernel modules, ie packages with *.ko files in /lib/modules/, and
5170 extract their modalias information. Another would be to look at
5171 packages with udev rules, ie packages with files in
5172 /lib/udev/rules.d/, and extract their vendor/model information to
5173 generate a modalias matching rule. I have not tested any of these to
5174 see if it work.
</p
>
5176 <p
>If you want to help implementing a system to let us propose what
5177 packages to install when new hardware is plugged into a Debian
5178 machine, please send me an email or talk to me on
5179 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5184 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5185 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5186 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5187 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5188 <description><p
>While looking into how to look up Debian packages based on hardware
5189 information, to find the packages that support a given piece of
5190 hardware, I refreshed my memory regarding modalias values, and decided
5191 to document the details. Here are my findings so far, also available
5193 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5194 Debian Edu subversion repository
</a
>:
5196 <p
><strong
>Modalias decoded
</strong
></p
>
5198 <p
>This document try to explain what the different types of modalias
5199 values stands for. It is in part based on information from
5200 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5201 &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;,
5202 &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
5203 &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;.
5205 <p
>The modalias entries for a given Linux machine can be found using
5206 this shell script:
</p
>
5209 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5212 <p
>The supported modalias globs for a given kernel module can be found
5213 using modinfo:
</p
>
5216 % /sbin/modinfo psmouse | grep alias:
5217 alias: serio:ty05pr*id*ex*
5218 alias: serio:ty01pr*id*ex*
5222 <p
><strong
>PCI subtype
</strong
></p
>
5224 <p
>A typical PCI entry can look like this. This is an Intel Host
5225 Bridge memory controller:
</p
>
5227 <p
><blockquote
>
5228 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5229 </blockquote
></p
>
5231 <p
>This represent these values:
</p
>
5236 sv
00001028 (subvendor)
5237 sd
000001AD (subdevice)
5239 sc
00 (bus subclass)
5243 <p
>The vendor/device values are the same values outputted from
'lspci
5244 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5245 0600. The
0600 class is a host bridge. Other useful bus values are
5246 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5248 <p
>Not sure how to figure out the interface value, nor what it
5251 <p
><strong
>USB subtype
</strong
></p
>
5253 <p
>Some typical USB entries can look like this. This is an internal
5254 USB hub in a laptop:
</p
>
5256 <p
><blockquote
>
5257 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5258 </blockquote
></p
>
5260 <p
>Here is the values included in this alias:
</p
>
5263 v
1D6B (device vendor)
5264 p
0001 (device product)
5266 dc
09 (device class)
5267 dsc
00 (device subclass)
5268 dp
00 (device protocol)
5269 ic
09 (interface class)
5270 isc
00 (interface subclass)
5271 ip
00 (interface protocol)
5274 <p
>The
0900 device class/subclass means hub. Some times the relevant
5275 class is in the interface class section. For a simple USB web camera,
5276 these alias entries show up:
</p
>
5278 <p
><blockquote
>
5279 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5280 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5281 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5282 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5283 </blockquote
></p
>
5285 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5286 camera),
0101 is audio control device and
0102 is audio streaming (aka
5287 microphone). Thus this is a camera with microphone included.
</p
>
5289 <p
><strong
>ACPI subtype
</strong
></p
>
5291 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5292 receiver in a Thinkpad X40:
</p
>
5294 <p
><blockquote
>
5295 acpi:IBM0071:PNP0511:
5296 </blockquote
></p
>
5298 <p
>The values between the colons are IDs.
</p
>
5300 <p
><strong
>DMI subtype
</strong
></p
>
5302 <p
>The DMI table contain lots of information about the computer case
5303 and model. This is an entry for a IBM Thinkpad X40, fetched from
5304 /sys/devices/virtual/dmi/id/modalias:
</p
>
5306 <p
><blockquote
>
5307 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5308 </blockquote
></p
>
5310 <p
>The values present are
</p
>
5313 bvn IBM (BIOS vendor)
5314 bvr
1UETB
6WW(
1.66) (BIOS version)
5315 bd
06/
15/
2005 (BIOS date)
5316 svn IBM (system vendor)
5317 pn
2371H4G (product name)
5318 pvr ThinkPadX40 (product version)
5319 rvn IBM (board vendor)
5320 rn
2371H4G (board name)
5321 rvr NotAvailable (board version)
5322 cvn IBM (chassis vendor)
5323 ct
10 (chassis type)
5324 cvr NotAvailable (chassis version)
5327 <p
>The chassis type
10 is Notebook. Other interesting values can be
5328 found in the dmidecode source:
</p
>
5332 4 Low Profile Desktop
5345 17 Main Server Chassis
5346 18 Expansion Chassis
5348 20 Bus Expansion Chassis
5349 21 Peripheral Chassis
5351 23 Rack Mount Chassis
5360 <p
>The chassis type values are not always accurately set in the DMI
5361 table. For example my home server is a tower, but the DMI modalias
5362 claim it is a desktop.
</p
>
5364 <p
><strong
>SerIO subtype
</strong
></p
>
5366 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5367 test machine:
</p
>
5369 <p
><blockquote
>
5370 serio:ty01pr00id00ex00
5371 </blockquote
></p
>
5373 <p
>The values present are
</p
>
5382 <p
>This type is supported by the psmouse driver. I am not sure what
5383 the valid values are.
</p
>
5385 <p
><strong
>Other subtypes
</strong
></p
>
5387 <p
>There are heaps of other modalias subtypes according to
5388 file2alias.c. There is the rest of the list from that source: amba,
5389 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5390 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5391 vmbus, x86cpu and zorro. I did not spend time documenting all of
5392 these, as they do not seem relevant for my intended use with mapping
5393 hardware to packages when new stuff is inserted during run time.
</p
>
5395 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5397 <p
>To check which kernel modules provide support for a given modalias,
5398 one can use the following shell script:
</p
>
5401 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5402 echo
"$id
" ; \
5403 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5407 <p
>The output can look like this (only the first few entries as the
5408 list is very long on my test machine):
</p
>
5412 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5414 FATAL: Module acpi:device: not found.
5416 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5417 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5418 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5419 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5420 acpi:IBM0071:PNP0511:
5421 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5422 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5423 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5427 <p
>If you want to help implementing a system to let us propose what
5428 packages to install when new hardware is plugged into a Debian
5429 machine, please send me an email or talk to me on
5430 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5432 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5433 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5434 in /sys/ with space in them.
</p
>
5439 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5440 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5441 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5442 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5443 <description><p
>As part of my investigation on how to improve the support in Debian
5444 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5445 Launcher and updated the Debian package
5446 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5447 sure udev will fix the device permissions when it is plugged in. I
5448 also added a
"Modaliases
" header to test it in the Debian archive and
5449 hopefully make the package be proposed by jockey in Ubuntu when a user
5450 plug in his rocket launcher. In the process I moved the source to a
5451 git repository under collab-maint, to make it easier for any DD to
5452 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5453 is not very active, but the software still work for me even after five
5454 years of relative silence. The new git repository is not listed in
5455 the uploaded package yet, because I want to test the other changes a
5456 bit more before I upload the new version. If you want to check out
5457 the new version with a .desktop file included, visit the
5458 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5459 view
</a
> or use
"<tt
>git clone
5460 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5465 <title>Lets make hardware dongles easier to use in Debian
</title>
5466 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5467 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5468 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5469 <description><p
>One thing that annoys me with Debian and Linux distributions in
5470 general, is that there is a great package management system with the
5471 ability to automatically install software packages by downloading them
5472 from the distribution mirrors, but no way to get it to automatically
5473 install the packages I need to use the hardware I plug into my
5474 machine. Even if the package to use it is easily available from the
5475 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5476 suggest to automatically install the python-nxt, nbc and t2n packages
5477 I need to talk to it. When I plug in a Yubikey, it could propose the
5478 yubikey-personalization package. The information required to do this
5479 is available, but no-one have pulled all the pieces together.
</p
>
5481 <p
>Some years ago, I proposed to
5482 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5483 the discover subsystem to implement this
</a
>. The idea is fairly
5488 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5489 starting when a user log in.
</li
>
5491 <li
>Set this program up to listen for kernel events emitted when new
5492 hardware is inserted into the computer.
</li
>
5494 <li
>When new hardware is inserted, look up the hardware ID in a
5495 database mapping to packages, and take note of any non-installed
5496 packages.
</li
>
5498 <li
>Show a message to the user proposing to install the discovered
5499 package, and make it easy to install it.
</li
>
5503 <p
>I am not sure what the best way to implement this is, but my
5504 initial idea was to use dbus events to discover new hardware, the
5505 discover database to find packages and
5506 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5509 <p
>Yesterday, I found time to try to implement this idea, and the
5510 draft package is now checked into
5511 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5512 Debian Edu subversion repository
</a
>. In the process, I updated the
5513 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5514 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5515 the relevant packages in Debian, and uploaded a new version
5516 2.2013.01.09 to unstable. I also discovered that the current
5517 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5518 package in Debian no longer discovered any USB devices, because
5519 /proc/bus/usb/devices is no longer present. I ported it to use
5520 libusb as a fall back option to get it working. The fixed package
5521 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5522 because of the freeze).
</p
>
5524 <p
>With this prototype in place, I can insert my Yubikey, and get this
5525 desktop notification to show up (only once, the first time it is
5526 inserted):
</p
>
5528 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5530 <p
>For this prototype to be really useful, some way to automatically
5531 install the proposed packages by pressing the
"Please install
5532 program(s)
" button should to be implemented.
</p
>
5534 <p
>If this idea seem useful to you, and you want to help make it
5535 happen, please help me update the discover-data database with mappings
5536 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5537 list the package you would like to have installed when a given
5538 hardware device is inserted into your computer, and report bugs using
5539 reportbug if it isn
't. Or, if you know of a better way to provide
5540 such mapping, please let me know.
</p
>
5542 <p
>This prototype need more work, and there are several questions that
5543 should be considered before it is ready for production use. Is dbus
5544 the correct way to detect new hardware? At the moment I look for HAL
5545 dbus events on the system bus, because that is the events I could see
5546 on my Debian Squeeze KDE desktop. Are there better events to use?
5547 How should the user be notified? Is the desktop notification
5548 mechanism the best option, or should the background daemon raise a
5549 popup instead? How should packages be installed? When should they
5550 not be installed?
</p
>
5552 <p
>If you want to help getting such feature implemented in Debian,
5553 please send me an email. :)
</p
>
5558 <title>New IRC channel for LEGO designers using Debian
</title>
5559 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5561 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5562 <description><p
>During Christmas, I have worked a bit on the Debian support for
5563 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5564 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5565 discovered I had to build all the tools myself because none were
5566 already in Debian Squeeze. If Debian support for LEGO is something
5567 you care about, please join me on the IRC channel
5568 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5569 irc.debian.org). There is a lot that could be done to improve the
5570 Debian support for LEGO designers. For example both CAD software
5571 and Mindstorm compilers are missing. :)
</p
>
5573 <p
>Update
2012-
01-
03: A
5574 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5575 including links to Lego related packages is now available.
</p
>
5580 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5581 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5583 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5584 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5585 year! I hope next year will prove to be a good year.
</p
>
5587 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5588 decentralised
"currency
" that allow people to transfer bitcoins
5589 between each other with minimal overhead, is a very interesting
5590 experiment. And as I wrote a few days ago, the bitcoin situation in
5591 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5592 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5593 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5594 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5595 for one of the ftpmasters to approve the new bitcoin-qt package
5598 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5599 team in Debian, you can easily test the package in Debian Squeeze
5600 using the following steps to get a set of working packages:
</p
>
5602 <blockquote
><pre
>
5603 git clone git://git.debian.org/git/collab-maint/bitcoin
5605 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5606 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5607 </pre
></blockquote
>
5609 <p
>You might have to install some build dependencies as well. The
5610 list of commands should give you two packages, bitcoind and
5611 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5612 client will download the complete set of bitcoin
"blocks
", which need
5613 around
5.6 GiB of data on my machine at the moment. Make sure your
5614 ~/.bitcoin/ directory have lots of spare room if you want to download
5615 all the blocks. The client will warn if the disk is getting full, so
5616 there is not really a problem if you got too little room, but you will
5617 not be able to get all the features out of the client.
</p
>
5619 <p
>As usual, if you use bitcoin and want to show your support of my
5620 activities, please send Bitcoin donations to my address
5621 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5626 <title>A word on bitcoin support in Debian
</title>
5627 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5629 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5630 <description><p
>It has been a while since I wrote about
5631 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5632 peer-to-peer based crypto-currency, and the reason is simply that I
5633 have been busy elsewhere. But two days ago, I started looking at the
5634 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5635 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5636 is now maintained by a
5637 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5638 people
</a
>, and the grunt work had already been done by this team. We
5639 owe a huge thank you to all these team members. :)
5640 But I was sad to discover that the bitcoin client is missing in
5641 Wheezy. It is only available in Sid (and an outdated client from
5642 backports). The client had several RC bugs registered in BTS blocking
5643 it from entering testing. To try to help the team and improve the
5644 situation, I spent some time providing patches and triaging the bug
5645 reports. I also had a look at the bitcoin package available from Matt
5647 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5648 Ubuntu
</a
>, and moved the useful pieces from that version into the
5649 Debian package.
</p
>
5651 <p
>After checking with the main package maintainer Jonas Smedegaard on
5652 IRC, I pushed several patches into the collab-maint git repository to
5653 improve the package. It now contains fixes for the RC issues (not from
5654 me, but fixed by Scott Howard), build rules for a Qt GUI client
5655 package, konqueror support for the bitcoin: URI and bash completion
5656 setup. As I work on Debian Squeeze, I also created
5657 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5658 patch to backport
</a
> the latest version. Jonas is going to look at
5659 it and try to integrate it into the git repository before uploading a
5660 new version to unstable.
5662 <p
>I would very much like bitcoin to succeed, to get rid of the
5663 centralized control currently exercised in the monetary system. I
5664 find it completely unacceptable that the USA government is collecting
5665 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5666 that the major credit card companies can block legal money
5667 transactions to Wikileaks. But for bitcoin to succeed, more people
5668 need to use bitcoins, and more people need to accept bitcoins when
5669 they sell products and services. Improving the bitcoin support in
5670 Debian is a small step in the right direction, but not enough.
5671 Unfortunately the user experience when browsing the web and wanting to
5672 pay with bitcoin is still not very good. The bitcoin: URI is a step
5673 in the right direction, but need to work in most or every browser in
5674 use. Also the bitcoin-qt client is too heavy to fire up to do a
5675 quick transaction. I believe there are other clients available, but
5676 have not tested them.
</p
>
5679 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5680 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5681 I received
20.15 BTC so far on the address I provided in my blog two
5682 years ago, as can be
5683 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5684 on the blockexplorer service
</a
>. Thank you everyone for your
5685 donation. The blockexplorer service demonstrates quite well that
5686 bitcoin is not quite anonymous and untracked. :) I wonder if the
5687 number of users have gone up since then. If you use bitcoin and want
5688 to show your support of my activity, please send Bitcoin donations to
5689 the same address as last time,
5690 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5695 <title>Git repository for song book for Computer Scientists
</title>
5696 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5697 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5698 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5699 <description><p
>As I
5700 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5701 this summer
</a
>, I have created a Computer Science song book a few
5702 years ago, and today I finally found time to create a public
5703 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5704 repository for the project
</a
>.
</p
>
5706 <p
>If you want to help out, please clone the source and submit patches
5707 to the HTML version. To generate the PDF and PostScript version,
5708 please use prince XML, or let me know about a useful free software
5709 processor capable of creating a good looking PDF from the HTML.
</p
>
5711 <p
>Want to sing? You can still find the song book in HTML, PDF and
5712 PostScript formats at
5713 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5714 Science Songbook
</a
>.
</p
>
5719 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5720 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5721 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5722 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5723 <description><p
>I dag fyller
5724 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5725 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5726 si gratulerer med dagen, Debian!
</p
>
5731 <title>Song book for Computer Scientists
</title>
5732 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5734 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5735 <description><p
>Many years ago, while studying Computer Science at the
5736 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5737 collecting computer related songs for use at parties. The original
5738 version was written in LaTeX, but a few years ago I got help from
5739 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5740 while keeping the ability to create a nice book in PDF format. I have
5741 not had time to maintain the book for a while now, and guess I should
5742 put it up on some public version control repository where others can
5743 help me extend and update the book. If anyone is volunteering to help
5744 me with this, send me an email. Also let me know if there are songs
5745 missing in my book.
</p
>
5747 <p
>I have not mentioned the book on my blog so far, and it occured to
5748 me today that I really should let all my readers share the joys of
5749 singing out load about programming, computers and computer networks.
5750 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5751 12</a
> is about to start (and I am not going). Want to sing? Check
5752 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5753 Computer Science Songbook
</a
>.
5758 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5759 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5760 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5761 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5762 <description><p
>At work we have heaps of servers. I believe the total count is
5763 around
1000 at the moment. To be able to get help from the vendors
5764 when something go wrong, we want to keep the firmware on the servers
5765 up to date. If the firmware isn
't the latest and greatest, the
5766 vendors typically refuse to start debugging any problems until the
5767 firmware is upgraded. So before every reboot, we want to upgrade the
5768 firmware, and we would really like everyone handling servers at the
5769 university to do this themselves when they plan to reboot a machine.
5770 For that to happen we at the unix server admin group need to provide
5771 the tools to do so.
</p
>
5773 <p
>To make firmware upgrading easier, I am working on a script to
5774 fetch and install the latest firmware for the servers we got. Most of
5775 our hardware are from Dell and HP, so I have focused on these servers
5776 so far. This blog post is about the Dell part.
</P
>
5778 <p
>On the Dell FTP site I was lucky enough to find
5779 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5780 with firmware information for all
11th generation servers, listing
5781 which firmware should be used on a given model and where on the FTP
5782 site I can find it. Using a simple perl XML parser I can then
5783 download the shell scripts Dell provides to do firmware upgrades from
5784 within Linux and reboot when all the firmware is primed and ready to
5785 be activated on the first reboot.
</p
>
5787 <p
>This is the Dell related fragment of the perl code I am working on.
5788 Are there anyone working on similar tools for firmware upgrading all
5789 servers at a site? Please get in touch and lets share resources.
</p
>
5791 <p
><pre
>
5795 use File::Temp qw(tempdir);
5797 # Install needed RHEL packages if missing
5799 'XML::Simple
' =
> 'perl-XML-Simple
',
5801 for my $module (keys %rhelmodules) {
5802 eval
"use $module;
";
5804 my $pkg = $rhelmodules{$module};
5805 system(
"yum install -y $pkg
");
5806 eval
"use $module;
";
5810 my $errorsto =
'pere@hungry.com
';
5816 sub run_firmware_script {
5817 my ($opts, $script) = @_;
5819 print STDERR
"fail: missing script name\n
";
5822 print STDERR
"Running $script\n\n
";
5824 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5825 print STDERR
"success: firmware script ran succcessfully\n
";
5827 print STDERR
"fail: firmware script returned error\n
";
5831 sub run_firmware_scripts {
5832 my ($opts, @dirs) = @_;
5833 # Run firmware packages
5834 for my $dir (@dirs) {
5835 print STDERR
"info: Running scripts in $dir\n
";
5836 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5837 while (my $s = readdir $dh) {
5838 next if $s =~ m/^\.\.?/;
5839 run_firmware_script($opts,
"$dir/$s
");
5847 print STDERR
"info: Downloading $url\n
";
5848 system(
"wget --quiet \
"$url\
"");
5853 my $product = `dmidecode -s system-product-name`;
5856 if ($product =~ m/PowerEdge/) {
5858 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5859 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5861 my $tmpdir = tempdir(
5865 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5866 system(
'gunzip Catalog.xml.gz
');
5867 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5868 # -q is quiet, disabling interactivity and reducing console output
5869 my $fwopts =
"-q
";
5871 for my $url (@paths) {
5872 fetch_dell_fw($url);
5874 run_firmware_scripts($fwopts, $tmpdir);
5876 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5877 print STDERR
"error: Please report to $errorsto.\n
";
5881 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5882 print STDERR
"error: Please report to $errorsto.\n
";
5888 my $url =
"ftp://ftp.us.dell.com/$path
";
5892 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5893 # firmware packages to download from Dell. Only work for Linux
5894 # machines and
11th generation Dell servers.
5895 sub fetch_dell_fw_list {
5896 my $filename = shift;
5898 my $product = `dmidecode -s system-product-name`;
5900 my ($mybrand, $mymodel) = split(/\s+/, $product);
5902 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5904 my $xml = XMLin($filename);
5906 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5907 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5908 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5910 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5911 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5913 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5915 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5917 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5920 for my $component (@{$xml-
>{SoftwareComponent}}) {
5921 my $componenttype = $component-
>{ComponentType}-
>{value};
5923 # Drop application packages, only firmware and BIOS
5924 next if
'APAC
' eq $componenttype;
5926 my $cpath = $component-
>{path};
5927 for my $path (@paths) {
5928 if ($cpath =~ m%/$path$%) {
5929 push(@paths, $cpath);
5937 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5938 it could work on other platforms with some tweaking. Anyone know a
5939 index like Catalog.xml is available from HP for HP servers? At the
5940 moment I maintain a similar list manually and it is quickly getting
5946 <title>How is booting into runlevel
1 different from single user boots?
</title>
5947 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5949 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5950 <description><p
>Wouter Verhelst have some
5951 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5952 comments and opinions
</a
> on my blog post on
5953 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5954 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5955 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5956 default KDE desktop in Debian
</a
>. I only have time to address one
5957 small piece of his comment now, and though it best to address the
5958 misunderstanding he bring forward:
</p
>
5960 <p
><blockquote
>
5961 Currently, a system admin has four options: [...] boot to a
5962 single-user system (by adding
'single
' to the kernel command line;
5963 this runs rcS and rc1 scripts)
5964 </blockquote
></p
>
5966 <p
>This make me believe Wouter believe booting into single user mode
5967 and booting into runlevel
1 is the same. I am not surprised he
5968 believe this, because it would make sense and is a quite sensible
5969 thing to believe. But because the boot in Debian is slightly broken,
5970 runlevel
1 do not work properly and it isn
't the same as single user
5971 mode. I
'll try to explain what is actually happing, but it is a bit
5972 hard to explain.
</p
>
5974 <p
>Single user mode is defined like this in /etc/inittab:
5975 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5976 executed in single user mode is sulogin. Single user mode is a boot
5977 state
"between
" the runlevels, and when booting into single user mode,
5978 only the scripts in /etc/rcS.d/ are executed before the init process
5979 enters the single user state. When switching to runlevel
1, the state
5980 is in fact not ending in runlevel
1, but it passes through runlevel
1
5981 and end up in the single user mode (see /etc/rc1.d/S03single, which
5982 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5983 1. It is confusing that the
'S
' (single user) init mode is not the
5984 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5987 <p
>This summary might make it clearer. When booting for the first
5988 time into single user mode, the following commands are executed:
5989 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5990 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5991 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5992 trying to continue after visiting single user mode. Not all services
5993 are started again as they should, causing the machine to end up in an
5994 unpredicatble state. This is why Debian admins recommend rebooting
5995 after visiting single user mode.
</p
>
5997 <p
>A similar problem with runlevel
1 is caused by the amount of
5998 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5999 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6000 stopped when passing through the scripts in /etc/rc1.d/, and not
6001 started again when switching away from runlevel
1 to the runlevels
6002 2-
5. I believe the problem is best fixed by moving all the scripts
6003 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6004 functioning single user mode during boot.
</p
>
6006 <p
>I have spent several years investigating the Debian boot system,
6007 and discovered this problem a few years ago. I suspect it originates
6008 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6013 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6014 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6016 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6017 <description><p
>In the Debian boot system, several packages include scripts that
6018 are started from /etc/rcS.d/. In fact, there is a bite more of them
6019 than make sense, and this causes a few problems. What kind of
6020 problems, you might ask. There are at least two problems. The first
6021 is that it is not possible to recover a machine after switching to
6022 runlevel
1. One need to actually reboot to get the machine back to
6023 the expected state. The other is that single user boot will sometimes
6024 run into problems because some of the subsystems are activated before
6025 the root login is presented, causing problems when trying to recover a
6026 machine from a problem in that subsystem. A minor additional point is
6027 that moving more scripts out of rcS.d/ and into the other rc#.d/
6028 directories will increase the amount of scripts that can run in
6029 parallel during boot, and thus decrease the boot time.
</p
>
6031 <p
>So, which scripts should start from rcS.d/. In short, only the
6032 scripts that _have_ to execute before the root login prompt is
6033 presented during a single user boot should go there. Everything else
6034 should go into the numeric runlevels. This means things like
6035 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6036 the numeric runlevels. Today in Debian, there are around
115 init.d
6037 scripts that are started from rcS.d/, and most of them should be moved
6038 out. Do your package have one of them? Please help us make single
6039 user and runlevel
1 better by moving it.
</p
>
6041 <p
>Scripts setting up the screen, keyboard, system partitions
6042 etc. should still be started from rcS.d/, but there is for example no
6043 need to have the network enabled before the single user login prompt
6044 is presented.
</p
>
6046 <p
>As always, things are not so easy to fix as they sound. To keep
6047 Debian systems working while scripts migrate and during upgrades, the
6048 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6049 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6050 and the next ones can only be moved when their dependencies have been
6051 moved first. This migration must be done sequentially while we ensure
6052 that the package system upgrade packages in the right order to keep
6053 the system state correct. This will require some coordination when it
6054 comes to network related packages, but most of the packages with
6055 scripts that should migrate do not have anything in rcS.d/ depending
6056 on them. Some packages have already been updated, like the sudo
6057 package, while others are still left to do. I wish I had time to work
6058 on this myself, but real live constrains make it unlikely that I will
6059 find time to push this forward.
</p
>
6064 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6065 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6066 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6067 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6068 <description><p
>While at Debconf11, I have several times during discussions
6069 mentioned the issues I believe should be improved in Debian for its
6070 desktop to be useful for more people. The use case for this is my
6071 parents, which are currently running Kubuntu which solve the
6074 <p
>I suspect these four missing features are not very hard to
6075 implement. After all, they are present in Ubuntu, so if we wanted to
6076 do this in Debian we would have a source.
</p
>
6080 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6081 are new packages available for upgrades, a icon in the KDE status bar
6082 indicate this, and clicking on it will activate the simple upgrade
6083 tool to handle it. I have no problem guiding both of my parents
6084 through the process over the phone. If a kernel reboot is required,
6085 this too is indicated by the status bars and the upgrade tool. Last
6086 time I checked, nothing with the same features was working in KDE in
6089 <li
><strong
>Simple handling of missing Firefox browser
6090 plugins.
</strong
> When the browser encounter a MIME type it do not
6091 currently have a handler for, it will ask the user if the system
6092 should search for a package that would add support for this MIME type,
6093 and if the user say yes, the APT sources will be searched for packages
6094 advertising the MIME type in their control file (visible in the
6095 Packages file in the APT archive). If one or more packages are found,
6096 it is a simple click of the mouse to add support for the missing mime
6097 type. If the package require the user to accept some non-free
6098 license, this is explained to the user. The entire process make it
6099 more clear to the user why something do not work in the browser, and
6100 make the chances higher for the user to blame the web page authors and
6101 not the browser for any missing features.
</li
>
6103 <li
><strong
>Simple handling of missing multimedia codec/format
6104 handlers.
</strong
> When the media players encounter a format or codec
6105 it is not supporting, a dialog pop up asking the user if the system
6106 should search for a package that would add support for it. This
6107 happen with things like MP3, Windows Media or H
.264. The selection
6108 and installation procedure is very similar to the Firefox browser
6109 plugin handling. This is as far as I know implemented using a
6110 gstreamer hook. The end result is that the user easily get access to
6111 the codecs that are present from the APT archives available, while
6112 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6114 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6115 displaying a text/plain file in my Debian browser, it will propose to
6116 start emacs to show it. If I remember correctly, when doing the same
6117 in Kunbutu it show the file as a text file in the browser. At least I
6118 know Opera will show text files within the browser. I much prefer the
6119 latter behaviour.
</li
>
6123 <p
>There are other nice features as well, like the simplified suite
6124 upgrader, but given that I am the one mostly doing the dist-upgrade,
6125 it do not matter much.
</p
>
6127 <p
>I really hope we could get these features in place for the next
6128 Debian release. It would require the coordinated effort of several
6129 maintainers, but would make the end user experience a lot better.
</p
>
6134 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6135 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6137 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6138 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6139 site is build on Debian/Squeeze, and this platform was chosen because
6140 I am most familiar with Debian (being a Debian Developer for around
10
6141 years) because it is the latest stable Debian release which should get
6142 security support for a few years.
</p
>
6144 <p
>The web service is written in Perl, and depend on some perl modules
6145 that are missing in Debian at the moment. It would be great if these
6146 modules were added to the Debian archive, allowing anyone to set up
6147 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6148 in their own country using only Debian packages. The list of modules
6149 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6150 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6151 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6152 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6153 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6154 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6155 easier in the future.
</p
>
6157 <p
>Thanks to the great tools in Debian, getting the missing modules
6158 installed on my server was a simple call to
'cpan2deb Module::Name
'
6159 and
'dpkg -i
' to install the resulting package. But this leave me
6160 with the responsibility of tracking security problems, which I really
6161 do not have time for.
</p
>
6166 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6167 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6169 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6170 <description><p
>Here is a small update for my English readers. Most of my blog
6171 posts have been in Norwegian the last few weeks, so here is a short
6172 update in English.
</p
>
6174 <p
>The kids still keep me too busy to get much free software work
6175 done, but I did manage to organise a project to get a Norwegian port
6176 of the British service
6177 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6178 and it has been running for a month now. The entire project has been
6179 organised by me and two others. Around Christmas we gathered sponsors
6180 to fund the development work. In January I drafted a contract with
6181 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6182 and in February the development took place. Most of it involved
6183 converting the source to use GPS coordinates instead of British
6184 easting/northing, and the resulting code should be a lot easier to get
6185 running in any country by now. The Norwegian
6186 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6187 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6188 source and the source for administrative borders in Norway, and
6189 support for this had to be added/fixed.
</p
>
6191 <p
>The Norwegian version went live March
3th, and we spent the weekend
6192 polishing the system before we announced it March
7th. The system is
6193 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6194 problem reports in a few weeks. Soon we hope to announce the Android
6195 and iPhone versions making it even easier to report problems with the
6196 public infrastructure.
</p
>
6198 <p
>Perhaps something to consider for those of you in countries without
6199 such service?
</p
>
6204 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6205 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6207 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6208 <description><p
>The last few days I have looked at ways to track open security
6209 issues here at my work with the University of Oslo. My idea is that
6210 it should be possible to use the information about security issues
6211 available on the Internet, and check our locally
6212 maintained/distributed software against this information. It should
6213 allow us to verify that no known security issues are forgotten. The
6214 CVE database listing vulnerabilities seem like a great central point,
6215 and by using the package lists from Debian mapped to CVEs provided by
6216 the testing security team, I believed it should be possible to figure
6217 out which security holes were present in our free software
6218 collection.
</p
>
6220 <p
>After reading up on the topic, it became obvious that the first
6221 building block is to be able to name software packages in a unique and
6222 consistent way across data sources. I considered several ways to do
6223 this, for example coming up with my own naming scheme like using URLs
6224 to project home pages or URLs to the Freshmeat entries, or using some
6225 existing naming scheme. And it seem like I am not the first one to
6226 come across this problem, as MITRE already proposed and implemented a
6227 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6228 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6229 software, hardware and other platform components. The CPE ids are
6230 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6231 Vulnerability Database
</a
>, allowing me to look up know security
6232 issues for any CPE name. With this in place, all I need to do is to
6233 locate the CPE id for the software packages we use at the university.
6234 This is fairly trivial (I google for
'cve cpe $package
' and check the
6235 NVD entry if a CVE for the package exist).
</p
>
6237 <p
>To give you an example. The GNU gzip source package have the CPE
6238 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6239 check out, one could look up
6240 <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
6241 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6242 The most recent one is
6243 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6244 and at the bottom of the NVD page for this vulnerability the complete
6245 list of affected versions is provided.
</p
>
6247 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6248 for offline processing of issues. Using this dump, I
've written a
6249 small script taking a list of CPEs as input and list all CVEs
6250 affecting the packages represented by these CPEs. One give it CPEs
6251 with version numbers as specified above and get a list of open
6252 security issues out.
</p
>
6254 <p
>Of course for this approach to be useful, the quality of the NVD
6255 information need to be high. For that to happen, I believe as many as
6256 possible need to use and contribute to the NVD database. I notice
6258 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6259 map from CVE to CPE
</a
>, indicating that they are using the CPE
6260 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6262 <p
>To get an idea about the quality for free software, I spent some
6263 time making it possible to compare the CVE database from Debian with
6264 the CVE database in NVD. The result look fairly good, but there are
6265 some inconsistencies in NVD (same software package having several
6266 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6267 Debian believe are affected by a CVE). Hope to find time to improve
6268 the quality of NVD, but that require being able to get in touch with
6269 someone maintaining it. So far my three emails with questions and
6270 corrections have not seen any reply, but I hope contact can be
6271 established soon.
</p
>
6273 <p
>An interesting application for CPEs is cross platform package
6274 mapping. It would be useful to know which packages in for example
6275 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6276 this would be trivial if all linux distributions provided CPE entries
6277 for their packages.
</p
>
6282 <title>Which module is loaded for a given PCI and USB device?
</title>
6283 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6284 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6285 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6286 <description><p
>In the
6287 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6288 package in Debian, there is a script to report useful information
6289 about the running hardware for use when people report missing
6290 information. One part of this script that I find very useful when
6291 debugging hardware problems, is the part mapping loaded kernel module
6292 to the PCI device it claims. It allow me to quickly see if the kernel
6293 module I expect is driving the hardware I am struggling with. To see
6294 the output, make sure discover-data is installed and run
6295 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6296 one of my machines like this:
</p
>
6300 10de:
03eb i2c_nforce2
6303 10de:
03f0 snd_hda_intel
6312 <p
>The code in question look like this, slightly modified for
6313 readability and to drop the output to file descriptor
3:
</p
>
6316 if [ -d /sys/bus/pci/devices/ ] ; then
6317 echo loaded pci modules:
6319 cd /sys/bus/pci/devices/
6320 for address in * ; do
6321 if [ -d
"$address/driver/module
" ] ; then
6322 module=`cd $address/driver/module ; pwd -P | xargs basename`
6323 if grep -q
"^$module
" /proc/modules ; then
6324 address=$(echo $address |sed s/
0000://)
6325 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6326 echo
"$id $module
"
6335 <p
>Similar code could be used to extract USB device module
6339 if [ -d /sys/bus/usb/devices/ ] ; then
6340 echo loaded usb modules:
6342 cd /sys/bus/usb/devices/
6343 for address in * ; do
6344 if [ -d
"$address/driver/module
" ] ; then
6345 module=`cd $address/driver/module ; pwd -P | xargs basename`
6346 if grep -q
"^$module
" /proc/modules ; then
6347 address=$(echo $address |sed s/
0000://)
6348 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6349 if [
"$id
" ] ; then
6350 echo
"$id $module
"
6360 <p
>This might perhaps be something to include in other tools as
6366 <title>How to test if a laptop is working with Linux
</title>
6367 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6369 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6370 <description><p
>The last few days I have spent at work here at the
<a
6371 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6372 batch of computers will work with Linux. Every year for the last few
6373 years the university have organised shared bid of a few thousand
6374 computers, and this year HP won the bid. Two different desktops and
6375 five different laptops are on the list this year. We in the UNIX
6376 group want to know which one of these computers work well with RHEL
6377 and Ubuntu, the two Linux distributions we currently handle at the
6378 university.
</p
>
6380 <p
>My test method is simple, and I share it here to get feedback and
6381 perhaps inspire others to test hardware as well. To test, I PXE
6382 install the OS version of choice, and log in as my normal user and run
6383 a few applications and plug in selected pieces of hardware. When
6384 something fail, I make a note about this in the test matrix and move
6385 on. If I have some spare time I try to report the bug to the OS
6386 vendor, but as I only have the machines for a short time, I rarely
6387 have the time to do this for all the problems I find.
</p
>
6389 <p
>Anyway, to get to the point of this post. Here is the simple tests
6390 I perform on a new model.
</p
>
6394 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6395 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6396 RHEL5 and Debian Edu/Squeeze.
</li
>
6398 <li
>Is X.org working? If the graphical login screen show up after
6399 installation, X.org is working.
</li
>
6401 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6402 package mesa-utils on Ubuntu) and writing down the frames per second
6403 reported by the program.
</li
>
6405 <li
>Is sound working? With Gnome and KDE, a sound is played when
6406 logging in, and if I can hear this the test is successful. If there
6407 are several audio exits on the machine, I try them all and check if
6408 the Gnome/KDE audio mixer can control where to send the sound. I
6409 normally test this by playing
6410 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6411 video
</a
> in Firefox/Iceweasel.
</li
>
6413 <li
>Is the USB subsystem working? I test this by plugging in a USB
6414 memory stick and see if Gnome/KDE notices this.
</li
>
6416 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6417 I have lying around, and see if Gnome/KDE notices this.
</li
>
6419 <li
>Is any built in camera working? Test using cheese, and see if a
6420 picture from the v4l device show up.
</li
>
6422 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6423 any bluetooth devices are discovered. In my office, I normally see a
6426 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6427 memory modules lying around, and stick them in and see if Gnome/KDE
6428 notice this.
</li
>
6430 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6431 special button work, and if the laptop continue to work after
6434 <li
>For laptops, is the extra buttons working, like audio level,
6435 adjusting background light, switching on/off external video output,
6436 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6437 laptop to laptop, so I just write down which are working and which are
6440 <li
>Some laptops have smart card readers, finger print readers,
6441 acceleration sensors etc. I rarely test these, as I do not know how
6442 to quickly test if they are working or not, so I only document their
6443 existence.
</li
>
6447 <p
>By now I suspect you are really curious what the test results are
6448 for the HP machines I am testing. I
'm not done yet, so I will report
6449 the test results later. For now I can report that HP
8100 Elite work
6450 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6451 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6452 can see, I have most machines left to test. One interesting
6453 observation is that Ubuntu Lucid has almost twice the frame rate than
6454 RHEL6 with glxgears. No idea why.
</p
>
6459 <title>Some thoughts on BitCoins
</title>
6460 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6461 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6462 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6463 <description><p
>As I continue to explore
6464 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6465 what properties the system have, and how it will be affected by laws
6466 and regulations here in Norway. Here are some random notes.
</p
>
6468 <p
>One interesting thing to note is that since the transactions are
6469 verified using a peer to peer network, all details about a transaction
6470 is known to everyone. This means that if a BitCoin address has been
6471 published like I did with mine in my initial post about BitCoin, it is
6472 possible for everyone to see how many BitCoins have been transfered to
6473 that address. There is even a web service to look at the details for
6474 all transactions. There I can see that my address
6475 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6476 have received
16.06 Bitcoin, the
6477 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6478 address of Simon Phipps have received
181.97 BitCoin and the address
6479 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6480 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6481 every one of you that donated bitcoins to support my activity. The
6482 fact that anyone can see how much money was transfered to a given
6483 address make it more obvious why the BitCoin community recommend to
6484 generate and hand out a new address for each transaction. I
'm told
6485 there is no way to track which addresses belong to a given person or
6486 organisation without the person or organisation revealing it
6487 themselves, as Simon, EFF and I have done.
</p
>
6489 <p
>In Norway, and in most other countries, there are laws and
6490 regulations limiting how much money one can transfer across the border
6491 without declaring it. There are money laundering, tax and accounting
6492 laws and regulations I would expect to apply to the use of BitCoin.
6493 If the Skolelinux foundation
6494 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6495 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6496 normal bank transfers like EFF is doing, how should this be accounted?
6497 Given that it is impossible to know if money can cross the border or
6498 not, should everything or nothing be declared? What exchange rate
6499 should be used when calculating taxes? Would receivers have to pay
6500 income tax if the foundation were to pay Skolelinux contributors in
6501 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6503 <p
>For a currency to be useful and successful, it must be trusted and
6504 accepted by a lot of users. It must be possible to get easy access to
6505 the currency (as a wage or using currency exchanges), and it must be
6506 easy to spend it. At the moment BitCoin seem fairly easy to get
6507 access to, but there are very few places to spend it. I am not really
6508 a regular user of any of the vendor types currently accepting BitCoin,
6509 so I wonder when my kind of shop would start accepting BitCoins. I
6510 would like to buy electronics, travels and subway tickets, not herbs
6511 and books. :) The currency is young, and this will improve over time
6512 if it become popular, but I suspect regular banks will start to lobby
6513 to get BitCoin declared illegal if it become popular. I
'm sure they
6514 will claim it is helping fund terrorism and money laundering (which
6515 probably would be true, as is any currency in existence), but I
6516 believe the problems should be solved elsewhere and not by blaming
6517 currencies.
</p
>
6519 <p
>The process of creating new BitCoins is called mining, and it is
6520 CPU intensive process that depend on a bit of luck as well (as one is
6521 competing against all the other miners currently spending CPU cycles
6522 to see which one get the next lump of cash). The
"winner
" get
50
6523 BitCoin when this happen. Yesterday I came across the obvious way to
6524 join forces to increase ones changes of getting at least some coins,
6525 by coordinating the work on mining BitCoins across several machines
6526 and people, and sharing the result if one is lucky and get the
50
6528 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6529 if this sounds interesting. I have not had time to try to set up a
6530 machine to participate there yet, but have seen that running on ones
6531 own for a few days have not yield any BitCoins througth mining
6534 <p
>Update
2010-
12-
15: Found an
<a
6535 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6536 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6537 it was interesting to read. The arguments presented seem to be
6538 equally valid for gold, which was used as a currency for many years.
</p
>
6543 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6544 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6545 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6546 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6547 <description><p
>With this weeks lawless
6548 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6549 attacks
</a
> on Wikileak and
6550 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6551 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6552 not be trusted to handle money transactions.
6554 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6555 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6556 mine mentioned earlier. I decided to follow Simon
's example, and get
6557 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6558 some help from my friend to get it all running, and he even handed me
6559 some bitcoins to get started. I even donated a few bitcoins to Simon
6560 for helping me remember BitCoin.
</p
>
6562 <p
>So, what is bitcoins, you probably wonder? It is a digital
6563 crypto-currency, decentralised and handled using peer-to-peer
6564 networks. It allows anonymous transactions and prohibits central
6565 control over the transactions, making it impossible for governments
6566 and companies alike to block donations and other transactions. The
6567 source is free software, and while the key dependency wxWidgets
2.9
6568 for the graphical user interface is missing in Debian, the command
6569 line client builds just fine. Hopefully Jonas
6570 <a href=
"http://bugs.debian.org/
578157">will get the package into
6571 Debian
</a
> soon.
</p
>
6573 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6574 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6575 bitcoins
</a
> when selling services and goods, and there are even
6576 currency
"stock
" markets where the exchange rate is decided. There
6577 are not many users so far, but the concept seems promising. If you
6578 want to get started and lack a friend with any bitcoins to spare,
6580 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6581 bitcoin at the time of writing). Use
6582 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6583 on the current exchange rates.
</p
>
6585 <p
>As an experiment, I have decided to set up bitcoind on one of my
6586 machines. If you want to support my activity, please send Bitcoin
6587 donations to the address
6588 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6593 <title>Why isn
't Debian Edu using VLC?
</title>
6594 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6596 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6597 <description><p
>In the latest issue of Linux Journal, the readers choices were
6598 presented, and the winner among the multimedia player were VLC.
6599 Personally, I like VLC, and it is my player of choice when I first try
6600 to play a video file or stream. Only if VLC fail will I drag out
6601 gmplayer to see if it can do better. The reason is mostly the failure
6602 model and trust. When VLC fail, it normally pop up a error message
6603 reporting the problem. When mplayer fail, it normally segfault or
6604 just hangs. The latter failure mode drain my trust in the program.
<p
>
6606 <p
>But even if VLC is my player of choice, we have choosen to use
6607 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6608 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6609 plugin to play web videos seamlessly, and the VLC browser plugin is
6610 not very good. For example, it lack in-line control buttons, so there
6611 is no way for the user to pause the video. Also, when I
6612 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6613 tested the browser plugins
</a
> available in Debian, the VLC plugin
6614 failed on several video pages where mplayer based plugins worked. If
6615 the browser plugin for VLC was as good as the gecko-mediaplayer
6616 package (which uses mplayer), we would switch.
</P
>
6618 <p
>While VLC is a good player, its user interface is slightly
6619 annoying. The most annoying feature is its inconsistent use of
6620 keyboard shortcuts. When the player is in full screen mode, its
6621 shortcuts are different from when it is playing the video in a window.
6622 For example, space only work as pause when in full screen mode. I
6623 wish it had consisten shortcuts and that space also would work when in
6624 window mode. Another nice shortcut in gmplayer is [enter] to restart
6625 the current video. It is very nice when playing short videos from the
6626 web and want to restart it when new people arrive to have a look at
6627 what is going on.
</p
>
6632 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6633 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6634 <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>
6635 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6636 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6637 upgrade testing of the
6638 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6639 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6640 This seem like a very good idea, so I adjusted by test scripts and
6641 can now present the updated result from today:
</p
>
6643 <p
>This is for Gnome:
</p
>
6645 <p
>Installed using apt-get, missing with aptitude
</p
>
6647 <blockquote
><p
>
6652 browser-plugin-gnash
6659 freedesktop-sound-theme
6661 gconf-defaults-service
6676 gnome-desktop-environment
6680 gnome-session-canberra
6685 gstreamer0.10-fluendo-mp3
6691 libapache2-mod-dnssd
6694 libaprutil1-dbd-sqlite3
6697 libboost-date-time1.42
.0
6698 libboost-python1.42
.0
6699 libboost-thread1.42
.0
6701 libchamplain-gtk-
0.4-
0
6703 libclutter-gtk-
0.10-
0
6710 libfreerdp-plugins-standard
6725 libgnomepanel2.24-cil
6730 libgtksourceview2.0-common
6731 libmono-addins-gui0.2-cil
6732 libmono-addins0.2-cil
6733 libmono-cairo2.0-cil
6734 libmono-corlib2.0-cil
6735 libmono-i18n-west2.0-cil
6736 libmono-posix2.0-cil
6737 libmono-security2.0-cil
6738 libmono-sharpzip2.84-cil
6739 libmono-system2.0-cil
6742 libndesk-dbus-glib1.0-cil
6743 libndesk-dbus1.0-cil
6753 libtelepathy-farsight0
6762 nautilus-sendto-empathy
6766 python-aptdaemon-gtk
6768 python-beautifulsoup
6783 python-gtksourceview2
6794 python-pkg-resources
6801 python-twisted-conch
6807 python-zope.interface
6812 rhythmbox-plugin-cdrecorder
6819 system-config-printer-udev
6821 telepathy-mission-control-
5
6832 </p
></blockquote
>
6834 <p
>Installed using apt-get, removed with aptitude
</p
>
6836 <blockquote
><p
>
6842 fast-user-switch-applet
6861 libgtksourceview2.0-
0
6863 libsdl1.2debian-alsa
6869 system-config-printer
6874 </p
></blockquote
>
6876 <p
>Installed using aptitude, missing with apt-get
</p
>
6878 <blockquote
><p
>
6879 gstreamer0.10-gnomevfs
6880 </p
></blockquote
>
6882 <p
>Installed using aptitude, removed with apt-get
</p
>
6884 <blockquote
><p
>
6886 </p
></blockquote
>
6888 <p
>This is for KDE:
</p
>
6890 <p
>Installed using apt-get, missing with aptitude
</p
>
6892 <blockquote
><p
>
6894 </p
></blockquote
>
6896 <p
>Installed using apt-get, removed with aptitude
</p
>
6898 <blockquote
><p
>
6901 </p
></blockquote
>
6903 <p
>Installed using aptitude, missing with apt-get
</p
>
6905 <blockquote
><p
>
6919 kdeartwork-emoticons
6921 kdeartwork-theme-icon
6925 kdebase-workspace-bin
6926 kdebase-workspace-data
6940 kscreensaver-xsavers
6955 plasma-dataengines-workspace
6957 plasma-desktopthemes-artwork
6958 plasma-runners-addons
6959 plasma-scriptengine-googlegadgets
6960 plasma-scriptengine-python
6961 plasma-scriptengine-qedje
6962 plasma-scriptengine-ruby
6963 plasma-scriptengine-webkit
6964 plasma-scriptengines
6965 plasma-wallpapers-addons
6966 plasma-widget-folderview
6967 plasma-widget-networkmanagement
6971 xscreensaver-data-extra
6973 xscreensaver-gl-extra
6974 xscreensaver-screensaver-bsod
6975 </p
></blockquote
>
6977 <p
>Installed using aptitude, removed with apt-get
</p
>
6979 <blockquote
><p
>
6981 google-gadgets-common
6999 libggadget-qt-
1.0-
0b
7004 libkonqsidebarplugin4a
7013 libplasma-geolocation-interface4
7015 libplasmagenericshell4
7029 libsmokeknewstuff2-
3
7030 libsmokeknewstuff3-
3
7032 libsmokektexteditor3
7040 libsmokeqtnetwork4-
3
7046 libsmokeqtuitools4-
3
7058 plasma-dataengines-addons
7059 plasma-scriptengine-superkaramba
7060 plasma-widget-lancelot
7061 plasma-widgets-addons
7062 plasma-widgets-workspace
7066 update-notifier-common
7067 </p
></blockquote
>
7069 <p
>Running apt-get autoremove made the results using apt-get and
7070 aptitude a bit more similar, but there are still quite a lott of
7071 differences. I have no idea what packages should be installed after
7072 the upgrade, but hope those that do can have a look.
</p
>
7077 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7078 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7080 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7081 <description><p
>Most of the computers in use by the
7082 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7083 are virtual machines. And they have been Xen machines running on a
7084 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7085 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7086 bit harder that it could have been, because we set up the Xen virtual
7087 machines to get the virtual partitions from LVM, which as far as I
7088 know is not supported by KVM. So to migrate, we had to convert
7089 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7092 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7093 nice recipe
</a
> to do this, and wrote the following script to do the
7094 migration. It uses qemu-img from the qemu package to make the disk
7095 image, parted to partition it, losetup and kpartx to present the disk
7096 image partions as devices, and dd to copy the data. I NFS mounted the
7097 new servers storage area on the old server to do the migration.
</p
>
7103 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7108 if [ -z
"$
1" ] ; then
7109 echo
"Usage: $
0 &lt;hostname
&gt;
"
7115 if [ ! -e /dev/vg_data/$host-disk ] ; then
7116 echo
"error: unable to find LVM volume for $host
"
7120 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7121 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7122 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7123 totalsize=$(( ( $disksize + $swapsize ) ))
7126 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7127 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7129 parted $img mklabel msdos
7130 parted $img mkpart primary linux-swap
0 $disksize
7131 parted $img mkpart primary ext2 $disksize $totalsize
7132 parted $img set
1 boot on
7135 losetup /dev/loop0 $img
7136 kpartx -a /dev/loop0
7138 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7139 fsck.ext3 -f /dev/mapper/loop0p1 || true
7140 mkswap /dev/mapper/loop0p2
7142 kpartx -d /dev/loop0
7143 losetup -d /dev/loop0
7146 <p
>The script is perhaps so simple that it is not copyrightable, but
7147 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7149 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7150 the new disk image attached, installed grub-pc and linux-image-
686 and
7151 set up grub to boot from the disk image. After this, the KVM machines
7152 seem to work just fine.
</p
>
7157 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7158 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7159 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7160 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7161 <description><p
>I
'm still running upgrade testing of the
7162 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7163 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7164 status. Here is a short update based on a test I ran
20101118.
</p
>
7166 <p
>I still do not know what a correct migration should look like, so I
7167 report any differences between apt and aptitude and hope someone else
7168 can see if anything should be changed.
</p
>
7170 <p
>This is for Gnome:
</p
>
7172 <p
>Installed using apt-get, missing with aptitude
</p
>
7174 <blockquote
><p
>
7175 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7176 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7177 dmz-cursor-theme empathy empathy-common finger
7178 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7179 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7180 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7181 gnome-cards-data gnome-codec-install gnome-core
7182 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7183 gnome-search-tool gnome-session-canberra gnome-spell
7184 gnome-system-log gnome-themes-extras gnome-themes-more
7185 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7186 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7187 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7188 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7189 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7190 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7191 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7192 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7193 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7194 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7195 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7196 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7197 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7198 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7199 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7200 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7201 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7202 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7203 libmono-security2.0-cil libmono-sharpzip2.84-cil
7204 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7205 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7206 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7207 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7208 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7209 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7210 libxalan2-java libxerces2-java media-player-info mesa-utils
7211 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7212 nautilus-sendto-empathy openoffice.org-writer2latex
7213 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7214 python-aptdaemon python-aptdaemon-gtk python-axiom
7215 python-beautifulsoup python-bugbuddy python-clientform
7216 python-coherence python-configobj python-crypto python-cupshelpers
7217 python-cupsutils python-eggtrayicon python-elementtree
7218 python-epsilon python-evolution python-feedparser python-gdata
7219 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7220 python-gtksourceview2 python-httplib2 python-louie python-mako
7221 python-markupsafe python-mechanize python-nevow python-notify
7222 python-opengl python-openssl python-pam python-pkg-resources
7223 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7224 python-tagpy python-twisted-bin python-twisted-conch
7225 python-twisted-core python-twisted-web python-utidylib python-webkit
7226 python-xdg python-zope.interface remmina remmina-plugin-data
7227 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7228 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7229 software-center svgalibg1 system-config-printer-udev
7230 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7231 totem totem-coherence totem-mozilla totem-plugins
7232 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7234 </p
></blockquote
>
7236 Installed using apt-get, removed with aptitude
7238 <blockquote
><p
>
7239 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7240 epiphany-extensions epiphany-gecko evolution-exchange
7241 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7242 gedit-common gnome-app-install gnome-games gnome-games-data
7243 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7244 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7245 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7246 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7247 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7248 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7249 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7250 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7251 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7252 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7253 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7254 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7255 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7256 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7257 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7258 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7259 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7260 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7261 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7262 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7263 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7264 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7265 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7266 sound-juicer swfdec-gnome system-config-printer totem-common
7267 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7268 </p
></blockquote
>
7270 <p
>Installed using aptitude, missing with apt-get
</p
>
7272 <blockquote
><p
>
7273 gstreamer0.10-gnomevfs
7274 </p
></blockquote
>
7276 <p
>Installed using aptitude, removed with apt-get
</p
>
7278 <blockquote
><p
>
7280 </p
></blockquote
>
7282 <p
>This is for KDE:
</p
>
7284 <p
>Installed using apt-get, missing with aptitude
</p
>
7286 <blockquote
><p
>
7287 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7288 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7289 ghostscript-x git gnome-audio gnugo granatier gs-common
7290 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7291 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7292 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7293 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7294 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7295 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7296 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7297 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7298 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7299 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7300 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7301 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7302 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7303 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7304 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7305 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7306 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7307 libkrossui4 libmailtools-perl libmime-tools-perl
7308 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7309 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7310 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7311 lirc luatex marble networkstatus noatun-plugins
7312 openoffice.org-writer2latex palapeli palapeli-data parley
7313 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7314 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7315 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7317 </p
></blockquote
>
7319 <p
>Installed using apt-get, removed with aptitude
</p
>
7321 <blockquote
><p
>
7322 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7323 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7324 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7325 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7326 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7327 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7328 kitchensync kiten kjumpingcube klatin klettres klickety klines
7329 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7330 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7331 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7332 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7333 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7334 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7335 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7336 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7337 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7338 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7339 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7340 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7341 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7342 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7343 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7344 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7345 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7346 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7347 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7348 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7349 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7350 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7351 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7352 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7353 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7354 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7355 </p
></blockquote
>
7357 <p
>Installed using aptitude, missing with apt-get
</p
>
7359 <blockquote
><p
>
7360 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7361 kdeartwork kdebase kdebase-apps kdebase-workspace
7362 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7363 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7364 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7365 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7366 xscreensaver-screensaver-bsod
7367 </p
></blockquote
>
7369 <p
>Installed using aptitude, removed with apt-get
</p
>
7371 <blockquote
><p
>
7372 kdebase-bin konq-plugins konqueror
7373 </p
></blockquote
>
7378 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7379 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7380 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7381 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7382 <description><p
>Answering
7383 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7384 call from the Gnash project
</a
> for
7385 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7386 current source, I have set up a virtual KVM machine on the Debian
7387 Edu/Skolelinux virtualization host to test the git source on
7388 Debian/Squeeze. I hope this can help the developers in getting new
7389 releases out more often.
</p
>
7391 <p
>As the developers want less main-stream build platforms tested to,
7392 I have considered setting up a
<a
7393 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7394 machine as well. I have also considered using the kfreebsd
7395 architecture in Debian as a file server in NUUG to get access to the
5
7396 TB zfs volume we currently use to store DV video. Because of this, I
7397 finally got around to do a test installation of Debian/Squeeze with
7398 kfreebsd. Installation went fairly smooth, thought I noticed some
7399 visual glitches in the cdebconf dialogs (black cursor left on the
7400 screen at random locations). Have not gotten very far with the
7401 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7402 fatal problem. Have to spend some more time on it to see if it is
7403 useful as a file server for NUUG. Will try to find time to set up a
7404 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7409 <title>Debian in
3D
</title>
7410 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7411 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7412 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7413 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7415 <p
>3D printing is just great. I just came across this Debian logo in
7417 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7418 thingiverse blog
</a
>.
</p
>
7423 <title>Software updates
2010-
10-
24</title>
7424 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7425 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7426 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7427 <description><p
>Some updates.
</p
>
7429 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7430 raise money for the project is going well. The lower limit of
10
7431 signers was reached in
24 hours, and so far
13 people have signed it.
7432 More signers and more funding is most welcome, and I am really curious
7433 how far we can get before the time limit of December
24 is reached.
7436 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7437 about what appear to be a great code coverage tool capable of
7438 generating code coverage stats without any changes to the source code.
7440 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7441 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7442 It is missing in Debian, but the git source built just fine in Squeeze
7443 after I installed libelf-dev, libdwarf-dev, pkg-config and
7444 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7445 solvable. I hope kcov make it into Debian soon.
</p
>
7447 <p
>Finally found time to wrap up the release notes for
<a
7448 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7449 new alpha release of Debian Edu
</a
>, and just published the second
7450 alpha test release of the Squeeze based Debian Edu /
7451 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7452 release. Give it a try if you need a complete linux solution for your
7453 school, including central infrastructure server, workstations, thin
7454 client servers and diskless workstations. A nice touch added
7455 yesterday is RDP support on the thin client servers, for windows
7456 clients to get a Linux desktop on request.
</p
>
7461 <title>Some notes on Flash in Debian and Debian Edu
</title>
7462 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7463 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7464 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7465 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7466 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7467 second most popular used package that is missing in Debian. The sixth
7468 most popular is flashplayer-mozilla. This is a clear indication that
7469 working flash is important for Debian users. Around
10 percent of the
7470 users submitting data to popcon.debian.org have this package
7471 installed.
</p
>
7473 <p
>In the report written by Lars Risan in August
2008
7474 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7475 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7476 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7477 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7478 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7479 web sites require Flash to work, and lacking working Flash support in
7480 the web browser and the problems with installing it was perceived as a
7481 good reason to stay with Windows.
</p
>
7483 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7484 said to be the retarded cousin that did not really understand
7485 everything you told him but could work fairly well. This was a
7486 comment regarding the problems Linux have with proprietary formats and
7487 non-standard web pages, and is sad because it exposes a fairly common
7488 understanding of whose fault it is if web pages that only work in for
7489 example Internet Explorer
6 fail to work on Firefox, and funny because
7490 it explain very well how annoying it is for users when Linux
7491 distributions do not work with the documents they receive or the web
7492 pages they want to visit.
</p
>
7494 <p
>This is part of the reason why I believe it is important for Debian
7495 and Debian Edu to have a well working Flash implementation in the
7496 distribution, to get at least popular sites as Youtube and Google
7497 Video to working out of the box. For Squeeze, Debian have the chance
7498 to include the latest version of Gnash that will make this happen, as
7499 the new release
0.8.8 was published a few weeks ago and is resting in
7500 unstable. The new version work with more sites that version
0.8.7.
7501 The Gnash maintainers have asked for a freeze exception, but the
7502 release team have not had time to reply to it yet. I hope they agree
7503 with me that Flash is important for the Debian desktop users, and thus
7504 accept the new package into Squeeze.
</p
>
7509 <title>Circular package dependencies harms apt recovery
</title>
7510 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7512 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7513 <description><p
>I discovered this while doing
7514 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7515 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7516 in Debian still got circular dependencies, and it is often claimed
7517 that apt and aptitude should be able to handle this just fine, but
7518 some times these dependency loops causes apt to fail.
</p
>
7520 <p
>An example is from todays
7521 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7522 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7523 causes perl-modules to fail to upgrade. The cause is simple. If a
7524 package fail to unpack, then only part of packages with the circular
7525 dependency might end up being unpacked when unpacking aborts, and the
7526 ones already unpacked will fail to configure in the recovery phase
7527 because its dependencies are unavailable.
</p
>
7529 <p
>In this log, the problem manifest itself with this error:
</p
>
7531 <blockquote
><pre
>
7532 dpkg: dependency problems prevent configuration of perl-modules:
7533 perl-modules depends on perl (
>=
5.10.1-
1); however:
7534 Version of perl on system is
5.10.0-
19lenny
2.
7535 dpkg: error processing perl-modules (--configure):
7536 dependency problems - leaving unconfigured
7537 </pre
></blockquote
>
7539 <p
>The perl/perl-modules circular dependency is already
7540 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7541 hopefully be solved as soon as possible, but it is not the only one,
7542 and each one of these loops in the dependency tree can cause similar
7543 failures. Of course, they only occur when there are bugs in other
7544 packages causing the unpacking to fail, but it is rather nasty when
7545 the failure of one package causes the problem to become worse because
7546 of dependency loops.
</p
>
7549 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7550 tireless effort by Bill Allombert
</a
>, the number of circular
7552 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7553 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7555 <p
>Todays testing also exposed a bug in
7556 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7557 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7558 apt-get and aptitude, the latter possibly caused by some circular
7559 dependency. Reported both to BTS to try to get someone to look at
7565 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7566 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7568 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7569 <description><p
>This is a
7570 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7572 <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
7574 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7575 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7577 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7578 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7579 and dhcp3-server-ldap in Debian use the LDAP server. The two
7580 implementations are quite different in how they use LDAP.
</p
>
7582 To get this information, I started slapd with debugging enabled and
7583 dumped the debug output to a file to get the LDAP searches performed
7584 on a Debian Edu main-server. Here is a summary.
7586 <p
><strong
>powerdns
</strong
></p
>
7588 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7589 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7592 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7593 One
"strict
" mode where the forward and reverse DNS lookups are done
7594 using the same LDAP objects, and a
"tree
" mode where the forward and
7595 reverse entries are in two different subtrees in LDAP with a structure
7596 based on the DNS names, as in tjener.intern and
7597 2.2.0.10.in-addr.arpa.
</p
>
7599 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7600 base, and uses a
"base
" scoped search for the DNS name by adding
7601 "dc=tjener,dc=intern,
" to the base with a filter for
7602 "(associateddomain=tjener.intern)
" for the forward entry and
7603 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7604 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7605 forward entries, it is looking for attributes named dnsttl, arecord,
7606 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7607 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7608 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7609 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7610 spfrecord and modifytimestamp. For reverse entries it is looking for
7611 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7612 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7613 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7614 ldapsearch commands could look like this:
</p
>
7616 <blockquote
><pre
>
7617 ldapsearch -h ldap \
7618 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7619 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7620 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7621 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7622 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7623 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7625 ldapsearch -h ldap \
7626 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7627 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7628 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7629 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7630 srvrecord naptrrecord modifytimestamp
7631 </pre
></blockquote
>
7633 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7634 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7635 example LDAP objects used there. In addition to these objects, the
7636 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7637 also exist.
</p
>
7639 <blockquote
><pre
>
7640 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7642 objectclass: dnsdomain
7643 objectclass: domainrelatedobject
7646 associateddomain: tjener.intern
7648 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7650 objectclass: dnsdomain2
7651 objectclass: domainrelatedobject
7653 ptrrecord: tjener.intern
7654 associateddomain:
2.2.0.10.in-addr.arpa
7655 </pre
></blockquote
>
7657 <p
>In strict mode, the server behaves differently. When looking for
7658 forward DNS entries, it is doing a
"subtree
" scoped search with the
7659 same base as in the tree mode for a object with filter
7660 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7661 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7662 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7663 naptrrecord and modifytimestamp. For reverse entires it also do a
7664 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7665 and the requested attributes are associateddomain, dnsttl and
7666 modifytimestamp. In short, in strict mode the objects with ptrrecord
7667 go away, and the arecord attribute in the forward object is used
7670 <p
>The forward and reverse searches can be simulated using ldapsearch
7671 like this:
</p
>
7673 <blockquote
><pre
>
7674 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7675 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7676 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7677 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7678 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7679 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7681 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7682 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7683 </pre
></blockquote
>
7685 <p
>In addition to the forward and reverse searches , there is also a
7686 search for SOA records, which behave similar to the forward and
7687 reverse lookups.
</p
>
7689 <p
>A thing to note with the PowerDNS behaviour is that it do not
7690 specify any objectclass names, and instead look for the attributes it
7691 need to generate a DNS reply. This make it able to work with any
7692 objectclass that provide the needed attributes.
</p
>
7694 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7695 dnsdomain2 schemas. The latter is used for reverse entries like
7696 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7698 <p
>In Debian Edu, we have created DNS objects using the object classes
7699 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7700 attributes) and domainrelatedobject (for associatedDomain). The use
7701 of structural object classes make it impossible to combine these
7702 classes with the object classes used by DHCP.
</p
>
7704 <p
>There are other schemas that could be used too, for example the
7705 dnszone structural object class used by Gosa and bind-sdb for the DNS
7706 attributes combined with the domainrelatedobject object class, but in
7707 this case some unused attributes would have to be included as well
7708 (zonename and relativedomainname).
</p
>
7710 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7711 mode and not use any of the existing objectclasses (dnsdomain,
7712 dnsdomain2 and dnszone) when one want to combine the DNS information
7713 with DHCP information, and instead create a auxiliary object class
7714 defined something like this (using the attributes defined for
7715 dnsdomain and dnsdomain2 or dnszone):
</p
>
7717 <blockquote
><pre
>
7718 objectclass ( some-oid NAME
'dnsDomainAux
'
7721 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7722 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7723 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7724 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7725 A6Record $ DNAMERecord
7727 </pre
></blockquote
>
7729 <p
>This will allow any object to become a DNS entry when combined with
7730 the domainrelatedobject object class, and allow any entity to include
7731 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7732 developers asking for their view on this schema and if they are
7733 interested in providing such schema with PowerDNS, and I hope my
7734 message will be accepted into their mailing list soon.
</p
>
7736 <p
><strong
>ISC dhcp
</strong
></p
>
7738 <p
>The DHCP server searches for specific objectclass and requests all
7739 the object attributes, and then uses the attributes it want. This
7740 make it harder to figure out exactly what attributes are used, but
7741 thanks to the working example in Debian Edu I can at least get an idea
7742 what is needed without having to read the source code.
</p
>
7744 <p
>In the DHCP server configuration, the LDAP base to use and the
7745 search filter to use to locate the correct dhcpServer entity is
7746 stored. These are the relevant entries from
7747 /etc/dhcp3/dhcpd.conf:
</p
>
7749 <blockquote
><pre
>
7750 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7751 ldap-dhcp-server-cn
"dhcp
";
7752 </pre
></blockquote
>
7754 <p
>The DHCP server uses this information to nest all the DHCP
7755 configuration it need. The cn
"dhcp
" is located using the given LDAP
7756 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7757 search result is this entry:
</p
>
7759 <blockquote
><pre
>
7760 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7763 objectClass: dhcpServer
7764 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7765 </pre
></blockquote
>
7767 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7768 subtree with DHCP configuration. The DHCP configuration subtree base
7769 is located using a base scope search with base
"cn=DHCP
7770 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7771 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7772 The search result is this entry:
</p
>
7774 <blockquote
><pre
>
7775 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7778 objectClass: dhcpService
7779 objectClass: dhcpOptions
7780 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7781 dhcpStatements: ddns-update-style none
7782 dhcpStatements: authoritative
7783 dhcpOption: smtp-server code
69 = array of ip-address
7784 dhcpOption: www-server code
72 = array of ip-address
7785 dhcpOption: wpad-url code
252 = text
7786 </pre
></blockquote
>
7788 <p
>Next, the entire subtree is processed, one level at the time. When
7789 all the DHCP configuration is loaded, it is ready to receive requests.
7790 The subtree in Debian Edu contain objects with object classes
7791 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7792 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7793 and information about netmasks, dynamic range etc. Leaving out the
7794 details here because it is not relevant for the focus of my
7795 investigation, which is to see if it is possible to merge dns and dhcp
7796 related computer objects.
</p
>
7798 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7799 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7800 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7801 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7802 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7805 <blockquote
><pre
>
7806 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7809 objectClass: dhcpHost
7810 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7811 dhcpStatements: fixed-address hostname
7812 </pre
></blockquote
>
7814 <p
>There is less flexiblity in the way LDAP searches are done here.
7815 The object classes need to have fixed names, and the configuration
7816 need to be stored in a fairly specific LDAP structure. On the
7817 positive side, the invidiual dhcpHost entires can be anywhere without
7818 the DN pointed to by the dhcpServer entries. The latter should make
7819 it possible to group all host entries in a subtree next to the
7820 configuration entries, and this subtree can also be shared with the
7821 DNS server if the schema proposed above is combined with the dhcpHost
7822 structural object class.
7824 <p
><strong
>Conclusion
</strong
></p
>
7826 <p
>The PowerDNS implementation seem to be very flexible when it come
7827 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7828 come to the the LDAP structure, the
"strict
" mode is very flexible,
7829 allowing DNS objects to be stored anywhere under the base cn specified
7830 in the configuration.
</p
>
7832 <p
>The DHCP implementation on the other hand is very inflexible, both
7833 regarding which LDAP schemas to use and which LDAP structure to use.
7834 I guess one could implement ones own schema, as long as the
7835 objectclasses and attributes have the names used, but this do not
7836 really help when the DHCP subtree need to have a fairly fixed
7837 structure.
</p
>
7839 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7840 this might work for Debian Edu:
</p
>
7842 <blockquote
><pre
>
7844 cn=machine-info (dhcpService) - dhcpServiceDN points here
7845 cn=dhcp (dhcpServer)
7846 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7847 cn=
10.0.2.0 (dhcpSubnet)
7848 cn=group1 (dhcpGroup/dhcpOptions)
7849 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7850 cn=
192.168.0.0 (dhcpSubnet)
7851 cn=group1 (dhcpGroup/dhcpOptions)
7852 ou=machines - PowerDNS base points here
7853 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7854 </pre
></blockquote
>
7856 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7857 entries to be in the dhcpGroup subtrees, the entries can be stored
7858 there instead of a common machines subtree, and the PowerDNS base
7859 would have to be moved one level up to the machine-info subtree.
</p
>
7861 <p
>The combined object under the machines subtree would look something
7862 like this:
</p
>
7864 <blockquote
><pre
>
7865 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7868 objectClass: dhcpHost
7869 objectclass: domainrelatedobject
7870 objectclass: dnsDomainAux
7871 associateddomain: hostname.intern
7872 arecord:
10.11.12.13
7873 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7874 dhcpStatements: fixed-address hostname.intern
7875 </pre
></blockquote
>
7877 </p
>One could even add the LTSP configuration associated with a given
7878 machine, as long as the required attributes are available in a
7879 auxiliary object class.
</p
>
7884 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7885 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7887 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7888 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7889 DHCP services in Debian Edu to use the same LDAP objects for a given
7890 computer, to avoid the possibility of having a inconsistent state for
7891 a computer in LDAP (as in DHCP but no DNS entry or the other way
7892 around) and make it easier to add computers to LDAP.
</p
>
7894 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7895 information finally found a solution that seem to work.
</p
>
7897 <p
>The old setup required three LDAP objects for a given computer.
7898 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7899 we switch powerdns to use its strict LDAP method (ldap-method=strict
7900 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7901 merged into one while making it impossible to transfer the reverse map
7902 to a slave DNS server.
</p
>
7904 <p
>If we also replace the object class used to get the DNS related
7905 attributes to one allowing these attributes to be combined with the
7906 dhcphost object class, we can merge the DNS and DHCP entries into one.
7907 I
've written such object class in the dnsdomainaux.schema file (need
7908 proper OIDs, but that is a minor issue), and tested the setup. It
7909 seem to work.
</p
>
7911 <p
>With this test setup in place, we can get away with one LDAP object
7912 for both DNS and DHCP, and even the LTSP configuration I suggested in
7913 an earlier email. The combined LDAP object will look something like
7916 <blockquote
><pre
>
7917 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7919 objectClass: dhcphost
7920 objectclass: domainrelatedobject
7921 objectclass: dnsdomainaux
7922 associateddomain: hostname.intern
7923 arecord:
10.11.12.13
7924 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7925 dhcpstatements: fixed-address hostname
7927 </pre
></blockquote
>
7929 <p
>The DNS server uses the associateddomain and arecord entries, while
7930 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7931 before asking DNS to resolve the fixed-adddress. LTSP will use
7932 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7934 <p
>I am not yet sure if I can get the DHCP server to look for its
7935 dhcphost in a different location, to allow us to put the objects
7936 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7937 that. If I can
't figure out a way to do that, we can still get rid of
7938 the hosts subtree and move all its content into the DHCP Config tree
7939 (which probably should be renamed to be more related to the new
7940 content. I suspect cn=dnsdhcp,ou=services or something like that
7941 might be a good place to put it.
</p
>
7943 <p
>If you want to help out with implementing this for Debian Edu,
7944 please contact us on debian-edu@lists.debian.org.
</p
>
7949 <title>Idea for storing LTSP configuration in LDAP
</title>
7950 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7951 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7952 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7953 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7954 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7955 clients, and that this can be used to fetch configuration from LDAP if
7956 Debian Edu choose to store configuration there.
</p
>
7958 <p
>Armed with this information, I got inspired and wrote a test module
7959 to get configuration from LDAP. The idea is to look up the MAC
7960 address of the client in LDAP, and look for attributes on the form
7961 ltspconfigsetting=value, and use this to export SETTING=value to the
7962 LTSP clients.
</p
>
7964 <p
>The goal is to be able to store the LTSP configuration attributes
7965 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7966 allowing us to store all information about a computer in one place.
</p
>
7968 <p
>This is a untested draft implementation, and I welcome feedback on
7969 this approach. A real LDAP schema for the ltspClientAux objectclass
7970 need to be written. Comments, suggestions, etc?
</p
>
7972 <blockquote
><pre
>
7973 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7975 # Fetch LTSP client settings from LDAP based on MAC address
7977 # Uses ethernet address as stored in the dhcpHost objectclass using
7978 # the dhcpHWAddress attribute or ethernet address stored in the
7979 # ieee802Device objectclass with the macAddress attribute.
7981 # This module is written to be schema agnostic, and only depend on the
7982 # existence of attribute names.
7984 # The LTSP configuration variables are saved directly using a
7985 # ltspConfig prefix and uppercasing the rest of the attribute name.
7986 # To set the SERVER variable, set the ltspConfigServer attribute.
7988 # Some LDAP schema should be created with all the relevant
7989 # configuration settings. Something like this should work:
7991 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7994 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7996 LDAPSERVER=$(debian-edu-ldapserver)
7997 if [
"$LDAPSERVER
" ] ; then
7998 LDAPBASE=$(debian-edu-ldapserver -b)
7999 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8000 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8001 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8002 grep
'^ltspConfig
' | while read attr value ; do
8003 # Remove prefix and convert to upper case
8004 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8005 # bass value on to clients
8006 eval
"$attr=$value; export $attr
"
8010 </pre
></blockquote
>
8012 <p
>I
'm not sure this shell construction will work, because I suspect
8013 the while block might end up in a subshell causing the variables set
8014 there to not show up in ltsp-config, but if that is the case I am sure
8015 the code can be restructured to make sure the variables are passed on.
8016 I expect that can be solved with some testing. :)
</p
>
8018 <p
>If you want to help out with implementing this for Debian Edu,
8019 please contact us on debian-edu@lists.debian.org.
</p
>
8021 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8022 configuration in LDAP that was created around year
2000 by
8023 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8024 Xperience, Inc.,
2000</a
>. I found its
8025 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8026 personal home page over at redhat.com.
</p
>
8031 <title>jXplorer, a very nice LDAP GUI
</title>
8032 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8034 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8035 <description><p
>Since
8036 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8037 last post
</a
> about available LDAP tools in Debian, I was told about a
8038 LDAP GUI that is even better than luma. The java application
8039 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8040 moving LDAP objects and subtrees using drag-and-drop, and can
8041 authenticate using Kerberos. I have only tested the Kerberos
8042 authentication, but do not have a LDAP setup allowing me to rewrite
8043 LDAP with my test user yet. It is
8044 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8045 Debian
</a
> testing and unstable at the moment. The only problem I
8046 have with it is how it handle errors. If something go wrong, its
8047 non-intuitive behaviour require me to go through some query work list
8048 and remove the failing query. Nothing big, but very annoying.
</p
>
8053 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8054 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8056 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8057 <description><p
>Here is a short update on my
<a
8058 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8059 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8060 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8061 not reporting the status for KDE, because the upgrade crashes when
8062 aptitude try because of missing conflicts
8063 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8064 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8066 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8067 complete list of the installed packages. Based on this I see these
8068 differences when I did a test run today. As usual, I do not really
8069 know what the correct set of packages would be, but thought it best to
8070 publish the difference.
</p
>
8072 <p
>Installed using apt-get, missing with aptitude
</p
>
8074 <blockquote
><p
>
8075 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8076 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8077 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8078 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8079 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8080 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8081 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8082 python-gtkmozembed svgalibg1 xserver-xephyr zip
8083 </p
></blockquote
>
8085 <p
>Installed using apt-get, removed with aptitude
</p
>
8087 <blockquote
><p
>
8088 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8089 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8090 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8091 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8092 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8093 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8094 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8095 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8096 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8097 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8098 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8099 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8100 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8101 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8102 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8103 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8104 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8105 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8106 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8107 mysql-common swfdec-gnome totem-gstreamer wodim
8108 </p
></blockquote
>
8110 <p
>Installed using aptitude, missing with apt-get
</p
>
8112 <blockquote
><p
>
8113 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8114 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8115 xserver-xorg-input-all xserver-xorg-input-evdev
8116 xserver-xorg-input-kbd xserver-xorg-input-mouse
8117 xserver-xorg-input-synaptics xserver-xorg-video-all
8118 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8119 xserver-xorg-video-chips xserver-xorg-video-cirrus
8120 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8121 xserver-xorg-video-glint xserver-xorg-video-i128
8122 xserver-xorg-video-i740 xserver-xorg-video-mach64
8123 xserver-xorg-video-mga xserver-xorg-video-neomagic
8124 xserver-xorg-video-nouveau xserver-xorg-video-nv
8125 xserver-xorg-video-r128 xserver-xorg-video-radeon
8126 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8127 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8128 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8129 xserver-xorg-video-sis xserver-xorg-video-sisusb
8130 xserver-xorg-video-tdfx xserver-xorg-video-tga
8131 xserver-xorg-video-trident xserver-xorg-video-tseng
8132 xserver-xorg-video-vesa xserver-xorg-video-vmware
8133 xserver-xorg-video-voodoo
8134 </p
></blockquote
>
8136 <p
>Installed using aptitude, removed with apt-get
</p
>
8138 <blockquote
><p
>
8139 deskbar-applet xserver-xorg xserver-xorg-core
8140 xserver-xorg-input-wacom xserver-xorg-video-intel
8141 xserver-xorg-video-openchrome
8142 </p
></blockquote
>
8144 <p
>I was told on IRC that the xorg-xserver package was
8145 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8146 in git
</a
> today to try to get apt-get to not remove xorg completely.
8147 No idea when it hits Squeeze, but when it does I hope it will reduce
8148 the difference somewhat.
8153 <title>LUMA, a very nice LDAP GUI
</title>
8154 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8155 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8156 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8157 <description><p
>The last few days I have been looking into the status of the LDAP
8158 directory in Debian Edu, and in the process I started to miss a GUI
8159 tool to browse the LDAP tree. The only one I was able to find in
8160 Debian/Squeeze and Lenny is
8161 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8162 be a great tool to get a overview of the current LDAP directory
8163 populated by default in Skolelinux. Thanks to it, I have been able to
8164 find empty and obsolete subtrees, misplaced objects and duplicate
8165 objects. It will be installed by default in Debian/Squeeze. If you
8166 are working with LDAP, give it a go. :)
</p
>
8168 <p
>I did notice one problem with it I have not had time to report to
8169 the BTS yet. There is no .desktop file in the package, so the tool do
8170 not show up in the Gnome and KDE menus, but only deep down in in the
8171 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8174 <p
>I have not yet been able to get it to modify the tree yet. I would
8175 like to move objects and remove subtrees directly in the GUI, but have
8176 not found a way to do that with LUMA yet. So in the mean time, I use
8177 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8179 <p
>If you have tips on other GUI tools for LDAP that might be useful
8180 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8182 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8183 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8184 useful GUI alternative. It seem like a good tool, but is unmaintained
8185 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8186 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8191 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8192 <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>
8193 <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>
8194 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8195 <description><p
>A while back, I
8196 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8197 about the fact
</a
> that it is not possible with the provided schemas
8198 for storing DNS and DHCP information in LDAP to combine the two sets
8199 of information into one LDAP object representing a computer.
</p
>
8201 <p
>In the mean time, I discovered that a simple fix would be to make
8202 the dhcpHost object class auxiliary, to allow it to be combined with
8203 the dNSDomain object class, and thus forming one object for one
8204 computer when storing both DHCP and DNS information in LDAP.
</p
>
8206 <p
>If I understand this correctly, it is not safe to do this change
8207 without also changing the assigned number for the object class, and I
8208 do not know enough about LDAP schema design to do that properly for
8209 Debian Edu.
</p
>
8211 <p
>Anyway, for future reference, this is how I believe we could change
8213 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8214 schema
</a
> to solve at least part of the problem with the LDAP schemas
8215 available today from IETF.
</p
>
8218 --- dhcp.schema (revision
65192)
8219 +++ dhcp.schema (working copy)
8221 objectclass (
2.16.840.1.113719.1.203.6.6
8222 NAME
'dhcpHost
'
8223 DESC
'This represents information about a particular client
'
8227 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8228 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8231 <p
>I very much welcome clues on how to do this properly for Debian
8232 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8233 package, and should thus be free to rewrite it as we see fit.
</p
>
8235 <p
>If you want to help out with implementing this for Debian Edu,
8236 please contact us on debian-edu@lists.debian.org.
</p
>
8241 <title>Calling tasksel like the installer, while still getting useful output
</title>
8242 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8244 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8245 <description><p
>A few times I have had the need to simulate the way tasksel
8246 installs packages during the normal debian-installer run. Until now,
8247 I have ended up letting tasksel do the work, with the annoying problem
8248 of not getting any feedback at all when something fails (like a
8249 conffile question from dpkg or a download that fails), using code like
8252 <blockquote
><pre
>
8253 export DEBIAN_FRONTEND=noninteractive
8254 tasksel --new-install
8255 </pre
></blockquote
>
8257 This would invoke tasksel, let its automatic task selection pick the
8258 tasks to install, and continue to install the requested tasks without
8259 any output what so ever.
8261 Recently I revisited this problem while working on the automatic
8262 package upgrade testing, because tasksel would some times hang without
8263 any useful feedback, and I want to see what is going on when it
8264 happen. Then it occured to me, I can parse the output from tasksel
8265 when asked to run in test mode, and use that aptitude command line
8266 printed by tasksel then to simulate the tasksel run. I ended up using
8269 <blockquote
><pre
>
8270 export DEBIAN_FRONTEND=noninteractive
8271 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8273 </pre
></blockquote
>
8275 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8276 --without-recommends -o APT::Install-Recommends=no -y install
8277 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8278 ~pimportant
</tt
>", which will install the gnome desktop task, the
8279 laptop task and all packages with priority standard , required and
8280 important, just like tasksel would have done it during
8281 installation.
</p
>
8283 <p
>A better approach is probably to extend tasksel to be able to
8284 install packages without using debconf-apt-progress, for use cases
8285 like this.
</p
>
8290 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8291 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8292 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8293 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8294 <description><p
>My
8295 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8296 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8297 finally made the upgrade logs available from
8298 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8299 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8300 apt and aptitude, and found their differences interesting. This time
8301 I will only focus on their removal plans.
</p
>
8303 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8304 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8305 surprising part is that it want to remove xorg and all
8306 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8307 sure why. When asking aptitude to do the same, it want to remove
129
8308 packages, but most of them are library packages I suspect are no
8309 longer needed. Both of them want to remove bluetooth packages, which
8310 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8312 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8313 which seem like a bad idea and xorg the same way as with Gnome. Asking
8314 aptitude for the same, it wants to remove
192 packages, none which are
8315 too surprising.
</p
>
8317 <p
>I guess the removal of xorg during upgrades should be investigated
8318 and avoided, and perhaps others as well. Here are the complete list
8319 of planned removals. The complete logs is available from the URL
8320 above. Note if you want to repeat these tests, that the upgrade test
8321 for kde+apt-get hung in the tasksel setup because of dpkg asking
8322 conffile questions. No idea why. I worked around it by using
8323 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8326 <p
><b
>apt-get gnome
72</b
>
8327 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8328 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8329 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8330 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8331 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8332 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8333 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8334 xserver-xorg-input-kbd xserver-xorg-input-mouse
8335 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8336 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8337 xserver-xorg-video-ati xserver-xorg-video-chips
8338 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8339 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8340 xserver-xorg-video-glint xserver-xorg-video-i128
8341 xserver-xorg-video-i740 xserver-xorg-video-imstt
8342 xserver-xorg-video-intel xserver-xorg-video-mach64
8343 xserver-xorg-video-mga xserver-xorg-video-neomagic
8344 xserver-xorg-video-nsc xserver-xorg-video-nv
8345 xserver-xorg-video-openchrome xserver-xorg-video-r128
8346 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8347 xserver-xorg-video-rendition xserver-xorg-video-s3
8348 xserver-xorg-video-s3virge xserver-xorg-video-savage
8349 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8350 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8351 xserver-xorg-video-tga xserver-xorg-video-trident
8352 xserver-xorg-video-tseng xserver-xorg-video-v4l
8353 xserver-xorg-video-vesa xserver-xorg-video-vga
8354 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8355 xulrunner-
1.9-gnome-support
</p
>
8357 <p
><b
>aptitude gnome
129</b
>
8359 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8360 djvulibre-desktop finger gnome-app-install gnome-mount
8361 gnome-network-admin gnome-spell gnome-vfs-obexftp
8362 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8363 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8364 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8365 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8366 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8367 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8368 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8369 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8370 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8371 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8372 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8373 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8374 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8375 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8376 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8377 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8378 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8379 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8380 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8381 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8382 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8383 openoffice.org-writer2latex openssl-blacklist p7zip
8384 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8385 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8386 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8387 swfdec-mozilla totem-gstreamer update-manager wodim
8388 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8389 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8392 <p
><b
>apt-get kde
82</b
>
8394 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8395 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8396 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8397 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8398 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8399 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8400 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8401 xserver-xorg-input-kbd xserver-xorg-input-mouse
8402 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8403 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8404 xserver-xorg-video-ati xserver-xorg-video-chips
8405 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8406 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8407 xserver-xorg-video-glint xserver-xorg-video-i128
8408 xserver-xorg-video-i740 xserver-xorg-video-imstt
8409 xserver-xorg-video-intel xserver-xorg-video-mach64
8410 xserver-xorg-video-mga xserver-xorg-video-neomagic
8411 xserver-xorg-video-nsc xserver-xorg-video-nv
8412 xserver-xorg-video-openchrome xserver-xorg-video-r128
8413 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8414 xserver-xorg-video-rendition xserver-xorg-video-s3
8415 xserver-xorg-video-s3virge xserver-xorg-video-savage
8416 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8417 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8418 xserver-xorg-video-tga xserver-xorg-video-trident
8419 xserver-xorg-video-tseng xserver-xorg-video-v4l
8420 xserver-xorg-video-vesa xserver-xorg-video-vga
8421 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8423 <p
><b
>aptitude kde
192</b
>
8424 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8425 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8426 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8427 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8428 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8429 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8430 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8431 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8432 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8433 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8434 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8435 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8436 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8437 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8438 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8439 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8440 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8441 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8442 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8443 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8444 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8445 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8446 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8447 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8448 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8449 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8450 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8451 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8452 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8453 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8454 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8455 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8456 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8457 texlive-common texlive-doc-base texlive-fonts-recommended
8458 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8459 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8460 xulrunner-
1.9</p
>
8466 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8467 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8469 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8470 <description><p
>The last few days I have done some upgrade testing in Debian, to
8471 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8472 have been discovered and reported in the process
8473 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8474 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8475 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8476 kdebase-workspace-data), and to get a more regular testing going on, I
8477 am working on a script to automate the test.
</p
>
8479 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8480 Gnome or KDE desktop installation inside the chroot before upgrading
8481 it. To ensure no services are started in the chroot, a policy-rc.d
8482 script is inserted. To make sure tasksel believe it is to install a
8483 desktop on a laptop, the tasksel tests are replaced in the chroot
8484 (only acceptable because this is a throw-away chroot).
</p
>
8486 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8487 currently always fail because udev refuses to upgrade with the kernel
8488 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8489 is created. The bug report
8490 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8491 this problem do not trigger in a chroot, but I touch the file anyway
8492 to make sure the upgrade go well. Testing on virtual and real
8493 hardware have failed me because of udev so far, and creating this file
8494 do the trick in such settings anyway. This is a
8495 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8496 issue
</a
> and the current udev behaviour is intended by the udev
8497 maintainer because he lack the resources to rewrite udev to keep
8498 working with old kernels or something like that. I really wish the
8499 udev upstream would keep udev backwards compatible, to avoid such
8500 upgrade problem, but given that they fail to do so, I guess
8501 documenting the way out of this mess is the best option we got for
8502 Debian Squeeze.
</p
>
8504 <p
>Anyway, back to the task at hand, testing upgrades. This test
8505 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8508 <blockquote
><pre
>
8512 if [
"$
1" ] ; then
8521 exec
&lt; /dev/null
8523 mirror=http://ftp.skolelinux.org/debian
8524 tmpdir=chroot-$from-upgrade-$to-$desktop
8526 debootstrap $from $tmpdir $mirror
8527 chroot $tmpdir aptitude update
8528 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8532 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8536 mount -t proc proc $tmpdir/proc
8537 # Make sure proc is unmounted also on failure
8538 trap exit_cleanup EXIT INT
8540 chroot $tmpdir aptitude -y install debconf-utils
8542 # Make sure tasksel autoselection trigger. It need the test scripts
8543 # to return the correct answers.
8544 echo tasksel tasksel/desktop multiselect $desktop | \
8545 chroot $tmpdir debconf-set-selections
8547 # Include the desktop and laptop task
8548 for test in desktop laptop ; do
8549 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8553 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8556 DEBIAN_FRONTEND=noninteractive
8557 DEBIAN_PRIORITY=critical
8558 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8559 chroot $tmpdir tasksel --new-install
8561 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8562 chroot $tmpdir aptitude update
8563 touch $tmpdir/etc/udev/kernel-upgrade
8564 chroot $tmpdir aptitude -y dist-upgrade
8566 </pre
></blockquote
>
8568 <p
>I suspect it would be useful to test upgrades with both apt-get and
8569 with aptitude, but I have not had time to look at how they behave
8570 differently so far. I hope to get a cron job running to do the test
8571 regularly and post the result on the web. The Gnome upgrade currently
8572 work, while the KDE upgrade fail because of the bug in
8573 kdebase-workspace-data
</p
>
8575 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8576 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8577 post, so I will refrain from trying. I can report that for Gnome,
8578 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8579 remove and
1 not upgraded and
1024MB need to be downloaded while for
8580 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8581 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8583 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8584 is able to migrate to dependency based boot sequencing and parallel
8585 booting without a hitch. Was unsure if there were still bugs with
8586 packages failing to clean up their obsolete init.d script during
8587 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8593 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8594 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8596 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8597 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8598 scripts to migrate (some of) their operations to upstart job while
8599 keeping the init.d for hurd and kfreebsd. The packages with such
8600 needs will need a way to get their init.d scripts to behave
8601 differently when used with sysvinit and with upstart. Because of
8602 this, I had a look at the environment variables set when a init.d
8603 script is running under upstart, and when it is not.
</p
>
8605 <p
>With upstart, I notice these environment variables are set when a
8606 script is started from rcS.d/ (ignoring some irrelevant ones like
8609 <blockquote
><pre
>
8615 UPSTART_EVENTS=startup
8617 UPSTART_JOB=rc-sysinit
8618 </pre
></blockquote
>
8620 <p
>With sysvinit, these environment variables are set for the same
8623 <blockquote
><pre
>
8624 INIT_VERSION=sysvinit-
2.88
8629 </pre
></blockquote
>
8631 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8632 sysvinit are not set by upstart. Not sure if it is intentional or not
8633 to not be compatible with sysvinit in this regard.
</p
>
8635 <p
>For scripts needing to behave differently when upstart is used,
8636 looking for the UPSTART_JOB environment variable seem to be a good
8642 <title>A manual for standards wars...
</title>
8643 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8645 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8646 <description><p
>Via the
8647 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8648 of Rob Weir
</a
> I came across the very interesting essay named
8649 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8650 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8651 following the standards wars of today.
</p
>
8656 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8657 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8658 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8659 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8660 <description><p
>When using sitesummary at a site to track machines, it is possible
8661 to get a list of the machine types in use thanks to the DMI
8662 information extracted from each machine. The script to do so is
8663 included in the sitesummary package, and here is example output from
8664 the Skolelinux build servers:
</p
>
8666 <blockquote
><pre
>
8667 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8669 Dell Computer Corporation
1
8672 eserver xSeries
345 -[
8670M1X]-
1
8676 </pre
></blockquote
>
8678 <p
>The quality of the report depend on the quality of the DMI tables
8679 provided in each machine. Here there are Intel machines without model
8680 information listed with Intel as vendor and no model, and virtual Xen
8681 machines listed as [no-dmi-info]. One can add -l as a command line
8682 option to list the individual machines.
</p
>
8684 <p
>A larger list is
8685 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8686 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8687 provide the basic sitesummary report publicly. In their report there
8688 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8689 their machines, and as sitesummary is available in both distributions,
8690 it is trivial to get all of them to report to the same central
8691 collector.
</p
>
8696 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8697 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8698 <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>
8699 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8700 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8701 start at boot when an NVidia video card is used is handled. The
8702 problem seem to be that the nvidia X.org driver uses a long time to
8703 initialize, and this duration is longer than kdm is configured to
8706 <p
>I came across two bugs related to this issue,
8707 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8708 against initscripts and passed on to nvidia-glx when it became obvious
8709 that the nvidia drivers were involved, and
8710 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8711 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8713 <p
>To me, it seem that no-one is interested in actually solving the
8714 problem nvidia video card owners experience and make sure the Debian
8715 distribution work out of the box for these users. The nvidia driver
8716 maintainers expect kdm to be set up to wait longer, while kdm expect
8717 the nvidia driver maintainers to fix the driver to start faster, and
8718 while they wait for each other I guess the users end up switching to a
8719 distribution that work for them. I have no idea what the solution is,
8720 but I am pretty sure that waiting for each other is not it.
</p
>
8722 <p
>I wonder why we end up handling bugs this way.
</p
>
8727 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8728 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8730 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8731 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8732 The feature seem to hold up pretty well, but three fairly serious
8733 issues are known and should be solved:
8737 <li
>The wicd package seen to
8738 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8739 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8740 parallel booting is enabled. No idea why, but the wicd maintainer
8741 seem to be on the case.
</li
>
8743 <li
>The nvidia X driver seem to
8744 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8745 triggered more easily when parallel booting is in effect. The
8746 maintainer is on the case.
</li
>
8748 <li
>The sysv-rc package fail to properly enable dependency based boot
8749 sequencing (the shutdown is broken) when old file-rc users
8750 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8751 sysv-rc. One way to solve it would be for file-rc to create
8752 /etc/init.d/.legacy-bootordering, and another is to try to make
8753 sysv-rc more robust. Will investigate some more and probably upload a
8754 workaround in sysv-rc to help those trying to move from file-rc to
8755 sysv-rc get a working shutdown.
</li
>
8757 </ul
></p
>
8759 <p
>All in all not many surprising issues, and all of them seem
8760 solvable before Squeeze is released. In addition to these there are
8761 some packages with bugs in their dependencies and run level settings,
8762 which I expect will be fixed in a reasonable time span.
</p
>
8764 <p
>If you report any problems with dependencies in init.d scripts to
8765 the BTS, please usertag the report to get it to show up at
8766 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8767 list of usertagged bugs related to this
</a
>.
</p
>
8769 <p
>Update: Correct bug number to file-rc issue.
</p
>
8774 <title>More flexible firmware handling in debian-installer
</title>
8775 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8777 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8778 <description><p
>After a long break from debian-installer development, I finally
8779 found time today to return to the project. Having to spend less time
8780 working dependency based boot in debian, as it is almost complete now,
8781 definitely helped freeing some time.
</p
>
8783 <p
>A while back, I ran into a problem while working on Debian Edu. We
8784 include some firmware packages on the Debian Edu CDs, those needed to
8785 get disk and network controllers working. Without having these
8786 firmware packages available during installation, it is impossible to
8787 install Debian Edu on the given machine, and because our target group
8788 are non-technical people, asking them to provide firmware packages on
8789 an external medium is a support pain. Initially, I expected it to be
8790 enough to include the firmware packages on the CD to get
8791 debian-installer to find and use them. This proved to be wrong.
8792 Next, I hoped it was enough to symlink the relevant firmware packages
8793 to some useful location on the CD (tried /cdrom/ and
8794 /cdrom/firmware/). This also proved to not work, and at this point I
8795 found time to look at the debian-installer code to figure out what was
8796 going to work.
</p
>
8798 <p
>The firmware loading code is in the hw-detect package, and a closer
8799 look revealed that it would only look for firmware packages outside
8800 the installation media, so the CD was never checked for firmware
8801 packages. It would only check USB sticks, floppies and other
8802 "external
" media devices. Today I changed it to also look in the
8803 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8804 solve the problem I ran into with Debian edu. I also changed it to
8805 look in /firmware/, to make sure the installer also find firmware
8806 provided in the initrd when booting the installer via PXE, to allow us
8807 to provide the same feature in the PXE setup included in Debian
8810 <p
>To make sure firmware deb packages with a license questions are not
8811 activated without asking if the license is accepted, I extended
8812 hw-detect to look for preinst scripts in the firmware packages, and
8813 run these before activating the firmware during installation. The
8814 license question is asked using debconf in the preinst, so this should
8815 solve the issue for the firmware packages I have looked at so far.
</p
>
8817 <p
>If you want to discuss the details of these features, please
8818 contact us on debian-boot@lists.debian.org.
</p
>
8823 <title>Parallellized boot is now the default in Debian/unstable
</title>
8824 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8826 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8827 <description><p
>Since this evening, parallel booting is the default in
8828 Debian/unstable for machines using dependency based boot sequencing.
8829 Apparently the testing of concurrent booting has been wider than
8830 expected, if I am to believe the
8831 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8832 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8833 with the feature this weekend, to give us some time to detect any
8834 remaining problems before Squeeze is frozen. If serious problems are
8835 detected, it is simple to change the default back to sequential boot.
8836 The upload of the new sysvinit package also activate a new upstream
8839 More information about
8840 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8841 based boot sequencing
</a
> is available from the Debian wiki. It is
8842 currently possible to disable parallel booting when one run into
8843 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8845 <blockquote
><pre
>
8847 </pre
></blockquote
>
8849 <p
>If you report any problems with dependencies in init.d scripts to
8850 the BTS, please usertag the report to get it to show up at
8851 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8852 list of usertagged bugs related to this
</a
>.
</p
>
8857 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8858 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8860 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8861 <description><p
>In the recent Debian Edu versions, the
8862 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8863 system
</a
> is used to keep track of the machines in the school
8864 network. Each machine will automatically report its status to the
8865 central server after boot and once per night. The network setup is
8866 also reported, and using this information it is possible to get the
8867 MAC address of all network interfaces in the machines. This is useful
8868 to update the DHCP configuration.
</p
>
8870 <p
>To give some idea how to use sitesummary, here is a one-liner to
8871 ist all MAC addresses of all machines reporting to sitesummary. Run
8872 this on the collector host:
</p
>
8874 <blockquote
><pre
>
8875 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8876 </pre
></blockquote
>
8878 <p
>This will list all MAC addresses assosiated with all machine, one
8879 line per machine and with space between the MAC addresses.
</p
>
8881 <p
>To allow system administrators easier job at adding static DHCP
8882 addresses for hosts, it would be possible to extend this to fetch
8883 machine information from sitesummary and update the DHCP and DNS
8884 tables in LDAP using this information. Such tool is unfortunately not
8885 written yet.
</p
>
8890 <title>systemd, an interesting alternative to upstart
</title>
8891 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8892 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8893 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8894 <description><p
>The last few days a new boot system called
8895 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8897 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8899 to the free software world. I have not yet had time to play around
8900 with it, but it seem to be a very interesting alternative to
8901 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8902 a good alternative for Debian when we are able to switch to an event
8903 based boot system. Tollef is
8904 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8905 systemd into Debian, and I look forward to seeing how well it work. I
8906 like the fact that systemd handles init.d scripts with dependency
8907 information natively, allowing them to run in parallel where upstart
8908 at the moment do not.
</p
>
8910 <p
>Unfortunately do systemd have the same problem as upstart regarding
8911 platform support. It only work on recent Linux kernels, and also need
8912 some new kernel features enabled to function properly. This means
8913 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8914 system. Not sure how that will be handled if systemd proves to be the
8915 way forward.
</p
>
8917 <p
>In the mean time, based on the
8918 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8919 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8920 decided to enable full parallel booting as the default in Debian as
8921 soon as possible (probably this weekend or early next week), to see if
8922 there are any remaining serious bugs in the init.d dependencies. A
8923 new version of the sysvinit package implementing this change is
8924 already in experimental. If all go well, Squeeze will be released
8925 with parallel booting enabled by default.
</p
>
8930 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8931 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8932 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8933 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8934 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8935 complete, so complete that it is actually possible to run all the
8936 init.d scripts in parallell based on these dependencies. If you want
8937 to test your Squeeze system, make sure
8938 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8939 based boot sequencing
</a
> is enabled, and add this line to
8940 /etc/default/rcS:
</p
>
8942 <blockquote
><pre
>
8943 CONCURRENCY=makefile
8944 </pre
></blockquote
>
8946 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8947 scripts in parallel using the dependency information stored in
8948 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8949 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8950 to try to start the kdm and gdm scripts as early as possible, and will
8951 start the facilities required by kdm or gdm as early as possible to
8952 make this happen.
</p
>
8954 <p
>Give it a try, and see if you like the result. If some services
8955 fail to start properly, it is most likely because they have incomplete
8956 init.d script dependencies in their startup script (or some of their
8957 dependent scripts have incomplete dependencies). Report bugs and get
8958 the package maintainers to fix it. :)
</p
>
8960 <p
>Running scripts in parallel could be the default in Debian when we
8961 manage to get the init.d script dependencies complete and correct. I
8962 expect we will get there in Squeeze+
1, if we get manage to test and
8963 fix the remaining issues.
</p
>
8965 <p
>If you report any problems with dependencies in init.d scripts to
8966 the BTS, please usertag the report to get it to show up at
8967 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8968 list of usertagged bugs related to this
</a
>.
</p
>
8973 <title>Debian has switched to dependency based boot sequencing
</title>
8974 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8975 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8976 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8977 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8978 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8979 have been migrated to using dependency based boot sequencing. This
8980 conclude work me and others have been doing for the last three days.
8981 It feels great to see this finally part of the default Debian
8982 installation. Now we just need to weed out the last few problems that
8983 are bound to show up, to get everything ready for Squeeze.
</p
>
8985 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8986 fixing the more fundamental problem of handing the event based
8987 non-predictable kernel in the early boot.
</p
>
8992 <title>Taking over sysvinit development
</title>
8993 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8994 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8995 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8996 <description><p
>After several years of frustration with the lack of activity from
8997 the existing sysvinit upstream developer, I decided a few weeks ago to
8998 take over the package and become the new upstream. The number of
8999 patches to track for the Debian package was becoming a burden, and the
9000 lack of synchronization between the distribution made it hard to keep
9001 the package up to date.
</p
>
9003 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9004 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9005 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9006 and Fedora), based on the patches currently in use in these
9007 distributions. We Debian maintainers plan to move to this tarball as
9008 the new upstream as soon as we find time to do the merge. Since the
9009 new tarball was created, we agreed with Werner at SuSe to make a new
9010 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9011 development there. The project is registered and currently waiting
9012 for approval by the Savannah administrators, and as soon as it is
9013 approved, we will import the old versions from svn and continue
9014 working on the future release.
</p
>
9016 <p
>It is a bit ironic that this is done now, when some of the involved
9017 distributions are moving to upstart as a syvinit replacement.
</p
>
9022 <title>Debian boots quicker and quicker
</title>
9023 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9025 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9026 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9027 people involved in the boot system on Debian and Ubuntu, to see if we
9028 could find more ways to speed up the boot system. This was an Ubuntu
9030 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9031 gathering
</a
>. It was quite productive. We also discussed the future
9032 of boot systems, and ways to handle the increasing number of boot
9033 issues introduced by the Linux kernel becoming more and more
9034 asynchronous and event base. The Ubuntu approach using udev and
9035 upstart might be a good way forward. Time will show.
</p
>
9037 <p
>Anyway, there are a few ways at the moment to speed up the boot
9038 process in Debian. All of these should be applied to get a quick
9043 <li
>Use dash as /bin/sh.
</li
>
9045 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9046 clock is in UTC.
</li
>
9048 <li
>Install and activate the insserv package to enable
9049 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9050 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9054 These points are based on the Google summer of code work done by
9055 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9058 <p
>Support for makefile-style concurrency during boot was uploaded to
9059 unstable yesterday. When we tested it, we were able to cut
6 seconds
9060 from the boot sequence. It depend on very correct dependency
9061 declaration in all init.d scripts, so I expect us to find edge cases
9062 where the dependences in some scripts are slightly wrong when we start
9063 using this.
</p
>
9065 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9066 introduced by Raphael Geissert today, one that could affect the
9067 startup speed as well. Instead of starting some scripts concurrently
9068 from rcS.d/ and another set of scripts from rc2.d/, it would be
9069 possible to run a of them in the same process. A quick way to test
9070 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9071 insserv
'. Will need to test if that work. :)
</p
>
9076 <title>BSAs påstander om piratkopiering møter motstand
</title>
9077 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9079 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9080 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9081 programvareselskapene som Microsoft og Apple, publisert en rapport der
9082 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9083 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9085 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9086 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9087 dagene. Et spesielt interessant kommentar fra Sverige,
9088 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9089 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9092 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9093 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9094 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9095 exakta
", säger BSAs Sverigechef John Hugosson.
9098 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9099 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9100 piracy figures need a shot of reality
</a
> og
<a
9101 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9102 Copyright Treaty Work?
</a
></p
>
9104 <p
>Fant lenkene via
<a
9105 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9106 på Slashdot
</a
>.
</p
>
9111 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9112 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9114 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9115 <description><p
>Kom over
9116 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9117 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9118 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9119 jobber til daglig. En rask opptelling forteller meg at vi har
490
9120 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9121 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9122 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9127 <title>Kryptert harddisk - naturligvis
</title>
9128 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9130 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9131 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9132 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9133 når en tar tap av arbeidstid, fortrolige dokumenter,
9134 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9135 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9136 til at jeg har kryptert harddisken på både kontormaskinen og min
9137 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9138 komme på avveie, den første informasjon relatert til jobben min ved
9139 Universitetet i Oslo, og den andre relatert til blant annet
9140 foreningsarbeide. Kryptering av diskene gjør at det er lite
9141 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9142 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9143 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9144 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9145 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9146 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9147 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9148 det er gjort slik jeg gjør det er minimale, og gevinstene er
9149 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9150 maskinen reinstalleres og alt er tapt.
</p
>
9152 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9153 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9154 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9155 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9156 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9157 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9158 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9159 betydelige.
</p
>
9164 <title>Two projects that have improved the quality of free software a lot
</title>
9165 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9167 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9168 <description><p
>There are two software projects that have had huge influence on the
9169 quality of free software, and I wanted to mention both in case someone
9170 do not yet know them.
</p
>
9172 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9173 tool to detect and expose errors in the memory handling of programs.
9174 It is easy to use, all one need to do is to run
'valgrind program
',
9175 and it will report any problems on stdout. It is even better if the
9176 program include debug information. With debug information, it is able
9177 to report the source file name and line number where the problem
9178 occurs. It can report things like
'reading past memory block in file
9179 X line N, the memory block was allocated in file Y, line M
', and
9180 'using uninitialised value in control logic
'. This tool has made it
9181 trivial to investigate reproducible crash bugs in programs, and have
9182 reduced the number of this kind of bugs in free software a lot.
9184 <p
>The second one is
9185 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9186 a source code checker. It is able to process the source of a program
9187 and find problems in the logic without running the program. It
9188 started out as the Stanford Checker and became well known when it was
9189 used to find bugs in the Linux kernel. It is now a commercial tool
9190 and the company behind it is running
9191 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9192 free software community, where a lot of free software projects get
9193 their source checked for free. Several thousand defects have been
9194 found and fixed so far. It can find errors like
'lock L taken in file
9195 X line N is never released if exiting in line M
', or
'the code in file
9196 Y lines O to P can never be executed
'. The projects included in the
9197 community service project have managed to get rid of a lot of
9198 reliability problems thanks to Coverity.
</p
>
9200 <p
>I believe tools like this, that are able to automatically find
9201 errors in the source, are vital to improve the quality of software and
9202 make sure we can get rid of the crashing and failing software we are
9203 surrounded by today.
</p
>
9208 <title>No patch is not better than a useless patch
</title>
9209 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9210 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9211 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9212 <description><p
>Julien Blache
9213 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9214 patch is better than a useless patch
</a
>. I completely disagree, as a
9215 patch allow one to discuss a concrete and proposed solution, and also
9216 prove that the issue at hand is important enough for someone to spent
9217 time on fixing it. No patch do not provide any of these positive
9218 properties.
</p
>
9223 <title>Standardize on protocols and formats, not vendors and applications
</title>
9224 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9226 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9227 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9228 very good one to form a long lived computer infrastructure. It is the
9229 simple one, lost by many in todays computer industry: Standardize on
9230 open network protocols and open exchange/storage formats, not applications.
9231 Applications come and go, while protocols and files tend to stay, and
9232 thus one want to make it easy to change application and vendor, while
9233 avoiding conversion costs and locking users to a specific platform or
9234 application.
</p
>
9236 <p
>This approach make it possible to replace the client applications
9237 independently of the server applications. One can even allow users to
9238 use several different applications as long as they handle the selected
9239 protocol and format. In the normal case, only one client application
9240 is recommended and users only get help if they choose to use this
9241 application, but those that want to deviate from the easy path are not
9242 blocked from doing so.
</p
>
9244 <p
>It also allow us to replace the server side without forcing the
9245 users to replace their applications, and thus allow us to select the
9246 best server implementation at any moment, when scale and resouce
9247 requirements change.
</p
>
9249 <p
>I strongly recommend standardizing - on open network protocols and
9250 open formats, but I would never recommend standardizing on a single
9251 application that do not use open network protocol or open formats.
</p
>
9256 <title>Returning from Skolelinux developer gathering
</title>
9257 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9258 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9259 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9260 <description><p
>I
'm sitting on the train going home from this weekends Debian
9261 Edu/Skolelinux development gathering. I got a bit done tuning the
9262 desktop, and looked into the dynamic service location protocol
9263 implementation avahi. It look like it could be useful for us. Almost
9264 30 people participated, and I believe it was a great environment to
9265 get to know the Skolelinux system. Walter Bender, involved in the
9266 development of the Sugar educational platform, presented his stuff and
9267 also helped me improve my OLPC installation. He also showed me that
9268 his Turtle Art application can be used in standalone mode, and we
9269 agreed that I would help getting it packaged for Debian. As a
9270 standalone application it would be great for Debian Edu. We also
9271 tried to get the video conferencing working with two OLPCs, but that
9272 proved to be too hard for us. The application seem to need more work
9273 before it is ready for me. I look forward to getting home and relax
9279 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9280 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9281 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9282 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9283 <description><p
>The state of standardized LDAP schemas on Linux is far from
9284 optimal. There is RFC
2307 documenting one way to store NIS maps in
9285 LDAP, and a modified version of this normally called RFC
2307bis, with
9286 some modifications to be compatible with Active Directory. The RFC
9287 specification handle the content of a lot of system databases, but do
9288 not handle DNS zones and DHCP configuration.
</p
>
9290 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9291 we would like to store information about users, SMB clients/hosts,
9292 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9293 and LTSP configuration in LDAP. These objects have a lot in common,
9294 but with the current LDAP schemas it is not possible to have one
9295 object per entity. For example, one need to have at least three LDAP
9296 objects for a given computer, one with the SMB related stuff, one with
9297 DNS information and another with DHCP information. The schemas
9298 provided for DNS and DHCP are impossible to combine into one LDAP
9299 object. In addition, it is impossible to implement quick queries for
9300 netgroup membership, because of the way NIS triples are implemented.
9301 It just do not scale. I believe it is time for a few RFC
9302 specifications to cleam up this mess.
</p
>
9304 <p
>I would like to have one LDAP object representing each computer in
9305 the network, and this object can then keep the SMB (ie host key), DHCP
9306 (mac address/name) and DNS (name/IP address) settings in one place.
9307 It need to be efficently stored to make sure it scale well.
</p
>
9309 <p
>I would also like to have a quick way to map from a user or
9310 computer and to the net group this user or computer is a member.
</p
>
9312 <p
>Active Directory have done a better job than unix heads like myself
9313 in this regard, and the unix side need to catch up. Time to start a
9314 new IETF work group?
</p
>
9319 <title>Endelig er Debian Lenny gitt ut
</title>
9320 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9321 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9322 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9323 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9324 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9325 Et langt steg videre for Debian-prosjektet, og en rekke nye
9326 programpakker blir nå tilgjengelig for de av oss som bruker den
9327 stabile utgaven av Debian. Neste steg er nå å få
9328 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9329 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9330 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9331 slippes løs på skolene. Takk til alle debian-utviklerne som har
9332 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9333 bootsekvens tilgjengelig i stabil utgave, vha pakken
9334 <tt
>insserv
</tt
>.
</p
>
9339 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9340 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9342 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9343 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9344 Oslo. Most of Saturday was used for the general assemly for the
9345 member organization, but the rest of the weekend I used to tune the
9346 LTSP installation. LTSP now work out of the box on the
10-network.
9347 Acer Aspire One proved to be a very nice thin client, with both
9348 screen, mouse and keybard in a small box. Was working on getting the
9349 diskless workstation setup configured out of the box, but did not
9350 finish it before the weekend was up.
</p
>
9352 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9353 the Brazilian group, so that will have to wait for the next
9354 development gathering. Would love to have the Debian Edu installer
9355 automatically detect and configure a multiseat setup when it find one
9356 of these cards.
</p
>
9361 <title>The sorry state of multimedia browser plugins in Debian
</title>
9362 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9364 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9365 <description><p
>Recently I have spent some time evaluating the multimedia browser
9366 plugins available in Debian Lenny, to see which one we should use by
9367 default in Debian Edu. We need an embedded video playing plugin with
9368 control buttons to pause or stop the video, and capable of streaming
9369 all the multimedia content available on the web. The test results and
9370 notes are available on
9371 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9372 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9373 fill this need. My personal video player favorite, VLC, has a really
9374 bad plugin which fail on a lot of the test pages. A lot of the MIME
9375 types I would expect to work with any free software player (like
9376 video/ogg), just do not work. And simple formats like the
9377 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9378 totem and vlc plugins. I hope the situation will improve soon. No
9379 wonder sites use the proprietary Adobe flash to play video.
</p
>
9381 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9382 be the only one fitting our needs. :/
</p
>