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>New laptop - some more clues and ideas based on feedback
</title>
11 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
13 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
14 <description><p
>Several people contacted me after my previous blog post about my
15 need for a new laptop, and provided very useful feedback. I wish to
16 thank every one of these. Several pointed me to the possibility of
17 fixing my X230, and I am already in the process of getting Lenovo to
18 do so thanks to the on site, next day support contract covering the
19 machine. But the battery is almost useless (I expect to replace it
20 with a non-official battery) and I do not expect the machine to live
21 for many more years, so it is time to plan its replacement. If I did
22 not have a support contract, it was suggested to find replacement parts
23 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
24 might present a language barrier as I do not understand French.
</p
>
26 <p
>One tip I got was to use the
27 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
28 compare laptop models. It seem to have more models available than
29 prisjakt.no. Another tip I got from someone I know have similar
30 keyboard preferences was that the HP EliteBook
840 keyboard is not
31 very good, and this matches my experience with earlier EliteBook
32 keyboards I tested. Because of this, I will not consider it any further.
34 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
35 newest Thinkpad X model. The keyboard reintroduces mouse buttons
36 (which is missing from the X240), and is working fairly well with
37 Debian Sid/Unstable according to
38 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
39 got on the keyboard quality are not consistent. Some say the keyboard
40 is good, others say it is ok, while others say it is not very good.
41 Those with experience from X41 and and X60 agree that the X250
42 keyboard is not as good as those trusty old laptops, and suggest I
43 keep and fix my X230 instead of upgrading, or get a used X230 to
44 replace it. I
'm also told that the X250 lack leds for caps lock, disk
45 activity and battery status, which is very convenient on my X230. I
'm
46 also told that the CPU fan is running very often, making it a bit
47 noisy. In any case, the X250 do not work out of the box with Debian
48 Stable/Jessie, one of my requirements.
</p
>
50 <p
>I have also gotten a few vendor proposals, one was
51 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
52 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
53 The latter look very attractive to me.
</p
>
55 <p
>Again, thank you all for the very useful feedback. It help a lot
56 as I keep looking for a replacement.
</p
>
58 <p
>Update
2015-
07-
06: I was recommended to check out the
59 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
61 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
62 thinkpad X models
</a
>, and provide one year warranty.
</p
>
67 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
68 <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>
69 <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>
70 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
71 <description><p
>My primary work horse laptop is failing, and will need a
72 replacement soon. The left
5 cm of the screen on my Thinkpad X230
73 started flickering yesterday, and I suspect the cause is a broken
74 cable, as changing the angle of the screen some times get rid of the
77 <p
>My requirements have not really changed since I bought it, and is
79 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
80 described them in
2013</a
>. The last time I bought a laptop, I had
82 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
83 where I could select at least a few of the requirements (mouse pin,
84 wifi, weight) and go through the rest manually. Three button mouse
85 and a good keyboard is not available as an option, and all the three
86 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
87 G2) lack three mouse buttons). It is also unclear to me how good the
88 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
89 the keyboard, even if the quality and robustness in the X series have
90 deteriorated since X41.
</p
>
92 <p
>I wonder how I can find a sensible laptop when none of the options
93 seem sensible to me? Are there better services around to search the
94 set of available laptops for features? Please send me an email if you
95 have suggestions.
</p
>
100 <title>How to stay with sysvinit in Debian Jessie
</title>
101 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
102 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
103 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
104 <description><p
>By now, it is well known that Debian Jessie will not be using
105 sysvinit as its boot system by default. But how can one keep using
106 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
108 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
109 Schubert
</a
> and
110 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
113 <p
>If you already are using Wheezy and want to upgrade to Jessie and
114 keep sysvinit as your boot system, create a file
115 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
116 you upgrade:
</p
>
118 <p
><blockquote
><pre
>
119 Package: systemd-sysv
120 Pin: release o=Debian
122 </pre
></blockquote
><p
>
124 <p
>This file content will tell apt and aptitude to not consider
125 installing systemd-sysv as part of any installation and upgrade
126 solution when resolving dependencies, and thus tell it to avoid
127 systemd as a default boot system. The end result should be that the
128 upgraded system keep using sysvinit.
</p
>
130 <p
>If you are installing Jessie for the first time, there is no way to
131 get sysvinit installed by default (debootstrap used by
132 debian-installer have no option for this), but one can tell the
133 installer to switch to sysvinit before the first boot. Either by
134 using a kernel argument to the installer, or by adding a line to the
135 preseed file used. First, the kernel command line argument:
137 <p
><blockquote
><pre
>
138 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
139 </pre
></blockquote
><p
>
141 <p
>Next, the line to use in a preseed file:
</p
>
143 <p
><blockquote
><pre
>
144 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
145 </pre
></blockquote
><p
>
147 <p
>One can of course also do this after the first boot by installing
148 the sysvinit-core package.
</p
>
150 <p
>I recommend only using sysvinit if you really need it, as the
151 sysvinit boot sequence in Debian have several hardware specific bugs
152 on Linux caused by the fact that it is unpredictable when hardware
153 devices show up during boot. But on the other hand, the new default
154 boot system still have a few rough edges I hope will be fixed before
155 Jessie is released.
</p
>
157 <p
>Update
2014-
11-
26: Inspired by
158 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
159 blog post by Torsten Glaser
</a
>, added --purge to the preseed
165 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
166 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
167 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
168 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
169 <description><p
>The right to communicate with your friends and family in private,
170 without anyone snooping, is a right every citicen have in a liberal
171 democracy. But this right is under serious attack these days.
</p
>
173 <p
>A while back it occurred to me that one way to make the dragnet
174 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
175 the whisleblower Snowden) more expensive for Internet email,
176 is to deliver all email using SMTP via Tor. Such SMTP option would be
177 a nice addition to the FreedomBox project if we could send email
178 between FreedomBox machines without leaking metadata about the emails
179 to the people peeking on the wire. I
180 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
181 this on the FreedomBox project mailing list in October
</a
> and got a
182 lot of useful feedback and suggestions. It also became obvious to me
183 that this was not a novel idea, as the same idea was tested and
184 documented by Johannes Berg as early as
2006, and both
185 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
186 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
187 propose a similar method / protocol to pass emails between users.
</p
>
189 <p
>To implement such system one need to set up a Tor hidden service
190 providing the SMTP protocol on port
25, and use email addresses
191 looking like username@hidden-service-name.onion. With such addresses
192 the connections to port
25 on hidden-service-name.onion using Tor will
193 go to the correct SMTP server. To do this, one need to configure the
194 Tor daemon to provide the hidden service and the mail server to accept
195 emails for this .onion domain. To learn more about Exim configuration
196 in Debian and test the design provided by Johannes Berg in his FAQ, I
197 set out yesterday to create a Debian package for making it trivial to
198 set up such SMTP over Tor service based on Debian. Getting it to work
199 were fairly easy, and
200 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
201 source code for the Debian package
</a
> is available from github. I
202 plan to move it into Debian if further testing prove this to be a
203 useful approach.
</p
>
205 <p
>If you want to test this, set up a blank Debian machine without any
206 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
207 get rid of exim4). Install tor, clone the git repository mentioned
208 above, build the deb and install it on the machine. Next, run
209 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
210 the instructions to get the service up and running. Restart tor and
211 exim when it is done, and test mail delivery using swaks like
214 <p
><blockquote
><pre
>
215 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
216 --to fbx@dutlqrrmjhtfa3vp.onion
217 </pre
></blockquote
></p
>
219 <p
>This will test the SMTP delivery using tor. Replace the email
220 address with your own address to test your server. :)
</p
>
222 <p
>The setup procedure is still to complex, and I hope it can be made
223 easier and more automatic. Especially the tor setup need more work.
224 Also, the package include a tor-smtp tool written in C, but its task
225 should probably be rewritten in some script language to make the deb
226 architecture independent. It would probably also make the code easier
227 to review. The tor-smtp tool currently need to listen on a socket for
228 exim to talk to it and is started using xinetd. It would be better if
229 no daemon and no socket is needed. I suspect it is possible to get
230 exim to run a command line tool for delivery instead of talking to a
231 socket, and hope to figure out how in a future version of this
234 <p
>Until I wipe my test machine, I can be reached using the
235 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
241 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
242 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
244 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
245 <description><p
>If you ever had to moderate a mailman list, like the ones on
246 alioth.debian.org, you know the web interface is fairly slow to
247 operate. First you visit one web page, enter the moderation password
248 and get a new page shown with a list of all the messages to moderate
249 and various options for each email address. This take a while for
250 every list you moderate, and you need to do it regularly to do a good
251 job as a list moderator. But there is a quick alternative,
252 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
253 listadmin program
</a
>. It allow you to check lists for new messages
254 to moderate in a fraction of a second. Here is a test run on two
255 lists I recently took over:
</p
>
257 <p
><blockquote
><pre
>
258 % time listadmin xiph
259 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
260 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
266 </pre
></blockquote
></p
>
268 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
269 there are no message in the moderation queue. Every morning I
270 currently moderate
68 mailman lists, and it normally take around two
271 minutes. When I took over the two pkg-xiph lists above a few days
272 ago, there were
400 emails waiting in the moderator queue. It took me
273 less than
15 minutes to process them all using the listadmin
276 <p
>If you install
277 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
278 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
279 with content like this, the moderation task is a breeze:
</p
>
281 <p
><blockquote
><pre
>
282 username username@example.org
285 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
288 adminurl https://{domain}/mailman/admindb/{list}
289 mailman-list@lists.example.com
292 other-list@otherserver.example.org
293 </pre
></blockquote
></p
>
295 <p
>There are other options to set as well. Check the manual page to
296 learn the details.
</p
>
298 <p
>If you are forced to moderate lists on a mailman installation where
299 the SSL certificate is self signed or not properly signed by a
300 generally accepted signing authority, you can set a environment
301 variable when calling listadmin to disable SSL verification:
</p
>
303 <p
><blockquote
><pre
>
304 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
305 </pre
></blockquote
></p
>
307 <p
>If you want to moderate a subset of the lists you take care of, you
308 can provide an argument to the listadmin script like I do in the
309 initial screen dump (the xiph argument). Using an argument, only
310 lists matching the argument string will be processed. This make it
311 quick to accept messages if you notice the moderation request in your
314 <p
>Without the listadmin program, I would never be the moderator of
68
315 mailing lists, as I simply do not have time to spend on that if the
316 process was any slower. The listadmin program have saved me hours of
317 time I could spend elsewhere over the years. It truly is nice free
320 <p
>As usual, if you use Bitcoin and want to show your support of my
321 activities, please send Bitcoin donations to my address
322 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
324 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
325 configuration example. Also, I
've been told that the
326 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
332 <title>Debian Jessie, PXE and automatic firmware installation
</title>
333 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
335 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
336 <description><p
>When PXE installing laptops with Debian, I often run into the
337 problem that the WiFi card require some firmware to work properly.
338 And it has been a pain to fix this using preseeding in Debian.
339 Normally something more is needed. But thanks to
340 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
341 package
</a
> and its recent tasksel extension, it has now become easy
342 to do this using simple preseeding.
</p
>
344 <p
>The isenkram-cli package provide tasksel tasks which will install
345 firmware for the hardware found in the machine (actually, requested by
346 the kernel modules for the hardware). (It can also install user space
347 programs supporting the hardware detected, but that is not the focus
348 of this story.)
</p
>
350 <p
>To get this working in the default installation, two preeseding
351 values are needed. First, the isenkram-cli package must be installed
352 into the target chroot (aka the hard drive) before tasksel is executed
353 in the pkgsel step of the debian-installer system. This is done by
354 preseeding the base-installer/includes debconf value to include the
355 isenkram-cli package. The package name is next passed to debootstrap
356 for installation. With the isenkram-cli package in place, tasksel
357 will automatically use the isenkram tasks to detect hardware specific
358 packages for the machine being installed and install them, because
359 isenkram-cli contain tasksel tasks.
</p
>
361 <p
>Second, one need to enable the non-free APT repository, because
362 most firmware unfortunately is non-free. This is done by preseeding
363 the apt-mirror-setup step. This is unfortunate, but for a lot of
364 hardware it is the only option in Debian.
</p
>
366 <p
>The end result is two lines needed in your preseeding file to get
367 firmware installed automatically by the installer:
</p
>
369 <p
><blockquote
><pre
>
370 base-installer base-installer/includes string isenkram-cli
371 apt-mirror-setup apt-setup/non-free boolean true
372 </pre
></blockquote
></p
>
374 <p
>The current version of isenkram-cli in testing/jessie will install
375 both firmware and user space packages when using this method. It also
376 do not work well, so use version
0.15 or later. Installing both
377 firmware and user space packages might give you a bit more than you
378 want, so I decided to split the tasksel task in two, one for firmware
379 and one for user space programs. The firmware task is enabled by
380 default, while the one for user space programs is not. This split is
381 implemented in the package currently in unstable.
</p
>
383 <p
>If you decide to give this a go, please let me know (via email) how
384 this recipe work for you. :)
</p
>
386 <p
>So, I bet you are wondering, how can this work. First and
387 foremost, it work because tasksel is modular, and driven by whatever
388 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
389 isenkram-cli package place two files for tasksel to find. First there
390 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
392 <p
><blockquote
><pre
>
393 Task: isenkram-packages
395 Description: Hardware specific packages (autodetected by isenkram)
396 Based on the detected hardware various hardware specific packages are
398 Test-new-install: show show
400 Packages: for-current-hardware
402 Task: isenkram-firmware
404 Description: Hardware specific firmware packages (autodetected by isenkram)
405 Based on the detected hardware various hardware specific firmware
406 packages are proposed.
407 Test-new-install: mark show
409 Packages: for-current-hardware-firmware
410 </pre
></blockquote
></p
>
412 <p
>The key parts are Test-new-install which indicate how the task
413 should be handled and the Packages line referencing to a script in
414 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
415 list of packages to install. The for-current-hardware-firmware script
416 look like this to list relevant firmware for the machine:
418 <p
><blockquote
><pre
>
423 isenkram-autoinstall-firmware -l
424 </pre
></blockquote
></p
>
426 <p
>With those two pieces in place, the firmware is installed by
427 tasksel during the normal d-i run. :)
</p
>
429 <p
>If you want to test what tasksel will install when isenkram-cli is
430 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
431 --new-install
</tt
> to get the list of packages that tasksel would
434 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
435 pilots in testing this feature, as isenkram is used there now to
436 install firmware, replacing the earlier scripts.
</p
>
441 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
442 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
444 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
445 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
446 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
447 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
448 on a screen normally showing the bread types and prizes:
</p
>
450 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
452 <p
>If it had booted as it was supposed to, I would never had known
453 about this hidden Linux installation. It is interesting what
454 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
459 <title>New lsdvd release version
0.17 is ready
</title>
460 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
461 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
462 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
463 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
464 got a new set of developers a few weeks ago, after the original
465 developer decided to step down and pass the project to fresh blood.
466 This project is now maintained by Petter Reinholdtsen and Steve
469 <p
>I just wrapped up
470 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
471 new lsdvd release
</a
>, available in git or from
472 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
473 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
478 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
479 <li
>Check for garbage in the program chains, which indicate that a track is
480 non-existant, to work around additional copy protection
</li
>
481 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
482 <li
>Fix pallete display of first entry
</li
>
483 <li
>Fix include orders
</li
>
484 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
485 <li
>Fix the chapter count
</li
>
486 <li
>Make sure the array size and the array limit used when initialising
487 the palette size is the same.
</li
>
488 <li
>Fix array printing.
</li
>
489 <li
>Correct subsecond calculations.
</li
>
490 <li
>Add sector information to the output format.
</li
>
491 <li
>Clean up code to be closer to ANSI C and compile without warnings
492 with more GCC compiler warnings.
</li
>
496 <p
>This change bring together patches for lsdvd in use in various
497 Linux and Unix distributions, as well as patches submitted to the
498 project the last nine years. Please check it out. :)
</p
>
503 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
504 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
506 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
507 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
508 project
</a
> provide a Linux solution for schools, including a
509 powerful desktop with education software, a central server providing
510 web pages, user database, user home directories, central login and PXE
511 boot of both clients without disk and the installation to install Debian
512 Edu on machines with disk (and a few other services perhaps to small
513 to mention here). We in the Debian Edu team are currently working on
514 the Jessie based version, trying to get everything in shape before the
515 freeze, to avoid having to maintain our own package repository in the
517 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
518 status
</a
> can be seen on the Debian wiki, and there is still heaps of
519 work left. Some fatal problems block testing, breaking the installer,
520 but it is possible to work around these to get anyway. Here is a
521 recipe on how to get the installation limping along.
</p
>
523 <p
>First, download the test ISO via
524 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
525 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
527 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
528 The ISO build was broken on Tuesday, so we do not get a new ISO every
529 12 hours or so, but thankfully the ISO we already got we are able to
530 install with some tweaking.
</p
>
532 <p
>When you get to the Debian Edu profile question, go to tty2
533 (use Alt-Ctrl-F2), run
</p
>
535 <p
><blockquote
><pre
>
536 nano /usr/bin/edu-eatmydata-install
537 </pre
></blockquote
></p
>
539 <p
>and add
'exit
0' as the second line, disabling the eatmydata
540 optimization. Return to the installation, select the profile you want
541 and continue. Without this change, exim4-config will fail to install
542 due to a known bug in eatmydata.
</p
>
544 <p
>When you get the grub question at the end, answer /dev/sda (or if
545 this do not work, figure out what your correct value would be. All my
546 test machines need /dev/sda, so I have no advice if it do not fit
549 <p
>If you installed a profile including a graphical desktop, log in as
550 root after the initial boot from hard drive, and install the
551 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
552 or mate. If you want several desktop options, install more than one
553 metapackage. Once this is done, reboot and you should have a working
554 graphical login screen. This workaround should no longer be needed
555 once the education-tasks package version
1.801 enter testing in two
558 <p
>I believe the ISO build will start working on two days when the new
559 tasksel package enter testing and Steve McIntyre get a chance to
560 update the debian-cd git repository. The eatmydata, grub and desktop
561 issues are already fixed in unstable and testing, and should show up
562 on the ISO as soon as the ISO build start working again. Well the
563 eatmydata optimization is really just disabled. The proper fix
564 require an upload by the eatmydata maintainer applying the patch
565 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
566 The rest have proper fixes in unstable.
</p
>
568 <p
>I hope this get you going with the installation testing, as we are
569 quickly running out of time trying to get our Jessie based
570 installation ready before the distribution freeze in a month.
</p
>
575 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
576 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
577 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
578 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
579 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
580 to handle my fairly large DVD collection. It is a nice command line
581 tool to get details about a DVD, like title, tracks, track length,
582 etc, in XML, Perl or human readable format. But lsdvd have not seen
583 any new development since
2006 and had a few irritating bugs affecting
584 its use with some DVDs. Upstream seemed to be dead, and in January I
585 sent a small probe asking for a version control repository for the
586 project, without any reply. But I use it regularly and would like to
587 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
588 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
589 the project admin, and after getting a reply from him explaining that
590 he was no longer interested in the project, I asked if I could take
591 over. And yesterday, I became project admin.
</p
>
593 <p
>I
've been in touch with a Gentoo developer and the Debian
594 maintainer interested in joining forces to maintain the upstream
595 project, and I hope we can get a new release out fairly quickly,
596 collecting the patches spread around on the internet into on place.
597 I
've added the relevant Debian patches to the freshly created git
598 repository, and expect the Gentoo patches to make it too. If you got
599 a DVD collection and care about command line tools, check out
600 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
601 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
602 list
</a
>. :)
</p
>
607 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
608 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
610 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
611 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
612 a lot quicker. When we install more than
2000 packages in
613 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
614 tasksel in the installer, unpacking the binary packages take forever.
615 A part of the slow I/O issue was discussed in
616 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
617 much file system sync-ing done by dpkg, which is the package
618 responsible for unpacking the binary packages. Other parts (like code
619 executed by postinst scripts) might also sync to disk during
620 installation. All this sync-ing to disk do not really make sense to
621 me. If the machine crash half-way through, I start over, I do not try
622 to salvage the half installed system. So the failure sync-ing is
623 supposed to protect against, hardware or system crash, is not really
624 relevant while the installer is running.
</p
>
626 <p
>A few days ago, I thought of a way to get rid of all the file
627 system sync()-ing in a fairly non-intrusive way, without the need to
628 change the code in several packages. The idea is not new, but I have
629 not heard anyone propose the approach using dpkg-divert before. It
630 depend on the small and clever package
631 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
632 uses LD_PRELOAD to replace the system functions for syncing data to
633 disk with functions doing nothing, thus allowing programs to live
634 dangerous while speeding up disk I/O significantly. Instead of
635 modifying the implementation of dpkg, apt and tasksel (which are the
636 packages responsible for selecting, fetching and installing packages),
637 it occurred to me that we could just divert the programs away, replace
638 them with a simple shell wrapper calling
639 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
640 Two days ago I decided to test the idea, and wrapped up a simple
641 implementation for the Debian Edu udeb.
</p
>
643 <p
>The effect was stunning. In my first test it reduced the running
644 time of the pkgsel step (installing tasks) from
64 to less than
44
645 minutes (
20 minutes shaved off the installation) on an old Dell
646 Latitude D505 machine. I am not quite sure what the optimised time
647 would have been, as I messed up the testing a bit, causing the debconf
648 priority to get low enough for two questions to pop up during
649 installation. As soon as I saw the questions I moved the installation
650 along, but do not know how long the question were holding up the
651 installation. I did some more measurements using Debian Edu Jessie,
652 and got these results. The time measured is the time stamp in
653 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
654 "pkgsel: finishing up
" lines, if you want to do the same measurement
655 yourself. In Debian Edu, the tasksel dialog do not show up, and the
656 timing thus do not depend on how quickly the user handle the tasksel
659 <p
><table
>
662 <th
>Machine/setup
</th
>
663 <th
>Original tasksel
</th
>
664 <th
>Optimised tasksel
</th
>
665 <th
>Reduction
</th
>
669 <td
>Latitude D505 Main+LTSP LXDE
</td
>
670 <td
>64 min (
07:
46-
08:
50)
</td
>
671 <td
><44 min (
11:
27-
12:
11)
</td
>
672 <td
>>20 min
18%
</td
>
676 <td
>Latitude D505 Roaming LXDE
</td
>
677 <td
>57 min (
08:
48-
09:
45)
</td
>
678 <td
>34 min (
07:
43-
08:
17)
</td
>
679 <td
>23 min
40%
</td
>
683 <td
>Latitude D505 Minimal
</td
>
684 <td
>22 min (
10:
37-
10:
59)
</td
>
685 <td
>11 min (
11:
16-
11:
27)
</td
>
686 <td
>11 min
50%
</td
>
690 <td
>Thinkpad X200 Minimal
</td
>
691 <td
>6 min (
08:
19-
08:
25)
</td
>
692 <td
>4 min (
08:
04-
08:
08)
</td
>
693 <td
>2 min
33%
</td
>
697 <td
>Thinkpad X200 Roaming KDE
</td
>
698 <td
>19 min (
09:
21-
09:
40)
</td
>
699 <td
>15 min (
10:
25-
10:
40)
</td
>
700 <td
>4 min
21%
</td
>
703 </table
></p
>
705 <p
>The test is done using a netinst ISO on a USB stick, so some of the
706 time is spent downloading packages. The connection to the Internet
707 was
100Mbit/s during testing, so downloading should not be a
708 significant factor in the measurement. Download typically took a few
709 seconds to a few minutes, depending on the amount of packages being
712 <p
>The speedup is implemented by using two hooks in
713 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
714 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
715 finish-install.d hook to remove the divert at the end of the
716 installation. I picked the pre-pkgsel.d hook instead of the
717 post-base-installer.d hook because I test using an ISO without the
718 eatmydata package included, and the post-base-installer.d hook in
719 Debian Edu can only operate on packages included in the ISO. The
720 negative effect of this is that I am unable to activate this
721 optimization for the kernel installation step in d-i. If the code is
722 moved to the post-base-installer.d hook, the speedup would be larger
723 for the entire installation.
</p
>
725 <p
>I
've implemented this in the
726 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
727 git repository, and plan to provide the optimization as part of the
728 Debian Edu installation. If you want to test this yourself, you can
729 create two files in the installer (or in an udeb). One shell script
730 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
732 <p
><blockquote
><pre
>
735 . /usr/share/debconf/confmodule
737 logger -t my-pkgsel
"info: $*
"
740 logger -t my-pkgsel
"error: $*
"
743 apt-install eatmydata || true
744 if [ -x /target/usr/bin/eatmydata ] ; then
745 for bin in dpkg apt-get aptitude tasksel ; do
747 # Test that the file exist and have not been diverted already.
748 if [ -f /target$file ] ; then
749 info
"diverting $file using eatmydata
"
750 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
751 > /target$file.edu
752 chmod
755 /target$file.edu
753 in-target dpkg-divert --package debian-edu-config \
754 --rename --quiet --add $file
755 ln -sf ./$bin.edu /target$file
757 error
"unable to divert $file, as it is missing.
"
761 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
766 </pre
></blockquote
></p
>
768 <p
>To clean up, another shell script should go into
769 /usr/lib/finish-install.d/ with code like this:
771 <p
><blockquote
><pre
>
773 . /usr/share/debconf/confmodule
775 logger -t my-finish-install
"error: $@
"
777 remove_install_override() {
778 for bin in dpkg apt-get aptitude tasksel ; do
780 if [ -x /target$file.edu ] ; then
782 in-target dpkg-divert --package debian-edu-config \
783 --rename --quiet --remove $file
786 error
"Missing divert for $file.
"
789 sync # Flush file buffers before continuing
792 remove_install_override
793 </pre
></blockquote
></p
>
795 <p
>In Debian Edu, I placed both code fragments in a separate script
796 edu-eatmydata-install and call it from the pre-pkgsel.d and
797 finish-install.d scripts.
</p
>
799 <p
>By now you might ask if this change should get into the normal
800 Debian installer too? I suspect it should, but am not sure the
801 current debian-installer coordinators find it useful enough. It also
802 depend on the side effects of the change. I
'm not aware of any, but I
803 guess we will see if the change is safe after some more testing.
804 Perhaps there is some package in Debian depending on sync() and
805 fsync() having effect? Perhaps it should go into its own udeb, to
806 allow those of us wanting to enable it to do so without affecting
809 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
810 will break installation of all programs using gnutls because of
811 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
812 eatmydata package in Debian will solve it.
</p
>
814 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
815 the optimization work again. And I have discovered that the
816 dpkg-divert trick is not really needed and implemented a slightly
817 simpler approach as part of the debian-edu-install package. See
818 tools/edu-eatmydata-install in the source package.
</p
>
820 <p
>Update
2014-
11-
11: Unfortunately, a new
821 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
822 triggering on i386 made it into testing, and broke this installation
823 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
824 request
768893</a
> is accepted, it should be working again.
</p
>
829 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
830 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
832 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
833 <description><p
>Yesterday, I had the pleasure of attending a talk with the
834 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
835 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
836 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
837 learn that there is a large set of publicly available key servers to
838 use when looking for peoples public key. So far I have used
839 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
840 were misbehaving, but those days are ended. The servers I have used
841 up until yesterday have been slow and some times unavailable. I hope
842 those problems are gone now.
</p
>
844 <p
>Behind the round robin DNS entry of the
845 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
846 there is a pool of more than
100 keyservers which are checked every
847 day to ensure they are well connected and up to date. It must be
848 better than what I have used so far. :)
</p
>
850 <p
>Yesterdays speaker told me that the service is the default
851 keyserver provided by the default configuration in GnuPG, but this do
852 not seem to be used in Debian. Perhaps it should?
</p
>
854 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
857 <p
><blockquote
><pre
>
858 keyserver pool.sks-keyservers.net
859 </pre
></blockquote
></p
>
861 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
862 entries in DNS. Just for fun, I did just that at work, so now every
863 user of GnuPG at the University of Oslo should find a OpenGPG
864 keyserver automatically should their need it:
</p
>
866 <p
><blockquote
><pre
>
867 % host -t srv _pgpkey-http._tcp.uio.no
868 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
870 </pre
></blockquote
></p
>
873 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
874 HKP lookup protocol
</a
> supported finding signature paths, I would be
875 very happy. It can look up a given key or search for a user ID, but I
876 normally do not want that, but to find a trust path from my key to
877 another key. Given a user ID or key ID, I would like to find (and
878 download) the keys representing a signature path from my key to the
879 key in question, to be able to get a trust path between the two keys.
880 This is as far as I can tell not possible today. Perhaps something
881 for a future version of the protocol?
</p
>
886 <title>From English wiki to translated PDF and epub via Docbook
</title>
887 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
888 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
889 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
890 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
891 project
</a
> provide an instruction manual for teachers, system
892 administrators and other users that contain useful tips for setting up
893 and maintaining a Debian Edu installation. This text is about how the
894 text processing of this manual is handled in the project.
</p
>
896 <p
>One goal of the project is to provide information in the native
897 language of its users, and for this we need to handle translations.
898 But we also want to make sure each language contain the same
899 information, so for this we need a good way to keep the translations
900 in sync. And we want it to be easy for our users to improve the
901 documentation, avoiding the need to learn special formats or tools to
902 contribute, and the obvious way to do this is to make it possible to
903 edit the documentation using a web browser. We also want it to be
904 easy for translators to keep the translation up to date, and give them
905 help in figuring out what need to be translated. Here is the list of
906 tools and the process we have found trying to reach all these
909 <p
>We maintain the authoritative source of our manual in the
910 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
911 wiki
</a
>, as several wiki pages written in English. It consist of one
912 front page with references to the different chapters, several pages
913 for each chapter, and finally one
"collection page
" gluing all the
914 chapters together into one large web page (aka
915 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
916 AllInOne page
</a
>). The AllInOne page is the one used for further
917 processing and translations. Thanks to the fact that the
918 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
919 wiki.debian.org support exporting pages in
920 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
921 the list of pages to export using the raw version of the AllInOne
922 page, loop over each of them to generate a Docbook XML version of the
923 manual. This process also download images and transform image
924 references to use the locally downloaded images. The generated
925 Docbook XML files are slightly broken, so some post-processing is done
926 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
927 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
928 a handfull of images. The XML file can now be used to generate PDF, HTML
929 and epub versions of the English manual. This is the basic step of
930 our process, making PDF (using dblatex), HTML (using xsltproc) and
931 epub (using dbtoepub) version from Docbook XML, and the resulting files
932 are placed in the debian-edu-doc-en binary package.
</p
>
934 <p
>But English documentation is not enough for us. We want translated
935 documentation too, and we want to make it easy for translators to
936 track the English original. For this we use the
937 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
938 which allow us to transform the English Docbook XML file into a
939 translation file (a .pot file), usable with the normal gettext based
940 translation tools used by those translating free software. The pot
941 file is used to create and maintain translation files (several .po
942 files), which the translations update with the native language
943 translations of all titles, paragraphs and blocks of text in the
944 original. The next step is combining the original English Docbook XML
945 and the translation file (say debian-edu-wheezy-manual.nb.po), to
946 create a translated Docbook XML file (in this case
947 debian-edu-wheezy-manual.nb.xml). This translated (or partly
948 translated, if the translation is not complete) Docbook XML file can
949 then be used like the original to create a PDF, HTML and epub version
950 of the documentation.
</p
>
952 <p
>The translators use different tools to edit the .po files. We
954 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
955 while some use emacs and vi, others can use web based editors like
956 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
957 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
958 is where the .po file end up, in our git repository. Updated
959 translations can either be committed directly to git, or submitted as
960 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
961 against the debian-edu-doc package
</a
>.
</p
>
963 <p
>One challenge is images, which both might need to be translated (if
964 they show translated user applications), and are needed in different
965 formats when creating PDF and HTML versions (epub is a HTML version in
966 this regard). For this we transform the original PNG images to the
967 needed density and format during build, and have a way to provide
968 translated images by storing translated versions in
969 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
970 package maintainers know more.
</p
>
972 <p
>If you wonder what the result look like, we provide
973 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
974 of the documentation packages on the web
</a
>. See for example the
975 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
976 PDF version
</a
> or the
977 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
978 HTML version
</a
>. We do not yet build the epub version by default,
979 but perhaps it will be done in the future.
</p
>
981 <p
>To learn more, check out
982 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
983 debian-edu-doc package
</a
>,
984 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
985 manual on the wiki
</a
> and
986 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
987 translation instructions
</a
> in the manual.
</p
>
992 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
993 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
994 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
995 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
996 <description><p
>It would be nice if it was easier in Debian to get all the hardware
997 related packages relevant for the computer installed automatically.
998 So I implemented one, using
999 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
1000 package
</a
>. To use it, install the tasksel and isenkram packages and
1001 run tasksel as user root. You should be presented with a new option,
1002 "Hardware specific packages (autodetected by isenkram)
". When you
1003 select it, tasksel will install the packages isenkram claim is fit for
1004 the current hardware, hot pluggable or not.
<p
>
1006 <p
>The implementation is in two files, one is the tasksel menu entry
1007 description, and the other is the script used to extract the list of
1008 packages to install. The first part is in
1009 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
1012 <p
><blockquote
><pre
>
1015 Description: Hardware specific packages (autodetected by isenkram)
1016 Based on the detected hardware various hardware specific packages are
1018 Test-new-install: mark show
1020 Packages: for-current-hardware
1021 </pre
></blockquote
></p
>
1023 <p
>The second part is in
1024 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
1027 <p
><blockquote
><pre
>
1032 isenkram-autoinstall-firmware -l
1034 </pre
></blockquote
></p
>
1036 <p
>All in all, a very short and simple implementation making it
1037 trivial to install the hardware dependent package we all may want to
1038 have installed on our machines. I
've not been able to find a way to
1039 get tasksel to tell you exactly which packages it plan to install
1040 before doing the installation. So if you are curious or careful,
1041 check the output from the isenkram-* command line tools first.
</p
>
1043 <p
>The information about which packages are handling which hardware is
1044 fetched either from the isenkram package itself in
1045 /usr/share/isenkram/, from git.debian.org or from the APT package
1046 database (using the Modaliases header). The APT package database
1047 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1048 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
1049 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
1050 the python-apt code (bug
1051 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
1052 workaround I was able to get rid of the file descriptor leak and
1053 reduce the memory leak from ~
30 MiB per hardware detection down to
1054 around
2 MiB per hardware detection. It should make the desktop
1055 daemon a lot more useful. The fix is in version
0.7 uploaded to
1056 unstable today.
</p
>
1058 <p
>I believe the current way of mapping hardware to packages in
1059 Isenkram is is a good draft, but in the future I expect isenkram to
1060 use the AppStream data source for this. A proposal for getting proper
1061 AppStream support into Debian is floating around as
1062 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
1063 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
1064 project
</a
> will take place this summer to improve the situation. I
1065 look forward to seeing the result, and welcome patches for isenkram to
1066 start using the information when it is ready.
</p
>
1068 <p
>If you want your package to map to some specific hardware, either
1069 add a
"Xb-Modaliases
" header to your control file like I did in
1070 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
1071 package
</a
> or submit a bug report with the details to the isenkram
1073 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
1074 blog posts tagged isenkram
</a
> for details on the notation. I expect
1075 the information will be migrated to AppStream eventually, but for the
1076 moment I got no better place to store it.
</p
>
1081 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
1082 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
1083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
1084 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
1085 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1086 project
</a
> is working on providing the software and hardware to make
1087 it easy for non-technical people to host their data and communication
1088 at home, and being able to communicate with their friends and family
1089 encrypted and away from prying eyes. It is still going strong, and
1090 today a major mile stone was reached.
</p
>
1092 <p
>Today, the last of the packages currently used by the project to
1093 created the system images were accepted into Debian Unstable. It was
1094 the freedombox-setup package, which is used to configure the images
1095 during build and on the first boot. Now all one need to get going is
1096 the build code from the freedom-maker git repository and packages from
1097 Debian. And once the freedombox-setup package enter testing, we can
1098 build everything directly from Debian. :)
</p
>
1100 <p
>Some key packages used by Freedombox are
1101 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
1102 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
1103 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
1104 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
1105 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
1106 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
1107 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
1108 are plans to integrate more packages into the setup. User
1109 documentation is maintained on the Debian wiki. Please
1110 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
1111 the manual
</a
> and help us improve it.
</p
>
1113 <p
>To test for yourself and create boot images with the FreedomBox
1114 setup, run this on a Debian machine using a user with sudo rights to
1115 become root:
</p
>
1117 <p
><pre
>
1118 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1119 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1121 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1123 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1124 </pre
></p
>
1126 <p
>Root access is needed to run debootstrap and mount loopback
1127 devices. See the README in the freedom-maker git repo for more
1128 details on the build. If you do not want all three images, trim the
1129 make line. Note that the virtualbox-image target is not really
1130 virtualbox specific. It create a x86 image usable in kvm, qemu,
1131 vmware and any other x86 virtual machine environment. You might need
1132 the version of vmdebootstrap in Jessie to get the build working, as it
1133 include fixes for a race condition with kpartx.
</p
>
1135 <p
>If you instead want to install using a Debian CD and the preseed
1136 method, boot a Debian Wheezy ISO and use this boot argument to load
1137 the preseed values:
</p
>
1139 <p
><pre
>
1140 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1141 </pre
></p
>
1143 <p
>I have not tested it myself the last few weeks, so I do not know if
1144 it still work.
</p
>
1146 <p
>If you wonder how to help, one task you could look at is using
1147 systemd as the boot system. It will become the default for Linux in
1148 Jessie, so we need to make sure it is usable on the Freedombox. I did
1149 a simple test a few weeks ago, and noticed dnsmasq failed to start
1150 during boot when using systemd. I suspect there are other problems
1151 too. :) To detect problems, there is a test suite included, which can
1152 be run from the plinth web interface.
</p
>
1154 <p
>Give it a go and let us know how it goes on the mailing list, and help
1155 us get the new release published. :) Please join us on
1156 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1157 irc.debian.org)
</a
> and
1158 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1159 mailing list
</a
> if you want to help make this vision come true.
</p
>
1164 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
1165 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
1166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
1167 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
1168 <description><p
>For a while now, I have been looking for a sensible offsite backup
1169 solution for use at home. My requirements are simple, it must be
1170 cheap and locally encrypted (in other words, I keep the encryption
1171 keys, the storage provider do not have access to my private files).
1172 One idea me and my friends had many years ago, before the cloud
1173 storage providers showed up, was to use Google mail as storage,
1174 writing a Linux block device storing blocks as emails in the mail
1175 service provided by Google, and thus get heaps of free space. On top
1176 of this one can add encryption, RAID and volume management to have
1177 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1178 I never found time to implement such system. But the last few weeks I
1179 have looked at a system called
1180 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
1181 mounted network backed file system with the features I need.
</p
>
1183 <p
>S3QL is a fuse file system with a local cache and cloud storage,
1184 handling several different storage providers, any with Amazon S3,
1185 Google Drive or OpenStack API. There are heaps of such storage
1186 providers. S3QL can also use a local directory as storage, which
1187 combined with sshfs allow for file storage on any ssh server. S3QL
1188 include support for encryption, compression, de-duplication, snapshots
1189 and immutable file systems, allowing me to mount the remote storage as
1190 a local mount point, look at and use the files as if they were local,
1191 while the content is stored in the cloud as well. This allow me to
1192 have a backup that should survive fire. The file system can not be
1193 shared between several machines at the same time, as only one can
1194 mount it at the time, but any machine with the encryption key and
1195 access to the storage service can mount it if it is unmounted.
</p
>
1197 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
1198 package is included already. So to get started, run
<tt
>apt-get
1199 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
1200 Greenqloud, after reading their nice recipe on
1201 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
1202 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
1203 in Iceland more than those in USA when it come to keeping my personal
1204 data safe and private, and thus would rather spend money on a company
1205 in Iceland. Another nice recipe is available from the article
1206 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
1207 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
1208 Admin magazine. When the provider is picked, figure out how to get
1209 the API key needed to connect to the storage API. With Greencloud,
1210 the key did not show up until I had added payment details to my
1213 <p
>Armed with the API access details, it is time to create the file
1214 system. First, create a new bucket in the cloud. This bucket is the
1215 file system storage area. I picked a bucket name reflecting the
1216 machine that was going to store data there, but any name will do.
1217 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
1218 the API login and password, and a locally created password. Store it
1219 all in ~root/.s3ql/authinfo2 like this:
1221 <p
><blockquote
><pre
>
1223 storage-url: s3c://s.greenqloud.com:
443/bucket-name
1224 backend-login: API-login
1225 backend-password: API-password
1226 fs-passphrase: local-password
1227 </pre
></blockquote
></p
>
1229 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
1230 but any sensible way to create a fairly random password should do it.
1231 Armed with these details, it is now time to run mkfs, entering the API
1232 details and password to create it:
</p
>
1234 <p
><blockquote
><pre
>
1235 # mkdir -m
700 /var/lib/s3ql-cache
1236 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1237 --ssl s3c://s.greenqloud.com:
443/bucket-name
1238 Enter backend login:
1239 Enter backend password:
1240 Before using S3QL, make sure to read the user
's guide, especially
1241 the
'Important Rules to Avoid Loosing Data
' section.
1242 Enter encryption password:
1243 Confirm encryption password:
1244 Generating random encryption key...
1245 Creating metadata tables...
1255 Compressing and uploading metadata...
1256 Wrote
0.00 MB of compressed metadata.
1257 #
</pre
></blockquote
></p
>
1259 <p
>The next step is mounting the file system to make the storage available.
1261 <p
><blockquote
><pre
>
1262 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1263 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1264 Using
4 upload threads.
1265 Downloading and decompressing metadata...
1275 Mounting filesystem...
1277 Filesystem Size Used Avail Use% Mounted on
1278 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
1280 </pre
></blockquote
></p
>
1282 <p
>The file system is now ready for use. I use rsync to store my
1283 backups in it, and as the metadata used by rsync is downloaded at
1284 mount time, no network traffic (and storage cost) is triggered by
1285 running rsync. To unmount, one should not use the normal umount
1286 command, as this will not flush the cache to the cloud storage, but
1287 instead running the umount.s3ql command like this:
1289 <p
><blockquote
><pre
>
1292 </pre
></blockquote
></p
>
1294 <p
>There is a fsck command available to check the file system and
1295 correct any problems detected. This can be used if the local server
1296 crashes while the file system is mounted, to reset the
"already
1297 mounted
" flag. This is what it look like when processing a working
1298 file system:
</p
>
1300 <p
><blockquote
><pre
>
1301 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
1302 Using cached metadata.
1303 File system seems clean, checking anyway.
1304 Checking DB integrity...
1305 Creating temporary extra indices...
1306 Checking lost+found...
1307 Checking cached objects...
1308 Checking names (refcounts)...
1309 Checking contents (names)...
1310 Checking contents (inodes)...
1311 Checking contents (parent inodes)...
1312 Checking objects (reference counts)...
1313 Checking objects (backend)...
1314 ..processed
5000 objects so far..
1315 ..processed
10000 objects so far..
1316 ..processed
15000 objects so far..
1317 Checking objects (sizes)...
1318 Checking blocks (referenced objects)...
1319 Checking blocks (refcounts)...
1320 Checking inode-block mapping (blocks)...
1321 Checking inode-block mapping (inodes)...
1322 Checking inodes (refcounts)...
1323 Checking inodes (sizes)...
1324 Checking extended attributes (names)...
1325 Checking extended attributes (inodes)...
1326 Checking symlinks (inodes)...
1327 Checking directory reachability...
1328 Checking unix conventions...
1329 Checking referential integrity...
1330 Dropping temporary indices...
1331 Backing up old metadata...
1341 Compressing and uploading metadata...
1342 Wrote
0.89 MB of compressed metadata.
1344 </pre
></blockquote
></p
>
1346 <p
>Thanks to the cache, working on files that fit in the cache is very
1347 quick, about the same speed as local file access. Uploading large
1348 amount of data is to me limited by the bandwidth out of and into my
1349 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
1350 which is very close to my upload speed, and downloading the same
1351 Debian installation ISO gave me
610 kiB/s, close to my download speed.
1352 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
1353 network, not the file system code. I do not know what a good cache
1354 size would be, but suspect that the cache should e larger than your
1355 working set.
</p
>
1357 <p
>I mentioned that only one machine can mount the file system at the
1358 time. If another machine try, it is told that the file system is
1361 <p
><blockquote
><pre
>
1362 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1363 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1364 Using
8 upload threads.
1365 Backend reports that fs is still mounted elsewhere, aborting.
1367 </pre
></blockquote
></p
>
1369 <p
>The file content is uploaded when the cache is full, while the
1370 metadata is uploaded once every
24 hour by default. To ensure the
1371 file system content is flushed to the cloud, one can either umount the
1372 file system, or ask S3QL to flush the cache and metadata using
1375 <p
><blockquote
><pre
>
1376 # s3qlctrl upload-meta /s3ql
1377 # s3qlctrl flushcache /s3ql
1379 </pre
></blockquote
></p
>
1381 <p
>If you are curious about how much space your data uses in the
1382 cloud, and how much compression and deduplication cut down on the
1383 storage usage, you can use s3qlstat on the mounted file system to get
1386 <p
><blockquote
><pre
>
1388 Directory entries:
9141
1391 Total data size:
22049.38 MB
1392 After de-duplication:
21955.46 MB (
99.57% of total)
1393 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
1394 Database size:
2.39 MB (uncompressed)
1395 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1397 </pre
></blockquote
></p
>
1399 <p
>I mentioned earlier that there are several possible suppliers of
1400 storage. I did not try to locate them all, but am aware of at least
1401 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
1402 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
1403 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
1404 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
1405 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
1406 accept payment in Bitcoin. Pick one that suit your need. Some of
1407 them provide several GiB of free storage, but the prize models are
1408 quite different and you will have to figure out what suits you
1411 <p
>While researching this blog post, I had a look at research papers
1412 and posters discussing the S3QL file system. There are several, which
1413 told me that the file system is getting a critical check by the
1414 science community and increased my confidence in using it. One nice
1416 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
1417 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1418 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
1419 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1420 and Pamela Smith. Please have a look.
</p
>
1422 <p
>Given my problems with different file systems earlier, I decided to
1423 check out the mounted S3QL file system to see if it would be usable as
1424 a home directory (in other word, that it provided POSIX semantics when
1425 it come to locking and umask handling etc). Running
1426 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
1427 test code to check file system semantics
</a
>, I was happy to discover that
1428 no error was found. So the file system can be used for home
1429 directories, if one chooses to do so.
</p
>
1431 <p
>If you do not want a locally file system, and want something that
1432 work without the Linux fuse file system, I would like to mention the
1433 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
1434 provide locally encrypted backup using a command line client. It have
1435 a nicer access control system, where one can split out read and write
1436 access, allowing some systems to write to the backup and others to
1437 only read from it.
</p
>
1439 <p
>As usual, if you use Bitcoin and want to show your support of my
1440 activities, please send Bitcoin donations to my address
1441 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1446 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
1447 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
1448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
1449 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
1450 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1451 project
</a
> is working on providing the software and hardware for
1452 making it easy for non-technical people to host their data and
1453 communication at home, and being able to communicate with their
1454 friends and family encrypted and away from prying eyes. It has been
1455 going on for a while, and is slowly progressing towards a new test
1456 release (
0.2).
</p
>
1458 <p
>And what day could be better than the Pi day to announce that the
1459 new version will provide
"hard drive
" / SD card / USB stick images for
1460 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1461 system), and can also be installed using a Debian installer preseed
1462 file. The Debian based Freedombox is now based on Debian Jessie,
1463 where most of the needed packages used are already present. Only one,
1464 the freedombox-setup package, is missing. To try to build your own
1465 boot image to test the current status, fetch the freedom-maker scripts
1467 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
1468 with a user with sudo access to become root:
1471 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1473 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1474 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1476 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1479 <p
>Root access is needed to run debootstrap and mount loopback
1480 devices. See the README for more details on the build. If you do not
1481 want all three images, trim the make line. But note that thanks to
<a
1482 href=
"https://bugs.debian.org/
741407">a race condition in
1483 vmdebootstrap
</a
>, the build might fail without the patch to the
1484 kpartx call.
</p
>
1486 <p
>If you instead want to install using a Debian CD and the preseed
1487 method, boot a Debian Wheezy ISO and use this boot argument to load
1488 the preseed values:
</p
>
1491 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1494 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
1495 recently introduced bug in apt in Jessie
</a
>, the installer will
1496 currently hang while setting up APT sources. Killing the
1497 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
1498 installation will get the installation going. This affect all
1499 installations in Jessie, and I expect it will be fixed soon.
</p
>
1501 <p
>Give it a go and let us know how it goes on the mailing list, and help
1502 us get the new release published. :) Please join us on
1503 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1504 irc.debian.org)
</a
> and
1505 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1506 mailing list
</a
> if you want to help make this vision come true.
</p
>
1511 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1512 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1514 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1515 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1516 innetgr tools, because I needed them in
1517 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1518 ng-utils, and it has served me well. I placed the project under the
1519 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1520 repository. But many years ago, the CVS repository was dropped (lost,
1521 not migrated to new hardware, not sure), and the project have lacked a
1522 proper home since then.
</p
>
1524 <p
>Last summer, I had a look at the package and made a new release
1525 fixing a irritating crash bug, but was unable to store the changes in
1526 a proper source control system. I applied for a project on
1527 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1528 to follow up on it. Until today. :)
</p
>
1530 <p
>After many hours of cleaning and migration, the ng-utils project
1531 now have a new home, and a git repository with the highlight of the
1532 history of the project. I published all release tarballs and imported
1533 them into the git repository. As the project is really stable and not
1534 expected to gain new features any time soon, I decided to make a new
1535 release and call it
1.0. Visit the new project home on
1536 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1537 if you want to check it out. The new version is also uploaded into
1538 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1543 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1544 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1545 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1546 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1547 <description><p
>A few days ago I decided to try to help the Hurd people to get
1548 their changes into sysvinit, to allow them to use the normal sysvinit
1549 boot system instead of their old one. This follow up on the
1550 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1551 Google Summer of Code work
</a
> done last summer by Justus Winter to
1552 get Debian on Hurd working more like Debian on Linux. To get started,
1553 I downloaded a prebuilt hard disk image from
1554 <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
>,
1555 and started it using virt-manager.
</p
>
1557 <p
>The first think I had to do after logging in (root without any
1558 password) was to get the network operational. I followed
1559 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1560 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1561 commands as root to get the machine to accept a IP address from the
1562 kvm internal DHCP server:
</p
>
1564 <p
><blockquote
><pre
>
1565 settrans -fgap /dev/netdde /hurd/netdde
1566 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1567 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1569 </pre
></blockquote
></p
>
1571 <p
>After this, the machine had internet connectivity, and I could
1572 upgrade it and install the sysvinit packages from experimental and
1573 enable it as the default boot system in Hurd.
</p
>
1575 <p
>But before I did that, I set a password on the root user, as ssh is
1576 running on the machine it for ssh login to work a password need to be
1577 set. Also, note that a bug somewhere in openssh on Hurd block
1578 compression from working. Remember to turn that off on the client
1581 <p
>Run these commands as root to upgrade and test the new sysvinit
1584 <p
><blockquote
><pre
>
1585 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1586 deb http://http.debian.net/debian/ experimental main
1589 apt-get dist-upgrade
1590 apt-get install -t experimental initscripts sysv-rc sysvinit \
1591 sysvinit-core sysvinit-utils
1592 update-alternatives --config runsystem
1593 </pre
></blockquote
></p
>
1595 <p
>To reboot after switching boot system, you have to use
1596 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1597 yet a sysvinit process able to receive the signals from the normal
1598 'reboot
' command. After switching to sysvinit as the boot system,
1599 upgrading every package and rebooting, the network come up with DHCP
1600 after boot as it should, and the settrans/pkill hack mentioned at the
1601 start is no longer needed. But for some strange reason, there are no
1602 longer any login prompt in the virtual console, so I logged in using
1605 <p
>Note that there are some race conditions in Hurd making the boot
1606 fail some times. No idea what the cause is, but hope the Hurd porters
1607 figure it out. At least Justus said on IRC (#debian-hurd on
1608 irc.debian.org) that they are aware of the problem. A way to reduce
1609 the impact is to upgrade to the Hurd packages built by Justus by
1610 adding this repository to the machine:
</p
>
1612 <p
><blockquote
><pre
>
1613 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
1614 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1616 </pre
></blockquote
></p
>
1618 <p
>At the moment the prebuilt virtual machine get some packages from
1619 http://ftp.debian-ports.org/debian, because some of the packages in
1620 unstable do not yet include the required patches that are lingering in
1621 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
1623 <p
><blockquote
><pre
>
1624 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
1625 i emacs - GNU Emacs editor (metapackage)
1626 i gdb - GNU Debugger
1627 i hurd-recommended - Miscellaneous translators
1628 i isc-dhcp-client - ISC DHCP client
1629 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1630 i libc-bin - Embedded GNU C Library: Binaries
1631 i libc-dev-bin - Embedded GNU C Library: Development binaries
1632 i libc0.3 - Embedded GNU C Library: Shared libraries
1633 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1634 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1635 i multiarch-support - Transitional package to ensure multiarch compatibilit
1636 i A x11-common - X Window System (X.Org) infrastructure
1637 i xorg - X.Org X Window System
1638 i A xserver-xorg - X.Org X server
1639 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1641 </pre
></blockquote
></p
>
1643 <p
>All in all, testing hurd has been an interesting experience. :)
1644 X.org did not work out of the box and I never took the time to follow
1645 the porters instructions to fix it. This time I was interested in the
1646 command line stuff.
<p
>
1651 <title>New chrpath release
0.16</title>
1652 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
1653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
1654 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
1655 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
1656 find problems in C, C++ and Java code using static source code
1657 analysis. It can detect a lot of different problems, and is very
1658 useful to find memory and locking bugs in the error handling part of
1659 the source. The company behind it provide
1660 <a href=
"https://scan.coverity.com/
">check of free software projects as
1661 a community service
</a
>, and many hundred free software projects are
1662 already checked. A few days ago I decided to have a closer look at
1663 the Coverity system, and discovered that the
1664 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
1665 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
1666 projects I am involved with was already registered. But these are
1667 fairly big, and I would also like to have a small and easy project to
1668 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
1669 checking of the chrpath project
</a
>. It was
1670 added to the checker and discovered seven potential defects. Six of
1671 these were real, mostly resource
"leak
" when the program detected an
1672 error. Nothing serious, as the resources would be released a fraction
1673 of a second later when the program exited because of the error, but it
1674 is nice to do it right in case the source of the program some time in
1675 the future end up in a library. Having fixed all defects and added
1676 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
1677 mailing list for the chrpath developers
</a
>, I decided it was time to
1678 publish a new release. These are the release notes:
</p
>
1680 <p
>New in
0.16 released
2014-
01-
14:
</p
>
1684 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
1685 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
1686 <li
>Mention new project mailing list in the documentation.
</li
>
1691 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1692 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
1693 project if something is wrong with the new release. The test suite
1694 did not discover any old errors, so if you find a new one, please also
1695 include a test suite check.
</p
>
1700 <title>New chrpath release
0.15</title>
1701 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
1702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
1703 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
1704 <description><p
>After many years break from the package and a vain hope that
1705 development would be continued by someone else, I finally pulled my
1706 acts together this morning and wrapped up a new release of chrpath,
1707 the command line tool to modify the rpath and runpath of already
1708 compiled ELF programs. The update was triggered by the persistence of
1709 Isha Vishnoi at IBM, which needed a new config.guess file to get
1710 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
1711 is working on. I checked the
1712 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
1713 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
1714 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
1715 packages for interesting patches (failed to find the source from
1716 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1717 These are the release notes:
</p
>
1719 <p
>New in
0.15 released
2013-
11-
24:
</p
>
1723 <li
>Updated config.sub and config.guess from the GNU project to work
1724 with newer architectures. Thanks to isha vishnoi for the heads
1727 <li
>Updated README with current URLs.
</li
>
1729 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1730 Matthias Klose.
</li
>
1732 <li
>Added missing help for -k|--keepgoing option, using patch by
1733 Petr Machata found in Fedora.
</li
>
1735 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
1736 .dynamic is a NULL terminated string. Based on patch found in
1737 Fedora credited Axel Thimm and Christian Krause.
</li
>
1742 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1743 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
1744 project if something is wrong with the new release. The test suite
1745 did not discover any old errors, so if you find a new one, please also
1746 include a testsuite check.
</p
>
1751 <title>Debian init.d boot script example for rsyslog
</title>
1752 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
1753 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
1754 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
1755 <description><p
>If one of the points of switching to a new init system in Debian is
1756 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
1757 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
1758 init.d scripts at all. Here is an example init.d script, ie a rewrite
1759 of /etc/init.d/rsyslog:
</p
>
1761 <p
><pre
>
1762 #!/lib/init/init-d-script
1765 # Required-Start: $remote_fs $time
1766 # Required-Stop: umountnfs $time
1767 # X-Stop-After: sendsigs
1768 # Default-Start:
2 3 4 5
1769 # Default-Stop:
0 1 6
1770 # Short-Description: enhanced syslogd
1771 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1772 # It is quite compatible to stock sysklogd and can be
1773 # used as a drop-in replacement.
1775 DESC=
"enhanced syslogd
"
1776 DAEMON=/usr/sbin/rsyslogd
1777 </pre
></p
>
1779 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
1780 script was
137 lines, and the above is just
15 lines, most of it meta
1781 info/comments.
</p
>
1783 <p
>How to do this, you ask? Well, one create a new script
1784 /lib/init/init-d-script looking something like this:
1786 <p
><pre
>
1789 # Define LSB log_* functions.
1790 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
1791 # and status_of_proc is working.
1792 . /lib/lsb/init-functions
1795 # Function that starts the daemon/service
1801 #
0 if daemon has been started
1802 #
1 if daemon was already running
1803 #
2 if daemon could not be started
1804 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
1806 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1809 # Add code here, if necessary, that waits for the process to be ready
1810 # to handle requests from services started subsequently which depend
1811 # on this one. As a last resort, sleep for some time.
1815 # Function that stops the daemon/service
1820 #
0 if daemon has been stopped
1821 #
1 if daemon was already stopped
1822 #
2 if daemon could not be stopped
1823 # other if a failure occurred
1824 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
1825 RETVAL=
"$?
"
1826 [
"$RETVAL
" =
2 ]
&& return
2
1827 # Wait for children to finish too if this is a daemon that forks
1828 # and if the daemon is only ever run from this initscript.
1829 # If the above conditions are not satisfied then add some other code
1830 # that waits for the process to drop all resources that could be
1831 # needed by services started subsequently. A last resort is to
1832 # sleep for some time.
1833 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
1834 [
"$?
" =
2 ]
&& return
2
1835 # Many daemons don
't delete their pidfiles when they exit.
1837 return
"$RETVAL
"
1841 # Function that sends a SIGHUP to the daemon/service
1845 # If the daemon can reload its configuration without
1846 # restarting (for example, when it is sent a SIGHUP),
1847 # then implement that here.
1849 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
1854 scriptbasename=
"$(basename $
1)
"
1855 echo
"SN: $scriptbasename
"
1856 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
1857 script=
"$
1"
1864 NAME=$(basename $DAEMON)
1865 PIDFILE=/var/run/$NAME.pid
1867 # Exit if the package is not installed
1868 #[ -x
"$DAEMON
" ] || exit
0
1870 # Read configuration variable file if it is present
1871 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
1873 # Load the VERBOSE setting and other rcS variables
1876 case
"$
1" in
1878 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
1880 case
"$?
" in
1881 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1882 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1886 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
1888 case
"$?
" in
1889 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1890 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1894 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
1896 #reload|force-reload)
1898 # If do_reload() is not implemented then leave this commented out
1899 # and leave
'force-reload
' as an alias for
'restart
'.
1901 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
1905 restart|force-reload)
1907 # If the
"reload
" option is implemented then remove the
1908 #
'force-reload
' alias
1910 log_daemon_msg
"Restarting $DESC
" "$NAME
"
1912 case
"$?
" in
1915 case
"$?
" in
1917 1) log_end_msg
1 ;; # Old process is still running
1918 *) log_end_msg
1 ;; # Failed to start
1928 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
1934 </pre
></p
>
1936 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
1937 lot. I did not really polish the approach, so it might not always
1938 work out of the box, but you get the idea. I did not try very hard to
1939 optimize it nor make it more robust either.
</p
>
1941 <p
>A better argument for switching init system in Debian than reducing
1942 the size of init scripts (which is a good thing to do anyway), is to
1943 get boot system that is able to handle the kernel events sensibly and
1944 robustly, and do not depend on the boot to run sequentially. The boot
1945 and the kernel have not behaved sequentially in years.
</p
>
1950 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
1951 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
1952 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
1953 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
1954 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
1955 remote display access is the preferred solution with oVirt and RedHat
1956 Enterprise Virtualization, and I was sad to discover the other day
1957 that the browser plugin needed to use these systems seamlessly was
1958 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
1959 for a package
</a
> was from
2012-
04-
10 with no progress since
1960 2013-
04-
01, so I decided to wrap up a package based on the great work
1961 from Cajus Pollmeier and put it in a collab-maint maintained git
1962 repository to get a package I could use. I would very much like
1963 others to help me maintain the package (or just take over, I do not
1964 mind), but as no-one had volunteered so far, I just uploaded it to
1965 NEW. I hope it will be available in Debian in a few days.
</p
>
1967 <p
>The source is now available from
1968 <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
>
1973 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
1974 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
1975 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
1976 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
1977 <description><p
>The
1978 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
1979 program is a a very nice system to create virtual machine images. It
1980 create a image file, add a partition table, mount it and run
1981 debootstrap in the mounted directory to create a Debian system on a
1982 stick. Yesterday, I decided to try to teach it how to make images for
1983 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
1984 of a plan to simplify the build system for
1985 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
1986 project
</a
>. The FreedomBox project already uses vmdebootstrap for
1987 the virtualbox images, but its current build system made multistrap
1988 based system for Dreamplug images, and it is lacking support for
1989 Raspberry Pi.
</p
>
1991 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
1992 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1993 code and adjusted it to be able to build armel images on my amd64
1994 Debian laptop. I ended up giving vmdebootstrap five new options,
1995 allowing me to replicate the image creation process I use to make
1996 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
1997 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
1998 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
1999 call debootstrap with --foreign and to copy the handler into the
2000 generated chroot before running the second stage. This allow
2001 vmdebootstrap to create armel images on an amd64 host. Next I added
2002 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
2003 fstype
</tt
> to teach it to create a separate /boot/ partition with the
2004 given file system type, allowing me to create an image with a vfat
2005 partition for the /boot/ stuff. I also added a
<tt
>--variant
2006 variant
</tt
> option to allow me to create smaller images without the
2007 Debian base system packages installed. Finally, I added an option
2008 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
2009 as a boot loader. It is not needed on the Raspberry Pi and probably
2010 most other non-x86 architectures. The changes were accepted by the
2011 upstream author of vmdebootstrap yesterday and today, and is now
2013 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
2014 upstream project page
</a
>.
</p
>
2016 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
2017 create a small script (the customize script) to add the non-free
2018 binary blob needed to boot the Raspberry Pi and the APT source
2021 <p
><pre
>
2023 set -e # Exit on first error
2024 rootdir=
"$
1"
2025 cd
"$rootdir
"
2026 cat
&lt;
&lt;EOF
> etc/apt/sources.list
2027 deb http://http.debian.net/debian/ jessie main contrib non-free
2029 # Install non-free binary blob needed to boot Raspberry Pi. This
2030 # install a kernel somewhere too.
2031 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2032 -O $rootdir/usr/bin/rpi-update
2033 chmod a+x $rootdir/usr/bin/rpi-update
2034 mkdir -p $rootdir/lib/modules
2035 touch $rootdir/boot/start.elf
2036 chroot $rootdir rpi-update
2037 </pre
></p
>
2039 <p
>Next, fetch the latest vmdebootstrap script and call it like this
2040 to build the image:
</p
>
2043 sudo ./vmdebootstrap \
2046 --distribution jessie \
2047 --mirror http://http.debian.net/debian \
2056 --root-password raspberry \
2057 --hostname raspberrypi \
2058 --foreign /usr/bin/qemu-arm-static \
2059 --customize `pwd`/customize \
2061 --package git-core \
2062 --package binutils \
2063 --package ca-certificates \
2066 </pre
></p
>
2068 <p
>The list of packages being installed are the ones needed by
2069 rpi-update to make the image bootable on the Raspberry Pi, with the
2070 exception of netbase, which is needed by debootstrap to find
2071 /etc/hosts with the minbase variant. I really wish there was a way to
2072 set up an Raspberry Pi using only packages in the Debian archive, but
2073 that is not possible as far as I know, because it boots from the GPU
2074 using a non-free binary blob.
</p
>
2076 <p
>The build host need debootstrap, kpartx and qemu-user-static and
2077 probably a few others installed. I have not checked the complete
2078 build dependency list.
</p
>
2080 <p
>The resulting image will not use the hardware floating point unit
2081 on the Raspberry PI, because the armel architecture in Debian is not
2082 optimized for that use. So the images created will be a bit slower
2083 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
2088 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
2089 <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>
2090 <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>
2091 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
2092 <description><p
>The last few days I came across a few good causes that should get
2093 wider attention. I recommend signing and donating to each one of
2096 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
2097 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
2098 Women program which is a Google Summer of Code like initiative to get
2099 more women involved in free software. One debian sponsor has offered
2100 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
2101 earmarked
</a
> for this initiative. I donated a few minutes ago, and
2102 hope you will to. :)
</p
>
2104 <p
>And the Electronic Frontier Foundation just announced plans to
2105 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
2106 documentaries about the excessive spying
</a
> on every Internet user that
2107 take place these days, and their need to fund the work. I
've already
2108 donated. Are you next?
</p
>
2110 <p
>For my Norwegian audience, the organisation Studentenes og
2111 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2112 statement under the heading
2113 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
2114 Access
</a
> for those of us asking for more focus on open access in the
2115 Norwegian government. So far
499 signatures. I hope you will sign it
2121 <title>Videos about the Freedombox project - for inspiration and learning
</title>
2122 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
2123 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
2124 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
2125 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
2126 project
</a
> have been going on for a while, and have presented the
2127 vision, ideas and solution several places. Here is a little
2128 collection of videos of talks and presentation of the project.
</p
>
2132 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
2133 2,
5 minute marketing film
</a
> (Youtube)
</li
>
2135 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
2136 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
2138 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
2139 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2140 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
2141 (Youtube)
</li
>
2143 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
2144 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
2146 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
2147 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
2149 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
2150 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2151 York City in
2012</a
> (Youtube)
</li
>
2153 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
2154 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
2155 (Youtube)
</li
>
2157 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
2158 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
2160 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
2161 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
2163 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
2164 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2165 2013</a
> (Youtube)
</li
>
2169 <p
>A larger list is available from
2170 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
2171 Freedombox Wiki
</a
>.
</p
>
2173 <p
>On other news, I am happy to report that Freedombox based on Debian
2174 Jessie is coming along quite well, and soon both Owncloud and using
2175 Tor should be available for testers of the Freedombox solution. :) In
2176 a few weeks I hope everything needed to test it is included in Debian.
2177 The withsqlite package is already in Debian, and the plinth package is
2178 pending in NEW. The third and vital part of that puzzle is the
2179 metapackage/setup framework, which is still pending an upload. Join
2180 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
2181 (#freedombox on irc.debian.org)
</a
> and
2182 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2183 mailing list
</a
> if you want to help make this vision come true.
</p
>
2188 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
2189 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
2190 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
2191 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
2192 <description><p
>I was introduced to the
2193 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
2194 in
2010, when Eben Moglen presented his vision about serving the need
2195 of non-technical people to keep their personal information private and
2196 within the legal protection of their own homes. The idea is to give
2197 people back the power over their network and machines, and return
2198 Internet back to its intended peer-to-peer architecture. Instead of
2199 depending on a central service, the Freedombox will give everyone
2200 control over their own basic infrastructure.
</p
>
2202 <p
>I
've intended to join the effort since then, but other tasks have
2203 taken priority. But this summers nasty news about the misuse of trust
2204 and privilege exercised by the
"western
" intelligence gathering
2205 communities increased my eagerness to contribute to a point where I
2206 actually started working on the project a while back.
</p
>
2208 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
2209 Debian initiative
</a
> based on the vision from Eben Moglen, is to
2210 create a simple and cheap Debian based appliance that anyone can hook
2211 up in their home and get access to secure and private services and
2212 communication. The initial deployment platform have been the
2213 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
2214 which is a piece of hardware I do not own. So to be able to test what
2215 the current Freedombox setup look like, I had to come up with a way to install
2216 it on some hardware I do have access to. I have rewritten the
2217 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
2218 image build framework to use .deb packages instead of only copying
2219 setup into the boot images, and thanks to this rewrite I am able to
2220 set up any machine supported by Debian Wheezy as a Freedombox, using
2221 the previously mentioned deb (and a few support debs for packages
2222 missing in Debian).
</p
>
2224 <p
>The current Freedombox setup consist of a set of bootstrapping
2226 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
2227 and a administrative web interface
2228 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
2229 withsqlite), as well as a privacy enhancing proxy based on
2230 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
2231 (freedombox-privoxy). There is also a web/javascript based XMPP
2232 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
2233 trying (unsuccessfully so far) to talk to the XMPP server
2234 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
2235 web interface is pluggable, and the goal is to use it to enable OpenID
2236 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2237 this is really working yet, see
2238 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
2239 project TODO
</a
> for links to GIT repositories. Most of the code is
2240 on github at the moment. The HTTP proxy is operational out of the
2241 box, and the admin web interface can be used to add/remove plinth
2242 users. I
've not been able to do anything else with it so far, but
2243 know there are several branches spread around github and other places
2244 with lots of half baked features.
</p
>
2246 <p
>Anyway, if you want to have a look at the current state, the
2247 following recipes should work to give you a test machine to poke
2250 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
2254 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
2255 <li
>Boot from it, either as CD or USB stick.
</li
>
2256 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
2257 to the Debian installer:
<p
>
2258 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
2260 <li
>Answer the few language/region/password questions and pick disk to
2261 install on.
</li
>
2263 <li
>When the installation is finished and the machine have rebooted a
2264 few times, your Freedombox is ready for testing.
</li
>
2268 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
2272 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
2273 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
2274 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
2276 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
2277 </pre
></li
>
2278 <li
><p
>Run this as root:
</p
>
2280 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2283 apt-get install freedombox-setup
2284 /usr/lib/freedombox/setup
2285 </pre
></li
>
2286 <li
>Reboot into your freshly created Freedombox.
</li
>
2290 <p
>You can test it on other architectures too, but because the
2291 freedombox-privoxy package is binary, it will only work as intended on
2292 the architectures where I have had time to build the binary and put it
2293 in my APT repository. But do not let this stop you. It is only a
2294 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
2296 <p
>Note that by default Freedombox is a DHCP server on the
2297 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
2298 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
2299 disable
</tt
>" as root.
</p
>
2301 <p
>Please let me know if this works for you, or if you have any
2302 problems. We gather on the IRC channel
2303 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
2304 irc.debian.org and the
2305 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
2306 mailing list
</a
>.
</p
>
2308 <p
>Once you get your freedombox operational, you can visit
2309 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
2310 welcome screen (dead end - do not be surprised if you are unable to
2311 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
2312 to look at the rest of plinth. The default user is
'admin
' and the
2313 default password is
'secret
'.
</p
>
2318 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
2319 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
2320 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
2321 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
2322 <description><p
>Earlier, I reported about
2323 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
2324 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
2325 told by IBM that the original disk should be thrown away. And as
2326 there no longer was a problem if I bricked the firmware, I decided
2327 today to try to install Intel firmware to replace the Lenovo firmware
2328 currently on the disk.
</p
>
2330 <p
>I searched the Intel site for firmware, and found
2331 <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
>
2332 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2333 according to the site should contain the latest firmware for SSD
2334 disks. I inserted the broken disk in one of my spare laptops and
2335 booted the ISO from a USB stick. The disk was recognized, but the
2336 program claimed the newest firmware already were installed and refused
2337 to insert any Intel firmware. So no change, and the disk is still
2338 unable to handle write load. :( I guess the only way to get them
2339 working would be if Lenovo releases new firmware. No idea how likely
2340 that is. Anyway, just blogging about this test for completeness. I
2341 got a working Samsung disk, and see no point in spending more time on
2342 the broken disks.
</p
>
2347 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
2348 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
2349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
2350 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
2351 <description><p
>Today I switched to
2352 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
2353 new laptop
</a
>. I
've previously written about the problems I had with
2354 my new Thinkpad X230, which was delivered with an
2355 <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
2356 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
2357 sustained writes. My hardware supplier have been very forthcoming in
2358 trying to find a solution, and after first trying with another
2359 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
2360 disk instead to fix it once and for all. The Samsung disk survived
2361 the installation of Debian with encrypted disks (filling the disk with
2362 random data during installation killed the first two), and I thus
2363 decided to trust it with my data. I have installed it as a Debian Edu
2364 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2365 server at home using Kerberos and LDAP, and will use it as my work
2366 station from now on.
</p
>
2368 <p
>As this is a solid state disk with no moving parts, I believe the
2369 Debian Wheezy default installation need to be tuned a bit to increase
2370 performance and increase life time of the disk. The Linux kernel and
2371 user space applications do not yet adjust automatically to such
2372 environment. To make it easier for my self, I created a draft Debian
2373 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
2374 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
2375 for the ssd-setup package
</a
> is available from collab-maint, and it
2376 is set up to adjust the setup of the machine by just installing the
2377 package. If there is any non-SSD disk in the machine, the package
2378 will refuse to install, as I did not try to write any logic to sort
2379 file systems in SSD and non-SSD file systems.
</p
>
2381 <p
>I consider the package a draft, as I am a bit unsure how to best
2382 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2383 where I set up the machine with one large encrypted partition (in
2384 addition to /boot), put LVM on top of this and set up partitions on
2385 top of this again. See the README file in the package source for the
2386 references I used to pick the settings. At the moment these
2387 parameters are tuned:
</p
>
2391 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
2392 (adding discard to /etc/crypttab)
</li
>
2394 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
2395 this case a cryptsetup partition) by changing issue_discards from
2396 0 to
1 in /etc/lvm/lvm.conf.
</li
>
2398 <li
>Set relatime as a file system option for ext3 and ext4 file
2401 <li
>Tell swap to use TRIM commands by adding
'discard
' to
2402 /etc/fstab.
</li
>
2404 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
2406 <li
>Run fstrim on every ext3 and ext4 file system every night (from
2407 cron.daily).
</li
>
2409 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
2410 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
2414 <p
>During installation, I cancelled the part where the installer fill
2415 the disk with random data, as this would kill the SSD performance for
2416 little gain. My goal with the encrypted file system is to ensure
2417 those stealing my laptop end up with a brick and not a working
2418 computer. I have no hope in keeping the really resourceful people
2419 from getting the data on the disk (see
2420 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
2421 Thus I concluded that adding the discard option to crypttab is the
2422 right thing to do.
</p
>
2424 <p
>I considered using the noop I/O scheduler, as several recommended
2425 it for SSD, but others recommended deadline and a benchmark I found
2426 indicated that deadline might be better for interactive use.
</p
>
2428 <p
>I also considered using the
'discard
' file system option for ext3
2429 and ext4, but read that it would give a performance hit ever time a
2430 file is removed, and thought it best to that that slowdown once a day
2431 instead of during my work.
</p
>
2433 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2434 this is already done by Debian Edu.
</p
>
2436 <p
>I have not yet started on the user space tuning. I expect
2437 iceweasel need some tuning, and perhaps other applications too, but
2438 have not yet had time to investigate those parts.
</p
>
2440 <p
>The package should work on Ubuntu too, but I have not yet tested it
2443 <p
>As for the answer to the question in the title of this blog post,
2444 as far as I know, the only solution I know about is to replace the
2445 disk. It might be possible to flash it with Intel firmware instead of
2446 the Lenovo firmware. But I have not tried and did not want to do so
2447 without approval from Lenovo as I wanted to keep the warranty on the
2448 disk until a solution was found and they wanted the broken disks
2454 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
2455 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
2456 <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>
2457 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
2458 <description><p
>A few days ago, I wrote about
2459 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
2460 problems I experienced with my new X230 and its SSD disk
</a
>, which
2461 was dying during installation because it is unable to cope with
2462 sustained write. My supplier is in contact with
2463 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
2464 replacement disk to try to fix the problem. They decided to send an
2465 identical model, so my hopes for a permanent fix was slim.
</p
>
2467 <p
>Anyway, today I got the replacement disk and tried to install
2468 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2469 same firmware version as the original. This time my hope raised
2470 slightly as the installation progressed, as the original disk used to
2471 die after
4-
7% of the disk was written to, while this time it kept
2472 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
2473 died again and I was back on square one. I still do not have a new
2474 laptop with a disk I can trust. I can not live with a disk that might
2475 lock up when I download a new
2476 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
2477 other large files. I look forward to hearing from my supplier with
2478 the next proposal from Lenovo.
</p
>
2480 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
2481 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2482 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2483 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
2484 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2485 P/N
45N8295, P0C38732.
</p
>
2487 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
2488 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
2489 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2490 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
2491 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2492 P/N
45N8295, P0C38732.
</p
>
2494 <p
>The only difference is in the first number (serial number?), ISN,
2495 SA, date and WNPP values. Mentioning all the details here in case
2496 someone is able to use the information to find a way to identify the
2497 failing disk among working ones (if any such working disk actually
2503 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
2504 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
2505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2506 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2507 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2508 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2509 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2510 member assosiation NUUG
</a
> and
2511 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2512 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2513 Bitraf
</a
>.
</p
>
2515 <p
>It starts
10:
00 and continue until late evening. Everyone is
2516 welcome, and there is no fee to participate. There is on the other
2517 hand limited space, and only room for
30 people. Please put your name
2518 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2519 wiki page
</a
> if you plan to join us.
</p
>
2524 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2525 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2526 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2527 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2528 <description><p
>Half a year ago, I reported that I had to find a
2529 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2530 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2531 time to spend on it, and it took a while to find a model I believe
2532 will do the job, but two days ago the replacement finally arrived. I
2534 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2535 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2536 a roaming workstation, and it seemed to work flawlessly. But my
2537 second installation with encrypted disk was not as successful. More
2538 on that below.
</p
>
2540 <p
>I had a hard time trying to track down a good laptop, as my most
2541 important requirements (robust and with a good keyboard) are never
2542 listed in the feature list. But I did get good help from the search
2543 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2544 allowed me to limit the list of interesting laptops based on my other
2545 requirements. A bit surprising that SSD disk are not disks according
2546 to that search interface, so I had to drop specifying the number of
2547 disks from my search parameters. I also asked around among friends to
2548 get their impression on keyboards and robustness.
</p
>
2550 <p
>So the new laptop arrived, and it is quite a lot wider than the
2551 X41. I am not quite convinced about the keyboard, as it is
2552 significantly wider than my old keyboard, and I have to stretch my
2553 hand a lot more to reach the edges. But the key response is fairly
2554 good and the individual key shape is fairly easy to handle, so I hope
2555 I will get used to it. My old X40 was starting to fail, and I really
2556 needed a new laptop now. :)
</p
>
2558 <p
>Turning off the touch pad was simple. All it took was a quick
2559 visit to the BIOS during boot it disable it.
</p
>
2561 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2562 lock up during load. And this happen when installing Debian Wheezy
2563 with encrypted disk, while the disk is being filled with random data.
2564 I also tested to install Ubuntu Raring, and it happen there too if I
2565 reenable the code to fill the disk with random data (it is disabled by
2566 default in Ubuntu). And the bug with is already known. It was
2567 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2568 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2569 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2570 kernel developers as
2571 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2572 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2573 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2574 Lenovo forums, both for
2575 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2576 2012-
11-
10</a
> and for
2577 <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
2578 03-
20-
2013</a
>. The problem do not only affect installation. The
2579 reports state that the disk lock up during use if many writes are done
2580 on the disk, so it is much no use to work around the installation
2581 problem and end up with a computer that can lock up at any moment.
2583 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2584 available
</a
> that will lock up the hard drive after running a few
2585 minutes by writing to a file.
</p
>
2587 <p
>I
've contacted my supplier and asked how to handle this, and after
2588 contacting PCHELP Norway (request
01D1FDP) which handle support
2589 requests for Lenovo, his first suggestion was to upgrade the disk
2590 firmware. Unfortunately there is no newer firmware available from
2591 Lenovo, as my disk already have the most recent one (version LF1i). I
2592 hope to hear more from him today and hope the problem can be
2598 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2599 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2600 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2601 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
2602 <description><p
>Half a year ago, I reported that I had to find a replacement for my
2603 trusty old Thinkpad X41. Unfortunately I did not have much time to
2604 spend on it, but today the replacement finally arrived. I ended up
2605 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
2606 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
2607 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2608 this, it is installing what I hope will be a more final installation,
2609 with a encrypted hard drive to ensure any dope head stealing it end up
2610 with an expencive door stop.
</p
>
2612 <p
>I had a hard time trying to track down a good laptop, as my most
2613 important requirements (robust and with a good keyboard) are never
2614 listed in the feature list. But I did get good help from the search
2615 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2616 allowed me to limit the list of interesting laptops based on my other
2617 requirements. A bit surprising that SSD disk are not disks, so I had
2618 to drop number of disks from my search parameters.
</p
>
2620 <p
>I am not quite convinced about the keyboard, as it is significantly
2621 wider than my old keyboard, and I have to stretch my hand a lot more
2622 to reach the edges. But the key response is fairly good and the
2623 individual key shape is fairly easy to handle, so I hope I will get
2624 used to it. My old X40 was starting to fail, and I really needed a
2625 new laptop now. :)
</p
>
2627 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
2632 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
2633 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
2634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
2635 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
2636 <description><p
>It annoys me when the computer fail to do automatically what it is
2637 perfectly capable of, and I have to do it manually to get things
2638 working. One such task is to find out what firmware packages are
2639 needed to get the hardware on my computer working. Most often this
2640 affect the wifi card, but some times it even affect the RAID
2641 controller or the ethernet card. Today I pushed version
0.4 of the
2642 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
2643 including a new script isenkram-autoinstall-firmware handling the
2644 process of asking all the loaded kernel modules what firmware files
2645 they want, find debian packages providing these files and install the
2646 debian packages. Here is a test run on my laptop:
</p
>
2648 <p
><pre
>
2649 # isenkram-autoinstall-firmware
2650 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2651 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2652 info: locating packages with the requested firmware files
2653 info: Updating APT sources after adding non-free APT source
2654 info: trying to install firmware-ipw2x00
2657 Preconfiguring packages ...
2658 Selecting previously deselected package firmware-ipw2x00.
2659 (Reading database ...
259727 files and directories currently installed.)
2660 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2661 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
2663 </pre
></p
>
2665 <p
>When all the requested firmware is present, a simple message is
2666 printed instead:
</p
>
2668 <p
><pre
>
2669 # isenkram-autoinstall-firmware
2670 info: did not find any firmware files requested by loaded kernel modules. exiting
2672 </pre
></p
>
2674 <p
>It could use some polish, but it is already working well and saving
2675 me some time when setting up new machines. :)
</p
>
2677 <p
>So, how does it work? It look at the set of currently loaded
2678 kernel modules, and look up each one of them using modinfo, to find
2679 the firmware files listed in the module meta-information. Next, it
2680 download the Contents file from a nearby APT mirror, and search for
2681 the firmware files in this file to locate the package with the
2682 requested firmware file. If the package is in the non-free section, a
2683 non-free APT source is added and the package is installed using
2684 <tt
>apt-get install
</tt
>. The end result is a slightly better working
2687 <p
>I hope someone find time to implement a more polished version of
2688 this script as part of the hw-detect debian-installer module, to
2689 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
2690 #
655507</a
>. There really is no need to insert USB sticks with
2691 firmware during a PXE install when the packages already are available
2692 from the nearby Debian mirror.
</p
>
2697 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
2698 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
2699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
2700 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
2701 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2702 the screen just turn black when Linux boot, either during installation
2703 or on first boot from the hard disk. I
've seen it once in a while the
2704 last few years, but only recently understood the cause. I
've seen it
2705 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2706 The reason seem to be in the wiring of some laptops. The system to
2707 control the screen background light is inverted, so when Linux try to
2708 turn the brightness fully on, it end up turning it off instead. I do
2709 not know which Linux drivers are affected, but this post is about the
2710 i915 driver used by the
2711 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2712 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
2714 <p
>The problem can be worked around two ways. Either by adding
2715 i915.invert_brightness=
1 as a kernel option, or by adding a file in
2716 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
2717 option when it load the i915 kernel module. On Debian and Ubuntu, it
2718 can be done by running these commands as root:
</p
>
2721 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
2722 update-initramfs -u -k all
2725 <p
>Since March
2012 there is
2726 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
2727 mechanism in the Linux kernel
</a
> to tell the i915 driver which
2728 hardware have this problem, and get the driver to invert the
2729 brightness setting automatically. To use it, one need to add a row in
2730 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
2731 intel_quirks array
</a
> in the driver source
2732 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
2733 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
2734 number (vendor number
8086 is assumed) and subdevice vendor and device
2737 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
2738 -vvnn
</tt
> for the video card in question:
</p
>
2740 <p
><pre
>
2741 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
2742 3rd Gen Core processor Graphics Controller [
8086:
0156] \
2743 (rev
09) (prog-if
00 [VGA controller])
2744 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
2745 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2746 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2747 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
2748 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
2750 Interrupt: pin A routed to IRQ
42
2751 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
2752 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
2753 Region
4: I/O ports at
4000 [size=
64]
2754 Expansion ROM at
<unassigned
> [disabled]
2755 Capabilities:
<access denied
>
2756 Kernel driver in use: i915
2757 </pre
></p
>
2759 <p
>The resulting intel_quirks entry would then look like this:
</p
>
2761 <p
><pre
>
2762 struct intel_quirk intel_quirks[] = {
2764 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2765 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
2768 </pre
></p
>
2770 <p
>According to the kernel module instructions (as seen using
2771 <tt
>modinfo i915
</tt
>), information about hardware needing the
2772 invert_brightness flag should be sent to the
2773 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
2774 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
2775 developers. But my email about the laptop sent
2013-
06-
03 have not
2777 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
2778 web archive for the mailing list
</a
>, so I suspect they do not accept
2779 emails from non-subscribers. Because of this, I sent my patch also to
2780 the Debian bug tracking system instead as
2781 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
2782 sure the patch is not lost.
</p
>
2784 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
2785 with this problem working properly with Linux. If you use Gnome, your
2786 worries should be over at this point. But if you use KDE, there is
2787 something in KDE ignoring the invert_brightness setting and turning on
2788 the screen during login. I
've reported it to Debian as
2789 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
2790 have no idea yet how to figure out exactly what subsystem is doing
2791 this. Perhaps you can help? Perhaps you know what the Gnome
2792 developers did to handle this, and this can give a clue to the KDE
2793 developers? Or you know where in KDE the screen brightness is changed
2794 during login? If so, please update the BTS report (or get in touch if
2795 you do not know how to update BTS).
</p
>
2797 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
2798 acpi_backlight=vendor, to disable ACPI backlight support completely,
2799 as the ACPI information on the machine is trash and it is better to
2800 leave it to the intel video driver to control the screen
2801 backlight.
</p
>
2806 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
2807 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
2808 <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>
2809 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
2810 <description><p
>Two days ago, I asked
2811 <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
2812 I could install Linux on a Packard Bell EasyNote LV computer
2813 preinstalled with Windows
8</a
>. I found a solution, but am horrified
2814 with the obstacles put in the way of Linux users on a laptop with UEFI
2815 and Windows
8.
</p
>
2817 <p
>I never found out if the cause of my problems were the use of UEFI
2818 secure booting or fast boot. I suspect fast boot was the problem,
2819 causing the firmware to boot directly from HD without considering any
2820 key presses and alternative devices, but do not know UEFI settings
2821 enough to tell.
</p
>
2823 <p
>There is no way to install Linux on the machine in question without
2824 opening the box and disconnecting the hard drive! This is as far as I
2825 can tell, the only way to get access to the firmware setup menu
2826 without accepting the Windows
8 license agreement. I am told (and
2827 found description on how to) that it is possible to configure the
2828 firmware setup once booted into Windows
8. But as I believe the terms
2829 of that agreement are completely unacceptable, accepting the license
2830 was never an alternative. I do not enter agreements I do not intend
2831 to follow.
</p
>
2833 <p
>I feared I had to return the laptops and ask for a refund, and
2834 waste many hours on this, but luckily there was a way to get it to
2835 work. But I would not recommend it to anyone planning to run Linux on
2836 it, and I have become sceptical to Windows
8 certified laptops. Is
2837 this the way Linux will be forced out of the market place, by making
2838 it close to impossible for
"normal
" users to install Linux without
2839 accepting the Microsoft Windows license terms? Or at least not
2840 without risking to loose the warranty?
</p
>
2842 <p
>I
've updated the
2843 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
2844 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
2845 do not have to struggle as much as I did to get Linux into the
2848 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2849 Michael Tokarev and others for feedback and ideas.
</p
>
2854 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
2855 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
2856 <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>
2857 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
2858 <description><p
>I
've run into quite a problem the last few days. I bought three
2859 new laptops for my parents and a few others. I bought Packard Bell
2860 Easynote LV to run Kubuntu on and use as their home computer. But I
2861 am completely unable to figure out how to install Linux on it. The
2862 computer is preinstalled with Windows
8, and I suspect it uses UEFI
2863 instead of a BIOS to boot.
</p
>
2865 <p
>The problem is that I am unable to get it to PXE boot, and unable
2866 to get it to boot the Linux installer from my USB stick. I have yet
2867 to try the DVD install, and still hope it will work. when I turn on
2868 the computer, there is no information on what buttons to press to get
2869 the normal boot menu. I expect to get some boot menu to select PXE or
2870 USB stick booting. When booting, it first ask for the language to
2871 use, then for some regional settings, and finally if I will accept the
2872 Windows
8 terms of use. As these terms are completely unacceptable to
2873 me, I have no other choice but to turn off the computer and try again
2874 to get it to boot the Linux installer.
</p
>
2876 <p
>I have gathered my findings so far on a Linlap page about the
2877 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2878 EasyNote LV
</a
> model. If you have any idea how to get Linux
2879 installed on this machine, please get in touch or update that wiki
2880 page. If I can
't find a way to install Linux, I will have to return
2881 the laptop to the seller and find another machine for my parents.
</p
>
2883 <p
>I wonder, is this the way Linux will be forced out of the market
2884 using UEFI and
"secure boot
" by making it impossible to install Linux
2885 on new Laptops?
</p
>
2890 <title>How to transform a Debian based system to a Debian Edu installation
</title>
2891 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
2892 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
2893 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
2894 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
2895 an operating system based on Debian intended for use in schools. It
2896 contain a turn-key solution for the computer network provided to
2897 pupils in the primary schools. It provide both the central server,
2898 network boot servers and desktop environments with heaps of
2899 educational software. The project was founded almost
12 years ago,
2900 2001-
07-
02. If you want to support the project, which is in need for
2901 cash to fund developer gatherings and other project related activity,
2902 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
2903 donate some money
</a
>.
2905 <p
>A topic that come up again and again on the Debian Edu mailing
2906 lists and elsewhere, is the question on how to transform a Debian or
2907 Ubuntu installation into a Debian Edu installation. It isn
't very
2908 hard, and last week I wrote a script to replicate the steps done by
2909 the Debian Edu installer.
</p
>
2911 <p
>The script,
2912 <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/
>
2913 in the debian-edu-config package, will go through these six steps and
2914 transform an existing Debian Wheezy or Ubuntu (untested) installation
2915 into a Debian Edu Workstation:
</p
>
2919 <li
>Add skolelinux related APT sources.
</li
>
2920 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
2921 <li
>Install debian-edu-install to load preseeding values and pull in
2922 our configuration.
</li
>
2923 <li
>Preseed debconf database with profile setup in
2924 /etc/debian-edu/config, and run tasksel to install packages
2925 according to the profile specified in the config above,
2926 overriding some of the Debian automation machinery.
</li
>
2927 <li
>Run debian-edu-cfengine-D installation to configure everything
2928 that could not be done using preseeding.
</li
>
2929 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
2933 <p
>There are some steps in the Debian Edu installation that can not be
2934 replicated like this. Disk partitioning and LVM setup, for example.
2935 So this script just assume there is enough disk space to install all
2936 the needed packages.
</p
>
2938 <p
>The script was created to help a Debian Edu student working on
2939 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
2940 Debian Edu client, and using it he can take the existing
2941 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
2942 transform it into a fully functioning Debian Edu Workstation (or
2943 Roaming Workstation, or whatever :).
</p
>
2945 <p
>The default setting in the script is to create a KDE Workstation.
2946 If a LXDE based Roaming workstation is wanted instead, modify the
2947 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
2949 <p
><pre
>
2950 PROFILE=
"Roaming-Workstation
"
2951 DESKTOP=
"lxde
"
2952 </pre
></p
>
2954 <p
>The script could even become useful to set up Debian Edu servers in
2955 the cloud, by starting with a virtual Debian installation at some
2956 virtual hosting service and setting up all the services on first
2962 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
2963 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
2964 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
2965 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
2966 <description><P
>In January,
2967 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
2968 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
2969 channel #debian-lego
</a
>, for those of us in the Debian and Linux
2970 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
2971 marvellous construction system from Denmark. We also created
2972 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
2973 a place to take notes and write down our plans and hopes. And several
2974 people showed up to help. I was very happy to see the effect of my
2975 call. Since the small start, we have a debtags tag
2976 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
2977 tag for LEGO related packages, and now count
10 packages related to
2978 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
2980 <p
><table
>
2981 <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
>
2982 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
2983 <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
>
2984 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
2985 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
2986 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
2987 <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
>
2988 <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
>
2989 <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
>
2990 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
2991 </table
></p
>
2993 <p
>Some of these are available in Wheezy, and all but one are
2994 currently available in Jessie/testing. leocad is so far only
2995 available in experimental.
</p
>
2997 <p
>If you care about LEGO in Debian, please join us on IRC and help
2998 adding the rest of the great free software tools available on Linux
2999 for LEGO designers.
</p
>
3004 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
3005 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
3006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
3007 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
3008 <description><p
>When I woke up this morning, I was very happy to see that the
3009 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
3010 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
3011 Debian release, and I expect to move my machines at home over to it fairly
3014 <p
>The new debian release contain heaps of new stuff, and one program
3015 in particular make me very happy to see included. The
3016 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
3017 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
3018 included for the first time. Alongside similar programs like
3019 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
3020 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
3021 it allow for visual programming where syntax errors can not happen,
3022 and a friendly programming environment for learning to control the
3023 computer. Scratch will also be included in the next release of Debian
3026 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
3027 Edu/Skolelinux release too. The
3028 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
3029 alpha release
</a
> went out last week, and the next should soon
3035 <title>Isenkram
0.2 finally in the Debian archive
</title>
3036 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
3037 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
3038 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
3039 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
3040 package
</a
> finally made it into the archive, after lingering in NEW
3041 for many months. I uploaded it to the Debian experimental suite
3042 2013-
01-
27, and today it was accepted into the archive.
</p
>
3044 <p
>Isenkram is a system for suggesting to users what packages to
3045 install to work with a pluggable hardware device. The suggestion pop
3046 up when the device is plugged in. For example if a Lego Mindstorm NXT
3047 is inserted, it will suggest to install the program needed to program
3048 the NXT controller. Give it a go, and report bugs and suggestions to
3054 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
3055 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
3056 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
3057 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
3058 <description><p
>My
3059 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
3060 bitcoin related blog post
</a
> mentioned that the new
3061 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
3062 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3063 2013-
01-
19, and have been available in unstable since then. It was
3064 automatically copied to Ubuntu, and is available in their Raring
3065 version too.
</p
>
3067 <p
>But there is a strange problem with the build that block this new
3068 version from being available on the i386 and kfreebsd-i386
3069 architectures. For some strange reason, the autobuilders in Debian
3070 for these architectures fail to run the test suite on these
3071 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
3072 We are so far unable to reproduce it when building it manually, and
3073 no-one have been able to propose a fix. If you got an idea what is
3074 failing, please let us know via the BTS.
</p
>
3076 <p
>One feature that is annoying me with of the bitcoin client, because
3077 I often run low on disk space, is the fact that the client will exit
3078 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
3079 #
696715</a
>). So make sure you have enough disk space when you run
3082 <p
>As usual, if you use bitcoin and want to show your support of my
3083 activities, please send Bitcoin donations to my address
3084 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3089 <title>Welcome to the world, Isenkram!
</title>
3090 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
3091 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
3092 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
3093 <description><p
>Yesterday, I
3094 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
3095 for testers
</a
> for my prototype for making Debian better at handling
3096 pluggable hardware devices, which I
3097 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
3098 out to create
</a
> earlier this month. Several valuable testers showed
3099 up, and caused me to really want to to open up the development to more
3100 people. But before I did this, I want to come up with a sensible name
3101 for this project. Today I finally decided on a new name, and I have
3102 renamed the project from hw-support-handler to this new name. In the
3103 process, I moved the source to git and made it available as a
3104 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
3105 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
3106 To fetch and build the latest version of the source, use
</p
>
3109 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3110 cd isenkram
&& git-buildpackage -us -uc
3113 <p
>I have not yet adjusted all files to use the new name yet. If you
3114 want to hack on the source or improve the package, please go ahead.
3115 But please talk to me first on IRC or via email before you do major
3116 changes, to make sure we do not step on each others toes. :)
</p
>
3118 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
3119 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3120 stuff, in other words. I
've been told it is the Norwegian variant of
3121 the German word eisenkram, for those that are familiar with that
3124 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
3125 instructions, to avoid confusing people with an error from the signing
3128 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
3129 clone argument to avoid the need for authentication.
</p
>
3134 <title>First prototype ready making hardware easier to use in Debian
</title>
3135 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
3136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
3137 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
3138 <description><p
>Early this month I set out to try to
3139 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
3140 the Debian support for pluggable hardware devices
</a
>. Now my
3141 prototype is working, and it is ready for a larger audience. To test
3143 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
3144 from the Debian Edu subversion repository
</a
>, build and install the
3145 package. You might have to log out and in again activate the
3146 autostart script.
</p
>
3148 <p
>The design is simple:
</p
>
3152 <li
>Add desktop entry in /usr/share/autostart/ causing a program
3153 hw-support-handlerd to start when the user log in.
</li
>
3155 <li
>This program listen for kernel events about new hardware (directly
3156 from the kernel like udev does), not using HAL dbus events as I
3157 initially did.
</li
>
3159 <li
>When new hardware is inserted, look up the hardware modalias in
3160 the APT database, a database
3161 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
3162 via HTTP
</a
> and a database available as part of the package.
</li
>
3164 <li
>If a package is mapped to the hardware in question, the package
3165 isn
't installed yet and this is the first time the hardware was
3166 plugged in, show a desktop notification suggesting to install the
3167 package or packages.
</li
>
3169 <li
>If the user click on the
'install package now
' button, ask
3170 aptdaemon via the PackageKit API to install the requrired package.
</li
>
3172 <li
>aptdaemon ask for root password or sudo password, and install the
3173 package while showing progress information in a window.
</li
>
3177 <p
>I still need to come up with a better name for the system. Here
3178 are some screen shots showing the prototype in action. First the
3179 notification, then the password request, and finally the request to
3180 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
3182 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
3183 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
3184 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
3185 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
3186 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
3188 <p
>The prototype still need to be improved with longer timeouts, but
3189 is already useful. The database of hardware to package mappings also
3190 need more work. It is currently compatible with the Ubuntu way of
3191 storing such information in the package control file, but could be
3192 changed to use other formats instead or in addition to the current
3193 method. I
've dropped the use of discover for this mapping, as the
3194 modalias approach is more flexible and easier to use on Linux as long
3195 as the Linux kernel expose its modalias strings directly.
</p
>
3197 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
3198 here is the command required to check out and build the source: Use
3199 '<tt
>svn checkout
3200 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3201 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
3202 devscripts package.
</p
>
3204 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
3205 renamed to Isenkram and the source moved from the Debian Edu
3206 subversion repository to a Debian collab-maint git repository. See
3207 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
3208 instructions
</a
> for details.
</p
>
3213 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
3214 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
3215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
3216 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
3217 <description><p
>This Christmas my trusty old laptop died. It died quietly and
3218 suddenly in bed. With a quiet whimper, it went completely quiet and
3219 black. The power button was no longer able to turn it on. It was a
3220 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3221 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3222 Compaq I had before that. Now I need to find a replacement. To keep
3223 going during Christmas, I moved the one year old SSD disk to my old
3224 X40 where it fitted (only one I had left that could use it), but it is
3225 not a durable solution.
3227 <p
>My laptop needs are fairly modest. This is my wishlist from when I
3228 got a new one more than
10 years ago. It still holds true.:)
</p
>
3232 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
3233 than A4).
</li
>
3234 <li
>Robust, it will be in my backpack every day.
</li
>
3235 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
3236 <li
>Long battery life time. Preferable a week.
</li
>
3237 <li
>Internal WIFI network card.
</li
>
3238 <li
>Internal Twisted Pair network card.
</li
>
3239 <li
>Some USB slots (
2-
3 is plenty)
</li
>
3240 <li
>Good keyboard - similar to the Thinkpad.
</li
>
3241 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
3243 <li
>Hardware supported by Debian Stable, ie the default kernel and
3244 X.org packages.
</li
>
3245 <li
>Quiet, preferably fan free (or at least not using the fan most of
3250 <p
>You will notice that there are no RAM and CPU requirements in the
3251 list. The reason is simply that the specifications on laptops the
3252 last
10-
15 years have been sufficient for my needs, and I have to look
3253 at other features to choose my laptop. But are there still made as
3254 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3255 robust, and Thinkpads seem to be heading in the wrong direction since
3256 Lenovo took over. But I
've been told that X220 and X1 Carbon might
3257 still be useful.
</p
>
3259 <p
>Perhaps I should rethink my needs, and look for a pad with an
3260 external keyboard? I
'll have to check the
3261 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
3262 well-supported laptops, or perhaps just buy one preinstalled from one
3263 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
3264 Pre-loaded site
</a
>.
</p
>
3269 <title>How to find a browser plugin supporting a given MIME type
</title>
3270 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
3271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
3272 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
3273 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
3274 install to get support for a given MIME type. Thanks to
3275 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
3276 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
3277 Unfortunately, not very many packages provide the needed meta
3278 information, Anyway, here is a small script to look up all browser
3279 plugin packages announcing ther MIME support using this specification:
</p
>
3285 def pkgs_handling_mimetype(mimetype):
3290 version = pkg.candidate
3292 version = pkg.installed
3295 record = version.record
3296 if not record.has_key(
'Npp-MimeType
'):
3298 mime_types = record[
'Npp-MimeType
'].split(
',
')
3299 for t in mime_types:
3300 t = t.rstrip().strip()
3302 thepkgs.append(pkg.name)
3304 mimetype =
"audio/ogg
"
3305 if
1 < len(sys.argv):
3306 mimetype = sys.argv[
1]
3307 print
"Browser plugin packages supporting %s:
" % mimetype
3308 for pkg in pkgs_handling_mimetype(mimetype):
3309 print
" %s
" %pkg
3312 <p
>It can be used like this to look up a given MIME type:
</p
>
3315 % ./apt-find-browserplug-for-mimetype
3316 Browser plugin packages supporting audio/ogg:
3318 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3319 Browser plugin packages supporting application/x-shockwave-flash:
3320 browser-plugin-gnash
3324 <p
>In Ubuntu this mechanism is combined with support in the browser
3325 itself to query for plugins and propose to install the needed
3326 packages. It would be great if Debian supported such feature too. Is
3327 anyone working on adding it?
</p
>
3329 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
3330 request for icweasel support for this feature is
3331 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
3332 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
3333 of manpower and wish for a different design is the reason thus feature
3334 is not yet in iceweasel from Debian.
</p
>
3339 <title>What is the most supported MIME type in Debian?
</title>
3340 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
3341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
3342 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
3343 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
3344 proposal to add AppStream information to the Debian archive
</a
>, is a
3345 proposal to make it possible for a Desktop application to propose to
3346 the user some package to install to gain support for a given MIME
3347 type, font, library etc. that is currently missing. With such
3348 mechanism in place, it would be possible for the desktop to
3349 automatically propose and install leocad if some LDraw file is
3350 downloaded by the browser.
</p
>
3352 <p
>To get some idea about the current content of the archive, I decided
3353 to write a simple program to extract all .desktop files from the
3354 Debian archive and look up the claimed MIME support there. The result
3356 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
3357 site
</a
>. Using the collected information, it become possible to
3358 answer the question in the title. Here are the
20 most supported MIME
3359 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3360 The complete list is available from the link above.
</p
>
3362 <p
><strong
>Debian Stable:
</strong
></p
>
3366 ----- -----------------------
3382 18 application/x-ogg
3389 <p
><strong
>Debian Testing:
</strong
></p
>
3393 ----- -----------------------
3409 18 application/x-ogg
3416 <p
><strong
>Debian Unstable:
</strong
></p
>
3420 ----- -----------------------
3437 18 application/x-ogg
3443 <p
>I am told that PackageKit can provide an API to access the kind of
3444 information mentioned in DEP-
11. I have not yet had time to look at
3445 it, but hope the PackageKit people in Debian are on top of these
3448 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
3449 discovering a typo in my script.
</p
>
3454 <title>Using modalias info to find packages handling my hardware
</title>
3455 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
3456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
3457 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
3458 <description><p
>Yesterday, I wrote about the
3459 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
3460 values provided by the Linux kernel
</a
> following my hope for
3461 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
3462 dongle support in Debian
</a
>. Using this knowledge, I have tested how
3463 modalias values attached to package names can be used to map packages
3464 to hardware. This allow the system to look up and suggest relevant
3465 packages when I plug in some new hardware into my machine, and replace
3466 discover and discover-data as the database used to map hardware to
3469 <p
>I create a modaliases file with entries like the following,
3470 containing package name, kernel module name (if relevant, otherwise
3471 the package name) and globs matching the relevant hardware
3474 <p
><blockquote
>
3475 Package: package-name
3476 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
3477 </blockquote
></p
>
3479 <p
>It is fairly trivial to write code to find the relevant packages
3480 for a given modalias value using this file.
</p
>
3482 <p
>An entry like this would suggest the video and picture application
3483 cheese for many USB web cameras (interface bus class
0E01):
</p
>
3485 <p
><blockquote
>
3487 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
3488 </blockquote
></p
>
3490 <p
>An entry like this would suggest the pcmciautils package when a
3491 CardBus bridge (bus class
0607) PCI device is present:
</p
>
3493 <p
><blockquote
>
3494 Package: pcmciautils
3495 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3496 </blockquote
></p
>
3498 <p
>An entry like this would suggest the package colorhug-client when
3499 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
3501 <p
><blockquote
>
3502 Package: colorhug-client
3503 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
3504 </blockquote
></p
>
3506 <p
>I believe the format is compatible with the format of the Packages
3507 file in the Debian archive. Ubuntu already uses their Packages file
3508 to store their mappings from packages to hardware.
</p
>
3510 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3511 announce the hardware it support in a way my prototype understand.
3512 This allow those publishing packages in an APT source outside the
3513 Debian archive as well as those backporting packages to make sure the
3514 hardware mapping are included in the package meta information. I
've
3515 tested such header in the pymissile package, and its modalias mapping
3516 is working as it should with my prototype. It even made it to Ubuntu
3519 <p
>To test if it was possible to look up supported hardware using only
3520 the shell tools available in the Debian installer, I wrote a shell
3521 implementation of the lookup code. The idea is to create files for
3522 each modalias and let the shell do the matching. Please check out and
3524 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3525 shell script. It run without any extra dependencies and fetch the
3526 hardware mappings from the Debian archive and the subversion
3527 repository where I currently work on my prototype.
</p
>
3529 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3530 install yubikey-personalization:
</p
>
3532 <p
><blockquote
>
3533 % ./hw-support-lookup
3534 <br
>yubikey-personalization
3536 </blockquote
></p
>
3538 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3539 propose to install the pcmciautils package:
</p
>
3541 <p
><blockquote
>
3542 % ./hw-support-lookup
3543 <br
>pcmciautils
3545 </blockquote
></p
>
3547 <p
>If you know of any hardware-package mapping that should be added to
3548 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3549 database
</a
>, please tell me about it.
</p
>
3551 <p
>It could be possible to generate several of the mappings between
3552 packages and hardware. One source would be to look at packages with
3553 kernel modules, ie packages with *.ko files in /lib/modules/, and
3554 extract their modalias information. Another would be to look at
3555 packages with udev rules, ie packages with files in
3556 /lib/udev/rules.d/, and extract their vendor/model information to
3557 generate a modalias matching rule. I have not tested any of these to
3558 see if it work.
</p
>
3560 <p
>If you want to help implementing a system to let us propose what
3561 packages to install when new hardware is plugged into a Debian
3562 machine, please send me an email or talk to me on
3563 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3568 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3569 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3571 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3572 <description><p
>While looking into how to look up Debian packages based on hardware
3573 information, to find the packages that support a given piece of
3574 hardware, I refreshed my memory regarding modalias values, and decided
3575 to document the details. Here are my findings so far, also available
3577 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3578 Debian Edu subversion repository
</a
>:
3580 <p
><strong
>Modalias decoded
</strong
></p
>
3582 <p
>This document try to explain what the different types of modalias
3583 values stands for. It is in part based on information from
3584 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3585 &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;,
3586 &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
3587 &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;.
3589 <p
>The modalias entries for a given Linux machine can be found using
3590 this shell script:
</p
>
3593 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3596 <p
>The supported modalias globs for a given kernel module can be found
3597 using modinfo:
</p
>
3600 % /sbin/modinfo psmouse | grep alias:
3601 alias: serio:ty05pr*id*ex*
3602 alias: serio:ty01pr*id*ex*
3606 <p
><strong
>PCI subtype
</strong
></p
>
3608 <p
>A typical PCI entry can look like this. This is an Intel Host
3609 Bridge memory controller:
</p
>
3611 <p
><blockquote
>
3612 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3613 </blockquote
></p
>
3615 <p
>This represent these values:
</p
>
3620 sv
00001028 (subvendor)
3621 sd
000001AD (subdevice)
3623 sc
00 (bus subclass)
3627 <p
>The vendor/device values are the same values outputted from
'lspci
3628 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
3629 0600. The
0600 class is a host bridge. Other useful bus values are
3630 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
3632 <p
>Not sure how to figure out the interface value, nor what it
3635 <p
><strong
>USB subtype
</strong
></p
>
3637 <p
>Some typical USB entries can look like this. This is an internal
3638 USB hub in a laptop:
</p
>
3640 <p
><blockquote
>
3641 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3642 </blockquote
></p
>
3644 <p
>Here is the values included in this alias:
</p
>
3647 v
1D6B (device vendor)
3648 p
0001 (device product)
3650 dc
09 (device class)
3651 dsc
00 (device subclass)
3652 dp
00 (device protocol)
3653 ic
09 (interface class)
3654 isc
00 (interface subclass)
3655 ip
00 (interface protocol)
3658 <p
>The
0900 device class/subclass means hub. Some times the relevant
3659 class is in the interface class section. For a simple USB web camera,
3660 these alias entries show up:
</p
>
3662 <p
><blockquote
>
3663 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3664 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3665 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3666 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3667 </blockquote
></p
>
3669 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
3670 camera),
0101 is audio control device and
0102 is audio streaming (aka
3671 microphone). Thus this is a camera with microphone included.
</p
>
3673 <p
><strong
>ACPI subtype
</strong
></p
>
3675 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
3676 receiver in a Thinkpad X40:
</p
>
3678 <p
><blockquote
>
3679 acpi:IBM0071:PNP0511:
3680 </blockquote
></p
>
3682 <p
>The values between the colons are IDs.
</p
>
3684 <p
><strong
>DMI subtype
</strong
></p
>
3686 <p
>The DMI table contain lots of information about the computer case
3687 and model. This is an entry for a IBM Thinkpad X40, fetched from
3688 /sys/devices/virtual/dmi/id/modalias:
</p
>
3690 <p
><blockquote
>
3691 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3692 </blockquote
></p
>
3694 <p
>The values present are
</p
>
3697 bvn IBM (BIOS vendor)
3698 bvr
1UETB
6WW(
1.66) (BIOS version)
3699 bd
06/
15/
2005 (BIOS date)
3700 svn IBM (system vendor)
3701 pn
2371H4G (product name)
3702 pvr ThinkPadX40 (product version)
3703 rvn IBM (board vendor)
3704 rn
2371H4G (board name)
3705 rvr NotAvailable (board version)
3706 cvn IBM (chassis vendor)
3707 ct
10 (chassis type)
3708 cvr NotAvailable (chassis version)
3711 <p
>The chassis type
10 is Notebook. Other interesting values can be
3712 found in the dmidecode source:
</p
>
3716 4 Low Profile Desktop
3729 17 Main Server Chassis
3730 18 Expansion Chassis
3732 20 Bus Expansion Chassis
3733 21 Peripheral Chassis
3735 23 Rack Mount Chassis
3744 <p
>The chassis type values are not always accurately set in the DMI
3745 table. For example my home server is a tower, but the DMI modalias
3746 claim it is a desktop.
</p
>
3748 <p
><strong
>SerIO subtype
</strong
></p
>
3750 <p
>This type is used for PS/
2 mouse plugs. One example is from my
3751 test machine:
</p
>
3753 <p
><blockquote
>
3754 serio:ty01pr00id00ex00
3755 </blockquote
></p
>
3757 <p
>The values present are
</p
>
3766 <p
>This type is supported by the psmouse driver. I am not sure what
3767 the valid values are.
</p
>
3769 <p
><strong
>Other subtypes
</strong
></p
>
3771 <p
>There are heaps of other modalias subtypes according to
3772 file2alias.c. There is the rest of the list from that source: amba,
3773 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3774 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3775 vmbus, x86cpu and zorro. I did not spend time documenting all of
3776 these, as they do not seem relevant for my intended use with mapping
3777 hardware to packages when new stuff is inserted during run time.
</p
>
3779 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
3781 <p
>To check which kernel modules provide support for a given modalias,
3782 one can use the following shell script:
</p
>
3785 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
3786 echo
"$id
" ; \
3787 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
3791 <p
>The output can look like this (only the first few entries as the
3792 list is very long on my test machine):
</p
>
3796 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
3798 FATAL: Module acpi:device: not found.
3800 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
3801 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
3802 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
3803 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3804 acpi:IBM0071:PNP0511:
3805 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
3806 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
3807 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
3811 <p
>If you want to help implementing a system to let us propose what
3812 packages to install when new hardware is plugged into a Debian
3813 machine, please send me an email or talk to me on
3814 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3816 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
3817 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
3818 in /sys/ with space in them.
</p
>
3823 <title>Moved the pymissile Debian packaging to collab-maint
</title>
3824 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
3825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
3826 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
3827 <description><p
>As part of my investigation on how to improve the support in Debian
3828 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3829 Launcher and updated the Debian package
3830 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
3831 sure udev will fix the device permissions when it is plugged in. I
3832 also added a
"Modaliases
" header to test it in the Debian archive and
3833 hopefully make the package be proposed by jockey in Ubuntu when a user
3834 plug in his rocket launcher. In the process I moved the source to a
3835 git repository under collab-maint, to make it easier for any DD to
3836 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
3837 is not very active, but the software still work for me even after five
3838 years of relative silence. The new git repository is not listed in
3839 the uploaded package yet, because I want to test the other changes a
3840 bit more before I upload the new version. If you want to check out
3841 the new version with a .desktop file included, visit the
3842 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
3843 view
</a
> or use
"<tt
>git clone
3844 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
3849 <title>Lets make hardware dongles easier to use in Debian
</title>
3850 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
3851 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
3852 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
3853 <description><p
>One thing that annoys me with Debian and Linux distributions in
3854 general, is that there is a great package management system with the
3855 ability to automatically install software packages by downloading them
3856 from the distribution mirrors, but no way to get it to automatically
3857 install the packages I need to use the hardware I plug into my
3858 machine. Even if the package to use it is easily available from the
3859 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3860 suggest to automatically install the python-nxt, nbc and t2n packages
3861 I need to talk to it. When I plug in a Yubikey, it could propose the
3862 yubikey-personalization package. The information required to do this
3863 is available, but no-one have pulled all the pieces together.
</p
>
3865 <p
>Some years ago, I proposed to
3866 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
3867 the discover subsystem to implement this
</a
>. The idea is fairly
3872 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
3873 starting when a user log in.
</li
>
3875 <li
>Set this program up to listen for kernel events emitted when new
3876 hardware is inserted into the computer.
</li
>
3878 <li
>When new hardware is inserted, look up the hardware ID in a
3879 database mapping to packages, and take note of any non-installed
3880 packages.
</li
>
3882 <li
>Show a message to the user proposing to install the discovered
3883 package, and make it easy to install it.
</li
>
3887 <p
>I am not sure what the best way to implement this is, but my
3888 initial idea was to use dbus events to discover new hardware, the
3889 discover database to find packages and
3890 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
3893 <p
>Yesterday, I found time to try to implement this idea, and the
3894 draft package is now checked into
3895 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3896 Debian Edu subversion repository
</a
>. In the process, I updated the
3897 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
3898 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3899 the relevant packages in Debian, and uploaded a new version
3900 2.2013.01.09 to unstable. I also discovered that the current
3901 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
3902 package in Debian no longer discovered any USB devices, because
3903 /proc/bus/usb/devices is no longer present. I ported it to use
3904 libusb as a fall back option to get it working. The fixed package
3905 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
3906 because of the freeze).
</p
>
3908 <p
>With this prototype in place, I can insert my Yubikey, and get this
3909 desktop notification to show up (only once, the first time it is
3910 inserted):
</p
>
3912 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
3914 <p
>For this prototype to be really useful, some way to automatically
3915 install the proposed packages by pressing the
"Please install
3916 program(s)
" button should to be implemented.
</p
>
3918 <p
>If this idea seem useful to you, and you want to help make it
3919 happen, please help me update the discover-data database with mappings
3920 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
3921 list the package you would like to have installed when a given
3922 hardware device is inserted into your computer, and report bugs using
3923 reportbug if it isn
't. Or, if you know of a better way to provide
3924 such mapping, please let me know.
</p
>
3926 <p
>This prototype need more work, and there are several questions that
3927 should be considered before it is ready for production use. Is dbus
3928 the correct way to detect new hardware? At the moment I look for HAL
3929 dbus events on the system bus, because that is the events I could see
3930 on my Debian Squeeze KDE desktop. Are there better events to use?
3931 How should the user be notified? Is the desktop notification
3932 mechanism the best option, or should the background daemon raise a
3933 popup instead? How should packages be installed? When should they
3934 not be installed?
</p
>
3936 <p
>If you want to help getting such feature implemented in Debian,
3937 please send me an email. :)
</p
>
3942 <title>New IRC channel for LEGO designers using Debian
</title>
3943 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
3944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
3945 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
3946 <description><p
>During Christmas, I have worked a bit on the Debian support for
3947 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
3948 NXT
</a
>. My son and I have played a bit with my NXT set, and I
3949 discovered I had to build all the tools myself because none were
3950 already in Debian Squeeze. If Debian support for LEGO is something
3951 you care about, please join me on the IRC channel
3952 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
3953 irc.debian.org). There is a lot that could be done to improve the
3954 Debian support for LEGO designers. For example both CAD software
3955 and Mindstorm compilers are missing. :)
</p
>
3957 <p
>Update
2012-
01-
03: A
3958 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
3959 including links to Lego related packages is now available.
</p
>
3964 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
3965 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
3966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
3967 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
3968 <description><p
>Let me start by wishing you all marry Christmas and a happy new
3969 year! I hope next year will prove to be a good year.
</p
>
3971 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
3972 decentralised
"currency
" that allow people to transfer bitcoins
3973 between each other with minimal overhead, is a very interesting
3974 experiment. And as I wrote a few days ago, the bitcoin situation in
3975 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
3976 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
3977 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
3978 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
3979 for one of the ftpmasters to approve the new bitcoin-qt package
3982 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
3983 team in Debian, you can easily test the package in Debian Squeeze
3984 using the following steps to get a set of working packages:
</p
>
3986 <blockquote
><pre
>
3987 git clone git://git.debian.org/git/collab-maint/bitcoin
3989 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3990 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3991 </pre
></blockquote
>
3993 <p
>You might have to install some build dependencies as well. The
3994 list of commands should give you two packages, bitcoind and
3995 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3996 client will download the complete set of bitcoin
"blocks
", which need
3997 around
5.6 GiB of data on my machine at the moment. Make sure your
3998 ~/.bitcoin/ directory have lots of spare room if you want to download
3999 all the blocks. The client will warn if the disk is getting full, so
4000 there is not really a problem if you got too little room, but you will
4001 not be able to get all the features out of the client.
</p
>
4003 <p
>As usual, if you use bitcoin and want to show your support of my
4004 activities, please send Bitcoin donations to my address
4005 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4010 <title>A word on bitcoin support in Debian
</title>
4011 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
4012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
4013 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
4014 <description><p
>It has been a while since I wrote about
4015 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
4016 peer-to-peer based crypto-currency, and the reason is simply that I
4017 have been busy elsewhere. But two days ago, I started looking at the
4018 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
4019 Debian
</a
> again to try to recover my old bitcoin wallet. The package
4020 is now maintained by a
4021 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
4022 people
</a
>, and the grunt work had already been done by this team. We
4023 owe a huge thank you to all these team members. :)
4024 But I was sad to discover that the bitcoin client is missing in
4025 Wheezy. It is only available in Sid (and an outdated client from
4026 backports). The client had several RC bugs registered in BTS blocking
4027 it from entering testing. To try to help the team and improve the
4028 situation, I spent some time providing patches and triaging the bug
4029 reports. I also had a look at the bitcoin package available from Matt
4031 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
4032 Ubuntu
</a
>, and moved the useful pieces from that version into the
4033 Debian package.
</p
>
4035 <p
>After checking with the main package maintainer Jonas Smedegaard on
4036 IRC, I pushed several patches into the collab-maint git repository to
4037 improve the package. It now contains fixes for the RC issues (not from
4038 me, but fixed by Scott Howard), build rules for a Qt GUI client
4039 package, konqueror support for the bitcoin: URI and bash completion
4040 setup. As I work on Debian Squeeze, I also created
4041 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
4042 patch to backport
</a
> the latest version. Jonas is going to look at
4043 it and try to integrate it into the git repository before uploading a
4044 new version to unstable.
4046 <p
>I would very much like bitcoin to succeed, to get rid of the
4047 centralized control currently exercised in the monetary system. I
4048 find it completely unacceptable that the USA government is collecting
4049 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4050 that the major credit card companies can block legal money
4051 transactions to Wikileaks. But for bitcoin to succeed, more people
4052 need to use bitcoins, and more people need to accept bitcoins when
4053 they sell products and services. Improving the bitcoin support in
4054 Debian is a small step in the right direction, but not enough.
4055 Unfortunately the user experience when browsing the web and wanting to
4056 pay with bitcoin is still not very good. The bitcoin: URI is a step
4057 in the right direction, but need to work in most or every browser in
4058 use. Also the bitcoin-qt client is too heavy to fire up to do a
4059 quick transaction. I believe there are other clients available, but
4060 have not tested them.
</p
>
4063 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
4064 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
4065 I received
20.15 BTC so far on the address I provided in my blog two
4066 years ago, as can be
4067 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
4068 on the blockexplorer service
</a
>. Thank you everyone for your
4069 donation. The blockexplorer service demonstrates quite well that
4070 bitcoin is not quite anonymous and untracked. :) I wonder if the
4071 number of users have gone up since then. If you use bitcoin and want
4072 to show your support of my activity, please send Bitcoin donations to
4073 the same address as last time,
4074 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4079 <title>Git repository for song book for Computer Scientists
</title>
4080 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
4081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
4082 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
4083 <description><p
>As I
4084 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
4085 this summer
</a
>, I have created a Computer Science song book a few
4086 years ago, and today I finally found time to create a public
4087 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
4088 repository for the project
</a
>.
</p
>
4090 <p
>If you want to help out, please clone the source and submit patches
4091 to the HTML version. To generate the PDF and PostScript version,
4092 please use prince XML, or let me know about a useful free software
4093 processor capable of creating a good looking PDF from the HTML.
</p
>
4095 <p
>Want to sing? You can still find the song book in HTML, PDF and
4096 PostScript formats at
4097 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
4098 Science Songbook
</a
>.
</p
>
4103 <title>Gratulerer med
19-årsdagen, Debian!
</title>
4104 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
4105 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
4106 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
4107 <description><p
>I dag fyller
4108 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
4109 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
4110 si gratulerer med dagen, Debian!
</p
>
4115 <title>Song book for Computer Scientists
</title>
4116 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
4117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
4118 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
4119 <description><p
>Many years ago, while studying Computer Science at the
4120 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
4121 collecting computer related songs for use at parties. The original
4122 version was written in LaTeX, but a few years ago I got help from
4123 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4124 while keeping the ability to create a nice book in PDF format. I have
4125 not had time to maintain the book for a while now, and guess I should
4126 put it up on some public version control repository where others can
4127 help me extend and update the book. If anyone is volunteering to help
4128 me with this, send me an email. Also let me know if there are songs
4129 missing in my book.
</p
>
4131 <p
>I have not mentioned the book on my blog so far, and it occured to
4132 me today that I really should let all my readers share the joys of
4133 singing out load about programming, computers and computer networks.
4134 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
4135 12</a
> is about to start (and I am not going). Want to sing? Check
4136 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
4137 Computer Science Songbook
</a
>.
4142 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
4143 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
4144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
4145 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
4146 <description><p
>At work we have heaps of servers. I believe the total count is
4147 around
1000 at the moment. To be able to get help from the vendors
4148 when something go wrong, we want to keep the firmware on the servers
4149 up to date. If the firmware isn
't the latest and greatest, the
4150 vendors typically refuse to start debugging any problems until the
4151 firmware is upgraded. So before every reboot, we want to upgrade the
4152 firmware, and we would really like everyone handling servers at the
4153 university to do this themselves when they plan to reboot a machine.
4154 For that to happen we at the unix server admin group need to provide
4155 the tools to do so.
</p
>
4157 <p
>To make firmware upgrading easier, I am working on a script to
4158 fetch and install the latest firmware for the servers we got. Most of
4159 our hardware are from Dell and HP, so I have focused on these servers
4160 so far. This blog post is about the Dell part.
</P
>
4162 <p
>On the Dell FTP site I was lucky enough to find
4163 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
4164 with firmware information for all
11th generation servers, listing
4165 which firmware should be used on a given model and where on the FTP
4166 site I can find it. Using a simple perl XML parser I can then
4167 download the shell scripts Dell provides to do firmware upgrades from
4168 within Linux and reboot when all the firmware is primed and ready to
4169 be activated on the first reboot.
</p
>
4171 <p
>This is the Dell related fragment of the perl code I am working on.
4172 Are there anyone working on similar tools for firmware upgrading all
4173 servers at a site? Please get in touch and lets share resources.
</p
>
4175 <p
><pre
>
4179 use File::Temp qw(tempdir);
4181 # Install needed RHEL packages if missing
4183 'XML::Simple
' =
> 'perl-XML-Simple
',
4185 for my $module (keys %rhelmodules) {
4186 eval
"use $module;
";
4188 my $pkg = $rhelmodules{$module};
4189 system(
"yum install -y $pkg
");
4190 eval
"use $module;
";
4194 my $errorsto =
'pere@hungry.com
';
4200 sub run_firmware_script {
4201 my ($opts, $script) = @_;
4203 print STDERR
"fail: missing script name\n
";
4206 print STDERR
"Running $script\n\n
";
4208 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
4209 print STDERR
"success: firmware script ran succcessfully\n
";
4211 print STDERR
"fail: firmware script returned error\n
";
4215 sub run_firmware_scripts {
4216 my ($opts, @dirs) = @_;
4217 # Run firmware packages
4218 for my $dir (@dirs) {
4219 print STDERR
"info: Running scripts in $dir\n
";
4220 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
4221 while (my $s = readdir $dh) {
4222 next if $s =~ m/^\.\.?/;
4223 run_firmware_script($opts,
"$dir/$s
");
4231 print STDERR
"info: Downloading $url\n
";
4232 system(
"wget --quiet \
"$url\
"");
4237 my $product = `dmidecode -s system-product-name`;
4240 if ($product =~ m/PowerEdge/) {
4242 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4243 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
4245 my $tmpdir = tempdir(
4249 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
4250 system(
'gunzip Catalog.xml.gz
');
4251 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
4252 # -q is quiet, disabling interactivity and reducing console output
4253 my $fwopts =
"-q
";
4255 for my $url (@paths) {
4256 fetch_dell_fw($url);
4258 run_firmware_scripts($fwopts, $tmpdir);
4260 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4261 print STDERR
"error: Please report to $errorsto.\n
";
4265 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4266 print STDERR
"error: Please report to $errorsto.\n
";
4272 my $url =
"ftp://ftp.us.dell.com/$path
";
4276 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4277 # firmware packages to download from Dell. Only work for Linux
4278 # machines and
11th generation Dell servers.
4279 sub fetch_dell_fw_list {
4280 my $filename = shift;
4282 my $product = `dmidecode -s system-product-name`;
4284 my ($mybrand, $mymodel) = split(/\s+/, $product);
4286 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
4288 my $xml = XMLin($filename);
4290 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
4291 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
4292 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
4294 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
4295 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
4297 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
4299 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
4301 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
4304 for my $component (@{$xml-
>{SoftwareComponent}}) {
4305 my $componenttype = $component-
>{ComponentType}-
>{value};
4307 # Drop application packages, only firmware and BIOS
4308 next if
'APAC
' eq $componenttype;
4310 my $cpath = $component-
>{path};
4311 for my $path (@paths) {
4312 if ($cpath =~ m%/$path$%) {
4313 push(@paths, $cpath);
4321 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
4322 it could work on other platforms with some tweaking. Anyone know a
4323 index like Catalog.xml is available from HP for HP servers? At the
4324 moment I maintain a similar list manually and it is quickly getting
4330 <title>How is booting into runlevel
1 different from single user boots?
</title>
4331 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
4332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
4333 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
4334 <description><p
>Wouter Verhelst have some
4335 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
4336 comments and opinions
</a
> on my blog post on
4337 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
4338 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
4339 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
4340 default KDE desktop in Debian
</a
>. I only have time to address one
4341 small piece of his comment now, and though it best to address the
4342 misunderstanding he bring forward:
</p
>
4344 <p
><blockquote
>
4345 Currently, a system admin has four options: [...] boot to a
4346 single-user system (by adding
'single
' to the kernel command line;
4347 this runs rcS and rc1 scripts)
4348 </blockquote
></p
>
4350 <p
>This make me believe Wouter believe booting into single user mode
4351 and booting into runlevel
1 is the same. I am not surprised he
4352 believe this, because it would make sense and is a quite sensible
4353 thing to believe. But because the boot in Debian is slightly broken,
4354 runlevel
1 do not work properly and it isn
't the same as single user
4355 mode. I
'll try to explain what is actually happing, but it is a bit
4356 hard to explain.
</p
>
4358 <p
>Single user mode is defined like this in /etc/inittab:
4359 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
4360 executed in single user mode is sulogin. Single user mode is a boot
4361 state
"between
" the runlevels, and when booting into single user mode,
4362 only the scripts in /etc/rcS.d/ are executed before the init process
4363 enters the single user state. When switching to runlevel
1, the state
4364 is in fact not ending in runlevel
1, but it passes through runlevel
1
4365 and end up in the single user mode (see /etc/rc1.d/S03single, which
4366 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
4367 1. It is confusing that the
'S
' (single user) init mode is not the
4368 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4371 <p
>This summary might make it clearer. When booting for the first
4372 time into single user mode, the following commands are executed:
4373 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
4374 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
4375 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
4376 trying to continue after visiting single user mode. Not all services
4377 are started again as they should, causing the machine to end up in an
4378 unpredicatble state. This is why Debian admins recommend rebooting
4379 after visiting single user mode.
</p
>
4381 <p
>A similar problem with runlevel
1 is caused by the amount of
4382 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
4383 to runlevel
1, the services started from /etc/rcS.d/ are not properly
4384 stopped when passing through the scripts in /etc/rc1.d/, and not
4385 started again when switching away from runlevel
1 to the runlevels
4386 2-
5. I believe the problem is best fixed by moving all the scripts
4387 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
4388 functioning single user mode during boot.
</p
>
4390 <p
>I have spent several years investigating the Debian boot system,
4391 and discovered this problem a few years ago. I suspect it originates
4392 from when sysvinit was introduced into Debian, a long time ago.
</p
>
4397 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
4398 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
4399 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
4400 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
4401 <description><p
>In the Debian boot system, several packages include scripts that
4402 are started from /etc/rcS.d/. In fact, there is a bite more of them
4403 than make sense, and this causes a few problems. What kind of
4404 problems, you might ask. There are at least two problems. The first
4405 is that it is not possible to recover a machine after switching to
4406 runlevel
1. One need to actually reboot to get the machine back to
4407 the expected state. The other is that single user boot will sometimes
4408 run into problems because some of the subsystems are activated before
4409 the root login is presented, causing problems when trying to recover a
4410 machine from a problem in that subsystem. A minor additional point is
4411 that moving more scripts out of rcS.d/ and into the other rc#.d/
4412 directories will increase the amount of scripts that can run in
4413 parallel during boot, and thus decrease the boot time.
</p
>
4415 <p
>So, which scripts should start from rcS.d/. In short, only the
4416 scripts that _have_ to execute before the root login prompt is
4417 presented during a single user boot should go there. Everything else
4418 should go into the numeric runlevels. This means things like
4419 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4420 the numeric runlevels. Today in Debian, there are around
115 init.d
4421 scripts that are started from rcS.d/, and most of them should be moved
4422 out. Do your package have one of them? Please help us make single
4423 user and runlevel
1 better by moving it.
</p
>
4425 <p
>Scripts setting up the screen, keyboard, system partitions
4426 etc. should still be started from rcS.d/, but there is for example no
4427 need to have the network enabled before the single user login prompt
4428 is presented.
</p
>
4430 <p
>As always, things are not so easy to fix as they sound. To keep
4431 Debian systems working while scripts migrate and during upgrades, the
4432 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4433 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4434 and the next ones can only be moved when their dependencies have been
4435 moved first. This migration must be done sequentially while we ensure
4436 that the package system upgrade packages in the right order to keep
4437 the system state correct. This will require some coordination when it
4438 comes to network related packages, but most of the packages with
4439 scripts that should migrate do not have anything in rcS.d/ depending
4440 on them. Some packages have already been updated, like the sudo
4441 package, while others are still left to do. I wish I had time to work
4442 on this myself, but real live constrains make it unlikely that I will
4443 find time to push this forward.
</p
>
4448 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
4449 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
4450 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
4451 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
4452 <description><p
>While at Debconf11, I have several times during discussions
4453 mentioned the issues I believe should be improved in Debian for its
4454 desktop to be useful for more people. The use case for this is my
4455 parents, which are currently running Kubuntu which solve the
4458 <p
>I suspect these four missing features are not very hard to
4459 implement. After all, they are present in Ubuntu, so if we wanted to
4460 do this in Debian we would have a source.
</p
>
4464 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
4465 are new packages available for upgrades, a icon in the KDE status bar
4466 indicate this, and clicking on it will activate the simple upgrade
4467 tool to handle it. I have no problem guiding both of my parents
4468 through the process over the phone. If a kernel reboot is required,
4469 this too is indicated by the status bars and the upgrade tool. Last
4470 time I checked, nothing with the same features was working in KDE in
4473 <li
><strong
>Simple handling of missing Firefox browser
4474 plugins.
</strong
> When the browser encounter a MIME type it do not
4475 currently have a handler for, it will ask the user if the system
4476 should search for a package that would add support for this MIME type,
4477 and if the user say yes, the APT sources will be searched for packages
4478 advertising the MIME type in their control file (visible in the
4479 Packages file in the APT archive). If one or more packages are found,
4480 it is a simple click of the mouse to add support for the missing mime
4481 type. If the package require the user to accept some non-free
4482 license, this is explained to the user. The entire process make it
4483 more clear to the user why something do not work in the browser, and
4484 make the chances higher for the user to blame the web page authors and
4485 not the browser for any missing features.
</li
>
4487 <li
><strong
>Simple handling of missing multimedia codec/format
4488 handlers.
</strong
> When the media players encounter a format or codec
4489 it is not supporting, a dialog pop up asking the user if the system
4490 should search for a package that would add support for it. This
4491 happen with things like MP3, Windows Media or H
.264. The selection
4492 and installation procedure is very similar to the Firefox browser
4493 plugin handling. This is as far as I know implemented using a
4494 gstreamer hook. The end result is that the user easily get access to
4495 the codecs that are present from the APT archives available, while
4496 explaining more on why a given format is unsupported by Ubuntu.
</li
>
4498 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
4499 displaying a text/plain file in my Debian browser, it will propose to
4500 start emacs to show it. If I remember correctly, when doing the same
4501 in Kunbutu it show the file as a text file in the browser. At least I
4502 know Opera will show text files within the browser. I much prefer the
4503 latter behaviour.
</li
>
4507 <p
>There are other nice features as well, like the simplified suite
4508 upgrader, but given that I am the one mostly doing the dist-upgrade,
4509 it do not matter much.
</p
>
4511 <p
>I really hope we could get these features in place for the next
4512 Debian release. It would require the coordinated effort of several
4513 maintainers, but would make the end user experience a lot better.
</p
>
4518 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4519 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4520 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4521 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4522 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4523 site is build on Debian/Squeeze, and this platform was chosen because
4524 I am most familiar with Debian (being a Debian Developer for around
10
4525 years) because it is the latest stable Debian release which should get
4526 security support for a few years.
</p
>
4528 <p
>The web service is written in Perl, and depend on some perl modules
4529 that are missing in Debian at the moment. It would be great if these
4530 modules were added to the Debian archive, allowing anyone to set up
4531 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4532 in their own country using only Debian packages. The list of modules
4533 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4534 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4535 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4536 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4537 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4538 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4539 easier in the future.
</p
>
4541 <p
>Thanks to the great tools in Debian, getting the missing modules
4542 installed on my server was a simple call to
'cpan2deb Module::Name
'
4543 and
'dpkg -i
' to install the resulting package. But this leave me
4544 with the responsibility of tracking security problems, which I really
4545 do not have time for.
</p
>
4550 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4551 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4552 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4553 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4554 <description><p
>Here is a small update for my English readers. Most of my blog
4555 posts have been in Norwegian the last few weeks, so here is a short
4556 update in English.
</p
>
4558 <p
>The kids still keep me too busy to get much free software work
4559 done, but I did manage to organise a project to get a Norwegian port
4560 of the British service
4561 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4562 and it has been running for a month now. The entire project has been
4563 organised by me and two others. Around Christmas we gathered sponsors
4564 to fund the development work. In January I drafted a contract with
4565 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4566 and in February the development took place. Most of it involved
4567 converting the source to use GPS coordinates instead of British
4568 easting/northing, and the resulting code should be a lot easier to get
4569 running in any country by now. The Norwegian
4570 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4571 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4572 source and the source for administrative borders in Norway, and
4573 support for this had to be added/fixed.
</p
>
4575 <p
>The Norwegian version went live March
3th, and we spent the weekend
4576 polishing the system before we announced it March
7th. The system is
4577 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4578 problem reports in a few weeks. Soon we hope to announce the Android
4579 and iPhone versions making it even easier to report problems with the
4580 public infrastructure.
</p
>
4582 <p
>Perhaps something to consider for those of you in countries without
4583 such service?
</p
>
4588 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4589 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4590 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4591 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4592 <description><p
>The last few days I have looked at ways to track open security
4593 issues here at my work with the University of Oslo. My idea is that
4594 it should be possible to use the information about security issues
4595 available on the Internet, and check our locally
4596 maintained/distributed software against this information. It should
4597 allow us to verify that no known security issues are forgotten. The
4598 CVE database listing vulnerabilities seem like a great central point,
4599 and by using the package lists from Debian mapped to CVEs provided by
4600 the testing security team, I believed it should be possible to figure
4601 out which security holes were present in our free software
4602 collection.
</p
>
4604 <p
>After reading up on the topic, it became obvious that the first
4605 building block is to be able to name software packages in a unique and
4606 consistent way across data sources. I considered several ways to do
4607 this, for example coming up with my own naming scheme like using URLs
4608 to project home pages or URLs to the Freshmeat entries, or using some
4609 existing naming scheme. And it seem like I am not the first one to
4610 come across this problem, as MITRE already proposed and implemented a
4611 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
4612 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
4613 software, hardware and other platform components. The CPE ids are
4614 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
4615 Vulnerability Database
</a
>, allowing me to look up know security
4616 issues for any CPE name. With this in place, all I need to do is to
4617 locate the CPE id for the software packages we use at the university.
4618 This is fairly trivial (I google for
'cve cpe $package
' and check the
4619 NVD entry if a CVE for the package exist).
</p
>
4621 <p
>To give you an example. The GNU gzip source package have the CPE
4622 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
4623 check out, one could look up
4624 <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
4625 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
4626 The most recent one is
4627 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
4628 and at the bottom of the NVD page for this vulnerability the complete
4629 list of affected versions is provided.
</p
>
4631 <p
>The NVD database of CVEs is also available as a XML dump, allowing
4632 for offline processing of issues. Using this dump, I
've written a
4633 small script taking a list of CPEs as input and list all CVEs
4634 affecting the packages represented by these CPEs. One give it CPEs
4635 with version numbers as specified above and get a list of open
4636 security issues out.
</p
>
4638 <p
>Of course for this approach to be useful, the quality of the NVD
4639 information need to be high. For that to happen, I believe as many as
4640 possible need to use and contribute to the NVD database. I notice
4642 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
4643 map from CVE to CPE
</a
>, indicating that they are using the CPE
4644 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
4646 <p
>To get an idea about the quality for free software, I spent some
4647 time making it possible to compare the CVE database from Debian with
4648 the CVE database in NVD. The result look fairly good, but there are
4649 some inconsistencies in NVD (same software package having several
4650 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4651 Debian believe are affected by a CVE). Hope to find time to improve
4652 the quality of NVD, but that require being able to get in touch with
4653 someone maintaining it. So far my three emails with questions and
4654 corrections have not seen any reply, but I hope contact can be
4655 established soon.
</p
>
4657 <p
>An interesting application for CPEs is cross platform package
4658 mapping. It would be useful to know which packages in for example
4659 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4660 this would be trivial if all linux distributions provided CPE entries
4661 for their packages.
</p
>
4666 <title>Which module is loaded for a given PCI and USB device?
</title>
4667 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
4668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
4669 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
4670 <description><p
>In the
4671 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
4672 package in Debian, there is a script to report useful information
4673 about the running hardware for use when people report missing
4674 information. One part of this script that I find very useful when
4675 debugging hardware problems, is the part mapping loaded kernel module
4676 to the PCI device it claims. It allow me to quickly see if the kernel
4677 module I expect is driving the hardware I am struggling with. To see
4678 the output, make sure discover-data is installed and run
4679 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
4680 one of my machines like this:
</p
>
4684 10de:
03eb i2c_nforce2
4687 10de:
03f0 snd_hda_intel
4696 <p
>The code in question look like this, slightly modified for
4697 readability and to drop the output to file descriptor
3:
</p
>
4700 if [ -d /sys/bus/pci/devices/ ] ; then
4701 echo loaded pci modules:
4703 cd /sys/bus/pci/devices/
4704 for address in * ; do
4705 if [ -d
"$address/driver/module
" ] ; then
4706 module=`cd $address/driver/module ; pwd -P | xargs basename`
4707 if grep -q
"^$module
" /proc/modules ; then
4708 address=$(echo $address |sed s/
0000://)
4709 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
4710 echo
"$id $module
"
4719 <p
>Similar code could be used to extract USB device module
4723 if [ -d /sys/bus/usb/devices/ ] ; then
4724 echo loaded usb modules:
4726 cd /sys/bus/usb/devices/
4727 for address in * ; do
4728 if [ -d
"$address/driver/module
" ] ; then
4729 module=`cd $address/driver/module ; pwd -P | xargs basename`
4730 if grep -q
"^$module
" /proc/modules ; then
4731 address=$(echo $address |sed s/
0000://)
4732 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
4733 if [
"$id
" ] ; then
4734 echo
"$id $module
"
4744 <p
>This might perhaps be something to include in other tools as
4750 <title>How to test if a laptop is working with Linux
</title>
4751 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
4752 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
4753 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
4754 <description><p
>The last few days I have spent at work here at the
<a
4755 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
4756 batch of computers will work with Linux. Every year for the last few
4757 years the university have organised shared bid of a few thousand
4758 computers, and this year HP won the bid. Two different desktops and
4759 five different laptops are on the list this year. We in the UNIX
4760 group want to know which one of these computers work well with RHEL
4761 and Ubuntu, the two Linux distributions we currently handle at the
4762 university.
</p
>
4764 <p
>My test method is simple, and I share it here to get feedback and
4765 perhaps inspire others to test hardware as well. To test, I PXE
4766 install the OS version of choice, and log in as my normal user and run
4767 a few applications and plug in selected pieces of hardware. When
4768 something fail, I make a note about this in the test matrix and move
4769 on. If I have some spare time I try to report the bug to the OS
4770 vendor, but as I only have the machines for a short time, I rarely
4771 have the time to do this for all the problems I find.
</p
>
4773 <p
>Anyway, to get to the point of this post. Here is the simple tests
4774 I perform on a new model.
</p
>
4778 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
4779 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4780 RHEL5 and Debian Edu/Squeeze.
</li
>
4782 <li
>Is X.org working? If the graphical login screen show up after
4783 installation, X.org is working.
</li
>
4785 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
4786 package mesa-utils on Ubuntu) and writing down the frames per second
4787 reported by the program.
</li
>
4789 <li
>Is sound working? With Gnome and KDE, a sound is played when
4790 logging in, and if I can hear this the test is successful. If there
4791 are several audio exits on the machine, I try them all and check if
4792 the Gnome/KDE audio mixer can control where to send the sound. I
4793 normally test this by playing
4794 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
4795 video
</a
> in Firefox/Iceweasel.
</li
>
4797 <li
>Is the USB subsystem working? I test this by plugging in a USB
4798 memory stick and see if Gnome/KDE notices this.
</li
>
4800 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
4801 I have lying around, and see if Gnome/KDE notices this.
</li
>
4803 <li
>Is any built in camera working? Test using cheese, and see if a
4804 picture from the v4l device show up.
</li
>
4806 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4807 any bluetooth devices are discovered. In my office, I normally see a
4810 <li
>For laptops, is the SD or Compaq Flash reader working. I have
4811 memory modules lying around, and stick them in and see if Gnome/KDE
4812 notice this.
</li
>
4814 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
4815 special button work, and if the laptop continue to work after
4818 <li
>For laptops, is the extra buttons working, like audio level,
4819 adjusting background light, switching on/off external video output,
4820 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4821 laptop to laptop, so I just write down which are working and which are
4824 <li
>Some laptops have smart card readers, finger print readers,
4825 acceleration sensors etc. I rarely test these, as I do not know how
4826 to quickly test if they are working or not, so I only document their
4827 existence.
</li
>
4831 <p
>By now I suspect you are really curious what the test results are
4832 for the HP machines I am testing. I
'm not done yet, so I will report
4833 the test results later. For now I can report that HP
8100 Elite work
4834 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
4835 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
4836 can see, I have most machines left to test. One interesting
4837 observation is that Ubuntu Lucid has almost twice the frame rate than
4838 RHEL6 with glxgears. No idea why.
</p
>
4843 <title>Some thoughts on BitCoins
</title>
4844 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
4845 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
4846 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
4847 <description><p
>As I continue to explore
4848 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
4849 what properties the system have, and how it will be affected by laws
4850 and regulations here in Norway. Here are some random notes.
</p
>
4852 <p
>One interesting thing to note is that since the transactions are
4853 verified using a peer to peer network, all details about a transaction
4854 is known to everyone. This means that if a BitCoin address has been
4855 published like I did with mine in my initial post about BitCoin, it is
4856 possible for everyone to see how many BitCoins have been transfered to
4857 that address. There is even a web service to look at the details for
4858 all transactions. There I can see that my address
4859 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
4860 have received
16.06 Bitcoin, the
4861 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
4862 address of Simon Phipps have received
181.97 BitCoin and the address
4863 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
4864 of EFF have received
2447.38 BitCoins so far. Thank you to each and
4865 every one of you that donated bitcoins to support my activity. The
4866 fact that anyone can see how much money was transfered to a given
4867 address make it more obvious why the BitCoin community recommend to
4868 generate and hand out a new address for each transaction. I
'm told
4869 there is no way to track which addresses belong to a given person or
4870 organisation without the person or organisation revealing it
4871 themselves, as Simon, EFF and I have done.
</p
>
4873 <p
>In Norway, and in most other countries, there are laws and
4874 regulations limiting how much money one can transfer across the border
4875 without declaring it. There are money laundering, tax and accounting
4876 laws and regulations I would expect to apply to the use of BitCoin.
4877 If the Skolelinux foundation
4878 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
4879 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
4880 normal bank transfers like EFF is doing, how should this be accounted?
4881 Given that it is impossible to know if money can cross the border or
4882 not, should everything or nothing be declared? What exchange rate
4883 should be used when calculating taxes? Would receivers have to pay
4884 income tax if the foundation were to pay Skolelinux contributors in
4885 BitCoin? I have no idea, but it would be interesting to know.
</p
>
4887 <p
>For a currency to be useful and successful, it must be trusted and
4888 accepted by a lot of users. It must be possible to get easy access to
4889 the currency (as a wage or using currency exchanges), and it must be
4890 easy to spend it. At the moment BitCoin seem fairly easy to get
4891 access to, but there are very few places to spend it. I am not really
4892 a regular user of any of the vendor types currently accepting BitCoin,
4893 so I wonder when my kind of shop would start accepting BitCoins. I
4894 would like to buy electronics, travels and subway tickets, not herbs
4895 and books. :) The currency is young, and this will improve over time
4896 if it become popular, but I suspect regular banks will start to lobby
4897 to get BitCoin declared illegal if it become popular. I
'm sure they
4898 will claim it is helping fund terrorism and money laundering (which
4899 probably would be true, as is any currency in existence), but I
4900 believe the problems should be solved elsewhere and not by blaming
4901 currencies.
</p
>
4903 <p
>The process of creating new BitCoins is called mining, and it is
4904 CPU intensive process that depend on a bit of luck as well (as one is
4905 competing against all the other miners currently spending CPU cycles
4906 to see which one get the next lump of cash). The
"winner
" get
50
4907 BitCoin when this happen. Yesterday I came across the obvious way to
4908 join forces to increase ones changes of getting at least some coins,
4909 by coordinating the work on mining BitCoins across several machines
4910 and people, and sharing the result if one is lucky and get the
50
4912 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
4913 if this sounds interesting. I have not had time to try to set up a
4914 machine to participate there yet, but have seen that running on ones
4915 own for a few days have not yield any BitCoins througth mining
4918 <p
>Update
2010-
12-
15: Found an
<a
4919 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
4920 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
4921 it was interesting to read. The arguments presented seem to be
4922 equally valid for gold, which was used as a currency for many years.
</p
>
4927 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
4928 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
4929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
4930 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
4931 <description><p
>With this weeks lawless
4932 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
4933 attacks
</a
> on Wikileak and
4934 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
4935 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
4936 not be trusted to handle money transactions.
4938 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
4939 Phipps on bitcoin
</a
> reminded me about a project that a friend of
4940 mine mentioned earlier. I decided to follow Simon
's example, and get
4941 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
4942 some help from my friend to get it all running, and he even handed me
4943 some bitcoins to get started. I even donated a few bitcoins to Simon
4944 for helping me remember BitCoin.
</p
>
4946 <p
>So, what is bitcoins, you probably wonder? It is a digital
4947 crypto-currency, decentralised and handled using peer-to-peer
4948 networks. It allows anonymous transactions and prohibits central
4949 control over the transactions, making it impossible for governments
4950 and companies alike to block donations and other transactions. The
4951 source is free software, and while the key dependency wxWidgets
2.9
4952 for the graphical user interface is missing in Debian, the command
4953 line client builds just fine. Hopefully Jonas
4954 <a href=
"http://bugs.debian.org/
578157">will get the package into
4955 Debian
</a
> soon.
</p
>
4957 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
4958 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
4959 bitcoins
</a
> when selling services and goods, and there are even
4960 currency
"stock
" markets where the exchange rate is decided. There
4961 are not many users so far, but the concept seems promising. If you
4962 want to get started and lack a friend with any bitcoins to spare,
4964 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
4965 bitcoin at the time of writing). Use
4966 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
4967 on the current exchange rates.
</p
>
4969 <p
>As an experiment, I have decided to set up bitcoind on one of my
4970 machines. If you want to support my activity, please send Bitcoin
4971 donations to the address
4972 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
4977 <title>Why isn
't Debian Edu using VLC?
</title>
4978 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
4979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
4980 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
4981 <description><p
>In the latest issue of Linux Journal, the readers choices were
4982 presented, and the winner among the multimedia player were VLC.
4983 Personally, I like VLC, and it is my player of choice when I first try
4984 to play a video file or stream. Only if VLC fail will I drag out
4985 gmplayer to see if it can do better. The reason is mostly the failure
4986 model and trust. When VLC fail, it normally pop up a error message
4987 reporting the problem. When mplayer fail, it normally segfault or
4988 just hangs. The latter failure mode drain my trust in the program.
<p
>
4990 <p
>But even if VLC is my player of choice, we have choosen to use
4991 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
4992 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
4993 plugin to play web videos seamlessly, and the VLC browser plugin is
4994 not very good. For example, it lack in-line control buttons, so there
4995 is no way for the user to pause the video. Also, when I
4996 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
4997 tested the browser plugins
</a
> available in Debian, the VLC plugin
4998 failed on several video pages where mplayer based plugins worked. If
4999 the browser plugin for VLC was as good as the gecko-mediaplayer
5000 package (which uses mplayer), we would switch.
</P
>
5002 <p
>While VLC is a good player, its user interface is slightly
5003 annoying. The most annoying feature is its inconsistent use of
5004 keyboard shortcuts. When the player is in full screen mode, its
5005 shortcuts are different from when it is playing the video in a window.
5006 For example, space only work as pause when in full screen mode. I
5007 wish it had consisten shortcuts and that space also would work when in
5008 window mode. Another nice shortcut in gmplayer is [enter] to restart
5009 the current video. It is very nice when playing short videos from the
5010 web and want to restart it when new people arrive to have a look at
5011 what is going on.
</p
>
5016 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
5017 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
5018 <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>
5019 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
5020 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
5021 upgrade testing of the
5022 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5023 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
5024 This seem like a very good idea, so I adjusted by test scripts and
5025 can now present the updated result from today:
</p
>
5027 <p
>This is for Gnome:
</p
>
5029 <p
>Installed using apt-get, missing with aptitude
</p
>
5031 <blockquote
><p
>
5036 browser-plugin-gnash
5043 freedesktop-sound-theme
5045 gconf-defaults-service
5060 gnome-desktop-environment
5064 gnome-session-canberra
5069 gstreamer0.10-fluendo-mp3
5075 libapache2-mod-dnssd
5078 libaprutil1-dbd-sqlite3
5081 libboost-date-time1.42
.0
5082 libboost-python1.42
.0
5083 libboost-thread1.42
.0
5085 libchamplain-gtk-
0.4-
0
5087 libclutter-gtk-
0.10-
0
5094 libfreerdp-plugins-standard
5109 libgnomepanel2.24-cil
5114 libgtksourceview2.0-common
5115 libmono-addins-gui0.2-cil
5116 libmono-addins0.2-cil
5117 libmono-cairo2.0-cil
5118 libmono-corlib2.0-cil
5119 libmono-i18n-west2.0-cil
5120 libmono-posix2.0-cil
5121 libmono-security2.0-cil
5122 libmono-sharpzip2.84-cil
5123 libmono-system2.0-cil
5126 libndesk-dbus-glib1.0-cil
5127 libndesk-dbus1.0-cil
5137 libtelepathy-farsight0
5146 nautilus-sendto-empathy
5150 python-aptdaemon-gtk
5152 python-beautifulsoup
5167 python-gtksourceview2
5178 python-pkg-resources
5185 python-twisted-conch
5191 python-zope.interface
5196 rhythmbox-plugin-cdrecorder
5203 system-config-printer-udev
5205 telepathy-mission-control-
5
5216 </p
></blockquote
>
5218 <p
>Installed using apt-get, removed with aptitude
</p
>
5220 <blockquote
><p
>
5226 fast-user-switch-applet
5245 libgtksourceview2.0-
0
5247 libsdl1.2debian-alsa
5253 system-config-printer
5258 </p
></blockquote
>
5260 <p
>Installed using aptitude, missing with apt-get
</p
>
5262 <blockquote
><p
>
5263 gstreamer0.10-gnomevfs
5264 </p
></blockquote
>
5266 <p
>Installed using aptitude, removed with apt-get
</p
>
5268 <blockquote
><p
>
5270 </p
></blockquote
>
5272 <p
>This is for KDE:
</p
>
5274 <p
>Installed using apt-get, missing with aptitude
</p
>
5276 <blockquote
><p
>
5278 </p
></blockquote
>
5280 <p
>Installed using apt-get, removed with aptitude
</p
>
5282 <blockquote
><p
>
5285 </p
></blockquote
>
5287 <p
>Installed using aptitude, missing with apt-get
</p
>
5289 <blockquote
><p
>
5303 kdeartwork-emoticons
5305 kdeartwork-theme-icon
5309 kdebase-workspace-bin
5310 kdebase-workspace-data
5324 kscreensaver-xsavers
5339 plasma-dataengines-workspace
5341 plasma-desktopthemes-artwork
5342 plasma-runners-addons
5343 plasma-scriptengine-googlegadgets
5344 plasma-scriptengine-python
5345 plasma-scriptengine-qedje
5346 plasma-scriptengine-ruby
5347 plasma-scriptengine-webkit
5348 plasma-scriptengines
5349 plasma-wallpapers-addons
5350 plasma-widget-folderview
5351 plasma-widget-networkmanagement
5355 xscreensaver-data-extra
5357 xscreensaver-gl-extra
5358 xscreensaver-screensaver-bsod
5359 </p
></blockquote
>
5361 <p
>Installed using aptitude, removed with apt-get
</p
>
5363 <blockquote
><p
>
5365 google-gadgets-common
5383 libggadget-qt-
1.0-
0b
5388 libkonqsidebarplugin4a
5397 libplasma-geolocation-interface4
5399 libplasmagenericshell4
5413 libsmokeknewstuff2-
3
5414 libsmokeknewstuff3-
3
5416 libsmokektexteditor3
5424 libsmokeqtnetwork4-
3
5430 libsmokeqtuitools4-
3
5442 plasma-dataengines-addons
5443 plasma-scriptengine-superkaramba
5444 plasma-widget-lancelot
5445 plasma-widgets-addons
5446 plasma-widgets-workspace
5450 update-notifier-common
5451 </p
></blockquote
>
5453 <p
>Running apt-get autoremove made the results using apt-get and
5454 aptitude a bit more similar, but there are still quite a lott of
5455 differences. I have no idea what packages should be installed after
5456 the upgrade, but hope those that do can have a look.
</p
>
5461 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
5462 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
5463 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
5464 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
5465 <description><p
>Most of the computers in use by the
5466 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
5467 are virtual machines. And they have been Xen machines running on a
5468 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
5469 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
5470 bit harder that it could have been, because we set up the Xen virtual
5471 machines to get the virtual partitions from LVM, which as far as I
5472 know is not supported by KVM. So to migrate, we had to convert
5473 several LVM logical volumes to partitions on a virtual disk file.
</p
>
5476 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
5477 nice recipe
</a
> to do this, and wrote the following script to do the
5478 migration. It uses qemu-img from the qemu package to make the disk
5479 image, parted to partition it, losetup and kpartx to present the disk
5480 image partions as devices, and dd to copy the data. I NFS mounted the
5481 new servers storage area on the old server to do the migration.
</p
>
5487 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5492 if [ -z
"$
1" ] ; then
5493 echo
"Usage: $
0 &lt;hostname
&gt;
"
5499 if [ ! -e /dev/vg_data/$host-disk ] ; then
5500 echo
"error: unable to find LVM volume for $host
"
5504 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5505 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5506 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5507 totalsize=$(( ( $disksize + $swapsize ) ))
5510 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5511 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5513 parted $img mklabel msdos
5514 parted $img mkpart primary linux-swap
0 $disksize
5515 parted $img mkpart primary ext2 $disksize $totalsize
5516 parted $img set
1 boot on
5519 losetup /dev/loop0 $img
5520 kpartx -a /dev/loop0
5522 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5523 fsck.ext3 -f /dev/mapper/loop0p1 || true
5524 mkswap /dev/mapper/loop0p2
5526 kpartx -d /dev/loop0
5527 losetup -d /dev/loop0
5530 <p
>The script is perhaps so simple that it is not copyrightable, but
5531 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5533 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5534 the new disk image attached, installed grub-pc and linux-image-
686 and
5535 set up grub to boot from the disk image. After this, the KVM machines
5536 seem to work just fine.
</p
>
5541 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5542 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5543 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5544 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5545 <description><p
>I
'm still running upgrade testing of the
5546 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5547 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5548 status. Here is a short update based on a test I ran
20101118.
</p
>
5550 <p
>I still do not know what a correct migration should look like, so I
5551 report any differences between apt and aptitude and hope someone else
5552 can see if anything should be changed.
</p
>
5554 <p
>This is for Gnome:
</p
>
5556 <p
>Installed using apt-get, missing with aptitude
</p
>
5558 <blockquote
><p
>
5559 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5560 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5561 dmz-cursor-theme empathy empathy-common finger
5562 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5563 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5564 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5565 gnome-cards-data gnome-codec-install gnome-core
5566 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5567 gnome-search-tool gnome-session-canberra gnome-spell
5568 gnome-system-log gnome-themes-extras gnome-themes-more
5569 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5570 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5571 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5572 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5573 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5574 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5575 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5576 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5577 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5578 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5579 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5580 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5581 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5582 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5583 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5584 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5585 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5586 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5587 libmono-security2.0-cil libmono-sharpzip2.84-cil
5588 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5589 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5590 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5591 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5592 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5593 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5594 libxalan2-java libxerces2-java media-player-info mesa-utils
5595 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5596 nautilus-sendto-empathy openoffice.org-writer2latex
5597 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5598 python-aptdaemon python-aptdaemon-gtk python-axiom
5599 python-beautifulsoup python-bugbuddy python-clientform
5600 python-coherence python-configobj python-crypto python-cupshelpers
5601 python-cupsutils python-eggtrayicon python-elementtree
5602 python-epsilon python-evolution python-feedparser python-gdata
5603 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5604 python-gtksourceview2 python-httplib2 python-louie python-mako
5605 python-markupsafe python-mechanize python-nevow python-notify
5606 python-opengl python-openssl python-pam python-pkg-resources
5607 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5608 python-tagpy python-twisted-bin python-twisted-conch
5609 python-twisted-core python-twisted-web python-utidylib python-webkit
5610 python-xdg python-zope.interface remmina remmina-plugin-data
5611 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5612 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5613 software-center svgalibg1 system-config-printer-udev
5614 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
5615 totem totem-coherence totem-mozilla totem-plugins
5616 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5618 </p
></blockquote
>
5620 Installed using apt-get, removed with aptitude
5622 <blockquote
><p
>
5623 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5624 epiphany-extensions epiphany-gecko evolution-exchange
5625 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5626 gedit-common gnome-app-install gnome-games gnome-games-data
5627 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5628 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5629 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5630 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
5631 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
5632 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
5633 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
5634 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5635 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5636 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5637 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
5638 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
5639 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5640 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5641 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5642 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5643 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
5644 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
5645 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
5646 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
5647 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
5648 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5649 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5650 sound-juicer swfdec-gnome system-config-printer totem-common
5651 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5652 </p
></blockquote
>
5654 <p
>Installed using aptitude, missing with apt-get
</p
>
5656 <blockquote
><p
>
5657 gstreamer0.10-gnomevfs
5658 </p
></blockquote
>
5660 <p
>Installed using aptitude, removed with apt-get
</p
>
5662 <blockquote
><p
>
5664 </p
></blockquote
>
5666 <p
>This is for KDE:
</p
>
5668 <p
>Installed using apt-get, missing with aptitude
</p
>
5670 <blockquote
><p
>
5671 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
5672 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5673 ghostscript-x git gnome-audio gnugo granatier gs-common
5674 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5675 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5676 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5677 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5678 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5679 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5680 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5681 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5682 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5683 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5684 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5685 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
5686 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5687 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5688 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5689 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5690 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5691 libkrossui4 libmailtools-perl libmime-tools-perl
5692 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5693 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5694 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5695 lirc luatex marble networkstatus noatun-plugins
5696 openoffice.org-writer2latex palapeli palapeli-data parley
5697 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5698 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5699 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5701 </p
></blockquote
>
5703 <p
>Installed using apt-get, removed with aptitude
</p
>
5705 <blockquote
><p
>
5706 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5707 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5708 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5709 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5710 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5711 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5712 kitchensync kiten kjumpingcube klatin klettres klickety klines
5713 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5714 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5715 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5716 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5717 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5718 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5719 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5720 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5721 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5722 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
5723 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
5724 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5725 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
5726 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
5727 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5728 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5729 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5730 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5731 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5732 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5733 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
5734 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
5735 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5736 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5737 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5738 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5739 </p
></blockquote
>
5741 <p
>Installed using aptitude, missing with apt-get
</p
>
5743 <blockquote
><p
>
5744 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5745 kdeartwork kdebase kdebase-apps kdebase-workspace
5746 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5747 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5748 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5749 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5750 xscreensaver-screensaver-bsod
5751 </p
></blockquote
>
5753 <p
>Installed using aptitude, removed with apt-get
</p
>
5755 <blockquote
><p
>
5756 kdebase-bin konq-plugins konqueror
5757 </p
></blockquote
>
5762 <title>Gnash buildbot slave and Debian kfreebsd
</title>
5763 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
5764 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
5765 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
5766 <description><p
>Answering
5767 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
5768 call from the Gnash project
</a
> for
5769 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
5770 current source, I have set up a virtual KVM machine on the Debian
5771 Edu/Skolelinux virtualization host to test the git source on
5772 Debian/Squeeze. I hope this can help the developers in getting new
5773 releases out more often.
</p
>
5775 <p
>As the developers want less main-stream build platforms tested to,
5776 I have considered setting up a
<a
5777 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
5778 machine as well. I have also considered using the kfreebsd
5779 architecture in Debian as a file server in NUUG to get access to the
5
5780 TB zfs volume we currently use to store DV video. Because of this, I
5781 finally got around to do a test installation of Debian/Squeeze with
5782 kfreebsd. Installation went fairly smooth, thought I noticed some
5783 visual glitches in the cdebconf dialogs (black cursor left on the
5784 screen at random locations). Have not gotten very far with the
5785 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5786 fatal problem. Have to spend some more time on it to see if it is
5787 useful as a file server for NUUG. Will try to find time to set up a
5788 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
5793 <title>Debian in
3D
</title>
5794 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
5795 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
5796 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
5797 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
5799 <p
>3D printing is just great. I just came across this Debian logo in
5801 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
5802 thingiverse blog
</a
>.
</p
>
5807 <title>Software updates
2010-
10-
24</title>
5808 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
5809 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
5810 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
5811 <description><p
>Some updates.
</p
>
5813 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
5814 raise money for the project is going well. The lower limit of
10
5815 signers was reached in
24 hours, and so far
13 people have signed it.
5816 More signers and more funding is most welcome, and I am really curious
5817 how far we can get before the time limit of December
24 is reached.
5820 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
5821 about what appear to be a great code coverage tool capable of
5822 generating code coverage stats without any changes to the source code.
5824 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
5825 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
5826 It is missing in Debian, but the git source built just fine in Squeeze
5827 after I installed libelf-dev, libdwarf-dev, pkg-config and
5828 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5829 solvable. I hope kcov make it into Debian soon.
</p
>
5831 <p
>Finally found time to wrap up the release notes for
<a
5832 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
5833 new alpha release of Debian Edu
</a
>, and just published the second
5834 alpha test release of the Squeeze based Debian Edu /
5835 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
5836 release. Give it a try if you need a complete linux solution for your
5837 school, including central infrastructure server, workstations, thin
5838 client servers and diskless workstations. A nice touch added
5839 yesterday is RDP support on the thin client servers, for windows
5840 clients to get a Linux desktop on request.
</p
>
5845 <title>Some notes on Flash in Debian and Debian Edu
</title>
5846 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
5847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
5848 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
5849 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
5850 popularity-contest numbers
</a
>, the adobe-flashplugin package the
5851 second most popular used package that is missing in Debian. The sixth
5852 most popular is flashplayer-mozilla. This is a clear indication that
5853 working flash is important for Debian users. Around
10 percent of the
5854 users submitting data to popcon.debian.org have this package
5855 installed.
</p
>
5857 <p
>In the report written by Lars Risan in August
2008
5858 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
5859 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5860 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
5861 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
5862 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
5863 web sites require Flash to work, and lacking working Flash support in
5864 the web browser and the problems with installing it was perceived as a
5865 good reason to stay with Windows.
</p
>
5867 <p
>I once saw a funny and sad comment in a web forum, where Linux was
5868 said to be the retarded cousin that did not really understand
5869 everything you told him but could work fairly well. This was a
5870 comment regarding the problems Linux have with proprietary formats and
5871 non-standard web pages, and is sad because it exposes a fairly common
5872 understanding of whose fault it is if web pages that only work in for
5873 example Internet Explorer
6 fail to work on Firefox, and funny because
5874 it explain very well how annoying it is for users when Linux
5875 distributions do not work with the documents they receive or the web
5876 pages they want to visit.
</p
>
5878 <p
>This is part of the reason why I believe it is important for Debian
5879 and Debian Edu to have a well working Flash implementation in the
5880 distribution, to get at least popular sites as Youtube and Google
5881 Video to working out of the box. For Squeeze, Debian have the chance
5882 to include the latest version of Gnash that will make this happen, as
5883 the new release
0.8.8 was published a few weeks ago and is resting in
5884 unstable. The new version work with more sites that version
0.8.7.
5885 The Gnash maintainers have asked for a freeze exception, but the
5886 release team have not had time to reply to it yet. I hope they agree
5887 with me that Flash is important for the Debian desktop users, and thus
5888 accept the new package into Squeeze.
</p
>
5893 <title>Circular package dependencies harms apt recovery
</title>
5894 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
5895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
5896 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
5897 <description><p
>I discovered this while doing
5898 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
5899 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
5900 in Debian still got circular dependencies, and it is often claimed
5901 that apt and aptitude should be able to handle this just fine, but
5902 some times these dependency loops causes apt to fail.
</p
>
5904 <p
>An example is from todays
5905 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
5906 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
5907 causes perl-modules to fail to upgrade. The cause is simple. If a
5908 package fail to unpack, then only part of packages with the circular
5909 dependency might end up being unpacked when unpacking aborts, and the
5910 ones already unpacked will fail to configure in the recovery phase
5911 because its dependencies are unavailable.
</p
>
5913 <p
>In this log, the problem manifest itself with this error:
</p
>
5915 <blockquote
><pre
>
5916 dpkg: dependency problems prevent configuration of perl-modules:
5917 perl-modules depends on perl (
>=
5.10.1-
1); however:
5918 Version of perl on system is
5.10.0-
19lenny
2.
5919 dpkg: error processing perl-modules (--configure):
5920 dependency problems - leaving unconfigured
5921 </pre
></blockquote
>
5923 <p
>The perl/perl-modules circular dependency is already
5924 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
5925 hopefully be solved as soon as possible, but it is not the only one,
5926 and each one of these loops in the dependency tree can cause similar
5927 failures. Of course, they only occur when there are bugs in other
5928 packages causing the unpacking to fail, but it is rather nasty when
5929 the failure of one package causes the problem to become worse because
5930 of dependency loops.
</p
>
5933 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
5934 tireless effort by Bill Allombert
</a
>, the number of circular
5936 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
5937 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
5939 <p
>Todays testing also exposed a bug in
5940 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
5941 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
5942 apt-get and aptitude, the latter possibly caused by some circular
5943 dependency. Reported both to BTS to try to get someone to look at
5949 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
5950 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
5951 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
5952 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
5953 <description><p
>This is a
5954 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
5956 <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
5958 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
5959 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
5961 <p
>As a step to try to see if it possible to merge the DNS and DHCP
5962 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5963 and dhcp3-server-ldap in Debian use the LDAP server. The two
5964 implementations are quite different in how they use LDAP.
</p
>
5966 To get this information, I started slapd with debugging enabled and
5967 dumped the debug output to a file to get the LDAP searches performed
5968 on a Debian Edu main-server. Here is a summary.
5970 <p
><strong
>powerdns
</strong
></p
>
5972 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
5973 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
5976 <p
>PowerDNS have two modes of operation using LDAP as its backend.
5977 One
"strict
" mode where the forward and reverse DNS lookups are done
5978 using the same LDAP objects, and a
"tree
" mode where the forward and
5979 reverse entries are in two different subtrees in LDAP with a structure
5980 based on the DNS names, as in tjener.intern and
5981 2.2.0.10.in-addr.arpa.
</p
>
5983 <p
>In tree mode, the server is set up to use a LDAP subtree as its
5984 base, and uses a
"base
" scoped search for the DNS name by adding
5985 "dc=tjener,dc=intern,
" to the base with a filter for
5986 "(associateddomain=tjener.intern)
" for the forward entry and
5987 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
5988 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
5989 forward entries, it is looking for attributes named dnsttl, arecord,
5990 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5991 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5992 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5993 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5994 spfrecord and modifytimestamp. For reverse entries it is looking for
5995 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5996 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5997 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5998 ldapsearch commands could look like this:
</p
>
6000 <blockquote
><pre
>
6001 ldapsearch -h ldap \
6002 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6003 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6004 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6005 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6006 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6007 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6009 ldapsearch -h ldap \
6010 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6011 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
6012 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6013 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6014 srvrecord naptrrecord modifytimestamp
6015 </pre
></blockquote
>
6017 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
6018 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6019 example LDAP objects used there. In addition to these objects, the
6020 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6021 also exist.
</p
>
6023 <blockquote
><pre
>
6024 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6026 objectclass: dnsdomain
6027 objectclass: domainrelatedobject
6030 associateddomain: tjener.intern
6032 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6034 objectclass: dnsdomain2
6035 objectclass: domainrelatedobject
6037 ptrrecord: tjener.intern
6038 associateddomain:
2.2.0.10.in-addr.arpa
6039 </pre
></blockquote
>
6041 <p
>In strict mode, the server behaves differently. When looking for
6042 forward DNS entries, it is doing a
"subtree
" scoped search with the
6043 same base as in the tree mode for a object with filter
6044 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
6045 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6046 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6047 naptrrecord and modifytimestamp. For reverse entires it also do a
6048 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
6049 and the requested attributes are associateddomain, dnsttl and
6050 modifytimestamp. In short, in strict mode the objects with ptrrecord
6051 go away, and the arecord attribute in the forward object is used
6054 <p
>The forward and reverse searches can be simulated using ldapsearch
6055 like this:
</p
>
6057 <blockquote
><pre
>
6058 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6059 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6060 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6061 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6062 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6063 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6065 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6066 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
6067 </pre
></blockquote
>
6069 <p
>In addition to the forward and reverse searches , there is also a
6070 search for SOA records, which behave similar to the forward and
6071 reverse lookups.
</p
>
6073 <p
>A thing to note with the PowerDNS behaviour is that it do not
6074 specify any objectclass names, and instead look for the attributes it
6075 need to generate a DNS reply. This make it able to work with any
6076 objectclass that provide the needed attributes.
</p
>
6078 <p
>The attributes are normally provided in the cosine (RFC
1274) and
6079 dnsdomain2 schemas. The latter is used for reverse entries like
6080 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
6082 <p
>In Debian Edu, we have created DNS objects using the object classes
6083 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6084 attributes) and domainrelatedobject (for associatedDomain). The use
6085 of structural object classes make it impossible to combine these
6086 classes with the object classes used by DHCP.
</p
>
6088 <p
>There are other schemas that could be used too, for example the
6089 dnszone structural object class used by Gosa and bind-sdb for the DNS
6090 attributes combined with the domainrelatedobject object class, but in
6091 this case some unused attributes would have to be included as well
6092 (zonename and relativedomainname).
</p
>
6094 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
6095 mode and not use any of the existing objectclasses (dnsdomain,
6096 dnsdomain2 and dnszone) when one want to combine the DNS information
6097 with DHCP information, and instead create a auxiliary object class
6098 defined something like this (using the attributes defined for
6099 dnsdomain and dnsdomain2 or dnszone):
</p
>
6101 <blockquote
><pre
>
6102 objectclass ( some-oid NAME
'dnsDomainAux
'
6105 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6106 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6107 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6108 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6109 A6Record $ DNAMERecord
6111 </pre
></blockquote
>
6113 <p
>This will allow any object to become a DNS entry when combined with
6114 the domainrelatedobject object class, and allow any entity to include
6115 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
6116 developers asking for their view on this schema and if they are
6117 interested in providing such schema with PowerDNS, and I hope my
6118 message will be accepted into their mailing list soon.
</p
>
6120 <p
><strong
>ISC dhcp
</strong
></p
>
6122 <p
>The DHCP server searches for specific objectclass and requests all
6123 the object attributes, and then uses the attributes it want. This
6124 make it harder to figure out exactly what attributes are used, but
6125 thanks to the working example in Debian Edu I can at least get an idea
6126 what is needed without having to read the source code.
</p
>
6128 <p
>In the DHCP server configuration, the LDAP base to use and the
6129 search filter to use to locate the correct dhcpServer entity is
6130 stored. These are the relevant entries from
6131 /etc/dhcp3/dhcpd.conf:
</p
>
6133 <blockquote
><pre
>
6134 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
6135 ldap-dhcp-server-cn
"dhcp
";
6136 </pre
></blockquote
>
6138 <p
>The DHCP server uses this information to nest all the DHCP
6139 configuration it need. The cn
"dhcp
" is located using the given LDAP
6140 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
6141 search result is this entry:
</p
>
6143 <blockquote
><pre
>
6144 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6147 objectClass: dhcpServer
6148 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6149 </pre
></blockquote
>
6151 <p
>The content of the dhcpServiceDN attribute is next used to locate the
6152 subtree with DHCP configuration. The DHCP configuration subtree base
6153 is located using a base scope search with base
"cn=DHCP
6154 Config,dc=skole,dc=skolelinux,dc=no
" and filter
6155 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
6156 The search result is this entry:
</p
>
6158 <blockquote
><pre
>
6159 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6162 objectClass: dhcpService
6163 objectClass: dhcpOptions
6164 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6165 dhcpStatements: ddns-update-style none
6166 dhcpStatements: authoritative
6167 dhcpOption: smtp-server code
69 = array of ip-address
6168 dhcpOption: www-server code
72 = array of ip-address
6169 dhcpOption: wpad-url code
252 = text
6170 </pre
></blockquote
>
6172 <p
>Next, the entire subtree is processed, one level at the time. When
6173 all the DHCP configuration is loaded, it is ready to receive requests.
6174 The subtree in Debian Edu contain objects with object classes
6175 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6176 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6177 and information about netmasks, dynamic range etc. Leaving out the
6178 details here because it is not relevant for the focus of my
6179 investigation, which is to see if it is possible to merge dns and dhcp
6180 related computer objects.
</p
>
6182 <p
>When a DHCP request come in, LDAP is searched for the MAC address
6183 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
6184 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
6185 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6186 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
6189 <blockquote
><pre
>
6190 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6193 objectClass: dhcpHost
6194 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6195 dhcpStatements: fixed-address hostname
6196 </pre
></blockquote
>
6198 <p
>There is less flexiblity in the way LDAP searches are done here.
6199 The object classes need to have fixed names, and the configuration
6200 need to be stored in a fairly specific LDAP structure. On the
6201 positive side, the invidiual dhcpHost entires can be anywhere without
6202 the DN pointed to by the dhcpServer entries. The latter should make
6203 it possible to group all host entries in a subtree next to the
6204 configuration entries, and this subtree can also be shared with the
6205 DNS server if the schema proposed above is combined with the dhcpHost
6206 structural object class.
6208 <p
><strong
>Conclusion
</strong
></p
>
6210 <p
>The PowerDNS implementation seem to be very flexible when it come
6211 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
6212 come to the the LDAP structure, the
"strict
" mode is very flexible,
6213 allowing DNS objects to be stored anywhere under the base cn specified
6214 in the configuration.
</p
>
6216 <p
>The DHCP implementation on the other hand is very inflexible, both
6217 regarding which LDAP schemas to use and which LDAP structure to use.
6218 I guess one could implement ones own schema, as long as the
6219 objectclasses and attributes have the names used, but this do not
6220 really help when the DHCP subtree need to have a fairly fixed
6221 structure.
</p
>
6223 <p
>Based on the observed behaviour, I suspect a LDAP structure like
6224 this might work for Debian Edu:
</p
>
6226 <blockquote
><pre
>
6228 cn=machine-info (dhcpService) - dhcpServiceDN points here
6229 cn=dhcp (dhcpServer)
6230 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6231 cn=
10.0.2.0 (dhcpSubnet)
6232 cn=group1 (dhcpGroup/dhcpOptions)
6233 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6234 cn=
192.168.0.0 (dhcpSubnet)
6235 cn=group1 (dhcpGroup/dhcpOptions)
6236 ou=machines - PowerDNS base points here
6237 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6238 </pre
></blockquote
>
6240 <P
>This is not tested yet. If the DHCP server require the dhcpHost
6241 entries to be in the dhcpGroup subtrees, the entries can be stored
6242 there instead of a common machines subtree, and the PowerDNS base
6243 would have to be moved one level up to the machine-info subtree.
</p
>
6245 <p
>The combined object under the machines subtree would look something
6246 like this:
</p
>
6248 <blockquote
><pre
>
6249 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6252 objectClass: dhcpHost
6253 objectclass: domainrelatedobject
6254 objectclass: dnsDomainAux
6255 associateddomain: hostname.intern
6256 arecord:
10.11.12.13
6257 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6258 dhcpStatements: fixed-address hostname.intern
6259 </pre
></blockquote
>
6261 </p
>One could even add the LTSP configuration associated with a given
6262 machine, as long as the required attributes are available in a
6263 auxiliary object class.
</p
>
6268 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
6269 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
6270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
6271 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
6272 <description><p
>For a while now, I have wanted to find a way to change the DNS and
6273 DHCP services in Debian Edu to use the same LDAP objects for a given
6274 computer, to avoid the possibility of having a inconsistent state for
6275 a computer in LDAP (as in DHCP but no DNS entry or the other way
6276 around) and make it easier to add computers to LDAP.
</p
>
6278 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
6279 information finally found a solution that seem to work.
</p
>
6281 <p
>The old setup required three LDAP objects for a given computer.
6282 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6283 we switch powerdns to use its strict LDAP method (ldap-method=strict
6284 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6285 merged into one while making it impossible to transfer the reverse map
6286 to a slave DNS server.
</p
>
6288 <p
>If we also replace the object class used to get the DNS related
6289 attributes to one allowing these attributes to be combined with the
6290 dhcphost object class, we can merge the DNS and DHCP entries into one.
6291 I
've written such object class in the dnsdomainaux.schema file (need
6292 proper OIDs, but that is a minor issue), and tested the setup. It
6293 seem to work.
</p
>
6295 <p
>With this test setup in place, we can get away with one LDAP object
6296 for both DNS and DHCP, and even the LTSP configuration I suggested in
6297 an earlier email. The combined LDAP object will look something like
6300 <blockquote
><pre
>
6301 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6303 objectClass: dhcphost
6304 objectclass: domainrelatedobject
6305 objectclass: dnsdomainaux
6306 associateddomain: hostname.intern
6307 arecord:
10.11.12.13
6308 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
6309 dhcpstatements: fixed-address hostname
6311 </pre
></blockquote
>
6313 <p
>The DNS server uses the associateddomain and arecord entries, while
6314 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6315 before asking DNS to resolve the fixed-adddress. LTSP will use
6316 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
6318 <p
>I am not yet sure if I can get the DHCP server to look for its
6319 dhcphost in a different location, to allow us to put the objects
6320 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
6321 that. If I can
't figure out a way to do that, we can still get rid of
6322 the hosts subtree and move all its content into the DHCP Config tree
6323 (which probably should be renamed to be more related to the new
6324 content. I suspect cn=dnsdhcp,ou=services or something like that
6325 might be a good place to put it.
</p
>
6327 <p
>If you want to help out with implementing this for Debian Edu,
6328 please contact us on debian-edu@lists.debian.org.
</p
>
6333 <title>Idea for storing LTSP configuration in LDAP
</title>
6334 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
6335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
6336 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
6337 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
6338 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6339 clients, and that this can be used to fetch configuration from LDAP if
6340 Debian Edu choose to store configuration there.
</p
>
6342 <p
>Armed with this information, I got inspired and wrote a test module
6343 to get configuration from LDAP. The idea is to look up the MAC
6344 address of the client in LDAP, and look for attributes on the form
6345 ltspconfigsetting=value, and use this to export SETTING=value to the
6346 LTSP clients.
</p
>
6348 <p
>The goal is to be able to store the LTSP configuration attributes
6349 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
6350 allowing us to store all information about a computer in one place.
</p
>
6352 <p
>This is a untested draft implementation, and I welcome feedback on
6353 this approach. A real LDAP schema for the ltspClientAux objectclass
6354 need to be written. Comments, suggestions, etc?
</p
>
6356 <blockquote
><pre
>
6357 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6359 # Fetch LTSP client settings from LDAP based on MAC address
6361 # Uses ethernet address as stored in the dhcpHost objectclass using
6362 # the dhcpHWAddress attribute or ethernet address stored in the
6363 # ieee802Device objectclass with the macAddress attribute.
6365 # This module is written to be schema agnostic, and only depend on the
6366 # existence of attribute names.
6368 # The LTSP configuration variables are saved directly using a
6369 # ltspConfig prefix and uppercasing the rest of the attribute name.
6370 # To set the SERVER variable, set the ltspConfigServer attribute.
6372 # Some LDAP schema should be created with all the relevant
6373 # configuration settings. Something like this should work:
6375 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
6378 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6380 LDAPSERVER=$(debian-edu-ldapserver)
6381 if [
"$LDAPSERVER
" ] ; then
6382 LDAPBASE=$(debian-edu-ldapserver -b)
6383 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
6384 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
6385 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
6386 grep
'^ltspConfig
' | while read attr value ; do
6387 # Remove prefix and convert to upper case
6388 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
6389 # bass value on to clients
6390 eval
"$attr=$value; export $attr
"
6394 </pre
></blockquote
>
6396 <p
>I
'm not sure this shell construction will work, because I suspect
6397 the while block might end up in a subshell causing the variables set
6398 there to not show up in ltsp-config, but if that is the case I am sure
6399 the code can be restructured to make sure the variables are passed on.
6400 I expect that can be solved with some testing. :)
</p
>
6402 <p
>If you want to help out with implementing this for Debian Edu,
6403 please contact us on debian-edu@lists.debian.org.
</p
>
6405 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
6406 configuration in LDAP that was created around year
2000 by
6407 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
6408 Xperience, Inc.,
2000</a
>. I found its
6409 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
6410 personal home page over at redhat.com.
</p
>
6415 <title>jXplorer, a very nice LDAP GUI
</title>
6416 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
6417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
6418 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
6419 <description><p
>Since
6420 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
6421 last post
</a
> about available LDAP tools in Debian, I was told about a
6422 LDAP GUI that is even better than luma. The java application
6423 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
6424 moving LDAP objects and subtrees using drag-and-drop, and can
6425 authenticate using Kerberos. I have only tested the Kerberos
6426 authentication, but do not have a LDAP setup allowing me to rewrite
6427 LDAP with my test user yet. It is
6428 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
6429 Debian
</a
> testing and unstable at the moment. The only problem I
6430 have with it is how it handle errors. If something go wrong, its
6431 non-intuitive behaviour require me to go through some query work list
6432 and remove the failing query. Nothing big, but very annoying.
</p
>
6437 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
6438 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
6439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
6440 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
6441 <description><p
>Here is a short update on my
<a
6442 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
6443 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
6444 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
6445 not reporting the status for KDE, because the upgrade crashes when
6446 aptitude try because of missing conflicts
6447 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
6448 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
6450 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
6451 complete list of the installed packages. Based on this I see these
6452 differences when I did a test run today. As usual, I do not really
6453 know what the correct set of packages would be, but thought it best to
6454 publish the difference.
</p
>
6456 <p
>Installed using apt-get, missing with aptitude
</p
>
6458 <blockquote
><p
>
6459 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
6460 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
6461 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6462 libgtksourceview-common libpt-
1.10.10-plugins-alsa
6463 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6464 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6465 python-
4suite-xml python-eggtrayicon python-gtkhtml2
6466 python-gtkmozembed svgalibg1 xserver-xephyr zip
6467 </p
></blockquote
>
6469 <p
>Installed using apt-get, removed with aptitude
</p
>
6471 <blockquote
><p
>
6472 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6473 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6474 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
6475 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
6476 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
6477 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
6478 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6479 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6480 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6481 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
6482 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
6483 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
6484 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6485 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
6486 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6487 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
6488 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
6489 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6490 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6491 mysql-common swfdec-gnome totem-gstreamer wodim
6492 </p
></blockquote
>
6494 <p
>Installed using aptitude, missing with apt-get
</p
>
6496 <blockquote
><p
>
6497 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6498 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6499 xserver-xorg-input-all xserver-xorg-input-evdev
6500 xserver-xorg-input-kbd xserver-xorg-input-mouse
6501 xserver-xorg-input-synaptics xserver-xorg-video-all
6502 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6503 xserver-xorg-video-chips xserver-xorg-video-cirrus
6504 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6505 xserver-xorg-video-glint xserver-xorg-video-i128
6506 xserver-xorg-video-i740 xserver-xorg-video-mach64
6507 xserver-xorg-video-mga xserver-xorg-video-neomagic
6508 xserver-xorg-video-nouveau xserver-xorg-video-nv
6509 xserver-xorg-video-r128 xserver-xorg-video-radeon
6510 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6511 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6512 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6513 xserver-xorg-video-sis xserver-xorg-video-sisusb
6514 xserver-xorg-video-tdfx xserver-xorg-video-tga
6515 xserver-xorg-video-trident xserver-xorg-video-tseng
6516 xserver-xorg-video-vesa xserver-xorg-video-vmware
6517 xserver-xorg-video-voodoo
6518 </p
></blockquote
>
6520 <p
>Installed using aptitude, removed with apt-get
</p
>
6522 <blockquote
><p
>
6523 deskbar-applet xserver-xorg xserver-xorg-core
6524 xserver-xorg-input-wacom xserver-xorg-video-intel
6525 xserver-xorg-video-openchrome
6526 </p
></blockquote
>
6528 <p
>I was told on IRC that the xorg-xserver package was
6529 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6530 in git
</a
> today to try to get apt-get to not remove xorg completely.
6531 No idea when it hits Squeeze, but when it does I hope it will reduce
6532 the difference somewhat.
6537 <title>LUMA, a very nice LDAP GUI
</title>
6538 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6540 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6541 <description><p
>The last few days I have been looking into the status of the LDAP
6542 directory in Debian Edu, and in the process I started to miss a GUI
6543 tool to browse the LDAP tree. The only one I was able to find in
6544 Debian/Squeeze and Lenny is
6545 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6546 be a great tool to get a overview of the current LDAP directory
6547 populated by default in Skolelinux. Thanks to it, I have been able to
6548 find empty and obsolete subtrees, misplaced objects and duplicate
6549 objects. It will be installed by default in Debian/Squeeze. If you
6550 are working with LDAP, give it a go. :)
</p
>
6552 <p
>I did notice one problem with it I have not had time to report to
6553 the BTS yet. There is no .desktop file in the package, so the tool do
6554 not show up in the Gnome and KDE menus, but only deep down in in the
6555 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6558 <p
>I have not yet been able to get it to modify the tree yet. I would
6559 like to move objects and remove subtrees directly in the GUI, but have
6560 not found a way to do that with LUMA yet. So in the mean time, I use
6561 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6563 <p
>If you have tips on other GUI tools for LDAP that might be useful
6564 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6566 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6567 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6568 useful GUI alternative. It seem like a good tool, but is unmaintained
6569 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6570 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6575 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6576 <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>
6577 <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>
6578 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6579 <description><p
>A while back, I
6580 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6581 about the fact
</a
> that it is not possible with the provided schemas
6582 for storing DNS and DHCP information in LDAP to combine the two sets
6583 of information into one LDAP object representing a computer.
</p
>
6585 <p
>In the mean time, I discovered that a simple fix would be to make
6586 the dhcpHost object class auxiliary, to allow it to be combined with
6587 the dNSDomain object class, and thus forming one object for one
6588 computer when storing both DHCP and DNS information in LDAP.
</p
>
6590 <p
>If I understand this correctly, it is not safe to do this change
6591 without also changing the assigned number for the object class, and I
6592 do not know enough about LDAP schema design to do that properly for
6593 Debian Edu.
</p
>
6595 <p
>Anyway, for future reference, this is how I believe we could change
6597 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6598 schema
</a
> to solve at least part of the problem with the LDAP schemas
6599 available today from IETF.
</p
>
6602 --- dhcp.schema (revision
65192)
6603 +++ dhcp.schema (working copy)
6605 objectclass (
2.16.840.1.113719.1.203.6.6
6606 NAME
'dhcpHost
'
6607 DESC
'This represents information about a particular client
'
6611 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6612 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
6615 <p
>I very much welcome clues on how to do this properly for Debian
6616 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6617 package, and should thus be free to rewrite it as we see fit.
</p
>
6619 <p
>If you want to help out with implementing this for Debian Edu,
6620 please contact us on debian-edu@lists.debian.org.
</p
>
6625 <title>Calling tasksel like the installer, while still getting useful output
</title>
6626 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
6627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
6628 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
6629 <description><p
>A few times I have had the need to simulate the way tasksel
6630 installs packages during the normal debian-installer run. Until now,
6631 I have ended up letting tasksel do the work, with the annoying problem
6632 of not getting any feedback at all when something fails (like a
6633 conffile question from dpkg or a download that fails), using code like
6636 <blockquote
><pre
>
6637 export DEBIAN_FRONTEND=noninteractive
6638 tasksel --new-install
6639 </pre
></blockquote
>
6641 This would invoke tasksel, let its automatic task selection pick the
6642 tasks to install, and continue to install the requested tasks without
6643 any output what so ever.
6645 Recently I revisited this problem while working on the automatic
6646 package upgrade testing, because tasksel would some times hang without
6647 any useful feedback, and I want to see what is going on when it
6648 happen. Then it occured to me, I can parse the output from tasksel
6649 when asked to run in test mode, and use that aptitude command line
6650 printed by tasksel then to simulate the tasksel run. I ended up using
6653 <blockquote
><pre
>
6654 export DEBIAN_FRONTEND=noninteractive
6655 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
6657 </pre
></blockquote
>
6659 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
6660 --without-recommends -o APT::Install-Recommends=no -y install
6661 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6662 ~pimportant
</tt
>", which will install the gnome desktop task, the
6663 laptop task and all packages with priority standard , required and
6664 important, just like tasksel would have done it during
6665 installation.
</p
>
6667 <p
>A better approach is probably to extend tasksel to be able to
6668 install packages without using debconf-apt-progress, for use cases
6669 like this.
</p
>
6674 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
6675 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
6676 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
6677 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
6678 <description><p
>My
6679 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
6680 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
6681 finally made the upgrade logs available from
6682 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
6683 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6684 apt and aptitude, and found their differences interesting. This time
6685 I will only focus on their removal plans.
</p
>
6687 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
6688 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
6689 surprising part is that it want to remove xorg and all
6690 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6691 sure why. When asking aptitude to do the same, it want to remove
129
6692 packages, but most of them are library packages I suspect are no
6693 longer needed. Both of them want to remove bluetooth packages, which
6694 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
6696 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
6697 which seem like a bad idea and xorg the same way as with Gnome. Asking
6698 aptitude for the same, it wants to remove
192 packages, none which are
6699 too surprising.
</p
>
6701 <p
>I guess the removal of xorg during upgrades should be investigated
6702 and avoided, and perhaps others as well. Here are the complete list
6703 of planned removals. The complete logs is available from the URL
6704 above. Note if you want to repeat these tests, that the upgrade test
6705 for kde+apt-get hung in the tasksel setup because of dpkg asking
6706 conffile questions. No idea why. I worked around it by using
6707 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
6710 <p
><b
>apt-get gnome
72</b
>
6711 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
6712 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6713 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
6714 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6715 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6716 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6717 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6718 xserver-xorg-input-kbd xserver-xorg-input-mouse
6719 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6720 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6721 xserver-xorg-video-ati xserver-xorg-video-chips
6722 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6723 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6724 xserver-xorg-video-glint xserver-xorg-video-i128
6725 xserver-xorg-video-i740 xserver-xorg-video-imstt
6726 xserver-xorg-video-intel xserver-xorg-video-mach64
6727 xserver-xorg-video-mga xserver-xorg-video-neomagic
6728 xserver-xorg-video-nsc xserver-xorg-video-nv
6729 xserver-xorg-video-openchrome xserver-xorg-video-r128
6730 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6731 xserver-xorg-video-rendition xserver-xorg-video-s3
6732 xserver-xorg-video-s3virge xserver-xorg-video-savage
6733 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6734 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6735 xserver-xorg-video-tga xserver-xorg-video-trident
6736 xserver-xorg-video-tseng xserver-xorg-video-v4l
6737 xserver-xorg-video-vesa xserver-xorg-video-vga
6738 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
6739 xulrunner-
1.9-gnome-support
</p
>
6741 <p
><b
>aptitude gnome
129</b
>
6743 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
6744 djvulibre-desktop finger gnome-app-install gnome-mount
6745 gnome-network-admin gnome-spell gnome-vfs-obexftp
6746 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6747 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6748 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6749 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
6750 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
6751 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
6752 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
6753 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
6754 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
6755 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
6756 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
6757 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
6758 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6759 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
6760 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
6761 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
6762 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
6763 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
6764 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6765 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6766 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6767 openoffice.org-writer2latex openssl-blacklist p7zip
6768 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
6769 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6770 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6771 swfdec-mozilla totem-gstreamer update-manager wodim
6772 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6773 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6776 <p
><b
>apt-get kde
82</b
>
6778 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6779 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6780 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6781 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6782 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6783 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6784 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6785 xserver-xorg-input-kbd xserver-xorg-input-mouse
6786 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6787 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6788 xserver-xorg-video-ati xserver-xorg-video-chips
6789 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6790 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6791 xserver-xorg-video-glint xserver-xorg-video-i128
6792 xserver-xorg-video-i740 xserver-xorg-video-imstt
6793 xserver-xorg-video-intel xserver-xorg-video-mach64
6794 xserver-xorg-video-mga xserver-xorg-video-neomagic
6795 xserver-xorg-video-nsc xserver-xorg-video-nv
6796 xserver-xorg-video-openchrome xserver-xorg-video-r128
6797 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6798 xserver-xorg-video-rendition xserver-xorg-video-s3
6799 xserver-xorg-video-s3virge xserver-xorg-video-savage
6800 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6801 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6802 xserver-xorg-video-tga xserver-xorg-video-trident
6803 xserver-xorg-video-tseng xserver-xorg-video-v4l
6804 xserver-xorg-video-vesa xserver-xorg-video-vga
6805 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
6807 <p
><b
>aptitude kde
192</b
>
6808 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
6809 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6810 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6811 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6812 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6813 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6814 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6815 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6816 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6817 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6818 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6819 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6820 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6821 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6822 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6823 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6824 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6825 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6826 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
6827 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6828 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6829 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
6830 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6831 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6832 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6833 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6834 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6835 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
6836 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
6837 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6838 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6839 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6840 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6841 texlive-common texlive-doc-base texlive-fonts-recommended
6842 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6843 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6844 xulrunner-
1.9</p
>
6850 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
6851 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
6852 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
6853 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
6854 <description><p
>The last few days I have done some upgrade testing in Debian, to
6855 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6856 have been discovered and reported in the process
6857 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
6858 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
6859 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
6860 kdebase-workspace-data), and to get a more regular testing going on, I
6861 am working on a script to automate the test.
</p
>
6863 <p
>The idea is to create a Lenny chroot and use tasksel to install a
6864 Gnome or KDE desktop installation inside the chroot before upgrading
6865 it. To ensure no services are started in the chroot, a policy-rc.d
6866 script is inserted. To make sure tasksel believe it is to install a
6867 desktop on a laptop, the tasksel tests are replaced in the chroot
6868 (only acceptable because this is a throw-away chroot).
</p
>
6870 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6871 currently always fail because udev refuses to upgrade with the kernel
6872 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6873 is created. The bug report
6874 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
6875 this problem do not trigger in a chroot, but I touch the file anyway
6876 to make sure the upgrade go well. Testing on virtual and real
6877 hardware have failed me because of udev so far, and creating this file
6878 do the trick in such settings anyway. This is a
6879 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
6880 issue
</a
> and the current udev behaviour is intended by the udev
6881 maintainer because he lack the resources to rewrite udev to keep
6882 working with old kernels or something like that. I really wish the
6883 udev upstream would keep udev backwards compatible, to avoid such
6884 upgrade problem, but given that they fail to do so, I guess
6885 documenting the way out of this mess is the best option we got for
6886 Debian Squeeze.
</p
>
6888 <p
>Anyway, back to the task at hand, testing upgrades. This test
6889 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
6892 <blockquote
><pre
>
6896 if [
"$
1" ] ; then
6905 exec
&lt; /dev/null
6907 mirror=http://ftp.skolelinux.org/debian
6908 tmpdir=chroot-$from-upgrade-$to-$desktop
6910 debootstrap $from $tmpdir $mirror
6911 chroot $tmpdir aptitude update
6912 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
6916 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6920 mount -t proc proc $tmpdir/proc
6921 # Make sure proc is unmounted also on failure
6922 trap exit_cleanup EXIT INT
6924 chroot $tmpdir aptitude -y install debconf-utils
6926 # Make sure tasksel autoselection trigger. It need the test scripts
6927 # to return the correct answers.
6928 echo tasksel tasksel/desktop multiselect $desktop | \
6929 chroot $tmpdir debconf-set-selections
6931 # Include the desktop and laptop task
6932 for test in desktop laptop ; do
6933 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
6937 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6940 DEBIAN_FRONTEND=noninteractive
6941 DEBIAN_PRIORITY=critical
6942 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6943 chroot $tmpdir tasksel --new-install
6945 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
6946 chroot $tmpdir aptitude update
6947 touch $tmpdir/etc/udev/kernel-upgrade
6948 chroot $tmpdir aptitude -y dist-upgrade
6950 </pre
></blockquote
>
6952 <p
>I suspect it would be useful to test upgrades with both apt-get and
6953 with aptitude, but I have not had time to look at how they behave
6954 differently so far. I hope to get a cron job running to do the test
6955 regularly and post the result on the web. The Gnome upgrade currently
6956 work, while the KDE upgrade fail because of the bug in
6957 kdebase-workspace-data
</p
>
6959 <p
>I am not quite sure what kind of extract from the huge upgrade logs
6960 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
6961 post, so I will refrain from trying. I can report that for Gnome,
6962 aptitude report
760 packages upgraded,
448 newly installed,
129 to
6963 remove and
1 not upgraded and
1024MB need to be downloaded while for
6964 KDE the same numbers are
702 packages upgraded,
507 newly installed,
6965 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
6967 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
6968 is able to migrate to dependency based boot sequencing and parallel
6969 booting without a hitch. Was unsure if there were still bugs with
6970 packages failing to clean up their obsolete init.d script during
6971 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6977 <title>Upstart or sysvinit - as init.d scripts see it
</title>
6978 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
6979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
6980 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
6981 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
6982 scripts to migrate (some of) their operations to upstart job while
6983 keeping the init.d for hurd and kfreebsd. The packages with such
6984 needs will need a way to get their init.d scripts to behave
6985 differently when used with sysvinit and with upstart. Because of
6986 this, I had a look at the environment variables set when a init.d
6987 script is running under upstart, and when it is not.
</p
>
6989 <p
>With upstart, I notice these environment variables are set when a
6990 script is started from rcS.d/ (ignoring some irrelevant ones like
6993 <blockquote
><pre
>
6999 UPSTART_EVENTS=startup
7001 UPSTART_JOB=rc-sysinit
7002 </pre
></blockquote
>
7004 <p
>With sysvinit, these environment variables are set for the same
7007 <blockquote
><pre
>
7008 INIT_VERSION=sysvinit-
2.88
7013 </pre
></blockquote
>
7015 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
7016 sysvinit are not set by upstart. Not sure if it is intentional or not
7017 to not be compatible with sysvinit in this regard.
</p
>
7019 <p
>For scripts needing to behave differently when upstart is used,
7020 looking for the UPSTART_JOB environment variable seem to be a good
7026 <title>A manual for standards wars...
</title>
7027 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
7028 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
7029 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
7030 <description><p
>Via the
7031 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
7032 of Rob Weir
</a
> I came across the very interesting essay named
7033 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
7034 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
7035 following the standards wars of today.
</p
>
7040 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
7041 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
7042 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
7043 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
7044 <description><p
>When using sitesummary at a site to track machines, it is possible
7045 to get a list of the machine types in use thanks to the DMI
7046 information extracted from each machine. The script to do so is
7047 included in the sitesummary package, and here is example output from
7048 the Skolelinux build servers:
</p
>
7050 <blockquote
><pre
>
7051 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7053 Dell Computer Corporation
1
7056 eserver xSeries
345 -[
8670M1X]-
1
7060 </pre
></blockquote
>
7062 <p
>The quality of the report depend on the quality of the DMI tables
7063 provided in each machine. Here there are Intel machines without model
7064 information listed with Intel as vendor and no model, and virtual Xen
7065 machines listed as [no-dmi-info]. One can add -l as a command line
7066 option to list the individual machines.
</p
>
7068 <p
>A larger list is
7069 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
7070 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
7071 provide the basic sitesummary report publicly. In their report there
7072 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
7073 their machines, and as sitesummary is available in both distributions,
7074 it is trivial to get all of them to report to the same central
7075 collector.
</p
>
7080 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
7081 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
7082 <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>
7083 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
7084 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
7085 start at boot when an NVidia video card is used is handled. The
7086 problem seem to be that the nvidia X.org driver uses a long time to
7087 initialize, and this duration is longer than kdm is configured to
7090 <p
>I came across two bugs related to this issue,
7091 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
7092 against initscripts and passed on to nvidia-glx when it became obvious
7093 that the nvidia drivers were involved, and
7094 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
7095 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
7097 <p
>To me, it seem that no-one is interested in actually solving the
7098 problem nvidia video card owners experience and make sure the Debian
7099 distribution work out of the box for these users. The nvidia driver
7100 maintainers expect kdm to be set up to wait longer, while kdm expect
7101 the nvidia driver maintainers to fix the driver to start faster, and
7102 while they wait for each other I guess the users end up switching to a
7103 distribution that work for them. I have no idea what the solution is,
7104 but I am pretty sure that waiting for each other is not it.
</p
>
7106 <p
>I wonder why we end up handling bugs this way.
</p
>
7111 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
7112 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
7113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
7114 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
7115 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
7116 The feature seem to hold up pretty well, but three fairly serious
7117 issues are known and should be solved:
7121 <li
>The wicd package seen to
7122 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
7123 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
7124 parallel booting is enabled. No idea why, but the wicd maintainer
7125 seem to be on the case.
</li
>
7127 <li
>The nvidia X driver seem to
7128 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
7129 triggered more easily when parallel booting is in effect. The
7130 maintainer is on the case.
</li
>
7132 <li
>The sysv-rc package fail to properly enable dependency based boot
7133 sequencing (the shutdown is broken) when old file-rc users
7134 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
7135 sysv-rc. One way to solve it would be for file-rc to create
7136 /etc/init.d/.legacy-bootordering, and another is to try to make
7137 sysv-rc more robust. Will investigate some more and probably upload a
7138 workaround in sysv-rc to help those trying to move from file-rc to
7139 sysv-rc get a working shutdown.
</li
>
7141 </ul
></p
>
7143 <p
>All in all not many surprising issues, and all of them seem
7144 solvable before Squeeze is released. In addition to these there are
7145 some packages with bugs in their dependencies and run level settings,
7146 which I expect will be fixed in a reasonable time span.
</p
>
7148 <p
>If you report any problems with dependencies in init.d scripts to
7149 the BTS, please usertag the report to get it to show up at
7150 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7151 list of usertagged bugs related to this
</a
>.
</p
>
7153 <p
>Update: Correct bug number to file-rc issue.
</p
>
7158 <title>More flexible firmware handling in debian-installer
</title>
7159 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
7160 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
7161 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
7162 <description><p
>After a long break from debian-installer development, I finally
7163 found time today to return to the project. Having to spend less time
7164 working dependency based boot in debian, as it is almost complete now,
7165 definitely helped freeing some time.
</p
>
7167 <p
>A while back, I ran into a problem while working on Debian Edu. We
7168 include some firmware packages on the Debian Edu CDs, those needed to
7169 get disk and network controllers working. Without having these
7170 firmware packages available during installation, it is impossible to
7171 install Debian Edu on the given machine, and because our target group
7172 are non-technical people, asking them to provide firmware packages on
7173 an external medium is a support pain. Initially, I expected it to be
7174 enough to include the firmware packages on the CD to get
7175 debian-installer to find and use them. This proved to be wrong.
7176 Next, I hoped it was enough to symlink the relevant firmware packages
7177 to some useful location on the CD (tried /cdrom/ and
7178 /cdrom/firmware/). This also proved to not work, and at this point I
7179 found time to look at the debian-installer code to figure out what was
7180 going to work.
</p
>
7182 <p
>The firmware loading code is in the hw-detect package, and a closer
7183 look revealed that it would only look for firmware packages outside
7184 the installation media, so the CD was never checked for firmware
7185 packages. It would only check USB sticks, floppies and other
7186 "external
" media devices. Today I changed it to also look in the
7187 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7188 solve the problem I ran into with Debian edu. I also changed it to
7189 look in /firmware/, to make sure the installer also find firmware
7190 provided in the initrd when booting the installer via PXE, to allow us
7191 to provide the same feature in the PXE setup included in Debian
7194 <p
>To make sure firmware deb packages with a license questions are not
7195 activated without asking if the license is accepted, I extended
7196 hw-detect to look for preinst scripts in the firmware packages, and
7197 run these before activating the firmware during installation. The
7198 license question is asked using debconf in the preinst, so this should
7199 solve the issue for the firmware packages I have looked at so far.
</p
>
7201 <p
>If you want to discuss the details of these features, please
7202 contact us on debian-boot@lists.debian.org.
</p
>
7207 <title>Parallellized boot is now the default in Debian/unstable
</title>
7208 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
7209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
7210 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
7211 <description><p
>Since this evening, parallel booting is the default in
7212 Debian/unstable for machines using dependency based boot sequencing.
7213 Apparently the testing of concurrent booting has been wider than
7214 expected, if I am to believe the
7215 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7216 on debian-devel@
</a
>, and I concluded a few days ago to move forward
7217 with the feature this weekend, to give us some time to detect any
7218 remaining problems before Squeeze is frozen. If serious problems are
7219 detected, it is simple to change the default back to sequential boot.
7220 The upload of the new sysvinit package also activate a new upstream
7223 More information about
7224 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7225 based boot sequencing
</a
> is available from the Debian wiki. It is
7226 currently possible to disable parallel booting when one run into
7227 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
7229 <blockquote
><pre
>
7231 </pre
></blockquote
>
7233 <p
>If you report any problems with dependencies in init.d scripts to
7234 the BTS, please usertag the report to get it to show up at
7235 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7236 list of usertagged bugs related to this
</a
>.
</p
>
7241 <title>Sitesummary tip: Listing MAC address of all clients
</title>
7242 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
7243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
7244 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
7245 <description><p
>In the recent Debian Edu versions, the
7246 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
7247 system
</a
> is used to keep track of the machines in the school
7248 network. Each machine will automatically report its status to the
7249 central server after boot and once per night. The network setup is
7250 also reported, and using this information it is possible to get the
7251 MAC address of all network interfaces in the machines. This is useful
7252 to update the DHCP configuration.
</p
>
7254 <p
>To give some idea how to use sitesummary, here is a one-liner to
7255 ist all MAC addresses of all machines reporting to sitesummary. Run
7256 this on the collector host:
</p
>
7258 <blockquote
><pre
>
7259 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
7260 </pre
></blockquote
>
7262 <p
>This will list all MAC addresses assosiated with all machine, one
7263 line per machine and with space between the MAC addresses.
</p
>
7265 <p
>To allow system administrators easier job at adding static DHCP
7266 addresses for hosts, it would be possible to extend this to fetch
7267 machine information from sitesummary and update the DHCP and DNS
7268 tables in LDAP using this information. Such tool is unfortunately not
7269 written yet.
</p
>
7274 <title>systemd, an interesting alternative to upstart
</title>
7275 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
7276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
7277 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
7278 <description><p
>The last few days a new boot system called
7279 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
7281 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
7283 to the free software world. I have not yet had time to play around
7284 with it, but it seem to be a very interesting alternative to
7285 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
7286 a good alternative for Debian when we are able to switch to an event
7287 based boot system. Tollef is
7288 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
7289 systemd into Debian, and I look forward to seeing how well it work. I
7290 like the fact that systemd handles init.d scripts with dependency
7291 information natively, allowing them to run in parallel where upstart
7292 at the moment do not.
</p
>
7294 <p
>Unfortunately do systemd have the same problem as upstart regarding
7295 platform support. It only work on recent Linux kernels, and also need
7296 some new kernel features enabled to function properly. This means
7297 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7298 system. Not sure how that will be handled if systemd proves to be the
7299 way forward.
</p
>
7301 <p
>In the mean time, based on the
7302 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7303 on debian-devel@
</a
> regarding parallel booting in Debian, I have
7304 decided to enable full parallel booting as the default in Debian as
7305 soon as possible (probably this weekend or early next week), to see if
7306 there are any remaining serious bugs in the init.d dependencies. A
7307 new version of the sysvinit package implementing this change is
7308 already in experimental. If all go well, Squeeze will be released
7309 with parallel booting enabled by default.
</p
>
7314 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
7315 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
7316 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
7317 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
7318 <description><p
>These days, the init.d script dependencies in Squeeze are quite
7319 complete, so complete that it is actually possible to run all the
7320 init.d scripts in parallell based on these dependencies. If you want
7321 to test your Squeeze system, make sure
7322 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7323 based boot sequencing
</a
> is enabled, and add this line to
7324 /etc/default/rcS:
</p
>
7326 <blockquote
><pre
>
7327 CONCURRENCY=makefile
7328 </pre
></blockquote
>
7330 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
7331 scripts in parallel using the dependency information stored in
7332 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7333 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7334 to try to start the kdm and gdm scripts as early as possible, and will
7335 start the facilities required by kdm or gdm as early as possible to
7336 make this happen.
</p
>
7338 <p
>Give it a try, and see if you like the result. If some services
7339 fail to start properly, it is most likely because they have incomplete
7340 init.d script dependencies in their startup script (or some of their
7341 dependent scripts have incomplete dependencies). Report bugs and get
7342 the package maintainers to fix it. :)
</p
>
7344 <p
>Running scripts in parallel could be the default in Debian when we
7345 manage to get the init.d script dependencies complete and correct. I
7346 expect we will get there in Squeeze+
1, if we get manage to test and
7347 fix the remaining issues.
</p
>
7349 <p
>If you report any problems with dependencies in init.d scripts to
7350 the BTS, please usertag the report to get it to show up at
7351 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7352 list of usertagged bugs related to this
</a
>.
</p
>
7357 <title>Debian has switched to dependency based boot sequencing
</title>
7358 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
7359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
7360 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
7361 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
7362 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
7363 have been migrated to using dependency based boot sequencing. This
7364 conclude work me and others have been doing for the last three days.
7365 It feels great to see this finally part of the default Debian
7366 installation. Now we just need to weed out the last few problems that
7367 are bound to show up, to get everything ready for Squeeze.
</p
>
7369 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
7370 fixing the more fundamental problem of handing the event based
7371 non-predictable kernel in the early boot.
</p
>
7376 <title>Taking over sysvinit development
</title>
7377 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
7378 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
7379 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
7380 <description><p
>After several years of frustration with the lack of activity from
7381 the existing sysvinit upstream developer, I decided a few weeks ago to
7382 take over the package and become the new upstream. The number of
7383 patches to track for the Debian package was becoming a burden, and the
7384 lack of synchronization between the distribution made it hard to keep
7385 the package up to date.
</p
>
7387 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7388 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
7389 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
7390 and Fedora), based on the patches currently in use in these
7391 distributions. We Debian maintainers plan to move to this tarball as
7392 the new upstream as soon as we find time to do the merge. Since the
7393 new tarball was created, we agreed with Werner at SuSe to make a new
7394 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
7395 development there. The project is registered and currently waiting
7396 for approval by the Savannah administrators, and as soon as it is
7397 approved, we will import the old versions from svn and continue
7398 working on the future release.
</p
>
7400 <p
>It is a bit ironic that this is done now, when some of the involved
7401 distributions are moving to upstart as a syvinit replacement.
</p
>
7406 <title>Debian boots quicker and quicker
</title>
7407 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
7408 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
7409 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
7410 <description><p
>I spent Monday and tuesday this week in London with a lot of the
7411 people involved in the boot system on Debian and Ubuntu, to see if we
7412 could find more ways to speed up the boot system. This was an Ubuntu
7414 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
7415 gathering
</a
>. It was quite productive. We also discussed the future
7416 of boot systems, and ways to handle the increasing number of boot
7417 issues introduced by the Linux kernel becoming more and more
7418 asynchronous and event base. The Ubuntu approach using udev and
7419 upstart might be a good way forward. Time will show.
</p
>
7421 <p
>Anyway, there are a few ways at the moment to speed up the boot
7422 process in Debian. All of these should be applied to get a quick
7427 <li
>Use dash as /bin/sh.
</li
>
7429 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
7430 clock is in UTC.
</li
>
7432 <li
>Install and activate the insserv package to enable
7433 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7434 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
7438 These points are based on the Google summer of code work done by
7439 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
7442 <p
>Support for makefile-style concurrency during boot was uploaded to
7443 unstable yesterday. When we tested it, we were able to cut
6 seconds
7444 from the boot sequence. It depend on very correct dependency
7445 declaration in all init.d scripts, so I expect us to find edge cases
7446 where the dependences in some scripts are slightly wrong when we start
7447 using this.
</p
>
7449 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7450 introduced by Raphael Geissert today, one that could affect the
7451 startup speed as well. Instead of starting some scripts concurrently
7452 from rcS.d/ and another set of scripts from rc2.d/, it would be
7453 possible to run a of them in the same process. A quick way to test
7454 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
7455 insserv
'. Will need to test if that work. :)
</p
>
7460 <title>BSAs påstander om piratkopiering møter motstand
</title>
7461 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
7462 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
7463 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
7464 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
7465 programvareselskapene som Microsoft og Apple, publisert en rapport der
7466 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7467 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7469 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
7470 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
7471 dagene. Et spesielt interessant kommentar fra Sverige,
7472 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
7473 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
7476 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
7477 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7478 företag.
"Man bör nog kanske inte se de här siffrorna som helt
7479 exakta
", säger BSAs Sverigechef John Hugosson.
7482 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
7483 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
7484 piracy figures need a shot of reality
</a
> og
<a
7485 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
7486 Copyright Treaty Work?
</a
></p
>
7488 <p
>Fant lenkene via
<a
7489 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
7490 på Slashdot
</a
>.
</p
>
7495 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
7496 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
7497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
7498 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
7499 <description><p
>Kom over
7500 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
7501 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7502 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7503 jobber til daglig. En rask opptelling forteller meg at vi har
490
7504 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
7505 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7506 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7511 <title>Kryptert harddisk - naturligvis
</title>
7512 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7514 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7515 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7516 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7517 når en tar tap av arbeidstid, fortrolige dokumenter,
7518 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7519 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7520 til at jeg har kryptert harddisken på både kontormaskinen og min
7521 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7522 komme på avveie, den første informasjon relatert til jobben min ved
7523 Universitetet i Oslo, og den andre relatert til blant annet
7524 foreningsarbeide. Kryptering av diskene gjør at det er lite
7525 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7526 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7527 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7528 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7529 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7530 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7531 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7532 det er gjort slik jeg gjør det er minimale, og gevinstene er
7533 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7534 maskinen reinstalleres og alt er tapt.
</p
>
7536 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7537 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7538 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7539 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7540 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7541 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7542 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7543 betydelige.
</p
>
7548 <title>Two projects that have improved the quality of free software a lot
</title>
7549 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7551 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7552 <description><p
>There are two software projects that have had huge influence on the
7553 quality of free software, and I wanted to mention both in case someone
7554 do not yet know them.
</p
>
7556 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7557 tool to detect and expose errors in the memory handling of programs.
7558 It is easy to use, all one need to do is to run
'valgrind program
',
7559 and it will report any problems on stdout. It is even better if the
7560 program include debug information. With debug information, it is able
7561 to report the source file name and line number where the problem
7562 occurs. It can report things like
'reading past memory block in file
7563 X line N, the memory block was allocated in file Y, line M
', and
7564 'using uninitialised value in control logic
'. This tool has made it
7565 trivial to investigate reproducible crash bugs in programs, and have
7566 reduced the number of this kind of bugs in free software a lot.
7568 <p
>The second one is
7569 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7570 a source code checker. It is able to process the source of a program
7571 and find problems in the logic without running the program. It
7572 started out as the Stanford Checker and became well known when it was
7573 used to find bugs in the Linux kernel. It is now a commercial tool
7574 and the company behind it is running
7575 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7576 free software community, where a lot of free software projects get
7577 their source checked for free. Several thousand defects have been
7578 found and fixed so far. It can find errors like
'lock L taken in file
7579 X line N is never released if exiting in line M
', or
'the code in file
7580 Y lines O to P can never be executed
'. The projects included in the
7581 community service project have managed to get rid of a lot of
7582 reliability problems thanks to Coverity.
</p
>
7584 <p
>I believe tools like this, that are able to automatically find
7585 errors in the source, are vital to improve the quality of software and
7586 make sure we can get rid of the crashing and failing software we are
7587 surrounded by today.
</p
>
7592 <title>No patch is not better than a useless patch
</title>
7593 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7595 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7596 <description><p
>Julien Blache
7597 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7598 patch is better than a useless patch
</a
>. I completely disagree, as a
7599 patch allow one to discuss a concrete and proposed solution, and also
7600 prove that the issue at hand is important enough for someone to spent
7601 time on fixing it. No patch do not provide any of these positive
7602 properties.
</p
>
7607 <title>Standardize on protocols and formats, not vendors and applications
</title>
7608 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
7609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
7610 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
7611 <description><p
>Where I work at the University of Oslo, one decision stand out as a
7612 very good one to form a long lived computer infrastructure. It is the
7613 simple one, lost by many in todays computer industry: Standardize on
7614 open network protocols and open exchange/storage formats, not applications.
7615 Applications come and go, while protocols and files tend to stay, and
7616 thus one want to make it easy to change application and vendor, while
7617 avoiding conversion costs and locking users to a specific platform or
7618 application.
</p
>
7620 <p
>This approach make it possible to replace the client applications
7621 independently of the server applications. One can even allow users to
7622 use several different applications as long as they handle the selected
7623 protocol and format. In the normal case, only one client application
7624 is recommended and users only get help if they choose to use this
7625 application, but those that want to deviate from the easy path are not
7626 blocked from doing so.
</p
>
7628 <p
>It also allow us to replace the server side without forcing the
7629 users to replace their applications, and thus allow us to select the
7630 best server implementation at any moment, when scale and resouce
7631 requirements change.
</p
>
7633 <p
>I strongly recommend standardizing - on open network protocols and
7634 open formats, but I would never recommend standardizing on a single
7635 application that do not use open network protocol or open formats.
</p
>
7640 <title>Returning from Skolelinux developer gathering
</title>
7641 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
7642 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
7643 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
7644 <description><p
>I
'm sitting on the train going home from this weekends Debian
7645 Edu/Skolelinux development gathering. I got a bit done tuning the
7646 desktop, and looked into the dynamic service location protocol
7647 implementation avahi. It look like it could be useful for us. Almost
7648 30 people participated, and I believe it was a great environment to
7649 get to know the Skolelinux system. Walter Bender, involved in the
7650 development of the Sugar educational platform, presented his stuff and
7651 also helped me improve my OLPC installation. He also showed me that
7652 his Turtle Art application can be used in standalone mode, and we
7653 agreed that I would help getting it packaged for Debian. As a
7654 standalone application it would be great for Debian Edu. We also
7655 tried to get the video conferencing working with two OLPCs, but that
7656 proved to be too hard for us. The application seem to need more work
7657 before it is ready for me. I look forward to getting home and relax
7663 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
7664 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
7665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
7666 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
7667 <description><p
>The state of standardized LDAP schemas on Linux is far from
7668 optimal. There is RFC
2307 documenting one way to store NIS maps in
7669 LDAP, and a modified version of this normally called RFC
2307bis, with
7670 some modifications to be compatible with Active Directory. The RFC
7671 specification handle the content of a lot of system databases, but do
7672 not handle DNS zones and DHCP configuration.
</p
>
7674 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
7675 we would like to store information about users, SMB clients/hosts,
7676 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7677 and LTSP configuration in LDAP. These objects have a lot in common,
7678 but with the current LDAP schemas it is not possible to have one
7679 object per entity. For example, one need to have at least three LDAP
7680 objects for a given computer, one with the SMB related stuff, one with
7681 DNS information and another with DHCP information. The schemas
7682 provided for DNS and DHCP are impossible to combine into one LDAP
7683 object. In addition, it is impossible to implement quick queries for
7684 netgroup membership, because of the way NIS triples are implemented.
7685 It just do not scale. I believe it is time for a few RFC
7686 specifications to cleam up this mess.
</p
>
7688 <p
>I would like to have one LDAP object representing each computer in
7689 the network, and this object can then keep the SMB (ie host key), DHCP
7690 (mac address/name) and DNS (name/IP address) settings in one place.
7691 It need to be efficently stored to make sure it scale well.
</p
>
7693 <p
>I would also like to have a quick way to map from a user or
7694 computer and to the net group this user or computer is a member.
</p
>
7696 <p
>Active Directory have done a better job than unix heads like myself
7697 in this regard, and the unix side need to catch up. Time to start a
7698 new IETF work group?
</p
>
7703 <title>Endelig er Debian Lenny gitt ut
</title>
7704 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
7705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
7706 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
7707 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
7708 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
7709 Et langt steg videre for Debian-prosjektet, og en rekke nye
7710 programpakker blir nå tilgjengelig for de av oss som bruker den
7711 stabile utgaven av Debian. Neste steg er nå å få
7712 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
7713 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
7714 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7715 slippes løs på skolene. Takk til alle debian-utviklerne som har
7716 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7717 bootsekvens tilgjengelig i stabil utgave, vha pakken
7718 <tt
>insserv
</tt
>.
</p
>
7723 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
7724 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
7725 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
7726 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
7727 <description><p
>This weekend we had a small developer gathering for Debian Edu in
7728 Oslo. Most of Saturday was used for the general assemly for the
7729 member organization, but the rest of the weekend I used to tune the
7730 LTSP installation. LTSP now work out of the box on the
10-network.
7731 Acer Aspire One proved to be a very nice thin client, with both
7732 screen, mouse and keybard in a small box. Was working on getting the
7733 diskless workstation setup configured out of the box, but did not
7734 finish it before the weekend was up.
</p
>
7736 <p
>Did not find time to look at the
4 VGA cards in one box we got from
7737 the Brazilian group, so that will have to wait for the next
7738 development gathering. Would love to have the Debian Edu installer
7739 automatically detect and configure a multiseat setup when it find one
7740 of these cards.
</p
>
7745 <title>The sorry state of multimedia browser plugins in Debian
</title>
7746 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
7747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
7748 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
7749 <description><p
>Recently I have spent some time evaluating the multimedia browser
7750 plugins available in Debian Lenny, to see which one we should use by
7751 default in Debian Edu. We need an embedded video playing plugin with
7752 control buttons to pause or stop the video, and capable of streaming
7753 all the multimedia content available on the web. The test results and
7754 notes are available on
7755 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
7756 Debian wiki
</a
>. I was surprised how few of the plugins are able to
7757 fill this need. My personal video player favorite, VLC, has a really
7758 bad plugin which fail on a lot of the test pages. A lot of the MIME
7759 types I would expect to work with any free software player (like
7760 video/ogg), just do not work. And simple formats like the
7761 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
7762 totem and vlc plugins. I hope the situation will improve soon. No
7763 wonder sites use the proprietary Adobe flash to play video.
</p
>
7765 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
7766 be the only one fitting our needs. :/
</p
>