1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
11 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
13 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
14 <description><p
>Around three years ago, I created
15 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
16 system
</a
> to get a more practical solution in Debian for handing
17 hardware related packages. A GUI system in the isenkram package will
18 present a pop-up dialog when some hardware dongle supported by
19 relevant packages in Debian is inserted into the machine. The same
20 lookup mechanism to detect packages is available as command line
21 tools in the isenkram-cli package. In addition to mapping hardware,
22 it will also map kernel firmware files to packages and make it easy to
23 install needed firmware packages automatically. The key for this
24 system to work is a good way to map hardware to packages, in other
25 words, allow packages to announce what hardware they will work
28 <p
>I started by providing data files in the isenkram source, and
29 adding code to download the latest version of these data files at run
30 time, to ensure every user had the most up to date mapping available.
31 I also added support for storing the mapping in the Packages file in
32 the apt repositories, but did not push this approach because while I
33 was trying to figure out how to best store hardware/package mappings,
34 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
35 appstream system
</a
> was announced. I got in touch and suggested to
36 add the hardware mapping into that data set to be able to use
37 appstream as a data source, and this was accepted at least for the
38 Debian version of appstream.
</p
>
40 <p
>A few days ago using appstream in Debian for this became possible,
41 and today I uploaded a new version
0.20 of isenkram adding support for
42 appstream as a data source for mapping hardware to packages. The only
43 package so far using appstream to announce its hardware support is my
44 pymissile package. I got help from Matthias Klumpp with figuring out
45 how do add the required
46 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
47 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
48 this content:
</p
>
50 <blockquote
><pre
>
51 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
52 &lt;component
&gt;
53 &lt;id
&gt;pymissile
&lt;/id
&gt;
54 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
55 &lt;name
&gt;pymissile
&lt;/name
&gt;
56 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
57 &lt;description
&gt;
59 Pymissile provides a curses interface to control an original
60 Marks and Spencer / Striker USB Missile Launcher, as well as a
61 motion control script to allow a webcamera to control the
64 &lt;/description
&gt;
65 &lt;provides
&gt;
66 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
67 &lt;/provides
&gt;
68 &lt;/component
&gt;
69 </pre
></blockquote
>
71 <p
>The key for isenkram is the component/provides/modalias value,
72 which is a glob style match rule for hardware specific strings
73 (modalias strings) provided by the Linux kernel. In this case, it
74 will map to all USB devices with vendor code
1130 and product code
77 <p
>Note, it is important that the license of all the metadata files
78 are compatible to have permissions to aggregate them into archive wide
79 appstream files. Matthias suggested to use MIT or BSD licenses for
80 these files. A challenge is figuring out a good id for the data, as
81 it is supposed to be globally unique and shared across distributions
82 (in other words, best to coordinate with upstream what to use). But
83 it can be changed later or, so we went with the package name as
84 upstream for this project is dormant.
</p
>
86 <p
>To get the metadata file installed in the correct location for the
87 mirror update scripts to pick it up and include its content the
88 appstream data source, the file must be installed in the binary
89 package under /usr/share/appdata/. I did this by adding the following
90 line to debian/pymissile.install:
</p
>
92 <blockquote
><pre
>
93 debian/pymissile.metainfo.xml usr/share/appdata
94 </pre
></blockquote
>
96 <p
>With that in place, the command line tool isenkram-lookup will list
97 all packages useful on the current computer automatically, and the GUI
98 pop-up handler will propose to install the package not already
99 installed if a hardware dongle is inserted into the machine in
102 <p
>Details of the modalias field in appstream is available from the
103 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
105 <p
>To locate the modalias values of all hardware present in a machine,
106 try running this command on the command line:
</p
>
108 <blockquote
><pre
>
109 cat $(find /sys/devices/|grep modalias)
110 </pre
></blockquote
>
112 <p
>To learn more about the isenkram system, please check out
113 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
114 blog posts tagged isenkram
</a
>.
</p
>
119 <title>The GNU General Public License is not magic pixie dust
</title>
120 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
122 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
123 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
124 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
125 GPL is not magic pixie dust
</a
>" explain the importance of making sure
126 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
127 I quote the blog post from Paul in full here with his permission:
<p
>
131 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
134 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
136 The first step is to choose a
137 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
140 The next step is, when someone fails to follow that copyleft license,
141 <b
>it must be enforced
</b
><br/
>
143 and its a simple fact of our modern society that such type of
146 is incredibly expensive to do and incredibly difficult to do.
149 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
150 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
151 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
152 0x57</a
></small
></p
>
154 <p
>As the Debian Website
155 <a href=
"https://bugs.debian.org/
794116">used
</a
>
156 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
157 imply, public domain and permissively licensed software can lead to
158 the production of more proprietary software as people discover useful
159 software, extend it and or incorporate it into their hardware or
160 software products. Copyleft licenses such as the GNU GPL were created
161 to close off this avenue to the production of proprietary software but
162 such licenses are not enough. With the ongoing adoption of Free
163 Software by individuals and groups, inevitably the community
's
164 expectations of license compliance are violated, usually out of
165 ignorance of the way Free Software works, but not always. As Karen
166 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
167 Freedom
">FaiF
</a
>
168 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
169 copyleft is nothing if no-one is willing and able to stand up in court
170 to protect it. The reality of today
's world is that legal
171 representation is expensive, difficult and time consuming. With
172 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
173 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
174 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
175 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
176 of the Linux project, Debian and other groups against GPL violations.
177 In March the SFC supported a
178 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
179 by Christoph Hellwig
</a
> against VMware for refusing to
180 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
181 with the GPL
</a
> in relation to their use of parts of the Linux
182 kernel. Since then two of their sponsors pulled corporate funding and
184 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
185 or cancelled their talks
</a
>. As a result they have decided to rely
186 less on corporate funding and more on the broad community of
187 individuals who support Free Software and copyleft. So the SFC has
188 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
189 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
190 a community of folks who stand up for copyleft and the GPL by
191 supporting their work on promoting and supporting copyleft and Free
194 <p
>If you support Free Software,
195 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
196 what the SFC do, agree with their
197 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
198 principles
</a
>, are happy about their
199 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
200 work on a project that is an SFC
201 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
202 just want to stand up for copyleft, please join
203 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
204 Allan Webber
</a
>,
205 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
207 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
208 Bacon
</a
>, myself and
209 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
211 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
212 next week your donation will be
213 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
214 by an anonymous donor. Please also consider asking your employer to
215 match your donation or become a sponsor of SFC. Don
't forget to
216 spread the word about your support for SFC via email, your blog and or
217 social media accounts.
</p
>
221 <p
>I agree with Paul on this topic and just signed up as a Supporter
222 of Software Freedom Conservancy myself. Perhaps you should be a
223 supporter too?
</p
>
228 <title>PGP key transition statement for key EE4E02F9
</title>
229 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
231 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
232 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
233 set it up properly. I wanted to generate it offline and have it
234 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
235 smart card
</a
> for daily use, and learning how to do it and finding
236 time to sit down with an offline machine almost took forever. But
237 finally I
've been able to complete the process, and have now moved
238 from my old GPG key to a new GPG key. See
239 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
240 full transition statement, signed with both my old and new key
</a
> for
241 the details. This is my new key:
</p
>
244 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
245 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
246 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
247 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
248 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
249 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
250 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
253 <p
>The key can be downloaded from the OpenPGP key servers, signed by
254 my old key.
</p
>
256 <p
>If you signed my old key
257 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
258 I
'd very much appreciate a signature on my new key, details and
259 instructions in the transition statement. I m happy to reciprocate if
260 you have a similarly signed transition statement to present.
</p
>
265 <title>The life and death of a laptop battery
</title>
266 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
267 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
268 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
269 <description><p
>When I get a new laptop, the battery life time at the start is OK.
270 But this do not last. The last few laptops gave me a feeling that
271 within a year, the life time is just a fraction of what it used to be,
272 and it slowly become painful to use the laptop without power connected
273 all the time. Because of this, when I got a new Thinkpad X230 laptop
274 about two years ago, I decided to monitor its battery state to have
275 more hard facts when the battery started to fail.
</p
>
277 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
279 <p
>First I tried to find a sensible Debian package to record the
280 battery status, assuming that this must be a problem already handled
281 by someone else. I found
282 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
283 which collects statistics from the battery, but it was completely
284 broken. I sent a few suggestions to the maintainer, but decided to
285 write my own collector as a shell script while I waited for feedback
287 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
288 blog post about the battery development on a MacBook Air
</a
> I also
290 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
291 available in Debian.
</p
>
293 <p
>I started my collector
2013-
07-
15, and it has been collecting
294 battery stats ever since. Now my
295 /var/log/hjemmenett-battery-status.log file contain around
115,
000
296 measurements, from the time the battery was working great until now,
297 when it is unable to charge above
7% of original capacity. My
298 collector shell script is quite simple and look like this:
</p
>
303 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
305 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
306 logfile=/var/log/hjemmenett-battery-status.log
308 files=
"manufacturer model_name technology serial_number \
309 energy_full energy_full_design energy_now cycle_count status
"
311 if [ ! -e
"$logfile
" ] ; then
313 printf
"timestamp,
"
315 printf
"%s,
" $f
318 )
> "$logfile
"
322 # Print complete message in one echo call, to avoid race condition
323 # when several log processes run in parallel.
324 msg=$(printf
"%s,
" $(date +%s); \
325 for f in $files; do \
326 printf
"%s,
" $(cat $f); \
328 echo
"$msg
"
331 cd /sys/class/power_supply
334 (cd $bat
&& log_battery
>> "$logfile
")
338 <p
>The script is called when the power management system detect a
339 change in the power status (power plug in or out), and when going into
340 and out of hibernation and suspend. In addition, it collect a value
341 every
10 minutes. This make it possible for me know when the battery
342 is discharging, charging and how the maximum charge change over time.
343 The code for the Debian package
344 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
345 available on github
</a
>.
</p
>
347 <p
>The collected log file look like this:
</p
>
350 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
351 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
353 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
354 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
357 <p
>I wrote a small script to create a graph of the charge development
358 over time. This graph depicted above show the slow death of my laptop
361 <p
>But why is this happening? Why are my laptop batteries always
362 dying in a year or two, while the batteries of space probes and
363 satellites keep working year after year. If we are to believe
364 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
365 University
</a
>, the cause is me charging the battery whenever I have a
366 chance, and the fix is to not charge the Lithium-ion batteries to
100%
367 all the time, but to stay below
90% of full charge most of the time.
368 I
've been told that the Tesla electric cars
369 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
370 the charge of their batteries to
80%
</a
>, with the option to charge to
371 100% when preparing for a longer trip (not that I would want a car
372 like Tesla where rights to privacy is abandoned, but that is another
373 story), which I guess is the option we should have for laptops on
376 <p
>Is there a good and generic way with Linux to tell the battery to
377 stop charging at
80%, unless requested to charge to
100% once in
378 preparation for a longer trip? I found
379 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
380 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
381 80%
</a
>, but could not get it to work (kernel module refused to
384 <p
>I wonder why the battery capacity was reported to be more than
100%
385 at the start. I also wonder why the
"full capacity
" increases some
386 times, and if it is possible to repeat the process to get the battery
387 back to design capacity. And I wonder if the discharge and charge
388 speed change over time, or if this stay the same. I did not yet try
389 to write a tool to calculate the derivative values of the battery
390 level, but suspect some interesting insights might be learned from
393 <p
>Update
2015-
09-
24: I got a tip to install the packages
394 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
395 packages instead of the tp-smapi-dkms package I had tried to use
396 initially, and use
'tlp setcharge
40 80' to change when charging start
397 and stop. I
've done so now, but expect my existing battery is toast
398 and need to be replaced. The proposal is unfortunately Thinkpad
404 <title>New laptop - some more clues and ideas based on feedback
</title>
405 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
406 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
407 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
408 <description><p
>Several people contacted me after my previous blog post about my
409 need for a new laptop, and provided very useful feedback. I wish to
410 thank every one of these. Several pointed me to the possibility of
411 fixing my X230, and I am already in the process of getting Lenovo to
412 do so thanks to the on site, next day support contract covering the
413 machine. But the battery is almost useless (I expect to replace it
414 with a non-official battery) and I do not expect the machine to live
415 for many more years, so it is time to plan its replacement. If I did
416 not have a support contract, it was suggested to find replacement parts
417 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
418 might present a language barrier as I do not understand French.
</p
>
420 <p
>One tip I got was to use the
421 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
422 compare laptop models. It seem to have more models available than
423 prisjakt.no. Another tip I got from someone I know have similar
424 keyboard preferences was that the HP EliteBook
840 keyboard is not
425 very good, and this matches my experience with earlier EliteBook
426 keyboards I tested. Because of this, I will not consider it any further.
428 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
429 newest Thinkpad X model. The keyboard reintroduces mouse buttons
430 (which is missing from the X240), and is working fairly well with
431 Debian Sid/Unstable according to
432 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
433 got on the keyboard quality are not consistent. Some say the keyboard
434 is good, others say it is ok, while others say it is not very good.
435 Those with experience from X41 and and X60 agree that the X250
436 keyboard is not as good as those trusty old laptops, and suggest I
437 keep and fix my X230 instead of upgrading, or get a used X230 to
438 replace it. I
'm also told that the X250 lack leds for caps lock, disk
439 activity and battery status, which is very convenient on my X230. I
'm
440 also told that the CPU fan is running very often, making it a bit
441 noisy. In any case, the X250 do not work out of the box with Debian
442 Stable/Jessie, one of my requirements.
</p
>
444 <p
>I have also gotten a few vendor proposals, one was
445 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
446 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
447 The latter look very attractive to me.
</p
>
449 <p
>Again, thank you all for the very useful feedback. It help a lot
450 as I keep looking for a replacement.
</p
>
452 <p
>Update
2015-
07-
06: I was recommended to check out the
453 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
455 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
456 thinkpad X models
</a
>, and provide one year warranty.
</p
>
461 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
462 <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>
463 <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>
464 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
465 <description><p
>My primary work horse laptop is failing, and will need a
466 replacement soon. The left
5 cm of the screen on my Thinkpad X230
467 started flickering yesterday, and I suspect the cause is a broken
468 cable, as changing the angle of the screen some times get rid of the
469 flickering.
</p
>
471 <p
>My requirements have not really changed since I bought it, and is
473 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
474 described them in
2013</a
>. The last time I bought a laptop, I had
476 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
477 where I could select at least a few of the requirements (mouse pin,
478 wifi, weight) and go through the rest manually. Three button mouse
479 and a good keyboard is not available as an option, and all the three
480 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
481 G2) lack three mouse buttons). It is also unclear to me how good the
482 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
483 the keyboard, even if the quality and robustness in the X series have
484 deteriorated since X41.
</p
>
486 <p
>I wonder how I can find a sensible laptop when none of the options
487 seem sensible to me? Are there better services around to search the
488 set of available laptops for features? Please send me an email if you
489 have suggestions.
</p
>
491 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
492 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
493 of endorsed hardware
</a
>, which is useful background information.
</p
>
498 <title>How to stay with sysvinit in Debian Jessie
</title>
499 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
501 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
502 <description><p
>By now, it is well known that Debian Jessie will not be using
503 sysvinit as its boot system by default. But how can one keep using
504 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
506 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
507 Schubert
</a
> and
508 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
511 <p
>If you already are using Wheezy and want to upgrade to Jessie and
512 keep sysvinit as your boot system, create a file
513 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
514 you upgrade:
</p
>
516 <p
><blockquote
><pre
>
517 Package: systemd-sysv
518 Pin: release o=Debian
520 </pre
></blockquote
><p
>
522 <p
>This file content will tell apt and aptitude to not consider
523 installing systemd-sysv as part of any installation and upgrade
524 solution when resolving dependencies, and thus tell it to avoid
525 systemd as a default boot system. The end result should be that the
526 upgraded system keep using sysvinit.
</p
>
528 <p
>If you are installing Jessie for the first time, there is no way to
529 get sysvinit installed by default (debootstrap used by
530 debian-installer have no option for this), but one can tell the
531 installer to switch to sysvinit before the first boot. Either by
532 using a kernel argument to the installer, or by adding a line to the
533 preseed file used. First, the kernel command line argument:
535 <p
><blockquote
><pre
>
536 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
537 </pre
></blockquote
><p
>
539 <p
>Next, the line to use in a preseed file:
</p
>
541 <p
><blockquote
><pre
>
542 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
543 </pre
></blockquote
><p
>
545 <p
>One can of course also do this after the first boot by installing
546 the sysvinit-core package.
</p
>
548 <p
>I recommend only using sysvinit if you really need it, as the
549 sysvinit boot sequence in Debian have several hardware specific bugs
550 on Linux caused by the fact that it is unpredictable when hardware
551 devices show up during boot. But on the other hand, the new default
552 boot system still have a few rough edges I hope will be fixed before
553 Jessie is released.
</p
>
555 <p
>Update
2014-
11-
26: Inspired by
556 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
557 blog post by Torsten Glaser
</a
>, added --purge to the preseed
563 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
564 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
565 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
566 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
567 <description><p
>The right to communicate with your friends and family in private,
568 without anyone snooping, is a right every citicen have in a liberal
569 democracy. But this right is under serious attack these days.
</p
>
571 <p
>A while back it occurred to me that one way to make the dragnet
572 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
573 the whisleblower Snowden) more expensive for Internet email,
574 is to deliver all email using SMTP via Tor. Such SMTP option would be
575 a nice addition to the FreedomBox project if we could send email
576 between FreedomBox machines without leaking metadata about the emails
577 to the people peeking on the wire. I
578 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
579 this on the FreedomBox project mailing list in October
</a
> and got a
580 lot of useful feedback and suggestions. It also became obvious to me
581 that this was not a novel idea, as the same idea was tested and
582 documented by Johannes Berg as early as
2006, and both
583 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
584 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
585 propose a similar method / protocol to pass emails between users.
</p
>
587 <p
>To implement such system one need to set up a Tor hidden service
588 providing the SMTP protocol on port
25, and use email addresses
589 looking like username@hidden-service-name.onion. With such addresses
590 the connections to port
25 on hidden-service-name.onion using Tor will
591 go to the correct SMTP server. To do this, one need to configure the
592 Tor daemon to provide the hidden service and the mail server to accept
593 emails for this .onion domain. To learn more about Exim configuration
594 in Debian and test the design provided by Johannes Berg in his FAQ, I
595 set out yesterday to create a Debian package for making it trivial to
596 set up such SMTP over Tor service based on Debian. Getting it to work
597 were fairly easy, and
598 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
599 source code for the Debian package
</a
> is available from github. I
600 plan to move it into Debian if further testing prove this to be a
601 useful approach.
</p
>
603 <p
>If you want to test this, set up a blank Debian machine without any
604 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
605 get rid of exim4). Install tor, clone the git repository mentioned
606 above, build the deb and install it on the machine. Next, run
607 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
608 the instructions to get the service up and running. Restart tor and
609 exim when it is done, and test mail delivery using swaks like
612 <p
><blockquote
><pre
>
613 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
614 --to fbx@dutlqrrmjhtfa3vp.onion
615 </pre
></blockquote
></p
>
617 <p
>This will test the SMTP delivery using tor. Replace the email
618 address with your own address to test your server. :)
</p
>
620 <p
>The setup procedure is still to complex, and I hope it can be made
621 easier and more automatic. Especially the tor setup need more work.
622 Also, the package include a tor-smtp tool written in C, but its task
623 should probably be rewritten in some script language to make the deb
624 architecture independent. It would probably also make the code easier
625 to review. The tor-smtp tool currently need to listen on a socket for
626 exim to talk to it and is started using xinetd. It would be better if
627 no daemon and no socket is needed. I suspect it is possible to get
628 exim to run a command line tool for delivery instead of talking to a
629 socket, and hope to figure out how in a future version of this
632 <p
>Until I wipe my test machine, I can be reached using the
633 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
639 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
640 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
642 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
643 <description><p
>If you ever had to moderate a mailman list, like the ones on
644 alioth.debian.org, you know the web interface is fairly slow to
645 operate. First you visit one web page, enter the moderation password
646 and get a new page shown with a list of all the messages to moderate
647 and various options for each email address. This take a while for
648 every list you moderate, and you need to do it regularly to do a good
649 job as a list moderator. But there is a quick alternative,
650 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
651 listadmin program
</a
>. It allow you to check lists for new messages
652 to moderate in a fraction of a second. Here is a test run on two
653 lists I recently took over:
</p
>
655 <p
><blockquote
><pre
>
656 % time listadmin xiph
657 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
658 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
664 </pre
></blockquote
></p
>
666 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
667 there are no message in the moderation queue. Every morning I
668 currently moderate
68 mailman lists, and it normally take around two
669 minutes. When I took over the two pkg-xiph lists above a few days
670 ago, there were
400 emails waiting in the moderator queue. It took me
671 less than
15 minutes to process them all using the listadmin
674 <p
>If you install
675 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
676 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
677 with content like this, the moderation task is a breeze:
</p
>
679 <p
><blockquote
><pre
>
680 username username@example.org
683 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
686 adminurl https://{domain}/mailman/admindb/{list}
687 mailman-list@lists.example.com
690 other-list@otherserver.example.org
691 </pre
></blockquote
></p
>
693 <p
>There are other options to set as well. Check the manual page to
694 learn the details.
</p
>
696 <p
>If you are forced to moderate lists on a mailman installation where
697 the SSL certificate is self signed or not properly signed by a
698 generally accepted signing authority, you can set a environment
699 variable when calling listadmin to disable SSL verification:
</p
>
701 <p
><blockquote
><pre
>
702 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
703 </pre
></blockquote
></p
>
705 <p
>If you want to moderate a subset of the lists you take care of, you
706 can provide an argument to the listadmin script like I do in the
707 initial screen dump (the xiph argument). Using an argument, only
708 lists matching the argument string will be processed. This make it
709 quick to accept messages if you notice the moderation request in your
712 <p
>Without the listadmin program, I would never be the moderator of
68
713 mailing lists, as I simply do not have time to spend on that if the
714 process was any slower. The listadmin program have saved me hours of
715 time I could spend elsewhere over the years. It truly is nice free
718 <p
>As usual, if you use Bitcoin and want to show your support of my
719 activities, please send Bitcoin donations to my address
720 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
722 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
723 configuration example. Also, I
've been told that the
724 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
730 <title>Debian Jessie, PXE and automatic firmware installation
</title>
731 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
733 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
734 <description><p
>When PXE installing laptops with Debian, I often run into the
735 problem that the WiFi card require some firmware to work properly.
736 And it has been a pain to fix this using preseeding in Debian.
737 Normally something more is needed. But thanks to
738 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
739 package
</a
> and its recent tasksel extension, it has now become easy
740 to do this using simple preseeding.
</p
>
742 <p
>The isenkram-cli package provide tasksel tasks which will install
743 firmware for the hardware found in the machine (actually, requested by
744 the kernel modules for the hardware). (It can also install user space
745 programs supporting the hardware detected, but that is not the focus
746 of this story.)
</p
>
748 <p
>To get this working in the default installation, two preeseding
749 values are needed. First, the isenkram-cli package must be installed
750 into the target chroot (aka the hard drive) before tasksel is executed
751 in the pkgsel step of the debian-installer system. This is done by
752 preseeding the base-installer/includes debconf value to include the
753 isenkram-cli package. The package name is next passed to debootstrap
754 for installation. With the isenkram-cli package in place, tasksel
755 will automatically use the isenkram tasks to detect hardware specific
756 packages for the machine being installed and install them, because
757 isenkram-cli contain tasksel tasks.
</p
>
759 <p
>Second, one need to enable the non-free APT repository, because
760 most firmware unfortunately is non-free. This is done by preseeding
761 the apt-mirror-setup step. This is unfortunate, but for a lot of
762 hardware it is the only option in Debian.
</p
>
764 <p
>The end result is two lines needed in your preseeding file to get
765 firmware installed automatically by the installer:
</p
>
767 <p
><blockquote
><pre
>
768 base-installer base-installer/includes string isenkram-cli
769 apt-mirror-setup apt-setup/non-free boolean true
770 </pre
></blockquote
></p
>
772 <p
>The current version of isenkram-cli in testing/jessie will install
773 both firmware and user space packages when using this method. It also
774 do not work well, so use version
0.15 or later. Installing both
775 firmware and user space packages might give you a bit more than you
776 want, so I decided to split the tasksel task in two, one for firmware
777 and one for user space programs. The firmware task is enabled by
778 default, while the one for user space programs is not. This split is
779 implemented in the package currently in unstable.
</p
>
781 <p
>If you decide to give this a go, please let me know (via email) how
782 this recipe work for you. :)
</p
>
784 <p
>So, I bet you are wondering, how can this work. First and
785 foremost, it work because tasksel is modular, and driven by whatever
786 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
787 isenkram-cli package place two files for tasksel to find. First there
788 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
790 <p
><blockquote
><pre
>
791 Task: isenkram-packages
793 Description: Hardware specific packages (autodetected by isenkram)
794 Based on the detected hardware various hardware specific packages are
796 Test-new-install: show show
798 Packages: for-current-hardware
800 Task: isenkram-firmware
802 Description: Hardware specific firmware packages (autodetected by isenkram)
803 Based on the detected hardware various hardware specific firmware
804 packages are proposed.
805 Test-new-install: mark show
807 Packages: for-current-hardware-firmware
808 </pre
></blockquote
></p
>
810 <p
>The key parts are Test-new-install which indicate how the task
811 should be handled and the Packages line referencing to a script in
812 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
813 list of packages to install. The for-current-hardware-firmware script
814 look like this to list relevant firmware for the machine:
816 <p
><blockquote
><pre
>
821 isenkram-autoinstall-firmware -l
822 </pre
></blockquote
></p
>
824 <p
>With those two pieces in place, the firmware is installed by
825 tasksel during the normal d-i run. :)
</p
>
827 <p
>If you want to test what tasksel will install when isenkram-cli is
828 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
829 --new-install
</tt
> to get the list of packages that tasksel would
832 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
833 pilots in testing this feature, as isenkram is used there now to
834 install firmware, replacing the earlier scripts.
</p
>
839 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
840 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
841 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
842 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
843 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
844 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
845 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
846 on a screen normally showing the bread types and prizes:
</p
>
848 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
850 <p
>If it had booted as it was supposed to, I would never had known
851 about this hidden Linux installation. It is interesting what
852 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
857 <title>New lsdvd release version
0.17 is ready
</title>
858 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
860 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
861 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
862 got a new set of developers a few weeks ago, after the original
863 developer decided to step down and pass the project to fresh blood.
864 This project is now maintained by Petter Reinholdtsen and Steve
867 <p
>I just wrapped up
868 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
869 new lsdvd release
</a
>, available in git or from
870 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
871 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
876 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
877 <li
>Check for garbage in the program chains, which indicate that a track is
878 non-existant, to work around additional copy protection
</li
>
879 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
880 <li
>Fix pallete display of first entry
</li
>
881 <li
>Fix include orders
</li
>
882 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
883 <li
>Fix the chapter count
</li
>
884 <li
>Make sure the array size and the array limit used when initialising
885 the palette size is the same.
</li
>
886 <li
>Fix array printing.
</li
>
887 <li
>Correct subsecond calculations.
</li
>
888 <li
>Add sector information to the output format.
</li
>
889 <li
>Clean up code to be closer to ANSI C and compile without warnings
890 with more GCC compiler warnings.
</li
>
894 <p
>This change bring together patches for lsdvd in use in various
895 Linux and Unix distributions, as well as patches submitted to the
896 project the last nine years. Please check it out. :)
</p
>
901 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
902 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
904 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
905 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
906 project
</a
> provide a Linux solution for schools, including a
907 powerful desktop with education software, a central server providing
908 web pages, user database, user home directories, central login and PXE
909 boot of both clients without disk and the installation to install Debian
910 Edu on machines with disk (and a few other services perhaps to small
911 to mention here). We in the Debian Edu team are currently working on
912 the Jessie based version, trying to get everything in shape before the
913 freeze, to avoid having to maintain our own package repository in the
915 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
916 status
</a
> can be seen on the Debian wiki, and there is still heaps of
917 work left. Some fatal problems block testing, breaking the installer,
918 but it is possible to work around these to get anyway. Here is a
919 recipe on how to get the installation limping along.
</p
>
921 <p
>First, download the test ISO via
922 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
923 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
925 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
926 The ISO build was broken on Tuesday, so we do not get a new ISO every
927 12 hours or so, but thankfully the ISO we already got we are able to
928 install with some tweaking.
</p
>
930 <p
>When you get to the Debian Edu profile question, go to tty2
931 (use Alt-Ctrl-F2), run
</p
>
933 <p
><blockquote
><pre
>
934 nano /usr/bin/edu-eatmydata-install
935 </pre
></blockquote
></p
>
937 <p
>and add
'exit
0' as the second line, disabling the eatmydata
938 optimization. Return to the installation, select the profile you want
939 and continue. Without this change, exim4-config will fail to install
940 due to a known bug in eatmydata.
</p
>
942 <p
>When you get the grub question at the end, answer /dev/sda (or if
943 this do not work, figure out what your correct value would be. All my
944 test machines need /dev/sda, so I have no advice if it do not fit
947 <p
>If you installed a profile including a graphical desktop, log in as
948 root after the initial boot from hard drive, and install the
949 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
950 or mate. If you want several desktop options, install more than one
951 metapackage. Once this is done, reboot and you should have a working
952 graphical login screen. This workaround should no longer be needed
953 once the education-tasks package version
1.801 enter testing in two
956 <p
>I believe the ISO build will start working on two days when the new
957 tasksel package enter testing and Steve McIntyre get a chance to
958 update the debian-cd git repository. The eatmydata, grub and desktop
959 issues are already fixed in unstable and testing, and should show up
960 on the ISO as soon as the ISO build start working again. Well the
961 eatmydata optimization is really just disabled. The proper fix
962 require an upload by the eatmydata maintainer applying the patch
963 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
964 The rest have proper fixes in unstable.
</p
>
966 <p
>I hope this get you going with the installation testing, as we are
967 quickly running out of time trying to get our Jessie based
968 installation ready before the distribution freeze in a month.
</p
>
973 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
974 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
975 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
976 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
977 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
978 to handle my fairly large DVD collection. It is a nice command line
979 tool to get details about a DVD, like title, tracks, track length,
980 etc, in XML, Perl or human readable format. But lsdvd have not seen
981 any new development since
2006 and had a few irritating bugs affecting
982 its use with some DVDs. Upstream seemed to be dead, and in January I
983 sent a small probe asking for a version control repository for the
984 project, without any reply. But I use it regularly and would like to
985 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
986 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
987 the project admin, and after getting a reply from him explaining that
988 he was no longer interested in the project, I asked if I could take
989 over. And yesterday, I became project admin.
</p
>
991 <p
>I
've been in touch with a Gentoo developer and the Debian
992 maintainer interested in joining forces to maintain the upstream
993 project, and I hope we can get a new release out fairly quickly,
994 collecting the patches spread around on the internet into on place.
995 I
've added the relevant Debian patches to the freshly created git
996 repository, and expect the Gentoo patches to make it too. If you got
997 a DVD collection and care about command line tools, check out
998 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
999 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1000 list
</a
>. :)
</p
>
1005 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1006 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1008 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1009 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1010 a lot quicker. When we install more than
2000 packages in
1011 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1012 tasksel in the installer, unpacking the binary packages take forever.
1013 A part of the slow I/O issue was discussed in
1014 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1015 much file system sync-ing done by dpkg, which is the package
1016 responsible for unpacking the binary packages. Other parts (like code
1017 executed by postinst scripts) might also sync to disk during
1018 installation. All this sync-ing to disk do not really make sense to
1019 me. If the machine crash half-way through, I start over, I do not try
1020 to salvage the half installed system. So the failure sync-ing is
1021 supposed to protect against, hardware or system crash, is not really
1022 relevant while the installer is running.
</p
>
1024 <p
>A few days ago, I thought of a way to get rid of all the file
1025 system sync()-ing in a fairly non-intrusive way, without the need to
1026 change the code in several packages. The idea is not new, but I have
1027 not heard anyone propose the approach using dpkg-divert before. It
1028 depend on the small and clever package
1029 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1030 uses LD_PRELOAD to replace the system functions for syncing data to
1031 disk with functions doing nothing, thus allowing programs to live
1032 dangerous while speeding up disk I/O significantly. Instead of
1033 modifying the implementation of dpkg, apt and tasksel (which are the
1034 packages responsible for selecting, fetching and installing packages),
1035 it occurred to me that we could just divert the programs away, replace
1036 them with a simple shell wrapper calling
1037 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1038 Two days ago I decided to test the idea, and wrapped up a simple
1039 implementation for the Debian Edu udeb.
</p
>
1041 <p
>The effect was stunning. In my first test it reduced the running
1042 time of the pkgsel step (installing tasks) from
64 to less than
44
1043 minutes (
20 minutes shaved off the installation) on an old Dell
1044 Latitude D505 machine. I am not quite sure what the optimised time
1045 would have been, as I messed up the testing a bit, causing the debconf
1046 priority to get low enough for two questions to pop up during
1047 installation. As soon as I saw the questions I moved the installation
1048 along, but do not know how long the question were holding up the
1049 installation. I did some more measurements using Debian Edu Jessie,
1050 and got these results. The time measured is the time stamp in
1051 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1052 "pkgsel: finishing up
" lines, if you want to do the same measurement
1053 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1054 timing thus do not depend on how quickly the user handle the tasksel
1057 <p
><table
>
1060 <th
>Machine/setup
</th
>
1061 <th
>Original tasksel
</th
>
1062 <th
>Optimised tasksel
</th
>
1063 <th
>Reduction
</th
>
1067 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1068 <td
>64 min (
07:
46-
08:
50)
</td
>
1069 <td
><44 min (
11:
27-
12:
11)
</td
>
1070 <td
>>20 min
18%
</td
>
1074 <td
>Latitude D505 Roaming LXDE
</td
>
1075 <td
>57 min (
08:
48-
09:
45)
</td
>
1076 <td
>34 min (
07:
43-
08:
17)
</td
>
1077 <td
>23 min
40%
</td
>
1081 <td
>Latitude D505 Minimal
</td
>
1082 <td
>22 min (
10:
37-
10:
59)
</td
>
1083 <td
>11 min (
11:
16-
11:
27)
</td
>
1084 <td
>11 min
50%
</td
>
1088 <td
>Thinkpad X200 Minimal
</td
>
1089 <td
>6 min (
08:
19-
08:
25)
</td
>
1090 <td
>4 min (
08:
04-
08:
08)
</td
>
1091 <td
>2 min
33%
</td
>
1095 <td
>Thinkpad X200 Roaming KDE
</td
>
1096 <td
>19 min (
09:
21-
09:
40)
</td
>
1097 <td
>15 min (
10:
25-
10:
40)
</td
>
1098 <td
>4 min
21%
</td
>
1101 </table
></p
>
1103 <p
>The test is done using a netinst ISO on a USB stick, so some of the
1104 time is spent downloading packages. The connection to the Internet
1105 was
100Mbit/s during testing, so downloading should not be a
1106 significant factor in the measurement. Download typically took a few
1107 seconds to a few minutes, depending on the amount of packages being
1108 installed.
</p
>
1110 <p
>The speedup is implemented by using two hooks in
1111 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
1112 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
1113 finish-install.d hook to remove the divert at the end of the
1114 installation. I picked the pre-pkgsel.d hook instead of the
1115 post-base-installer.d hook because I test using an ISO without the
1116 eatmydata package included, and the post-base-installer.d hook in
1117 Debian Edu can only operate on packages included in the ISO. The
1118 negative effect of this is that I am unable to activate this
1119 optimization for the kernel installation step in d-i. If the code is
1120 moved to the post-base-installer.d hook, the speedup would be larger
1121 for the entire installation.
</p
>
1123 <p
>I
've implemented this in the
1124 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
1125 git repository, and plan to provide the optimization as part of the
1126 Debian Edu installation. If you want to test this yourself, you can
1127 create two files in the installer (or in an udeb). One shell script
1128 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
1130 <p
><blockquote
><pre
>
1133 . /usr/share/debconf/confmodule
1135 logger -t my-pkgsel
"info: $*
"
1138 logger -t my-pkgsel
"error: $*
"
1140 override_install() {
1141 apt-install eatmydata || true
1142 if [ -x /target/usr/bin/eatmydata ] ; then
1143 for bin in dpkg apt-get aptitude tasksel ; do
1145 # Test that the file exist and have not been diverted already.
1146 if [ -f /target$file ] ; then
1147 info
"diverting $file using eatmydata
"
1148 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
1149 > /target$file.edu
1150 chmod
755 /target$file.edu
1151 in-target dpkg-divert --package debian-edu-config \
1152 --rename --quiet --add $file
1153 ln -sf ./$bin.edu /target$file
1155 error
"unable to divert $file, as it is missing.
"
1159 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
1164 </pre
></blockquote
></p
>
1166 <p
>To clean up, another shell script should go into
1167 /usr/lib/finish-install.d/ with code like this:
1169 <p
><blockquote
><pre
>
1171 . /usr/share/debconf/confmodule
1173 logger -t my-finish-install
"error: $@
"
1175 remove_install_override() {
1176 for bin in dpkg apt-get aptitude tasksel ; do
1178 if [ -x /target$file.edu ] ; then
1180 in-target dpkg-divert --package debian-edu-config \
1181 --rename --quiet --remove $file
1184 error
"Missing divert for $file.
"
1187 sync # Flush file buffers before continuing
1190 remove_install_override
1191 </pre
></blockquote
></p
>
1193 <p
>In Debian Edu, I placed both code fragments in a separate script
1194 edu-eatmydata-install and call it from the pre-pkgsel.d and
1195 finish-install.d scripts.
</p
>
1197 <p
>By now you might ask if this change should get into the normal
1198 Debian installer too? I suspect it should, but am not sure the
1199 current debian-installer coordinators find it useful enough. It also
1200 depend on the side effects of the change. I
'm not aware of any, but I
1201 guess we will see if the change is safe after some more testing.
1202 Perhaps there is some package in Debian depending on sync() and
1203 fsync() having effect? Perhaps it should go into its own udeb, to
1204 allow those of us wanting to enable it to do so without affecting
1207 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
1208 will break installation of all programs using gnutls because of
1209 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
1210 eatmydata package in Debian will solve it.
</p
>
1212 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
1213 the optimization work again. And I have discovered that the
1214 dpkg-divert trick is not really needed and implemented a slightly
1215 simpler approach as part of the debian-edu-install package. See
1216 tools/edu-eatmydata-install in the source package.
</p
>
1218 <p
>Update
2014-
11-
11: Unfortunately, a new
1219 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
1220 triggering on i386 made it into testing, and broke this installation
1221 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
1222 request
768893</a
> is accepted, it should be working again.
</p
>
1227 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
1228 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
1229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
1230 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
1231 <description><p
>Yesterday, I had the pleasure of attending a talk with the
1232 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
1233 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
1234 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
1235 learn that there is a large set of publicly available key servers to
1236 use when looking for peoples public key. So far I have used
1237 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1238 were misbehaving, but those days are ended. The servers I have used
1239 up until yesterday have been slow and some times unavailable. I hope
1240 those problems are gone now.
</p
>
1242 <p
>Behind the round robin DNS entry of the
1243 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
1244 there is a pool of more than
100 keyservers which are checked every
1245 day to ensure they are well connected and up to date. It must be
1246 better than what I have used so far. :)
</p
>
1248 <p
>Yesterdays speaker told me that the service is the default
1249 keyserver provided by the default configuration in GnuPG, but this do
1250 not seem to be used in Debian. Perhaps it should?
</p
>
1252 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
1255 <p
><blockquote
><pre
>
1256 keyserver pool.sks-keyservers.net
1257 </pre
></blockquote
></p
>
1259 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
1260 entries in DNS. Just for fun, I did just that at work, so now every
1261 user of GnuPG at the University of Oslo should find a OpenGPG
1262 keyserver automatically should their need it:
</p
>
1264 <p
><blockquote
><pre
>
1265 % host -t srv _pgpkey-http._tcp.uio.no
1266 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
1268 </pre
></blockquote
></p
>
1270 <p
>Now if only
1271 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
1272 HKP lookup protocol
</a
> supported finding signature paths, I would be
1273 very happy. It can look up a given key or search for a user ID, but I
1274 normally do not want that, but to find a trust path from my key to
1275 another key. Given a user ID or key ID, I would like to find (and
1276 download) the keys representing a signature path from my key to the
1277 key in question, to be able to get a trust path between the two keys.
1278 This is as far as I can tell not possible today. Perhaps something
1279 for a future version of the protocol?
</p
>
1284 <title>From English wiki to translated PDF and epub via Docbook
</title>
1285 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
1286 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
1287 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
1288 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1289 project
</a
> provide an instruction manual for teachers, system
1290 administrators and other users that contain useful tips for setting up
1291 and maintaining a Debian Edu installation. This text is about how the
1292 text processing of this manual is handled in the project.
</p
>
1294 <p
>One goal of the project is to provide information in the native
1295 language of its users, and for this we need to handle translations.
1296 But we also want to make sure each language contain the same
1297 information, so for this we need a good way to keep the translations
1298 in sync. And we want it to be easy for our users to improve the
1299 documentation, avoiding the need to learn special formats or tools to
1300 contribute, and the obvious way to do this is to make it possible to
1301 edit the documentation using a web browser. We also want it to be
1302 easy for translators to keep the translation up to date, and give them
1303 help in figuring out what need to be translated. Here is the list of
1304 tools and the process we have found trying to reach all these
1307 <p
>We maintain the authoritative source of our manual in the
1308 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
1309 wiki
</a
>, as several wiki pages written in English. It consist of one
1310 front page with references to the different chapters, several pages
1311 for each chapter, and finally one
"collection page
" gluing all the
1312 chapters together into one large web page (aka
1313 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
1314 AllInOne page
</a
>). The AllInOne page is the one used for further
1315 processing and translations. Thanks to the fact that the
1316 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
1317 wiki.debian.org support exporting pages in
1318 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
1319 the list of pages to export using the raw version of the AllInOne
1320 page, loop over each of them to generate a Docbook XML version of the
1321 manual. This process also download images and transform image
1322 references to use the locally downloaded images. The generated
1323 Docbook XML files are slightly broken, so some post-processing is done
1324 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
1325 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1326 a handfull of images. The XML file can now be used to generate PDF, HTML
1327 and epub versions of the English manual. This is the basic step of
1328 our process, making PDF (using dblatex), HTML (using xsltproc) and
1329 epub (using dbtoepub) version from Docbook XML, and the resulting files
1330 are placed in the debian-edu-doc-en binary package.
</p
>
1332 <p
>But English documentation is not enough for us. We want translated
1333 documentation too, and we want to make it easy for translators to
1334 track the English original. For this we use the
1335 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
1336 which allow us to transform the English Docbook XML file into a
1337 translation file (a .pot file), usable with the normal gettext based
1338 translation tools used by those translating free software. The pot
1339 file is used to create and maintain translation files (several .po
1340 files), which the translations update with the native language
1341 translations of all titles, paragraphs and blocks of text in the
1342 original. The next step is combining the original English Docbook XML
1343 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1344 create a translated Docbook XML file (in this case
1345 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1346 translated, if the translation is not complete) Docbook XML file can
1347 then be used like the original to create a PDF, HTML and epub version
1348 of the documentation.
</p
>
1350 <p
>The translators use different tools to edit the .po files. We
1352 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
1353 while some use emacs and vi, others can use web based editors like
1354 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
1355 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
1356 is where the .po file end up, in our git repository. Updated
1357 translations can either be committed directly to git, or submitted as
1358 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
1359 against the debian-edu-doc package
</a
>.
</p
>
1361 <p
>One challenge is images, which both might need to be translated (if
1362 they show translated user applications), and are needed in different
1363 formats when creating PDF and HTML versions (epub is a HTML version in
1364 this regard). For this we transform the original PNG images to the
1365 needed density and format during build, and have a way to provide
1366 translated images by storing translated versions in
1367 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1368 package maintainers know more.
</p
>
1370 <p
>If you wonder what the result look like, we provide
1371 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
1372 of the documentation packages on the web
</a
>. See for example the
1373 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
1374 PDF version
</a
> or the
1375 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
1376 HTML version
</a
>. We do not yet build the epub version by default,
1377 but perhaps it will be done in the future.
</p
>
1379 <p
>To learn more, check out
1380 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
1381 debian-edu-doc package
</a
>,
1382 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
1383 manual on the wiki
</a
> and
1384 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
1385 translation instructions
</a
> in the manual.
</p
>
1390 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
1391 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
1392 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
1393 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
1394 <description><p
>It would be nice if it was easier in Debian to get all the hardware
1395 related packages relevant for the computer installed automatically.
1396 So I implemented one, using
1397 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
1398 package
</a
>. To use it, install the tasksel and isenkram packages and
1399 run tasksel as user root. You should be presented with a new option,
1400 "Hardware specific packages (autodetected by isenkram)
". When you
1401 select it, tasksel will install the packages isenkram claim is fit for
1402 the current hardware, hot pluggable or not.
<p
>
1404 <p
>The implementation is in two files, one is the tasksel menu entry
1405 description, and the other is the script used to extract the list of
1406 packages to install. The first part is in
1407 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
1410 <p
><blockquote
><pre
>
1413 Description: Hardware specific packages (autodetected by isenkram)
1414 Based on the detected hardware various hardware specific packages are
1416 Test-new-install: mark show
1418 Packages: for-current-hardware
1419 </pre
></blockquote
></p
>
1421 <p
>The second part is in
1422 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
1425 <p
><blockquote
><pre
>
1430 isenkram-autoinstall-firmware -l
1432 </pre
></blockquote
></p
>
1434 <p
>All in all, a very short and simple implementation making it
1435 trivial to install the hardware dependent package we all may want to
1436 have installed on our machines. I
've not been able to find a way to
1437 get tasksel to tell you exactly which packages it plan to install
1438 before doing the installation. So if you are curious or careful,
1439 check the output from the isenkram-* command line tools first.
</p
>
1441 <p
>The information about which packages are handling which hardware is
1442 fetched either from the isenkram package itself in
1443 /usr/share/isenkram/, from git.debian.org or from the APT package
1444 database (using the Modaliases header). The APT package database
1445 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1446 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
1447 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
1448 the python-apt code (bug
1449 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
1450 workaround I was able to get rid of the file descriptor leak and
1451 reduce the memory leak from ~
30 MiB per hardware detection down to
1452 around
2 MiB per hardware detection. It should make the desktop
1453 daemon a lot more useful. The fix is in version
0.7 uploaded to
1454 unstable today.
</p
>
1456 <p
>I believe the current way of mapping hardware to packages in
1457 Isenkram is is a good draft, but in the future I expect isenkram to
1458 use the AppStream data source for this. A proposal for getting proper
1459 AppStream support into Debian is floating around as
1460 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
1461 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
1462 project
</a
> will take place this summer to improve the situation. I
1463 look forward to seeing the result, and welcome patches for isenkram to
1464 start using the information when it is ready.
</p
>
1466 <p
>If you want your package to map to some specific hardware, either
1467 add a
"Xb-Modaliases
" header to your control file like I did in
1468 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
1469 package
</a
> or submit a bug report with the details to the isenkram
1471 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
1472 blog posts tagged isenkram
</a
> for details on the notation. I expect
1473 the information will be migrated to AppStream eventually, but for the
1474 moment I got no better place to store it.
</p
>
1479 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
1480 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
1481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
1482 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
1483 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1484 project
</a
> is working on providing the software and hardware to make
1485 it easy for non-technical people to host their data and communication
1486 at home, and being able to communicate with their friends and family
1487 encrypted and away from prying eyes. It is still going strong, and
1488 today a major mile stone was reached.
</p
>
1490 <p
>Today, the last of the packages currently used by the project to
1491 created the system images were accepted into Debian Unstable. It was
1492 the freedombox-setup package, which is used to configure the images
1493 during build and on the first boot. Now all one need to get going is
1494 the build code from the freedom-maker git repository and packages from
1495 Debian. And once the freedombox-setup package enter testing, we can
1496 build everything directly from Debian. :)
</p
>
1498 <p
>Some key packages used by Freedombox are
1499 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
1500 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
1501 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
1502 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
1503 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
1504 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
1505 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
1506 are plans to integrate more packages into the setup. User
1507 documentation is maintained on the Debian wiki. Please
1508 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
1509 the manual
</a
> and help us improve it.
</p
>
1511 <p
>To test for yourself and create boot images with the FreedomBox
1512 setup, run this on a Debian machine using a user with sudo rights to
1513 become root:
</p
>
1515 <p
><pre
>
1516 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1517 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1519 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1521 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1522 </pre
></p
>
1524 <p
>Root access is needed to run debootstrap and mount loopback
1525 devices. See the README in the freedom-maker git repo for more
1526 details on the build. If you do not want all three images, trim the
1527 make line. Note that the virtualbox-image target is not really
1528 virtualbox specific. It create a x86 image usable in kvm, qemu,
1529 vmware and any other x86 virtual machine environment. You might need
1530 the version of vmdebootstrap in Jessie to get the build working, as it
1531 include fixes for a race condition with kpartx.
</p
>
1533 <p
>If you instead want to install using a Debian CD and the preseed
1534 method, boot a Debian Wheezy ISO and use this boot argument to load
1535 the preseed values:
</p
>
1537 <p
><pre
>
1538 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1539 </pre
></p
>
1541 <p
>I have not tested it myself the last few weeks, so I do not know if
1542 it still work.
</p
>
1544 <p
>If you wonder how to help, one task you could look at is using
1545 systemd as the boot system. It will become the default for Linux in
1546 Jessie, so we need to make sure it is usable on the Freedombox. I did
1547 a simple test a few weeks ago, and noticed dnsmasq failed to start
1548 during boot when using systemd. I suspect there are other problems
1549 too. :) To detect problems, there is a test suite included, which can
1550 be run from the plinth web interface.
</p
>
1552 <p
>Give it a go and let us know how it goes on the mailing list, and help
1553 us get the new release published. :) Please join us on
1554 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1555 irc.debian.org)
</a
> and
1556 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1557 mailing list
</a
> if you want to help make this vision come true.
</p
>
1562 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
1563 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
1564 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
1565 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
1566 <description><p
>For a while now, I have been looking for a sensible offsite backup
1567 solution for use at home. My requirements are simple, it must be
1568 cheap and locally encrypted (in other words, I keep the encryption
1569 keys, the storage provider do not have access to my private files).
1570 One idea me and my friends had many years ago, before the cloud
1571 storage providers showed up, was to use Google mail as storage,
1572 writing a Linux block device storing blocks as emails in the mail
1573 service provided by Google, and thus get heaps of free space. On top
1574 of this one can add encryption, RAID and volume management to have
1575 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1576 I never found time to implement such system. But the last few weeks I
1577 have looked at a system called
1578 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
1579 mounted network backed file system with the features I need.
</p
>
1581 <p
>S3QL is a fuse file system with a local cache and cloud storage,
1582 handling several different storage providers, any with Amazon S3,
1583 Google Drive or OpenStack API. There are heaps of such storage
1584 providers. S3QL can also use a local directory as storage, which
1585 combined with sshfs allow for file storage on any ssh server. S3QL
1586 include support for encryption, compression, de-duplication, snapshots
1587 and immutable file systems, allowing me to mount the remote storage as
1588 a local mount point, look at and use the files as if they were local,
1589 while the content is stored in the cloud as well. This allow me to
1590 have a backup that should survive fire. The file system can not be
1591 shared between several machines at the same time, as only one can
1592 mount it at the time, but any machine with the encryption key and
1593 access to the storage service can mount it if it is unmounted.
</p
>
1595 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
1596 package is included already. So to get started, run
<tt
>apt-get
1597 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
1598 Greenqloud, after reading their nice recipe on
1599 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
1600 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
1601 in Iceland more than those in USA when it come to keeping my personal
1602 data safe and private, and thus would rather spend money on a company
1603 in Iceland. Another nice recipe is available from the article
1604 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
1605 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
1606 Admin magazine. When the provider is picked, figure out how to get
1607 the API key needed to connect to the storage API. With Greencloud,
1608 the key did not show up until I had added payment details to my
1611 <p
>Armed with the API access details, it is time to create the file
1612 system. First, create a new bucket in the cloud. This bucket is the
1613 file system storage area. I picked a bucket name reflecting the
1614 machine that was going to store data there, but any name will do.
1615 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
1616 the API login and password, and a locally created password. Store it
1617 all in ~root/.s3ql/authinfo2 like this:
1619 <p
><blockquote
><pre
>
1621 storage-url: s3c://s.greenqloud.com:
443/bucket-name
1622 backend-login: API-login
1623 backend-password: API-password
1624 fs-passphrase: local-password
1625 </pre
></blockquote
></p
>
1627 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
1628 but any sensible way to create a fairly random password should do it.
1629 Armed with these details, it is now time to run mkfs, entering the API
1630 details and password to create it:
</p
>
1632 <p
><blockquote
><pre
>
1633 # mkdir -m
700 /var/lib/s3ql-cache
1634 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1635 --ssl s3c://s.greenqloud.com:
443/bucket-name
1636 Enter backend login:
1637 Enter backend password:
1638 Before using S3QL, make sure to read the user
's guide, especially
1639 the
'Important Rules to Avoid Loosing Data
' section.
1640 Enter encryption password:
1641 Confirm encryption password:
1642 Generating random encryption key...
1643 Creating metadata tables...
1653 Compressing and uploading metadata...
1654 Wrote
0.00 MB of compressed metadata.
1655 #
</pre
></blockquote
></p
>
1657 <p
>The next step is mounting the file system to make the storage available.
1659 <p
><blockquote
><pre
>
1660 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1661 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1662 Using
4 upload threads.
1663 Downloading and decompressing metadata...
1673 Mounting filesystem...
1675 Filesystem Size Used Avail Use% Mounted on
1676 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
1678 </pre
></blockquote
></p
>
1680 <p
>The file system is now ready for use. I use rsync to store my
1681 backups in it, and as the metadata used by rsync is downloaded at
1682 mount time, no network traffic (and storage cost) is triggered by
1683 running rsync. To unmount, one should not use the normal umount
1684 command, as this will not flush the cache to the cloud storage, but
1685 instead running the umount.s3ql command like this:
1687 <p
><blockquote
><pre
>
1690 </pre
></blockquote
></p
>
1692 <p
>There is a fsck command available to check the file system and
1693 correct any problems detected. This can be used if the local server
1694 crashes while the file system is mounted, to reset the
"already
1695 mounted
" flag. This is what it look like when processing a working
1696 file system:
</p
>
1698 <p
><blockquote
><pre
>
1699 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
1700 Using cached metadata.
1701 File system seems clean, checking anyway.
1702 Checking DB integrity...
1703 Creating temporary extra indices...
1704 Checking lost+found...
1705 Checking cached objects...
1706 Checking names (refcounts)...
1707 Checking contents (names)...
1708 Checking contents (inodes)...
1709 Checking contents (parent inodes)...
1710 Checking objects (reference counts)...
1711 Checking objects (backend)...
1712 ..processed
5000 objects so far..
1713 ..processed
10000 objects so far..
1714 ..processed
15000 objects so far..
1715 Checking objects (sizes)...
1716 Checking blocks (referenced objects)...
1717 Checking blocks (refcounts)...
1718 Checking inode-block mapping (blocks)...
1719 Checking inode-block mapping (inodes)...
1720 Checking inodes (refcounts)...
1721 Checking inodes (sizes)...
1722 Checking extended attributes (names)...
1723 Checking extended attributes (inodes)...
1724 Checking symlinks (inodes)...
1725 Checking directory reachability...
1726 Checking unix conventions...
1727 Checking referential integrity...
1728 Dropping temporary indices...
1729 Backing up old metadata...
1739 Compressing and uploading metadata...
1740 Wrote
0.89 MB of compressed metadata.
1742 </pre
></blockquote
></p
>
1744 <p
>Thanks to the cache, working on files that fit in the cache is very
1745 quick, about the same speed as local file access. Uploading large
1746 amount of data is to me limited by the bandwidth out of and into my
1747 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
1748 which is very close to my upload speed, and downloading the same
1749 Debian installation ISO gave me
610 kiB/s, close to my download speed.
1750 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
1751 network, not the file system code. I do not know what a good cache
1752 size would be, but suspect that the cache should e larger than your
1753 working set.
</p
>
1755 <p
>I mentioned that only one machine can mount the file system at the
1756 time. If another machine try, it is told that the file system is
1759 <p
><blockquote
><pre
>
1760 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1761 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1762 Using
8 upload threads.
1763 Backend reports that fs is still mounted elsewhere, aborting.
1765 </pre
></blockquote
></p
>
1767 <p
>The file content is uploaded when the cache is full, while the
1768 metadata is uploaded once every
24 hour by default. To ensure the
1769 file system content is flushed to the cloud, one can either umount the
1770 file system, or ask S3QL to flush the cache and metadata using
1773 <p
><blockquote
><pre
>
1774 # s3qlctrl upload-meta /s3ql
1775 # s3qlctrl flushcache /s3ql
1777 </pre
></blockquote
></p
>
1779 <p
>If you are curious about how much space your data uses in the
1780 cloud, and how much compression and deduplication cut down on the
1781 storage usage, you can use s3qlstat on the mounted file system to get
1784 <p
><blockquote
><pre
>
1786 Directory entries:
9141
1789 Total data size:
22049.38 MB
1790 After de-duplication:
21955.46 MB (
99.57% of total)
1791 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
1792 Database size:
2.39 MB (uncompressed)
1793 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1795 </pre
></blockquote
></p
>
1797 <p
>I mentioned earlier that there are several possible suppliers of
1798 storage. I did not try to locate them all, but am aware of at least
1799 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
1800 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
1801 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
1802 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
1803 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
1804 accept payment in Bitcoin. Pick one that suit your need. Some of
1805 them provide several GiB of free storage, but the prize models are
1806 quite different and you will have to figure out what suits you
1809 <p
>While researching this blog post, I had a look at research papers
1810 and posters discussing the S3QL file system. There are several, which
1811 told me that the file system is getting a critical check by the
1812 science community and increased my confidence in using it. One nice
1814 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
1815 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1816 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
1817 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1818 and Pamela Smith. Please have a look.
</p
>
1820 <p
>Given my problems with different file systems earlier, I decided to
1821 check out the mounted S3QL file system to see if it would be usable as
1822 a home directory (in other word, that it provided POSIX semantics when
1823 it come to locking and umask handling etc). Running
1824 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
1825 test code to check file system semantics
</a
>, I was happy to discover that
1826 no error was found. So the file system can be used for home
1827 directories, if one chooses to do so.
</p
>
1829 <p
>If you do not want a locally file system, and want something that
1830 work without the Linux fuse file system, I would like to mention the
1831 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
1832 provide locally encrypted backup using a command line client. It have
1833 a nicer access control system, where one can split out read and write
1834 access, allowing some systems to write to the backup and others to
1835 only read from it.
</p
>
1837 <p
>As usual, if you use Bitcoin and want to show your support of my
1838 activities, please send Bitcoin donations to my address
1839 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1844 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
1845 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
1846 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
1847 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
1848 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1849 project
</a
> is working on providing the software and hardware for
1850 making it easy for non-technical people to host their data and
1851 communication at home, and being able to communicate with their
1852 friends and family encrypted and away from prying eyes. It has been
1853 going on for a while, and is slowly progressing towards a new test
1854 release (
0.2).
</p
>
1856 <p
>And what day could be better than the Pi day to announce that the
1857 new version will provide
"hard drive
" / SD card / USB stick images for
1858 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1859 system), and can also be installed using a Debian installer preseed
1860 file. The Debian based Freedombox is now based on Debian Jessie,
1861 where most of the needed packages used are already present. Only one,
1862 the freedombox-setup package, is missing. To try to build your own
1863 boot image to test the current status, fetch the freedom-maker scripts
1865 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
1866 with a user with sudo access to become root:
1869 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1871 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1872 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1874 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1877 <p
>Root access is needed to run debootstrap and mount loopback
1878 devices. See the README for more details on the build. If you do not
1879 want all three images, trim the make line. But note that thanks to
<a
1880 href=
"https://bugs.debian.org/
741407">a race condition in
1881 vmdebootstrap
</a
>, the build might fail without the patch to the
1882 kpartx call.
</p
>
1884 <p
>If you instead want to install using a Debian CD and the preseed
1885 method, boot a Debian Wheezy ISO and use this boot argument to load
1886 the preseed values:
</p
>
1889 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1892 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
1893 recently introduced bug in apt in Jessie
</a
>, the installer will
1894 currently hang while setting up APT sources. Killing the
1895 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
1896 installation will get the installation going. This affect all
1897 installations in Jessie, and I expect it will be fixed soon.
</p
>
1899 <p
>Give it a go and let us know how it goes on the mailing list, and help
1900 us get the new release published. :) Please join us on
1901 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1902 irc.debian.org)
</a
> and
1903 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1904 mailing list
</a
> if you want to help make this vision come true.
</p
>
1909 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1910 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1911 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1912 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1913 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1914 innetgr tools, because I needed them in
1915 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1916 ng-utils, and it has served me well. I placed the project under the
1917 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1918 repository. But many years ago, the CVS repository was dropped (lost,
1919 not migrated to new hardware, not sure), and the project have lacked a
1920 proper home since then.
</p
>
1922 <p
>Last summer, I had a look at the package and made a new release
1923 fixing a irritating crash bug, but was unable to store the changes in
1924 a proper source control system. I applied for a project on
1925 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1926 to follow up on it. Until today. :)
</p
>
1928 <p
>After many hours of cleaning and migration, the ng-utils project
1929 now have a new home, and a git repository with the highlight of the
1930 history of the project. I published all release tarballs and imported
1931 them into the git repository. As the project is really stable and not
1932 expected to gain new features any time soon, I decided to make a new
1933 release and call it
1.0. Visit the new project home on
1934 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1935 if you want to check it out. The new version is also uploaded into
1936 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1941 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1942 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1943 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1944 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1945 <description><p
>A few days ago I decided to try to help the Hurd people to get
1946 their changes into sysvinit, to allow them to use the normal sysvinit
1947 boot system instead of their old one. This follow up on the
1948 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1949 Google Summer of Code work
</a
> done last summer by Justus Winter to
1950 get Debian on Hurd working more like Debian on Linux. To get started,
1951 I downloaded a prebuilt hard disk image from
1952 <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
>,
1953 and started it using virt-manager.
</p
>
1955 <p
>The first think I had to do after logging in (root without any
1956 password) was to get the network operational. I followed
1957 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1958 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1959 commands as root to get the machine to accept a IP address from the
1960 kvm internal DHCP server:
</p
>
1962 <p
><blockquote
><pre
>
1963 settrans -fgap /dev/netdde /hurd/netdde
1964 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1965 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1967 </pre
></blockquote
></p
>
1969 <p
>After this, the machine had internet connectivity, and I could
1970 upgrade it and install the sysvinit packages from experimental and
1971 enable it as the default boot system in Hurd.
</p
>
1973 <p
>But before I did that, I set a password on the root user, as ssh is
1974 running on the machine it for ssh login to work a password need to be
1975 set. Also, note that a bug somewhere in openssh on Hurd block
1976 compression from working. Remember to turn that off on the client
1979 <p
>Run these commands as root to upgrade and test the new sysvinit
1982 <p
><blockquote
><pre
>
1983 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1984 deb http://http.debian.net/debian/ experimental main
1987 apt-get dist-upgrade
1988 apt-get install -t experimental initscripts sysv-rc sysvinit \
1989 sysvinit-core sysvinit-utils
1990 update-alternatives --config runsystem
1991 </pre
></blockquote
></p
>
1993 <p
>To reboot after switching boot system, you have to use
1994 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1995 yet a sysvinit process able to receive the signals from the normal
1996 'reboot
' command. After switching to sysvinit as the boot system,
1997 upgrading every package and rebooting, the network come up with DHCP
1998 after boot as it should, and the settrans/pkill hack mentioned at the
1999 start is no longer needed. But for some strange reason, there are no
2000 longer any login prompt in the virtual console, so I logged in using
2003 <p
>Note that there are some race conditions in Hurd making the boot
2004 fail some times. No idea what the cause is, but hope the Hurd porters
2005 figure it out. At least Justus said on IRC (#debian-hurd on
2006 irc.debian.org) that they are aware of the problem. A way to reduce
2007 the impact is to upgrade to the Hurd packages built by Justus by
2008 adding this repository to the machine:
</p
>
2010 <p
><blockquote
><pre
>
2011 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2012 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2014 </pre
></blockquote
></p
>
2016 <p
>At the moment the prebuilt virtual machine get some packages from
2017 http://ftp.debian-ports.org/debian, because some of the packages in
2018 unstable do not yet include the required patches that are lingering in
2019 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2021 <p
><blockquote
><pre
>
2022 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2023 i emacs - GNU Emacs editor (metapackage)
2024 i gdb - GNU Debugger
2025 i hurd-recommended - Miscellaneous translators
2026 i isc-dhcp-client - ISC DHCP client
2027 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2028 i libc-bin - Embedded GNU C Library: Binaries
2029 i libc-dev-bin - Embedded GNU C Library: Development binaries
2030 i libc0.3 - Embedded GNU C Library: Shared libraries
2031 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2032 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2033 i multiarch-support - Transitional package to ensure multiarch compatibilit
2034 i A x11-common - X Window System (X.Org) infrastructure
2035 i xorg - X.Org X Window System
2036 i A xserver-xorg - X.Org X server
2037 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2039 </pre
></blockquote
></p
>
2041 <p
>All in all, testing hurd has been an interesting experience. :)
2042 X.org did not work out of the box and I never took the time to follow
2043 the porters instructions to fix it. This time I was interested in the
2044 command line stuff.
<p
>
2049 <title>New chrpath release
0.16</title>
2050 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2051 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2052 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2053 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2054 find problems in C, C++ and Java code using static source code
2055 analysis. It can detect a lot of different problems, and is very
2056 useful to find memory and locking bugs in the error handling part of
2057 the source. The company behind it provide
2058 <a href=
"https://scan.coverity.com/
">check of free software projects as
2059 a community service
</a
>, and many hundred free software projects are
2060 already checked. A few days ago I decided to have a closer look at
2061 the Coverity system, and discovered that the
2062 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2063 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2064 projects I am involved with was already registered. But these are
2065 fairly big, and I would also like to have a small and easy project to
2066 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2067 checking of the chrpath project
</a
>. It was
2068 added to the checker and discovered seven potential defects. Six of
2069 these were real, mostly resource
"leak
" when the program detected an
2070 error. Nothing serious, as the resources would be released a fraction
2071 of a second later when the program exited because of the error, but it
2072 is nice to do it right in case the source of the program some time in
2073 the future end up in a library. Having fixed all defects and added
2074 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
2075 mailing list for the chrpath developers
</a
>, I decided it was time to
2076 publish a new release. These are the release notes:
</p
>
2078 <p
>New in
0.16 released
2014-
01-
14:
</p
>
2082 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
2083 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
2084 <li
>Mention new project mailing list in the documentation.
</li
>
2089 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2090 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
2091 project if something is wrong with the new release. The test suite
2092 did not discover any old errors, so if you find a new one, please also
2093 include a test suite check.
</p
>
2098 <title>New chrpath release
0.15</title>
2099 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
2100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
2101 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
2102 <description><p
>After many years break from the package and a vain hope that
2103 development would be continued by someone else, I finally pulled my
2104 acts together this morning and wrapped up a new release of chrpath,
2105 the command line tool to modify the rpath and runpath of already
2106 compiled ELF programs. The update was triggered by the persistence of
2107 Isha Vishnoi at IBM, which needed a new config.guess file to get
2108 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
2109 is working on. I checked the
2110 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
2111 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
2112 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
2113 packages for interesting patches (failed to find the source from
2114 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2115 These are the release notes:
</p
>
2117 <p
>New in
0.15 released
2013-
11-
24:
</p
>
2121 <li
>Updated config.sub and config.guess from the GNU project to work
2122 with newer architectures. Thanks to isha vishnoi for the heads
2125 <li
>Updated README with current URLs.
</li
>
2127 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2128 Matthias Klose.
</li
>
2130 <li
>Added missing help for -k|--keepgoing option, using patch by
2131 Petr Machata found in Fedora.
</li
>
2133 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
2134 .dynamic is a NULL terminated string. Based on patch found in
2135 Fedora credited Axel Thimm and Christian Krause.
</li
>
2140 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2141 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
2142 project if something is wrong with the new release. The test suite
2143 did not discover any old errors, so if you find a new one, please also
2144 include a testsuite check.
</p
>
2149 <title>Debian init.d boot script example for rsyslog
</title>
2150 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
2151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
2152 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
2153 <description><p
>If one of the points of switching to a new init system in Debian is
2154 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
2155 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
2156 init.d scripts at all. Here is an example init.d script, ie a rewrite
2157 of /etc/init.d/rsyslog:
</p
>
2159 <p
><pre
>
2160 #!/lib/init/init-d-script
2163 # Required-Start: $remote_fs $time
2164 # Required-Stop: umountnfs $time
2165 # X-Stop-After: sendsigs
2166 # Default-Start:
2 3 4 5
2167 # Default-Stop:
0 1 6
2168 # Short-Description: enhanced syslogd
2169 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2170 # It is quite compatible to stock sysklogd and can be
2171 # used as a drop-in replacement.
2173 DESC=
"enhanced syslogd
"
2174 DAEMON=/usr/sbin/rsyslogd
2175 </pre
></p
>
2177 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
2178 script was
137 lines, and the above is just
15 lines, most of it meta
2179 info/comments.
</p
>
2181 <p
>How to do this, you ask? Well, one create a new script
2182 /lib/init/init-d-script looking something like this:
2184 <p
><pre
>
2187 # Define LSB log_* functions.
2188 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
2189 # and status_of_proc is working.
2190 . /lib/lsb/init-functions
2193 # Function that starts the daemon/service
2199 #
0 if daemon has been started
2200 #
1 if daemon was already running
2201 #
2 if daemon could not be started
2202 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
2204 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2207 # Add code here, if necessary, that waits for the process to be ready
2208 # to handle requests from services started subsequently which depend
2209 # on this one. As a last resort, sleep for some time.
2213 # Function that stops the daemon/service
2218 #
0 if daemon has been stopped
2219 #
1 if daemon was already stopped
2220 #
2 if daemon could not be stopped
2221 # other if a failure occurred
2222 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
2223 RETVAL=
"$?
"
2224 [
"$RETVAL
" =
2 ]
&& return
2
2225 # Wait for children to finish too if this is a daemon that forks
2226 # and if the daemon is only ever run from this initscript.
2227 # If the above conditions are not satisfied then add some other code
2228 # that waits for the process to drop all resources that could be
2229 # needed by services started subsequently. A last resort is to
2230 # sleep for some time.
2231 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
2232 [
"$?
" =
2 ]
&& return
2
2233 # Many daemons don
't delete their pidfiles when they exit.
2235 return
"$RETVAL
"
2239 # Function that sends a SIGHUP to the daemon/service
2243 # If the daemon can reload its configuration without
2244 # restarting (for example, when it is sent a SIGHUP),
2245 # then implement that here.
2247 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
2252 scriptbasename=
"$(basename $
1)
"
2253 echo
"SN: $scriptbasename
"
2254 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
2255 script=
"$
1"
2262 NAME=$(basename $DAEMON)
2263 PIDFILE=/var/run/$NAME.pid
2265 # Exit if the package is not installed
2266 #[ -x
"$DAEMON
" ] || exit
0
2268 # Read configuration variable file if it is present
2269 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
2271 # Load the VERBOSE setting and other rcS variables
2274 case
"$
1" in
2276 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
2278 case
"$?
" in
2279 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2280 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2284 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
2286 case
"$?
" in
2287 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
2288 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
2292 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
2294 #reload|force-reload)
2296 # If do_reload() is not implemented then leave this commented out
2297 # and leave
'force-reload
' as an alias for
'restart
'.
2299 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
2303 restart|force-reload)
2305 # If the
"reload
" option is implemented then remove the
2306 #
'force-reload
' alias
2308 log_daemon_msg
"Restarting $DESC
" "$NAME
"
2310 case
"$?
" in
2313 case
"$?
" in
2315 1) log_end_msg
1 ;; # Old process is still running
2316 *) log_end_msg
1 ;; # Failed to start
2326 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
2332 </pre
></p
>
2334 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
2335 lot. I did not really polish the approach, so it might not always
2336 work out of the box, but you get the idea. I did not try very hard to
2337 optimize it nor make it more robust either.
</p
>
2339 <p
>A better argument for switching init system in Debian than reducing
2340 the size of init scripts (which is a good thing to do anyway), is to
2341 get boot system that is able to handle the kernel events sensibly and
2342 robustly, and do not depend on the boot to run sequentially. The boot
2343 and the kernel have not behaved sequentially in years.
</p
>
2348 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
2349 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
2350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
2351 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
2352 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
2353 remote display access is the preferred solution with oVirt and RedHat
2354 Enterprise Virtualization, and I was sad to discover the other day
2355 that the browser plugin needed to use these systems seamlessly was
2356 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
2357 for a package
</a
> was from
2012-
04-
10 with no progress since
2358 2013-
04-
01, so I decided to wrap up a package based on the great work
2359 from Cajus Pollmeier and put it in a collab-maint maintained git
2360 repository to get a package I could use. I would very much like
2361 others to help me maintain the package (or just take over, I do not
2362 mind), but as no-one had volunteered so far, I just uploaded it to
2363 NEW. I hope it will be available in Debian in a few days.
</p
>
2365 <p
>The source is now available from
2366 <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
>
2371 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
2372 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
2373 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
2374 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
2375 <description><p
>The
2376 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
2377 program is a a very nice system to create virtual machine images. It
2378 create a image file, add a partition table, mount it and run
2379 debootstrap in the mounted directory to create a Debian system on a
2380 stick. Yesterday, I decided to try to teach it how to make images for
2381 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
2382 of a plan to simplify the build system for
2383 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
2384 project
</a
>. The FreedomBox project already uses vmdebootstrap for
2385 the virtualbox images, but its current build system made multistrap
2386 based system for Dreamplug images, and it is lacking support for
2387 Raspberry Pi.
</p
>
2389 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
2390 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2391 code and adjusted it to be able to build armel images on my amd64
2392 Debian laptop. I ended up giving vmdebootstrap five new options,
2393 allowing me to replicate the image creation process I use to make
2394 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
2395 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
2396 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
2397 call debootstrap with --foreign and to copy the handler into the
2398 generated chroot before running the second stage. This allow
2399 vmdebootstrap to create armel images on an amd64 host. Next I added
2400 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
2401 fstype
</tt
> to teach it to create a separate /boot/ partition with the
2402 given file system type, allowing me to create an image with a vfat
2403 partition for the /boot/ stuff. I also added a
<tt
>--variant
2404 variant
</tt
> option to allow me to create smaller images without the
2405 Debian base system packages installed. Finally, I added an option
2406 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
2407 as a boot loader. It is not needed on the Raspberry Pi and probably
2408 most other non-x86 architectures. The changes were accepted by the
2409 upstream author of vmdebootstrap yesterday and today, and is now
2411 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
2412 upstream project page
</a
>.
</p
>
2414 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
2415 create a small script (the customize script) to add the non-free
2416 binary blob needed to boot the Raspberry Pi and the APT source
2419 <p
><pre
>
2421 set -e # Exit on first error
2422 rootdir=
"$
1"
2423 cd
"$rootdir
"
2424 cat
&lt;
&lt;EOF
> etc/apt/sources.list
2425 deb http://http.debian.net/debian/ jessie main contrib non-free
2427 # Install non-free binary blob needed to boot Raspberry Pi. This
2428 # install a kernel somewhere too.
2429 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2430 -O $rootdir/usr/bin/rpi-update
2431 chmod a+x $rootdir/usr/bin/rpi-update
2432 mkdir -p $rootdir/lib/modules
2433 touch $rootdir/boot/start.elf
2434 chroot $rootdir rpi-update
2435 </pre
></p
>
2437 <p
>Next, fetch the latest vmdebootstrap script and call it like this
2438 to build the image:
</p
>
2441 sudo ./vmdebootstrap \
2444 --distribution jessie \
2445 --mirror http://http.debian.net/debian \
2454 --root-password raspberry \
2455 --hostname raspberrypi \
2456 --foreign /usr/bin/qemu-arm-static \
2457 --customize `pwd`/customize \
2459 --package git-core \
2460 --package binutils \
2461 --package ca-certificates \
2464 </pre
></p
>
2466 <p
>The list of packages being installed are the ones needed by
2467 rpi-update to make the image bootable on the Raspberry Pi, with the
2468 exception of netbase, which is needed by debootstrap to find
2469 /etc/hosts with the minbase variant. I really wish there was a way to
2470 set up an Raspberry Pi using only packages in the Debian archive, but
2471 that is not possible as far as I know, because it boots from the GPU
2472 using a non-free binary blob.
</p
>
2474 <p
>The build host need debootstrap, kpartx and qemu-user-static and
2475 probably a few others installed. I have not checked the complete
2476 build dependency list.
</p
>
2478 <p
>The resulting image will not use the hardware floating point unit
2479 on the Raspberry PI, because the armel architecture in Debian is not
2480 optimized for that use. So the images created will be a bit slower
2481 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
2486 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
2487 <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>
2488 <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>
2489 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
2490 <description><p
>The last few days I came across a few good causes that should get
2491 wider attention. I recommend signing and donating to each one of
2494 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
2495 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
2496 Women program which is a Google Summer of Code like initiative to get
2497 more women involved in free software. One debian sponsor has offered
2498 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
2499 earmarked
</a
> for this initiative. I donated a few minutes ago, and
2500 hope you will to. :)
</p
>
2502 <p
>And the Electronic Frontier Foundation just announced plans to
2503 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
2504 documentaries about the excessive spying
</a
> on every Internet user that
2505 take place these days, and their need to fund the work. I
've already
2506 donated. Are you next?
</p
>
2508 <p
>For my Norwegian audience, the organisation Studentenes og
2509 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2510 statement under the heading
2511 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
2512 Access
</a
> for those of us asking for more focus on open access in the
2513 Norwegian government. So far
499 signatures. I hope you will sign it
2519 <title>Videos about the Freedombox project - for inspiration and learning
</title>
2520 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
2521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
2522 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
2523 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
2524 project
</a
> have been going on for a while, and have presented the
2525 vision, ideas and solution several places. Here is a little
2526 collection of videos of talks and presentation of the project.
</p
>
2530 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
2531 2,
5 minute marketing film
</a
> (Youtube)
</li
>
2533 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
2534 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
2536 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
2537 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2538 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
2539 (Youtube)
</li
>
2541 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
2542 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
2544 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
2545 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
2547 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
2548 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2549 York City in
2012</a
> (Youtube)
</li
>
2551 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
2552 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
2553 (Youtube)
</li
>
2555 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
2556 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
2558 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
2559 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
2561 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
2562 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2563 2013</a
> (Youtube)
</li
>
2567 <p
>A larger list is available from
2568 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
2569 Freedombox Wiki
</a
>.
</p
>
2571 <p
>On other news, I am happy to report that Freedombox based on Debian
2572 Jessie is coming along quite well, and soon both Owncloud and using
2573 Tor should be available for testers of the Freedombox solution. :) In
2574 a few weeks I hope everything needed to test it is included in Debian.
2575 The withsqlite package is already in Debian, and the plinth package is
2576 pending in NEW. The third and vital part of that puzzle is the
2577 metapackage/setup framework, which is still pending an upload. Join
2578 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
2579 (#freedombox on irc.debian.org)
</a
> and
2580 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2581 mailing list
</a
> if you want to help make this vision come true.
</p
>
2586 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
2587 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
2588 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
2589 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
2590 <description><p
>I was introduced to the
2591 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
2592 in
2010, when Eben Moglen presented his vision about serving the need
2593 of non-technical people to keep their personal information private and
2594 within the legal protection of their own homes. The idea is to give
2595 people back the power over their network and machines, and return
2596 Internet back to its intended peer-to-peer architecture. Instead of
2597 depending on a central service, the Freedombox will give everyone
2598 control over their own basic infrastructure.
</p
>
2600 <p
>I
've intended to join the effort since then, but other tasks have
2601 taken priority. But this summers nasty news about the misuse of trust
2602 and privilege exercised by the
"western
" intelligence gathering
2603 communities increased my eagerness to contribute to a point where I
2604 actually started working on the project a while back.
</p
>
2606 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
2607 Debian initiative
</a
> based on the vision from Eben Moglen, is to
2608 create a simple and cheap Debian based appliance that anyone can hook
2609 up in their home and get access to secure and private services and
2610 communication. The initial deployment platform have been the
2611 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
2612 which is a piece of hardware I do not own. So to be able to test what
2613 the current Freedombox setup look like, I had to come up with a way to install
2614 it on some hardware I do have access to. I have rewritten the
2615 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
2616 image build framework to use .deb packages instead of only copying
2617 setup into the boot images, and thanks to this rewrite I am able to
2618 set up any machine supported by Debian Wheezy as a Freedombox, using
2619 the previously mentioned deb (and a few support debs for packages
2620 missing in Debian).
</p
>
2622 <p
>The current Freedombox setup consist of a set of bootstrapping
2624 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
2625 and a administrative web interface
2626 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
2627 withsqlite), as well as a privacy enhancing proxy based on
2628 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
2629 (freedombox-privoxy). There is also a web/javascript based XMPP
2630 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
2631 trying (unsuccessfully so far) to talk to the XMPP server
2632 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
2633 web interface is pluggable, and the goal is to use it to enable OpenID
2634 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2635 this is really working yet, see
2636 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
2637 project TODO
</a
> for links to GIT repositories. Most of the code is
2638 on github at the moment. The HTTP proxy is operational out of the
2639 box, and the admin web interface can be used to add/remove plinth
2640 users. I
've not been able to do anything else with it so far, but
2641 know there are several branches spread around github and other places
2642 with lots of half baked features.
</p
>
2644 <p
>Anyway, if you want to have a look at the current state, the
2645 following recipes should work to give you a test machine to poke
2648 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
2652 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
2653 <li
>Boot from it, either as CD or USB stick.
</li
>
2654 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
2655 to the Debian installer:
<p
>
2656 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
2658 <li
>Answer the few language/region/password questions and pick disk to
2659 install on.
</li
>
2661 <li
>When the installation is finished and the machine have rebooted a
2662 few times, your Freedombox is ready for testing.
</li
>
2666 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
2670 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
2671 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
2672 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
2674 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
2675 </pre
></li
>
2676 <li
><p
>Run this as root:
</p
>
2678 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2681 apt-get install freedombox-setup
2682 /usr/lib/freedombox/setup
2683 </pre
></li
>
2684 <li
>Reboot into your freshly created Freedombox.
</li
>
2688 <p
>You can test it on other architectures too, but because the
2689 freedombox-privoxy package is binary, it will only work as intended on
2690 the architectures where I have had time to build the binary and put it
2691 in my APT repository. But do not let this stop you. It is only a
2692 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
2694 <p
>Note that by default Freedombox is a DHCP server on the
2695 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
2696 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
2697 disable
</tt
>" as root.
</p
>
2699 <p
>Please let me know if this works for you, or if you have any
2700 problems. We gather on the IRC channel
2701 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
2702 irc.debian.org and the
2703 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
2704 mailing list
</a
>.
</p
>
2706 <p
>Once you get your freedombox operational, you can visit
2707 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
2708 welcome screen (dead end - do not be surprised if you are unable to
2709 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
2710 to look at the rest of plinth. The default user is
'admin
' and the
2711 default password is
'secret
'.
</p
>
2716 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
2717 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
2718 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
2719 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
2720 <description><p
>Earlier, I reported about
2721 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
2722 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
2723 told by IBM that the original disk should be thrown away. And as
2724 there no longer was a problem if I bricked the firmware, I decided
2725 today to try to install Intel firmware to replace the Lenovo firmware
2726 currently on the disk.
</p
>
2728 <p
>I searched the Intel site for firmware, and found
2729 <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
>
2730 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2731 according to the site should contain the latest firmware for SSD
2732 disks. I inserted the broken disk in one of my spare laptops and
2733 booted the ISO from a USB stick. The disk was recognized, but the
2734 program claimed the newest firmware already were installed and refused
2735 to insert any Intel firmware. So no change, and the disk is still
2736 unable to handle write load. :( I guess the only way to get them
2737 working would be if Lenovo releases new firmware. No idea how likely
2738 that is. Anyway, just blogging about this test for completeness. I
2739 got a working Samsung disk, and see no point in spending more time on
2740 the broken disks.
</p
>
2745 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
2746 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
2747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
2748 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
2749 <description><p
>Today I switched to
2750 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
2751 new laptop
</a
>. I
've previously written about the problems I had with
2752 my new Thinkpad X230, which was delivered with an
2753 <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
2754 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
2755 sustained writes. My hardware supplier have been very forthcoming in
2756 trying to find a solution, and after first trying with another
2757 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
2758 disk instead to fix it once and for all. The Samsung disk survived
2759 the installation of Debian with encrypted disks (filling the disk with
2760 random data during installation killed the first two), and I thus
2761 decided to trust it with my data. I have installed it as a Debian Edu
2762 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2763 server at home using Kerberos and LDAP, and will use it as my work
2764 station from now on.
</p
>
2766 <p
>As this is a solid state disk with no moving parts, I believe the
2767 Debian Wheezy default installation need to be tuned a bit to increase
2768 performance and increase life time of the disk. The Linux kernel and
2769 user space applications do not yet adjust automatically to such
2770 environment. To make it easier for my self, I created a draft Debian
2771 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
2772 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
2773 for the ssd-setup package
</a
> is available from collab-maint, and it
2774 is set up to adjust the setup of the machine by just installing the
2775 package. If there is any non-SSD disk in the machine, the package
2776 will refuse to install, as I did not try to write any logic to sort
2777 file systems in SSD and non-SSD file systems.
</p
>
2779 <p
>I consider the package a draft, as I am a bit unsure how to best
2780 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2781 where I set up the machine with one large encrypted partition (in
2782 addition to /boot), put LVM on top of this and set up partitions on
2783 top of this again. See the README file in the package source for the
2784 references I used to pick the settings. At the moment these
2785 parameters are tuned:
</p
>
2789 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
2790 (adding discard to /etc/crypttab)
</li
>
2792 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
2793 this case a cryptsetup partition) by changing issue_discards from
2794 0 to
1 in /etc/lvm/lvm.conf.
</li
>
2796 <li
>Set relatime as a file system option for ext3 and ext4 file
2799 <li
>Tell swap to use TRIM commands by adding
'discard
' to
2800 /etc/fstab.
</li
>
2802 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
2804 <li
>Run fstrim on every ext3 and ext4 file system every night (from
2805 cron.daily).
</li
>
2807 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
2808 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
2812 <p
>During installation, I cancelled the part where the installer fill
2813 the disk with random data, as this would kill the SSD performance for
2814 little gain. My goal with the encrypted file system is to ensure
2815 those stealing my laptop end up with a brick and not a working
2816 computer. I have no hope in keeping the really resourceful people
2817 from getting the data on the disk (see
2818 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
2819 Thus I concluded that adding the discard option to crypttab is the
2820 right thing to do.
</p
>
2822 <p
>I considered using the noop I/O scheduler, as several recommended
2823 it for SSD, but others recommended deadline and a benchmark I found
2824 indicated that deadline might be better for interactive use.
</p
>
2826 <p
>I also considered using the
'discard
' file system option for ext3
2827 and ext4, but read that it would give a performance hit ever time a
2828 file is removed, and thought it best to that that slowdown once a day
2829 instead of during my work.
</p
>
2831 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2832 this is already done by Debian Edu.
</p
>
2834 <p
>I have not yet started on the user space tuning. I expect
2835 iceweasel need some tuning, and perhaps other applications too, but
2836 have not yet had time to investigate those parts.
</p
>
2838 <p
>The package should work on Ubuntu too, but I have not yet tested it
2841 <p
>As for the answer to the question in the title of this blog post,
2842 as far as I know, the only solution I know about is to replace the
2843 disk. It might be possible to flash it with Intel firmware instead of
2844 the Lenovo firmware. But I have not tried and did not want to do so
2845 without approval from Lenovo as I wanted to keep the warranty on the
2846 disk until a solution was found and they wanted the broken disks
2852 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
2853 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
2854 <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>
2855 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
2856 <description><p
>A few days ago, I wrote about
2857 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
2858 problems I experienced with my new X230 and its SSD disk
</a
>, which
2859 was dying during installation because it is unable to cope with
2860 sustained write. My supplier is in contact with
2861 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
2862 replacement disk to try to fix the problem. They decided to send an
2863 identical model, so my hopes for a permanent fix was slim.
</p
>
2865 <p
>Anyway, today I got the replacement disk and tried to install
2866 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2867 same firmware version as the original. This time my hope raised
2868 slightly as the installation progressed, as the original disk used to
2869 die after
4-
7% of the disk was written to, while this time it kept
2870 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
2871 died again and I was back on square one. I still do not have a new
2872 laptop with a disk I can trust. I can not live with a disk that might
2873 lock up when I download a new
2874 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
2875 other large files. I look forward to hearing from my supplier with
2876 the next proposal from Lenovo.
</p
>
2878 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
2879 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2880 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2881 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
2882 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2883 P/N
45N8295, P0C38732.
</p
>
2885 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
2886 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
2887 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2888 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
2889 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2890 P/N
45N8295, P0C38732.
</p
>
2892 <p
>The only difference is in the first number (serial number?), ISN,
2893 SA, date and WNPP values. Mentioning all the details here in case
2894 someone is able to use the information to find a way to identify the
2895 failing disk among working ones (if any such working disk actually
2901 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
2902 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
2903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2904 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2905 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2906 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2907 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2908 member assosiation NUUG
</a
> and
2909 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2910 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2911 Bitraf
</a
>.
</p
>
2913 <p
>It starts
10:
00 and continue until late evening. Everyone is
2914 welcome, and there is no fee to participate. There is on the other
2915 hand limited space, and only room for
30 people. Please put your name
2916 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2917 wiki page
</a
> if you plan to join us.
</p
>
2922 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2923 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2924 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2925 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2926 <description><p
>Half a year ago, I reported that I had to find a
2927 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2928 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2929 time to spend on it, and it took a while to find a model I believe
2930 will do the job, but two days ago the replacement finally arrived. I
2932 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2933 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2934 a roaming workstation, and it seemed to work flawlessly. But my
2935 second installation with encrypted disk was not as successful. More
2936 on that below.
</p
>
2938 <p
>I had a hard time trying to track down a good laptop, as my most
2939 important requirements (robust and with a good keyboard) are never
2940 listed in the feature list. But I did get good help from the search
2941 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2942 allowed me to limit the list of interesting laptops based on my other
2943 requirements. A bit surprising that SSD disk are not disks according
2944 to that search interface, so I had to drop specifying the number of
2945 disks from my search parameters. I also asked around among friends to
2946 get their impression on keyboards and robustness.
</p
>
2948 <p
>So the new laptop arrived, and it is quite a lot wider than the
2949 X41. I am not quite convinced about the keyboard, as it is
2950 significantly wider than my old keyboard, and I have to stretch my
2951 hand a lot more to reach the edges. But the key response is fairly
2952 good and the individual key shape is fairly easy to handle, so I hope
2953 I will get used to it. My old X40 was starting to fail, and I really
2954 needed a new laptop now. :)
</p
>
2956 <p
>Turning off the touch pad was simple. All it took was a quick
2957 visit to the BIOS during boot it disable it.
</p
>
2959 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2960 lock up during load. And this happen when installing Debian Wheezy
2961 with encrypted disk, while the disk is being filled with random data.
2962 I also tested to install Ubuntu Raring, and it happen there too if I
2963 reenable the code to fill the disk with random data (it is disabled by
2964 default in Ubuntu). And the bug with is already known. It was
2965 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2966 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2967 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2968 kernel developers as
2969 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2970 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2971 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2972 Lenovo forums, both for
2973 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2974 2012-
11-
10</a
> and for
2975 <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
2976 03-
20-
2013</a
>. The problem do not only affect installation. The
2977 reports state that the disk lock up during use if many writes are done
2978 on the disk, so it is much no use to work around the installation
2979 problem and end up with a computer that can lock up at any moment.
2981 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2982 available
</a
> that will lock up the hard drive after running a few
2983 minutes by writing to a file.
</p
>
2985 <p
>I
've contacted my supplier and asked how to handle this, and after
2986 contacting PCHELP Norway (request
01D1FDP) which handle support
2987 requests for Lenovo, his first suggestion was to upgrade the disk
2988 firmware. Unfortunately there is no newer firmware available from
2989 Lenovo, as my disk already have the most recent one (version LF1i). I
2990 hope to hear more from him today and hope the problem can be
2996 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2997 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2999 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3000 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3001 trusty old Thinkpad X41. Unfortunately I did not have much time to
3002 spend on it, but today the replacement finally arrived. I ended up
3003 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3004 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3005 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3006 this, it is installing what I hope will be a more final installation,
3007 with a encrypted hard drive to ensure any dope head stealing it end up
3008 with an expencive door stop.
</p
>
3010 <p
>I had a hard time trying to track down a good laptop, as my most
3011 important requirements (robust and with a good keyboard) are never
3012 listed in the feature list. But I did get good help from the search
3013 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3014 allowed me to limit the list of interesting laptops based on my other
3015 requirements. A bit surprising that SSD disk are not disks, so I had
3016 to drop number of disks from my search parameters.
</p
>
3018 <p
>I am not quite convinced about the keyboard, as it is significantly
3019 wider than my old keyboard, and I have to stretch my hand a lot more
3020 to reach the edges. But the key response is fairly good and the
3021 individual key shape is fairly easy to handle, so I hope I will get
3022 used to it. My old X40 was starting to fail, and I really needed a
3023 new laptop now. :)
</p
>
3025 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3030 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3031 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3032 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3033 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3034 <description><p
>It annoys me when the computer fail to do automatically what it is
3035 perfectly capable of, and I have to do it manually to get things
3036 working. One such task is to find out what firmware packages are
3037 needed to get the hardware on my computer working. Most often this
3038 affect the wifi card, but some times it even affect the RAID
3039 controller or the ethernet card. Today I pushed version
0.4 of the
3040 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3041 including a new script isenkram-autoinstall-firmware handling the
3042 process of asking all the loaded kernel modules what firmware files
3043 they want, find debian packages providing these files and install the
3044 debian packages. Here is a test run on my laptop:
</p
>
3046 <p
><pre
>
3047 # isenkram-autoinstall-firmware
3048 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3049 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3050 info: locating packages with the requested firmware files
3051 info: Updating APT sources after adding non-free APT source
3052 info: trying to install firmware-ipw2x00
3055 Preconfiguring packages ...
3056 Selecting previously deselected package firmware-ipw2x00.
3057 (Reading database ...
259727 files and directories currently installed.)
3058 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3059 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3061 </pre
></p
>
3063 <p
>When all the requested firmware is present, a simple message is
3064 printed instead:
</p
>
3066 <p
><pre
>
3067 # isenkram-autoinstall-firmware
3068 info: did not find any firmware files requested by loaded kernel modules. exiting
3070 </pre
></p
>
3072 <p
>It could use some polish, but it is already working well and saving
3073 me some time when setting up new machines. :)
</p
>
3075 <p
>So, how does it work? It look at the set of currently loaded
3076 kernel modules, and look up each one of them using modinfo, to find
3077 the firmware files listed in the module meta-information. Next, it
3078 download the Contents file from a nearby APT mirror, and search for
3079 the firmware files in this file to locate the package with the
3080 requested firmware file. If the package is in the non-free section, a
3081 non-free APT source is added and the package is installed using
3082 <tt
>apt-get install
</tt
>. The end result is a slightly better working
3085 <p
>I hope someone find time to implement a more polished version of
3086 this script as part of the hw-detect debian-installer module, to
3087 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
3088 #
655507</a
>. There really is no need to insert USB sticks with
3089 firmware during a PXE install when the packages already are available
3090 from the nearby Debian mirror.
</p
>
3095 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
3096 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
3097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
3098 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
3099 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3100 the screen just turn black when Linux boot, either during installation
3101 or on first boot from the hard disk. I
've seen it once in a while the
3102 last few years, but only recently understood the cause. I
've seen it
3103 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3104 The reason seem to be in the wiring of some laptops. The system to
3105 control the screen background light is inverted, so when Linux try to
3106 turn the brightness fully on, it end up turning it off instead. I do
3107 not know which Linux drivers are affected, but this post is about the
3108 i915 driver used by the
3109 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3110 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
3112 <p
>The problem can be worked around two ways. Either by adding
3113 i915.invert_brightness=
1 as a kernel option, or by adding a file in
3114 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
3115 option when it load the i915 kernel module. On Debian and Ubuntu, it
3116 can be done by running these commands as root:
</p
>
3119 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
3120 update-initramfs -u -k all
3123 <p
>Since March
2012 there is
3124 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
3125 mechanism in the Linux kernel
</a
> to tell the i915 driver which
3126 hardware have this problem, and get the driver to invert the
3127 brightness setting automatically. To use it, one need to add a row in
3128 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
3129 intel_quirks array
</a
> in the driver source
3130 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
3131 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
3132 number (vendor number
8086 is assumed) and subdevice vendor and device
3135 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
3136 -vvnn
</tt
> for the video card in question:
</p
>
3138 <p
><pre
>
3139 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
3140 3rd Gen Core processor Graphics Controller [
8086:
0156] \
3141 (rev
09) (prog-if
00 [VGA controller])
3142 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
3143 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3144 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3145 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
3146 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
3148 Interrupt: pin A routed to IRQ
42
3149 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
3150 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
3151 Region
4: I/O ports at
4000 [size=
64]
3152 Expansion ROM at
<unassigned
> [disabled]
3153 Capabilities:
<access denied
>
3154 Kernel driver in use: i915
3155 </pre
></p
>
3157 <p
>The resulting intel_quirks entry would then look like this:
</p
>
3159 <p
><pre
>
3160 struct intel_quirk intel_quirks[] = {
3162 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3163 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
3166 </pre
></p
>
3168 <p
>According to the kernel module instructions (as seen using
3169 <tt
>modinfo i915
</tt
>), information about hardware needing the
3170 invert_brightness flag should be sent to the
3171 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
3172 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
3173 developers. But my email about the laptop sent
2013-
06-
03 have not
3175 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
3176 web archive for the mailing list
</a
>, so I suspect they do not accept
3177 emails from non-subscribers. Because of this, I sent my patch also to
3178 the Debian bug tracking system instead as
3179 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
3180 sure the patch is not lost.
</p
>
3182 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
3183 with this problem working properly with Linux. If you use Gnome, your
3184 worries should be over at this point. But if you use KDE, there is
3185 something in KDE ignoring the invert_brightness setting and turning on
3186 the screen during login. I
've reported it to Debian as
3187 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
3188 have no idea yet how to figure out exactly what subsystem is doing
3189 this. Perhaps you can help? Perhaps you know what the Gnome
3190 developers did to handle this, and this can give a clue to the KDE
3191 developers? Or you know where in KDE the screen brightness is changed
3192 during login? If so, please update the BTS report (or get in touch if
3193 you do not know how to update BTS).
</p
>
3195 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
3196 acpi_backlight=vendor, to disable ACPI backlight support completely,
3197 as the ACPI information on the machine is trash and it is better to
3198 leave it to the intel video driver to control the screen
3199 backlight.
</p
>
3204 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
3205 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
3206 <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>
3207 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
3208 <description><p
>Two days ago, I asked
3209 <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
3210 I could install Linux on a Packard Bell EasyNote LV computer
3211 preinstalled with Windows
8</a
>. I found a solution, but am horrified
3212 with the obstacles put in the way of Linux users on a laptop with UEFI
3213 and Windows
8.
</p
>
3215 <p
>I never found out if the cause of my problems were the use of UEFI
3216 secure booting or fast boot. I suspect fast boot was the problem,
3217 causing the firmware to boot directly from HD without considering any
3218 key presses and alternative devices, but do not know UEFI settings
3219 enough to tell.
</p
>
3221 <p
>There is no way to install Linux on the machine in question without
3222 opening the box and disconnecting the hard drive! This is as far as I
3223 can tell, the only way to get access to the firmware setup menu
3224 without accepting the Windows
8 license agreement. I am told (and
3225 found description on how to) that it is possible to configure the
3226 firmware setup once booted into Windows
8. But as I believe the terms
3227 of that agreement are completely unacceptable, accepting the license
3228 was never an alternative. I do not enter agreements I do not intend
3229 to follow.
</p
>
3231 <p
>I feared I had to return the laptops and ask for a refund, and
3232 waste many hours on this, but luckily there was a way to get it to
3233 work. But I would not recommend it to anyone planning to run Linux on
3234 it, and I have become sceptical to Windows
8 certified laptops. Is
3235 this the way Linux will be forced out of the market place, by making
3236 it close to impossible for
"normal
" users to install Linux without
3237 accepting the Microsoft Windows license terms? Or at least not
3238 without risking to loose the warranty?
</p
>
3240 <p
>I
've updated the
3241 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
3242 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
3243 do not have to struggle as much as I did to get Linux into the
3246 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3247 Michael Tokarev and others for feedback and ideas.
</p
>
3252 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
3253 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
3254 <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>
3255 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
3256 <description><p
>I
've run into quite a problem the last few days. I bought three
3257 new laptops for my parents and a few others. I bought Packard Bell
3258 Easynote LV to run Kubuntu on and use as their home computer. But I
3259 am completely unable to figure out how to install Linux on it. The
3260 computer is preinstalled with Windows
8, and I suspect it uses UEFI
3261 instead of a BIOS to boot.
</p
>
3263 <p
>The problem is that I am unable to get it to PXE boot, and unable
3264 to get it to boot the Linux installer from my USB stick. I have yet
3265 to try the DVD install, and still hope it will work. when I turn on
3266 the computer, there is no information on what buttons to press to get
3267 the normal boot menu. I expect to get some boot menu to select PXE or
3268 USB stick booting. When booting, it first ask for the language to
3269 use, then for some regional settings, and finally if I will accept the
3270 Windows
8 terms of use. As these terms are completely unacceptable to
3271 me, I have no other choice but to turn off the computer and try again
3272 to get it to boot the Linux installer.
</p
>
3274 <p
>I have gathered my findings so far on a Linlap page about the
3275 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3276 EasyNote LV
</a
> model. If you have any idea how to get Linux
3277 installed on this machine, please get in touch or update that wiki
3278 page. If I can
't find a way to install Linux, I will have to return
3279 the laptop to the seller and find another machine for my parents.
</p
>
3281 <p
>I wonder, is this the way Linux will be forced out of the market
3282 using UEFI and
"secure boot
" by making it impossible to install Linux
3283 on new Laptops?
</p
>
3288 <title>How to transform a Debian based system to a Debian Edu installation
</title>
3289 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
3290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
3291 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
3292 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
3293 an operating system based on Debian intended for use in schools. It
3294 contain a turn-key solution for the computer network provided to
3295 pupils in the primary schools. It provide both the central server,
3296 network boot servers and desktop environments with heaps of
3297 educational software. The project was founded almost
12 years ago,
3298 2001-
07-
02. If you want to support the project, which is in need for
3299 cash to fund developer gatherings and other project related activity,
3300 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
3301 donate some money
</a
>.
3303 <p
>A topic that come up again and again on the Debian Edu mailing
3304 lists and elsewhere, is the question on how to transform a Debian or
3305 Ubuntu installation into a Debian Edu installation. It isn
't very
3306 hard, and last week I wrote a script to replicate the steps done by
3307 the Debian Edu installer.
</p
>
3309 <p
>The script,
3310 <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/
>
3311 in the debian-edu-config package, will go through these six steps and
3312 transform an existing Debian Wheezy or Ubuntu (untested) installation
3313 into a Debian Edu Workstation:
</p
>
3317 <li
>Add skolelinux related APT sources.
</li
>
3318 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
3319 <li
>Install debian-edu-install to load preseeding values and pull in
3320 our configuration.
</li
>
3321 <li
>Preseed debconf database with profile setup in
3322 /etc/debian-edu/config, and run tasksel to install packages
3323 according to the profile specified in the config above,
3324 overriding some of the Debian automation machinery.
</li
>
3325 <li
>Run debian-edu-cfengine-D installation to configure everything
3326 that could not be done using preseeding.
</li
>
3327 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
3331 <p
>There are some steps in the Debian Edu installation that can not be
3332 replicated like this. Disk partitioning and LVM setup, for example.
3333 So this script just assume there is enough disk space to install all
3334 the needed packages.
</p
>
3336 <p
>The script was created to help a Debian Edu student working on
3337 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
3338 Debian Edu client, and using it he can take the existing
3339 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
3340 transform it into a fully functioning Debian Edu Workstation (or
3341 Roaming Workstation, or whatever :).
</p
>
3343 <p
>The default setting in the script is to create a KDE Workstation.
3344 If a LXDE based Roaming workstation is wanted instead, modify the
3345 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
3347 <p
><pre
>
3348 PROFILE=
"Roaming-Workstation
"
3349 DESKTOP=
"lxde
"
3350 </pre
></p
>
3352 <p
>The script could even become useful to set up Debian Edu servers in
3353 the cloud, by starting with a virtual Debian installation at some
3354 virtual hosting service and setting up all the services on first
3360 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
3361 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
3362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
3363 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
3364 <description><P
>In January,
3365 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
3366 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
3367 channel #debian-lego
</a
>, for those of us in the Debian and Linux
3368 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
3369 marvellous construction system from Denmark. We also created
3370 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
3371 a place to take notes and write down our plans and hopes. And several
3372 people showed up to help. I was very happy to see the effect of my
3373 call. Since the small start, we have a debtags tag
3374 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
3375 tag for LEGO related packages, and now count
10 packages related to
3376 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
3378 <p
><table
>
3379 <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
>
3380 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
3381 <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
>
3382 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
3383 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
3384 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
3385 <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
>
3386 <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
>
3387 <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
>
3388 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
3389 </table
></p
>
3391 <p
>Some of these are available in Wheezy, and all but one are
3392 currently available in Jessie/testing. leocad is so far only
3393 available in experimental.
</p
>
3395 <p
>If you care about LEGO in Debian, please join us on IRC and help
3396 adding the rest of the great free software tools available on Linux
3397 for LEGO designers.
</p
>
3402 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
3403 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
3404 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
3405 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
3406 <description><p
>When I woke up this morning, I was very happy to see that the
3407 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
3408 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
3409 Debian release, and I expect to move my machines at home over to it fairly
3412 <p
>The new debian release contain heaps of new stuff, and one program
3413 in particular make me very happy to see included. The
3414 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
3415 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
3416 included for the first time. Alongside similar programs like
3417 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
3418 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
3419 it allow for visual programming where syntax errors can not happen,
3420 and a friendly programming environment for learning to control the
3421 computer. Scratch will also be included in the next release of Debian
3424 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
3425 Edu/Skolelinux release too. The
3426 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
3427 alpha release
</a
> went out last week, and the next should soon
3433 <title>Isenkram
0.2 finally in the Debian archive
</title>
3434 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
3435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
3436 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
3437 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
3438 package
</a
> finally made it into the archive, after lingering in NEW
3439 for many months. I uploaded it to the Debian experimental suite
3440 2013-
01-
27, and today it was accepted into the archive.
</p
>
3442 <p
>Isenkram is a system for suggesting to users what packages to
3443 install to work with a pluggable hardware device. The suggestion pop
3444 up when the device is plugged in. For example if a Lego Mindstorm NXT
3445 is inserted, it will suggest to install the program needed to program
3446 the NXT controller. Give it a go, and report bugs and suggestions to
3452 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
3453 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
3454 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
3455 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
3456 <description><p
>My
3457 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
3458 bitcoin related blog post
</a
> mentioned that the new
3459 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
3460 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3461 2013-
01-
19, and have been available in unstable since then. It was
3462 automatically copied to Ubuntu, and is available in their Raring
3463 version too.
</p
>
3465 <p
>But there is a strange problem with the build that block this new
3466 version from being available on the i386 and kfreebsd-i386
3467 architectures. For some strange reason, the autobuilders in Debian
3468 for these architectures fail to run the test suite on these
3469 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
3470 We are so far unable to reproduce it when building it manually, and
3471 no-one have been able to propose a fix. If you got an idea what is
3472 failing, please let us know via the BTS.
</p
>
3474 <p
>One feature that is annoying me with of the bitcoin client, because
3475 I often run low on disk space, is the fact that the client will exit
3476 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
3477 #
696715</a
>). So make sure you have enough disk space when you run
3480 <p
>As usual, if you use bitcoin and want to show your support of my
3481 activities, please send Bitcoin donations to my address
3482 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3487 <title>Welcome to the world, Isenkram!
</title>
3488 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
3489 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
3490 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
3491 <description><p
>Yesterday, I
3492 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
3493 for testers
</a
> for my prototype for making Debian better at handling
3494 pluggable hardware devices, which I
3495 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
3496 out to create
</a
> earlier this month. Several valuable testers showed
3497 up, and caused me to really want to to open up the development to more
3498 people. But before I did this, I want to come up with a sensible name
3499 for this project. Today I finally decided on a new name, and I have
3500 renamed the project from hw-support-handler to this new name. In the
3501 process, I moved the source to git and made it available as a
3502 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
3503 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
3504 To fetch and build the latest version of the source, use
</p
>
3507 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3508 cd isenkram
&& git-buildpackage -us -uc
3511 <p
>I have not yet adjusted all files to use the new name yet. If you
3512 want to hack on the source or improve the package, please go ahead.
3513 But please talk to me first on IRC or via email before you do major
3514 changes, to make sure we do not step on each others toes. :)
</p
>
3516 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
3517 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3518 stuff, in other words. I
've been told it is the Norwegian variant of
3519 the German word eisenkram, for those that are familiar with that
3522 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
3523 instructions, to avoid confusing people with an error from the signing
3526 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
3527 clone argument to avoid the need for authentication.
</p
>
3532 <title>First prototype ready making hardware easier to use in Debian
</title>
3533 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
3534 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
3535 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
3536 <description><p
>Early this month I set out to try to
3537 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
3538 the Debian support for pluggable hardware devices
</a
>. Now my
3539 prototype is working, and it is ready for a larger audience. To test
3541 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
3542 from the Debian Edu subversion repository
</a
>, build and install the
3543 package. You might have to log out and in again activate the
3544 autostart script.
</p
>
3546 <p
>The design is simple:
</p
>
3550 <li
>Add desktop entry in /usr/share/autostart/ causing a program
3551 hw-support-handlerd to start when the user log in.
</li
>
3553 <li
>This program listen for kernel events about new hardware (directly
3554 from the kernel like udev does), not using HAL dbus events as I
3555 initially did.
</li
>
3557 <li
>When new hardware is inserted, look up the hardware modalias in
3558 the APT database, a database
3559 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
3560 via HTTP
</a
> and a database available as part of the package.
</li
>
3562 <li
>If a package is mapped to the hardware in question, the package
3563 isn
't installed yet and this is the first time the hardware was
3564 plugged in, show a desktop notification suggesting to install the
3565 package or packages.
</li
>
3567 <li
>If the user click on the
'install package now
' button, ask
3568 aptdaemon via the PackageKit API to install the requrired package.
</li
>
3570 <li
>aptdaemon ask for root password or sudo password, and install the
3571 package while showing progress information in a window.
</li
>
3575 <p
>I still need to come up with a better name for the system. Here
3576 are some screen shots showing the prototype in action. First the
3577 notification, then the password request, and finally the request to
3578 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
3580 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
3581 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
3582 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
3583 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
3584 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
3586 <p
>The prototype still need to be improved with longer timeouts, but
3587 is already useful. The database of hardware to package mappings also
3588 need more work. It is currently compatible with the Ubuntu way of
3589 storing such information in the package control file, but could be
3590 changed to use other formats instead or in addition to the current
3591 method. I
've dropped the use of discover for this mapping, as the
3592 modalias approach is more flexible and easier to use on Linux as long
3593 as the Linux kernel expose its modalias strings directly.
</p
>
3595 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
3596 here is the command required to check out and build the source: Use
3597 '<tt
>svn checkout
3598 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3599 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
3600 devscripts package.
</p
>
3602 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
3603 renamed to Isenkram and the source moved from the Debian Edu
3604 subversion repository to a Debian collab-maint git repository. See
3605 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
3606 instructions
</a
> for details.
</p
>
3611 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
3612 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
3613 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
3614 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
3615 <description><p
>This Christmas my trusty old laptop died. It died quietly and
3616 suddenly in bed. With a quiet whimper, it went completely quiet and
3617 black. The power button was no longer able to turn it on. It was a
3618 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3619 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3620 Compaq I had before that. Now I need to find a replacement. To keep
3621 going during Christmas, I moved the one year old SSD disk to my old
3622 X40 where it fitted (only one I had left that could use it), but it is
3623 not a durable solution.
3625 <p
>My laptop needs are fairly modest. This is my wishlist from when I
3626 got a new one more than
10 years ago. It still holds true.:)
</p
>
3630 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
3631 than A4).
</li
>
3632 <li
>Robust, it will be in my backpack every day.
</li
>
3633 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
3634 <li
>Long battery life time. Preferable a week.
</li
>
3635 <li
>Internal WIFI network card.
</li
>
3636 <li
>Internal Twisted Pair network card.
</li
>
3637 <li
>Some USB slots (
2-
3 is plenty)
</li
>
3638 <li
>Good keyboard - similar to the Thinkpad.
</li
>
3639 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
3641 <li
>Hardware supported by Debian Stable, ie the default kernel and
3642 X.org packages.
</li
>
3643 <li
>Quiet, preferably fan free (or at least not using the fan most of
3648 <p
>You will notice that there are no RAM and CPU requirements in the
3649 list. The reason is simply that the specifications on laptops the
3650 last
10-
15 years have been sufficient for my needs, and I have to look
3651 at other features to choose my laptop. But are there still made as
3652 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3653 robust, and Thinkpads seem to be heading in the wrong direction since
3654 Lenovo took over. But I
've been told that X220 and X1 Carbon might
3655 still be useful.
</p
>
3657 <p
>Perhaps I should rethink my needs, and look for a pad with an
3658 external keyboard? I
'll have to check the
3659 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
3660 well-supported laptops, or perhaps just buy one preinstalled from one
3661 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
3662 Pre-loaded site
</a
>.
</p
>
3667 <title>How to find a browser plugin supporting a given MIME type
</title>
3668 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
3669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
3670 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
3671 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
3672 install to get support for a given MIME type. Thanks to
3673 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
3674 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
3675 Unfortunately, not very many packages provide the needed meta
3676 information, Anyway, here is a small script to look up all browser
3677 plugin packages announcing ther MIME support using this specification:
</p
>
3683 def pkgs_handling_mimetype(mimetype):
3688 version = pkg.candidate
3690 version = pkg.installed
3693 record = version.record
3694 if not record.has_key(
'Npp-MimeType
'):
3696 mime_types = record[
'Npp-MimeType
'].split(
',
')
3697 for t in mime_types:
3698 t = t.rstrip().strip()
3700 thepkgs.append(pkg.name)
3702 mimetype =
"audio/ogg
"
3703 if
1 < len(sys.argv):
3704 mimetype = sys.argv[
1]
3705 print
"Browser plugin packages supporting %s:
" % mimetype
3706 for pkg in pkgs_handling_mimetype(mimetype):
3707 print
" %s
" %pkg
3710 <p
>It can be used like this to look up a given MIME type:
</p
>
3713 % ./apt-find-browserplug-for-mimetype
3714 Browser plugin packages supporting audio/ogg:
3716 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3717 Browser plugin packages supporting application/x-shockwave-flash:
3718 browser-plugin-gnash
3722 <p
>In Ubuntu this mechanism is combined with support in the browser
3723 itself to query for plugins and propose to install the needed
3724 packages. It would be great if Debian supported such feature too. Is
3725 anyone working on adding it?
</p
>
3727 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
3728 request for icweasel support for this feature is
3729 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
3730 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
3731 of manpower and wish for a different design is the reason thus feature
3732 is not yet in iceweasel from Debian.
</p
>
3737 <title>What is the most supported MIME type in Debian?
</title>
3738 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
3739 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
3740 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
3741 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
3742 proposal to add AppStream information to the Debian archive
</a
>, is a
3743 proposal to make it possible for a Desktop application to propose to
3744 the user some package to install to gain support for a given MIME
3745 type, font, library etc. that is currently missing. With such
3746 mechanism in place, it would be possible for the desktop to
3747 automatically propose and install leocad if some LDraw file is
3748 downloaded by the browser.
</p
>
3750 <p
>To get some idea about the current content of the archive, I decided
3751 to write a simple program to extract all .desktop files from the
3752 Debian archive and look up the claimed MIME support there. The result
3754 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
3755 site
</a
>. Using the collected information, it become possible to
3756 answer the question in the title. Here are the
20 most supported MIME
3757 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3758 The complete list is available from the link above.
</p
>
3760 <p
><strong
>Debian Stable:
</strong
></p
>
3764 ----- -----------------------
3780 18 application/x-ogg
3787 <p
><strong
>Debian Testing:
</strong
></p
>
3791 ----- -----------------------
3807 18 application/x-ogg
3814 <p
><strong
>Debian Unstable:
</strong
></p
>
3818 ----- -----------------------
3835 18 application/x-ogg
3841 <p
>I am told that PackageKit can provide an API to access the kind of
3842 information mentioned in DEP-
11. I have not yet had time to look at
3843 it, but hope the PackageKit people in Debian are on top of these
3846 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
3847 discovering a typo in my script.
</p
>
3852 <title>Using modalias info to find packages handling my hardware
</title>
3853 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
3854 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
3855 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
3856 <description><p
>Yesterday, I wrote about the
3857 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
3858 values provided by the Linux kernel
</a
> following my hope for
3859 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
3860 dongle support in Debian
</a
>. Using this knowledge, I have tested how
3861 modalias values attached to package names can be used to map packages
3862 to hardware. This allow the system to look up and suggest relevant
3863 packages when I plug in some new hardware into my machine, and replace
3864 discover and discover-data as the database used to map hardware to
3867 <p
>I create a modaliases file with entries like the following,
3868 containing package name, kernel module name (if relevant, otherwise
3869 the package name) and globs matching the relevant hardware
3872 <p
><blockquote
>
3873 Package: package-name
3874 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
3875 </blockquote
></p
>
3877 <p
>It is fairly trivial to write code to find the relevant packages
3878 for a given modalias value using this file.
</p
>
3880 <p
>An entry like this would suggest the video and picture application
3881 cheese for many USB web cameras (interface bus class
0E01):
</p
>
3883 <p
><blockquote
>
3885 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
3886 </blockquote
></p
>
3888 <p
>An entry like this would suggest the pcmciautils package when a
3889 CardBus bridge (bus class
0607) PCI device is present:
</p
>
3891 <p
><blockquote
>
3892 Package: pcmciautils
3893 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3894 </blockquote
></p
>
3896 <p
>An entry like this would suggest the package colorhug-client when
3897 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
3899 <p
><blockquote
>
3900 Package: colorhug-client
3901 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
3902 </blockquote
></p
>
3904 <p
>I believe the format is compatible with the format of the Packages
3905 file in the Debian archive. Ubuntu already uses their Packages file
3906 to store their mappings from packages to hardware.
</p
>
3908 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3909 announce the hardware it support in a way my prototype understand.
3910 This allow those publishing packages in an APT source outside the
3911 Debian archive as well as those backporting packages to make sure the
3912 hardware mapping are included in the package meta information. I
've
3913 tested such header in the pymissile package, and its modalias mapping
3914 is working as it should with my prototype. It even made it to Ubuntu
3917 <p
>To test if it was possible to look up supported hardware using only
3918 the shell tools available in the Debian installer, I wrote a shell
3919 implementation of the lookup code. The idea is to create files for
3920 each modalias and let the shell do the matching. Please check out and
3922 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3923 shell script. It run without any extra dependencies and fetch the
3924 hardware mappings from the Debian archive and the subversion
3925 repository where I currently work on my prototype.
</p
>
3927 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3928 install yubikey-personalization:
</p
>
3930 <p
><blockquote
>
3931 % ./hw-support-lookup
3932 <br
>yubikey-personalization
3934 </blockquote
></p
>
3936 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3937 propose to install the pcmciautils package:
</p
>
3939 <p
><blockquote
>
3940 % ./hw-support-lookup
3941 <br
>pcmciautils
3943 </blockquote
></p
>
3945 <p
>If you know of any hardware-package mapping that should be added to
3946 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3947 database
</a
>, please tell me about it.
</p
>
3949 <p
>It could be possible to generate several of the mappings between
3950 packages and hardware. One source would be to look at packages with
3951 kernel modules, ie packages with *.ko files in /lib/modules/, and
3952 extract their modalias information. Another would be to look at
3953 packages with udev rules, ie packages with files in
3954 /lib/udev/rules.d/, and extract their vendor/model information to
3955 generate a modalias matching rule. I have not tested any of these to
3956 see if it work.
</p
>
3958 <p
>If you want to help implementing a system to let us propose what
3959 packages to install when new hardware is plugged into a Debian
3960 machine, please send me an email or talk to me on
3961 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3966 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3967 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3968 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3969 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3970 <description><p
>While looking into how to look up Debian packages based on hardware
3971 information, to find the packages that support a given piece of
3972 hardware, I refreshed my memory regarding modalias values, and decided
3973 to document the details. Here are my findings so far, also available
3975 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3976 Debian Edu subversion repository
</a
>:
3978 <p
><strong
>Modalias decoded
</strong
></p
>
3980 <p
>This document try to explain what the different types of modalias
3981 values stands for. It is in part based on information from
3982 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3983 &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;,
3984 &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
3985 &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;.
3987 <p
>The modalias entries for a given Linux machine can be found using
3988 this shell script:
</p
>
3991 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3994 <p
>The supported modalias globs for a given kernel module can be found
3995 using modinfo:
</p
>
3998 % /sbin/modinfo psmouse | grep alias:
3999 alias: serio:ty05pr*id*ex*
4000 alias: serio:ty01pr*id*ex*
4004 <p
><strong
>PCI subtype
</strong
></p
>
4006 <p
>A typical PCI entry can look like this. This is an Intel Host
4007 Bridge memory controller:
</p
>
4009 <p
><blockquote
>
4010 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4011 </blockquote
></p
>
4013 <p
>This represent these values:
</p
>
4018 sv
00001028 (subvendor)
4019 sd
000001AD (subdevice)
4021 sc
00 (bus subclass)
4025 <p
>The vendor/device values are the same values outputted from
'lspci
4026 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4027 0600. The
0600 class is a host bridge. Other useful bus values are
4028 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4030 <p
>Not sure how to figure out the interface value, nor what it
4033 <p
><strong
>USB subtype
</strong
></p
>
4035 <p
>Some typical USB entries can look like this. This is an internal
4036 USB hub in a laptop:
</p
>
4038 <p
><blockquote
>
4039 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4040 </blockquote
></p
>
4042 <p
>Here is the values included in this alias:
</p
>
4045 v
1D6B (device vendor)
4046 p
0001 (device product)
4048 dc
09 (device class)
4049 dsc
00 (device subclass)
4050 dp
00 (device protocol)
4051 ic
09 (interface class)
4052 isc
00 (interface subclass)
4053 ip
00 (interface protocol)
4056 <p
>The
0900 device class/subclass means hub. Some times the relevant
4057 class is in the interface class section. For a simple USB web camera,
4058 these alias entries show up:
</p
>
4060 <p
><blockquote
>
4061 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4062 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4063 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4064 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4065 </blockquote
></p
>
4067 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4068 camera),
0101 is audio control device and
0102 is audio streaming (aka
4069 microphone). Thus this is a camera with microphone included.
</p
>
4071 <p
><strong
>ACPI subtype
</strong
></p
>
4073 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
4074 receiver in a Thinkpad X40:
</p
>
4076 <p
><blockquote
>
4077 acpi:IBM0071:PNP0511:
4078 </blockquote
></p
>
4080 <p
>The values between the colons are IDs.
</p
>
4082 <p
><strong
>DMI subtype
</strong
></p
>
4084 <p
>The DMI table contain lots of information about the computer case
4085 and model. This is an entry for a IBM Thinkpad X40, fetched from
4086 /sys/devices/virtual/dmi/id/modalias:
</p
>
4088 <p
><blockquote
>
4089 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4090 </blockquote
></p
>
4092 <p
>The values present are
</p
>
4095 bvn IBM (BIOS vendor)
4096 bvr
1UETB
6WW(
1.66) (BIOS version)
4097 bd
06/
15/
2005 (BIOS date)
4098 svn IBM (system vendor)
4099 pn
2371H4G (product name)
4100 pvr ThinkPadX40 (product version)
4101 rvn IBM (board vendor)
4102 rn
2371H4G (board name)
4103 rvr NotAvailable (board version)
4104 cvn IBM (chassis vendor)
4105 ct
10 (chassis type)
4106 cvr NotAvailable (chassis version)
4109 <p
>The chassis type
10 is Notebook. Other interesting values can be
4110 found in the dmidecode source:
</p
>
4114 4 Low Profile Desktop
4127 17 Main Server Chassis
4128 18 Expansion Chassis
4130 20 Bus Expansion Chassis
4131 21 Peripheral Chassis
4133 23 Rack Mount Chassis
4142 <p
>The chassis type values are not always accurately set in the DMI
4143 table. For example my home server is a tower, but the DMI modalias
4144 claim it is a desktop.
</p
>
4146 <p
><strong
>SerIO subtype
</strong
></p
>
4148 <p
>This type is used for PS/
2 mouse plugs. One example is from my
4149 test machine:
</p
>
4151 <p
><blockquote
>
4152 serio:ty01pr00id00ex00
4153 </blockquote
></p
>
4155 <p
>The values present are
</p
>
4164 <p
>This type is supported by the psmouse driver. I am not sure what
4165 the valid values are.
</p
>
4167 <p
><strong
>Other subtypes
</strong
></p
>
4169 <p
>There are heaps of other modalias subtypes according to
4170 file2alias.c. There is the rest of the list from that source: amba,
4171 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4172 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4173 vmbus, x86cpu and zorro. I did not spend time documenting all of
4174 these, as they do not seem relevant for my intended use with mapping
4175 hardware to packages when new stuff is inserted during run time.
</p
>
4177 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
4179 <p
>To check which kernel modules provide support for a given modalias,
4180 one can use the following shell script:
</p
>
4183 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
4184 echo
"$id
" ; \
4185 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
4189 <p
>The output can look like this (only the first few entries as the
4190 list is very long on my test machine):
</p
>
4194 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
4196 FATAL: Module acpi:device: not found.
4198 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
4199 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
4200 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
4201 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4202 acpi:IBM0071:PNP0511:
4203 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
4204 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
4205 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
4209 <p
>If you want to help implementing a system to let us propose what
4210 packages to install when new hardware is plugged into a Debian
4211 machine, please send me an email or talk to me on
4212 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4214 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
4215 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
4216 in /sys/ with space in them.
</p
>
4221 <title>Moved the pymissile Debian packaging to collab-maint
</title>
4222 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
4223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
4224 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
4225 <description><p
>As part of my investigation on how to improve the support in Debian
4226 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4227 Launcher and updated the Debian package
4228 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
4229 sure udev will fix the device permissions when it is plugged in. I
4230 also added a
"Modaliases
" header to test it in the Debian archive and
4231 hopefully make the package be proposed by jockey in Ubuntu when a user
4232 plug in his rocket launcher. In the process I moved the source to a
4233 git repository under collab-maint, to make it easier for any DD to
4234 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
4235 is not very active, but the software still work for me even after five
4236 years of relative silence. The new git repository is not listed in
4237 the uploaded package yet, because I want to test the other changes a
4238 bit more before I upload the new version. If you want to check out
4239 the new version with a .desktop file included, visit the
4240 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
4241 view
</a
> or use
"<tt
>git clone
4242 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
4247 <title>Lets make hardware dongles easier to use in Debian
</title>
4248 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
4249 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
4250 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
4251 <description><p
>One thing that annoys me with Debian and Linux distributions in
4252 general, is that there is a great package management system with the
4253 ability to automatically install software packages by downloading them
4254 from the distribution mirrors, but no way to get it to automatically
4255 install the packages I need to use the hardware I plug into my
4256 machine. Even if the package to use it is easily available from the
4257 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4258 suggest to automatically install the python-nxt, nbc and t2n packages
4259 I need to talk to it. When I plug in a Yubikey, it could propose the
4260 yubikey-personalization package. The information required to do this
4261 is available, but no-one have pulled all the pieces together.
</p
>
4263 <p
>Some years ago, I proposed to
4264 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
4265 the discover subsystem to implement this
</a
>. The idea is fairly
4270 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
4271 starting when a user log in.
</li
>
4273 <li
>Set this program up to listen for kernel events emitted when new
4274 hardware is inserted into the computer.
</li
>
4276 <li
>When new hardware is inserted, look up the hardware ID in a
4277 database mapping to packages, and take note of any non-installed
4278 packages.
</li
>
4280 <li
>Show a message to the user proposing to install the discovered
4281 package, and make it easy to install it.
</li
>
4285 <p
>I am not sure what the best way to implement this is, but my
4286 initial idea was to use dbus events to discover new hardware, the
4287 discover database to find packages and
4288 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
4291 <p
>Yesterday, I found time to try to implement this idea, and the
4292 draft package is now checked into
4293 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4294 Debian Edu subversion repository
</a
>. In the process, I updated the
4295 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
4296 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4297 the relevant packages in Debian, and uploaded a new version
4298 2.2013.01.09 to unstable. I also discovered that the current
4299 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
4300 package in Debian no longer discovered any USB devices, because
4301 /proc/bus/usb/devices is no longer present. I ported it to use
4302 libusb as a fall back option to get it working. The fixed package
4303 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
4304 because of the freeze).
</p
>
4306 <p
>With this prototype in place, I can insert my Yubikey, and get this
4307 desktop notification to show up (only once, the first time it is
4308 inserted):
</p
>
4310 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
4312 <p
>For this prototype to be really useful, some way to automatically
4313 install the proposed packages by pressing the
"Please install
4314 program(s)
" button should to be implemented.
</p
>
4316 <p
>If this idea seem useful to you, and you want to help make it
4317 happen, please help me update the discover-data database with mappings
4318 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
4319 list the package you would like to have installed when a given
4320 hardware device is inserted into your computer, and report bugs using
4321 reportbug if it isn
't. Or, if you know of a better way to provide
4322 such mapping, please let me know.
</p
>
4324 <p
>This prototype need more work, and there are several questions that
4325 should be considered before it is ready for production use. Is dbus
4326 the correct way to detect new hardware? At the moment I look for HAL
4327 dbus events on the system bus, because that is the events I could see
4328 on my Debian Squeeze KDE desktop. Are there better events to use?
4329 How should the user be notified? Is the desktop notification
4330 mechanism the best option, or should the background daemon raise a
4331 popup instead? How should packages be installed? When should they
4332 not be installed?
</p
>
4334 <p
>If you want to help getting such feature implemented in Debian,
4335 please send me an email. :)
</p
>
4340 <title>New IRC channel for LEGO designers using Debian
</title>
4341 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
4342 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
4343 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
4344 <description><p
>During Christmas, I have worked a bit on the Debian support for
4345 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
4346 NXT
</a
>. My son and I have played a bit with my NXT set, and I
4347 discovered I had to build all the tools myself because none were
4348 already in Debian Squeeze. If Debian support for LEGO is something
4349 you care about, please join me on the IRC channel
4350 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
4351 irc.debian.org). There is a lot that could be done to improve the
4352 Debian support for LEGO designers. For example both CAD software
4353 and Mindstorm compilers are missing. :)
</p
>
4355 <p
>Update
2012-
01-
03: A
4356 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
4357 including links to Lego related packages is now available.
</p
>
4362 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
4363 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
4364 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
4365 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
4366 <description><p
>Let me start by wishing you all marry Christmas and a happy new
4367 year! I hope next year will prove to be a good year.
</p
>
4369 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
4370 decentralised
"currency
" that allow people to transfer bitcoins
4371 between each other with minimal overhead, is a very interesting
4372 experiment. And as I wrote a few days ago, the bitcoin situation in
4373 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
4374 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
4375 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
4376 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
4377 for one of the ftpmasters to approve the new bitcoin-qt package
4380 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
4381 team in Debian, you can easily test the package in Debian Squeeze
4382 using the following steps to get a set of working packages:
</p
>
4384 <blockquote
><pre
>
4385 git clone git://git.debian.org/git/collab-maint/bitcoin
4387 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4388 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4389 </pre
></blockquote
>
4391 <p
>You might have to install some build dependencies as well. The
4392 list of commands should give you two packages, bitcoind and
4393 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4394 client will download the complete set of bitcoin
"blocks
", which need
4395 around
5.6 GiB of data on my machine at the moment. Make sure your
4396 ~/.bitcoin/ directory have lots of spare room if you want to download
4397 all the blocks. The client will warn if the disk is getting full, so
4398 there is not really a problem if you got too little room, but you will
4399 not be able to get all the features out of the client.
</p
>
4401 <p
>As usual, if you use bitcoin and want to show your support of my
4402 activities, please send Bitcoin donations to my address
4403 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4408 <title>A word on bitcoin support in Debian
</title>
4409 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
4410 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
4411 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
4412 <description><p
>It has been a while since I wrote about
4413 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
4414 peer-to-peer based crypto-currency, and the reason is simply that I
4415 have been busy elsewhere. But two days ago, I started looking at the
4416 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
4417 Debian
</a
> again to try to recover my old bitcoin wallet. The package
4418 is now maintained by a
4419 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
4420 people
</a
>, and the grunt work had already been done by this team. We
4421 owe a huge thank you to all these team members. :)
4422 But I was sad to discover that the bitcoin client is missing in
4423 Wheezy. It is only available in Sid (and an outdated client from
4424 backports). The client had several RC bugs registered in BTS blocking
4425 it from entering testing. To try to help the team and improve the
4426 situation, I spent some time providing patches and triaging the bug
4427 reports. I also had a look at the bitcoin package available from Matt
4429 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
4430 Ubuntu
</a
>, and moved the useful pieces from that version into the
4431 Debian package.
</p
>
4433 <p
>After checking with the main package maintainer Jonas Smedegaard on
4434 IRC, I pushed several patches into the collab-maint git repository to
4435 improve the package. It now contains fixes for the RC issues (not from
4436 me, but fixed by Scott Howard), build rules for a Qt GUI client
4437 package, konqueror support for the bitcoin: URI and bash completion
4438 setup. As I work on Debian Squeeze, I also created
4439 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
4440 patch to backport
</a
> the latest version. Jonas is going to look at
4441 it and try to integrate it into the git repository before uploading a
4442 new version to unstable.
4444 <p
>I would very much like bitcoin to succeed, to get rid of the
4445 centralized control currently exercised in the monetary system. I
4446 find it completely unacceptable that the USA government is collecting
4447 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4448 that the major credit card companies can block legal money
4449 transactions to Wikileaks. But for bitcoin to succeed, more people
4450 need to use bitcoins, and more people need to accept bitcoins when
4451 they sell products and services. Improving the bitcoin support in
4452 Debian is a small step in the right direction, but not enough.
4453 Unfortunately the user experience when browsing the web and wanting to
4454 pay with bitcoin is still not very good. The bitcoin: URI is a step
4455 in the right direction, but need to work in most or every browser in
4456 use. Also the bitcoin-qt client is too heavy to fire up to do a
4457 quick transaction. I believe there are other clients available, but
4458 have not tested them.
</p
>
4461 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
4462 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
4463 I received
20.15 BTC so far on the address I provided in my blog two
4464 years ago, as can be
4465 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
4466 on the blockexplorer service
</a
>. Thank you everyone for your
4467 donation. The blockexplorer service demonstrates quite well that
4468 bitcoin is not quite anonymous and untracked. :) I wonder if the
4469 number of users have gone up since then. If you use bitcoin and want
4470 to show your support of my activity, please send Bitcoin donations to
4471 the same address as last time,
4472 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4477 <title>Git repository for song book for Computer Scientists
</title>
4478 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
4479 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
4480 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
4481 <description><p
>As I
4482 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
4483 this summer
</a
>, I have created a Computer Science song book a few
4484 years ago, and today I finally found time to create a public
4485 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
4486 repository for the project
</a
>.
</p
>
4488 <p
>If you want to help out, please clone the source and submit patches
4489 to the HTML version. To generate the PDF and PostScript version,
4490 please use prince XML, or let me know about a useful free software
4491 processor capable of creating a good looking PDF from the HTML.
</p
>
4493 <p
>Want to sing? You can still find the song book in HTML, PDF and
4494 PostScript formats at
4495 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
4496 Science Songbook
</a
>.
</p
>
4501 <title>Gratulerer med
19-årsdagen, Debian!
</title>
4502 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
4503 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
4504 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
4505 <description><p
>I dag fyller
4506 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
4507 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
4508 si gratulerer med dagen, Debian!
</p
>
4513 <title>Song book for Computer Scientists
</title>
4514 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
4515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
4516 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
4517 <description><p
>Many years ago, while studying Computer Science at the
4518 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
4519 collecting computer related songs for use at parties. The original
4520 version was written in LaTeX, but a few years ago I got help from
4521 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4522 while keeping the ability to create a nice book in PDF format. I have
4523 not had time to maintain the book for a while now, and guess I should
4524 put it up on some public version control repository where others can
4525 help me extend and update the book. If anyone is volunteering to help
4526 me with this, send me an email. Also let me know if there are songs
4527 missing in my book.
</p
>
4529 <p
>I have not mentioned the book on my blog so far, and it occured to
4530 me today that I really should let all my readers share the joys of
4531 singing out load about programming, computers and computer networks.
4532 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
4533 12</a
> is about to start (and I am not going). Want to sing? Check
4534 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
4535 Computer Science Songbook
</a
>.
4540 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
4541 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
4542 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
4543 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
4544 <description><p
>At work we have heaps of servers. I believe the total count is
4545 around
1000 at the moment. To be able to get help from the vendors
4546 when something go wrong, we want to keep the firmware on the servers
4547 up to date. If the firmware isn
't the latest and greatest, the
4548 vendors typically refuse to start debugging any problems until the
4549 firmware is upgraded. So before every reboot, we want to upgrade the
4550 firmware, and we would really like everyone handling servers at the
4551 university to do this themselves when they plan to reboot a machine.
4552 For that to happen we at the unix server admin group need to provide
4553 the tools to do so.
</p
>
4555 <p
>To make firmware upgrading easier, I am working on a script to
4556 fetch and install the latest firmware for the servers we got. Most of
4557 our hardware are from Dell and HP, so I have focused on these servers
4558 so far. This blog post is about the Dell part.
</P
>
4560 <p
>On the Dell FTP site I was lucky enough to find
4561 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
4562 with firmware information for all
11th generation servers, listing
4563 which firmware should be used on a given model and where on the FTP
4564 site I can find it. Using a simple perl XML parser I can then
4565 download the shell scripts Dell provides to do firmware upgrades from
4566 within Linux and reboot when all the firmware is primed and ready to
4567 be activated on the first reboot.
</p
>
4569 <p
>This is the Dell related fragment of the perl code I am working on.
4570 Are there anyone working on similar tools for firmware upgrading all
4571 servers at a site? Please get in touch and lets share resources.
</p
>
4573 <p
><pre
>
4577 use File::Temp qw(tempdir);
4579 # Install needed RHEL packages if missing
4581 'XML::Simple
' =
> 'perl-XML-Simple
',
4583 for my $module (keys %rhelmodules) {
4584 eval
"use $module;
";
4586 my $pkg = $rhelmodules{$module};
4587 system(
"yum install -y $pkg
");
4588 eval
"use $module;
";
4592 my $errorsto =
'pere@hungry.com
';
4598 sub run_firmware_script {
4599 my ($opts, $script) = @_;
4601 print STDERR
"fail: missing script name\n
";
4604 print STDERR
"Running $script\n\n
";
4606 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
4607 print STDERR
"success: firmware script ran succcessfully\n
";
4609 print STDERR
"fail: firmware script returned error\n
";
4613 sub run_firmware_scripts {
4614 my ($opts, @dirs) = @_;
4615 # Run firmware packages
4616 for my $dir (@dirs) {
4617 print STDERR
"info: Running scripts in $dir\n
";
4618 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
4619 while (my $s = readdir $dh) {
4620 next if $s =~ m/^\.\.?/;
4621 run_firmware_script($opts,
"$dir/$s
");
4629 print STDERR
"info: Downloading $url\n
";
4630 system(
"wget --quiet \
"$url\
"");
4635 my $product = `dmidecode -s system-product-name`;
4638 if ($product =~ m/PowerEdge/) {
4640 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4641 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
4643 my $tmpdir = tempdir(
4647 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
4648 system(
'gunzip Catalog.xml.gz
');
4649 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
4650 # -q is quiet, disabling interactivity and reducing console output
4651 my $fwopts =
"-q
";
4653 for my $url (@paths) {
4654 fetch_dell_fw($url);
4656 run_firmware_scripts($fwopts, $tmpdir);
4658 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4659 print STDERR
"error: Please report to $errorsto.\n
";
4663 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4664 print STDERR
"error: Please report to $errorsto.\n
";
4670 my $url =
"ftp://ftp.us.dell.com/$path
";
4674 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4675 # firmware packages to download from Dell. Only work for Linux
4676 # machines and
11th generation Dell servers.
4677 sub fetch_dell_fw_list {
4678 my $filename = shift;
4680 my $product = `dmidecode -s system-product-name`;
4682 my ($mybrand, $mymodel) = split(/\s+/, $product);
4684 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
4686 my $xml = XMLin($filename);
4688 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
4689 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
4690 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
4692 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
4693 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
4695 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
4697 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
4699 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
4702 for my $component (@{$xml-
>{SoftwareComponent}}) {
4703 my $componenttype = $component-
>{ComponentType}-
>{value};
4705 # Drop application packages, only firmware and BIOS
4706 next if
'APAC
' eq $componenttype;
4708 my $cpath = $component-
>{path};
4709 for my $path (@paths) {
4710 if ($cpath =~ m%/$path$%) {
4711 push(@paths, $cpath);
4719 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
4720 it could work on other platforms with some tweaking. Anyone know a
4721 index like Catalog.xml is available from HP for HP servers? At the
4722 moment I maintain a similar list manually and it is quickly getting
4728 <title>How is booting into runlevel
1 different from single user boots?
</title>
4729 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
4730 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
4731 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
4732 <description><p
>Wouter Verhelst have some
4733 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
4734 comments and opinions
</a
> on my blog post on
4735 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
4736 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
4737 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
4738 default KDE desktop in Debian
</a
>. I only have time to address one
4739 small piece of his comment now, and though it best to address the
4740 misunderstanding he bring forward:
</p
>
4742 <p
><blockquote
>
4743 Currently, a system admin has four options: [...] boot to a
4744 single-user system (by adding
'single
' to the kernel command line;
4745 this runs rcS and rc1 scripts)
4746 </blockquote
></p
>
4748 <p
>This make me believe Wouter believe booting into single user mode
4749 and booting into runlevel
1 is the same. I am not surprised he
4750 believe this, because it would make sense and is a quite sensible
4751 thing to believe. But because the boot in Debian is slightly broken,
4752 runlevel
1 do not work properly and it isn
't the same as single user
4753 mode. I
'll try to explain what is actually happing, but it is a bit
4754 hard to explain.
</p
>
4756 <p
>Single user mode is defined like this in /etc/inittab:
4757 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
4758 executed in single user mode is sulogin. Single user mode is a boot
4759 state
"between
" the runlevels, and when booting into single user mode,
4760 only the scripts in /etc/rcS.d/ are executed before the init process
4761 enters the single user state. When switching to runlevel
1, the state
4762 is in fact not ending in runlevel
1, but it passes through runlevel
1
4763 and end up in the single user mode (see /etc/rc1.d/S03single, which
4764 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
4765 1. It is confusing that the
'S
' (single user) init mode is not the
4766 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4769 <p
>This summary might make it clearer. When booting for the first
4770 time into single user mode, the following commands are executed:
4771 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
4772 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
4773 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
4774 trying to continue after visiting single user mode. Not all services
4775 are started again as they should, causing the machine to end up in an
4776 unpredicatble state. This is why Debian admins recommend rebooting
4777 after visiting single user mode.
</p
>
4779 <p
>A similar problem with runlevel
1 is caused by the amount of
4780 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
4781 to runlevel
1, the services started from /etc/rcS.d/ are not properly
4782 stopped when passing through the scripts in /etc/rc1.d/, and not
4783 started again when switching away from runlevel
1 to the runlevels
4784 2-
5. I believe the problem is best fixed by moving all the scripts
4785 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
4786 functioning single user mode during boot.
</p
>
4788 <p
>I have spent several years investigating the Debian boot system,
4789 and discovered this problem a few years ago. I suspect it originates
4790 from when sysvinit was introduced into Debian, a long time ago.
</p
>
4795 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
4796 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
4797 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
4798 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
4799 <description><p
>In the Debian boot system, several packages include scripts that
4800 are started from /etc/rcS.d/. In fact, there is a bite more of them
4801 than make sense, and this causes a few problems. What kind of
4802 problems, you might ask. There are at least two problems. The first
4803 is that it is not possible to recover a machine after switching to
4804 runlevel
1. One need to actually reboot to get the machine back to
4805 the expected state. The other is that single user boot will sometimes
4806 run into problems because some of the subsystems are activated before
4807 the root login is presented, causing problems when trying to recover a
4808 machine from a problem in that subsystem. A minor additional point is
4809 that moving more scripts out of rcS.d/ and into the other rc#.d/
4810 directories will increase the amount of scripts that can run in
4811 parallel during boot, and thus decrease the boot time.
</p
>
4813 <p
>So, which scripts should start from rcS.d/. In short, only the
4814 scripts that _have_ to execute before the root login prompt is
4815 presented during a single user boot should go there. Everything else
4816 should go into the numeric runlevels. This means things like
4817 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4818 the numeric runlevels. Today in Debian, there are around
115 init.d
4819 scripts that are started from rcS.d/, and most of them should be moved
4820 out. Do your package have one of them? Please help us make single
4821 user and runlevel
1 better by moving it.
</p
>
4823 <p
>Scripts setting up the screen, keyboard, system partitions
4824 etc. should still be started from rcS.d/, but there is for example no
4825 need to have the network enabled before the single user login prompt
4826 is presented.
</p
>
4828 <p
>As always, things are not so easy to fix as they sound. To keep
4829 Debian systems working while scripts migrate and during upgrades, the
4830 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4831 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4832 and the next ones can only be moved when their dependencies have been
4833 moved first. This migration must be done sequentially while we ensure
4834 that the package system upgrade packages in the right order to keep
4835 the system state correct. This will require some coordination when it
4836 comes to network related packages, but most of the packages with
4837 scripts that should migrate do not have anything in rcS.d/ depending
4838 on them. Some packages have already been updated, like the sudo
4839 package, while others are still left to do. I wish I had time to work
4840 on this myself, but real live constrains make it unlikely that I will
4841 find time to push this forward.
</p
>
4846 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
4847 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
4848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
4849 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
4850 <description><p
>While at Debconf11, I have several times during discussions
4851 mentioned the issues I believe should be improved in Debian for its
4852 desktop to be useful for more people. The use case for this is my
4853 parents, which are currently running Kubuntu which solve the
4856 <p
>I suspect these four missing features are not very hard to
4857 implement. After all, they are present in Ubuntu, so if we wanted to
4858 do this in Debian we would have a source.
</p
>
4862 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
4863 are new packages available for upgrades, a icon in the KDE status bar
4864 indicate this, and clicking on it will activate the simple upgrade
4865 tool to handle it. I have no problem guiding both of my parents
4866 through the process over the phone. If a kernel reboot is required,
4867 this too is indicated by the status bars and the upgrade tool. Last
4868 time I checked, nothing with the same features was working in KDE in
4871 <li
><strong
>Simple handling of missing Firefox browser
4872 plugins.
</strong
> When the browser encounter a MIME type it do not
4873 currently have a handler for, it will ask the user if the system
4874 should search for a package that would add support for this MIME type,
4875 and if the user say yes, the APT sources will be searched for packages
4876 advertising the MIME type in their control file (visible in the
4877 Packages file in the APT archive). If one or more packages are found,
4878 it is a simple click of the mouse to add support for the missing mime
4879 type. If the package require the user to accept some non-free
4880 license, this is explained to the user. The entire process make it
4881 more clear to the user why something do not work in the browser, and
4882 make the chances higher for the user to blame the web page authors and
4883 not the browser for any missing features.
</li
>
4885 <li
><strong
>Simple handling of missing multimedia codec/format
4886 handlers.
</strong
> When the media players encounter a format or codec
4887 it is not supporting, a dialog pop up asking the user if the system
4888 should search for a package that would add support for it. This
4889 happen with things like MP3, Windows Media or H
.264. The selection
4890 and installation procedure is very similar to the Firefox browser
4891 plugin handling. This is as far as I know implemented using a
4892 gstreamer hook. The end result is that the user easily get access to
4893 the codecs that are present from the APT archives available, while
4894 explaining more on why a given format is unsupported by Ubuntu.
</li
>
4896 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
4897 displaying a text/plain file in my Debian browser, it will propose to
4898 start emacs to show it. If I remember correctly, when doing the same
4899 in Kunbutu it show the file as a text file in the browser. At least I
4900 know Opera will show text files within the browser. I much prefer the
4901 latter behaviour.
</li
>
4905 <p
>There are other nice features as well, like the simplified suite
4906 upgrader, but given that I am the one mostly doing the dist-upgrade,
4907 it do not matter much.
</p
>
4909 <p
>I really hope we could get these features in place for the next
4910 Debian release. It would require the coordinated effort of several
4911 maintainers, but would make the end user experience a lot better.
</p
>
4916 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4917 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4918 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4919 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4920 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4921 site is build on Debian/Squeeze, and this platform was chosen because
4922 I am most familiar with Debian (being a Debian Developer for around
10
4923 years) because it is the latest stable Debian release which should get
4924 security support for a few years.
</p
>
4926 <p
>The web service is written in Perl, and depend on some perl modules
4927 that are missing in Debian at the moment. It would be great if these
4928 modules were added to the Debian archive, allowing anyone to set up
4929 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4930 in their own country using only Debian packages. The list of modules
4931 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4932 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4933 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4934 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4935 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4936 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4937 easier in the future.
</p
>
4939 <p
>Thanks to the great tools in Debian, getting the missing modules
4940 installed on my server was a simple call to
'cpan2deb Module::Name
'
4941 and
'dpkg -i
' to install the resulting package. But this leave me
4942 with the responsibility of tracking security problems, which I really
4943 do not have time for.
</p
>
4948 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4949 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4951 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4952 <description><p
>Here is a small update for my English readers. Most of my blog
4953 posts have been in Norwegian the last few weeks, so here is a short
4954 update in English.
</p
>
4956 <p
>The kids still keep me too busy to get much free software work
4957 done, but I did manage to organise a project to get a Norwegian port
4958 of the British service
4959 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4960 and it has been running for a month now. The entire project has been
4961 organised by me and two others. Around Christmas we gathered sponsors
4962 to fund the development work. In January I drafted a contract with
4963 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4964 and in February the development took place. Most of it involved
4965 converting the source to use GPS coordinates instead of British
4966 easting/northing, and the resulting code should be a lot easier to get
4967 running in any country by now. The Norwegian
4968 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4969 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4970 source and the source for administrative borders in Norway, and
4971 support for this had to be added/fixed.
</p
>
4973 <p
>The Norwegian version went live March
3th, and we spent the weekend
4974 polishing the system before we announced it March
7th. The system is
4975 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4976 problem reports in a few weeks. Soon we hope to announce the Android
4977 and iPhone versions making it even easier to report problems with the
4978 public infrastructure.
</p
>
4980 <p
>Perhaps something to consider for those of you in countries without
4981 such service?
</p
>
4986 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4987 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4988 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4989 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4990 <description><p
>The last few days I have looked at ways to track open security
4991 issues here at my work with the University of Oslo. My idea is that
4992 it should be possible to use the information about security issues
4993 available on the Internet, and check our locally
4994 maintained/distributed software against this information. It should
4995 allow us to verify that no known security issues are forgotten. The
4996 CVE database listing vulnerabilities seem like a great central point,
4997 and by using the package lists from Debian mapped to CVEs provided by
4998 the testing security team, I believed it should be possible to figure
4999 out which security holes were present in our free software
5000 collection.
</p
>
5002 <p
>After reading up on the topic, it became obvious that the first
5003 building block is to be able to name software packages in a unique and
5004 consistent way across data sources. I considered several ways to do
5005 this, for example coming up with my own naming scheme like using URLs
5006 to project home pages or URLs to the Freshmeat entries, or using some
5007 existing naming scheme. And it seem like I am not the first one to
5008 come across this problem, as MITRE already proposed and implemented a
5009 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5010 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5011 software, hardware and other platform components. The CPE ids are
5012 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5013 Vulnerability Database
</a
>, allowing me to look up know security
5014 issues for any CPE name. With this in place, all I need to do is to
5015 locate the CPE id for the software packages we use at the university.
5016 This is fairly trivial (I google for
'cve cpe $package
' and check the
5017 NVD entry if a CVE for the package exist).
</p
>
5019 <p
>To give you an example. The GNU gzip source package have the CPE
5020 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5021 check out, one could look up
5022 <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
5023 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5024 The most recent one is
5025 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5026 and at the bottom of the NVD page for this vulnerability the complete
5027 list of affected versions is provided.
</p
>
5029 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5030 for offline processing of issues. Using this dump, I
've written a
5031 small script taking a list of CPEs as input and list all CVEs
5032 affecting the packages represented by these CPEs. One give it CPEs
5033 with version numbers as specified above and get a list of open
5034 security issues out.
</p
>
5036 <p
>Of course for this approach to be useful, the quality of the NVD
5037 information need to be high. For that to happen, I believe as many as
5038 possible need to use and contribute to the NVD database. I notice
5040 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5041 map from CVE to CPE
</a
>, indicating that they are using the CPE
5042 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5044 <p
>To get an idea about the quality for free software, I spent some
5045 time making it possible to compare the CVE database from Debian with
5046 the CVE database in NVD. The result look fairly good, but there are
5047 some inconsistencies in NVD (same software package having several
5048 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5049 Debian believe are affected by a CVE). Hope to find time to improve
5050 the quality of NVD, but that require being able to get in touch with
5051 someone maintaining it. So far my three emails with questions and
5052 corrections have not seen any reply, but I hope contact can be
5053 established soon.
</p
>
5055 <p
>An interesting application for CPEs is cross platform package
5056 mapping. It would be useful to know which packages in for example
5057 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5058 this would be trivial if all linux distributions provided CPE entries
5059 for their packages.
</p
>
5064 <title>Which module is loaded for a given PCI and USB device?
</title>
5065 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5066 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5067 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5068 <description><p
>In the
5069 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5070 package in Debian, there is a script to report useful information
5071 about the running hardware for use when people report missing
5072 information. One part of this script that I find very useful when
5073 debugging hardware problems, is the part mapping loaded kernel module
5074 to the PCI device it claims. It allow me to quickly see if the kernel
5075 module I expect is driving the hardware I am struggling with. To see
5076 the output, make sure discover-data is installed and run
5077 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
5078 one of my machines like this:
</p
>
5082 10de:
03eb i2c_nforce2
5085 10de:
03f0 snd_hda_intel
5094 <p
>The code in question look like this, slightly modified for
5095 readability and to drop the output to file descriptor
3:
</p
>
5098 if [ -d /sys/bus/pci/devices/ ] ; then
5099 echo loaded pci modules:
5101 cd /sys/bus/pci/devices/
5102 for address in * ; do
5103 if [ -d
"$address/driver/module
" ] ; then
5104 module=`cd $address/driver/module ; pwd -P | xargs basename`
5105 if grep -q
"^$module
" /proc/modules ; then
5106 address=$(echo $address |sed s/
0000://)
5107 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
5108 echo
"$id $module
"
5117 <p
>Similar code could be used to extract USB device module
5121 if [ -d /sys/bus/usb/devices/ ] ; then
5122 echo loaded usb modules:
5124 cd /sys/bus/usb/devices/
5125 for address in * ; do
5126 if [ -d
"$address/driver/module
" ] ; then
5127 module=`cd $address/driver/module ; pwd -P | xargs basename`
5128 if grep -q
"^$module
" /proc/modules ; then
5129 address=$(echo $address |sed s/
0000://)
5130 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
5131 if [
"$id
" ] ; then
5132 echo
"$id $module
"
5142 <p
>This might perhaps be something to include in other tools as
5148 <title>How to test if a laptop is working with Linux
</title>
5149 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
5150 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
5151 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
5152 <description><p
>The last few days I have spent at work here at the
<a
5153 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
5154 batch of computers will work with Linux. Every year for the last few
5155 years the university have organised shared bid of a few thousand
5156 computers, and this year HP won the bid. Two different desktops and
5157 five different laptops are on the list this year. We in the UNIX
5158 group want to know which one of these computers work well with RHEL
5159 and Ubuntu, the two Linux distributions we currently handle at the
5160 university.
</p
>
5162 <p
>My test method is simple, and I share it here to get feedback and
5163 perhaps inspire others to test hardware as well. To test, I PXE
5164 install the OS version of choice, and log in as my normal user and run
5165 a few applications and plug in selected pieces of hardware. When
5166 something fail, I make a note about this in the test matrix and move
5167 on. If I have some spare time I try to report the bug to the OS
5168 vendor, but as I only have the machines for a short time, I rarely
5169 have the time to do this for all the problems I find.
</p
>
5171 <p
>Anyway, to get to the point of this post. Here is the simple tests
5172 I perform on a new model.
</p
>
5176 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
5177 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5178 RHEL5 and Debian Edu/Squeeze.
</li
>
5180 <li
>Is X.org working? If the graphical login screen show up after
5181 installation, X.org is working.
</li
>
5183 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
5184 package mesa-utils on Ubuntu) and writing down the frames per second
5185 reported by the program.
</li
>
5187 <li
>Is sound working? With Gnome and KDE, a sound is played when
5188 logging in, and if I can hear this the test is successful. If there
5189 are several audio exits on the machine, I try them all and check if
5190 the Gnome/KDE audio mixer can control where to send the sound. I
5191 normally test this by playing
5192 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
5193 video
</a
> in Firefox/Iceweasel.
</li
>
5195 <li
>Is the USB subsystem working? I test this by plugging in a USB
5196 memory stick and see if Gnome/KDE notices this.
</li
>
5198 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
5199 I have lying around, and see if Gnome/KDE notices this.
</li
>
5201 <li
>Is any built in camera working? Test using cheese, and see if a
5202 picture from the v4l device show up.
</li
>
5204 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5205 any bluetooth devices are discovered. In my office, I normally see a
5208 <li
>For laptops, is the SD or Compaq Flash reader working. I have
5209 memory modules lying around, and stick them in and see if Gnome/KDE
5210 notice this.
</li
>
5212 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
5213 special button work, and if the laptop continue to work after
5216 <li
>For laptops, is the extra buttons working, like audio level,
5217 adjusting background light, switching on/off external video output,
5218 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5219 laptop to laptop, so I just write down which are working and which are
5222 <li
>Some laptops have smart card readers, finger print readers,
5223 acceleration sensors etc. I rarely test these, as I do not know how
5224 to quickly test if they are working or not, so I only document their
5225 existence.
</li
>
5229 <p
>By now I suspect you are really curious what the test results are
5230 for the HP machines I am testing. I
'm not done yet, so I will report
5231 the test results later. For now I can report that HP
8100 Elite work
5232 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
5233 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
5234 can see, I have most machines left to test. One interesting
5235 observation is that Ubuntu Lucid has almost twice the frame rate than
5236 RHEL6 with glxgears. No idea why.
</p
>
5241 <title>Some thoughts on BitCoins
</title>
5242 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
5243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
5244 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
5245 <description><p
>As I continue to explore
5246 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
5247 what properties the system have, and how it will be affected by laws
5248 and regulations here in Norway. Here are some random notes.
</p
>
5250 <p
>One interesting thing to note is that since the transactions are
5251 verified using a peer to peer network, all details about a transaction
5252 is known to everyone. This means that if a BitCoin address has been
5253 published like I did with mine in my initial post about BitCoin, it is
5254 possible for everyone to see how many BitCoins have been transfered to
5255 that address. There is even a web service to look at the details for
5256 all transactions. There I can see that my address
5257 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
5258 have received
16.06 Bitcoin, the
5259 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
5260 address of Simon Phipps have received
181.97 BitCoin and the address
5261 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
5262 of EFF have received
2447.38 BitCoins so far. Thank you to each and
5263 every one of you that donated bitcoins to support my activity. The
5264 fact that anyone can see how much money was transfered to a given
5265 address make it more obvious why the BitCoin community recommend to
5266 generate and hand out a new address for each transaction. I
'm told
5267 there is no way to track which addresses belong to a given person or
5268 organisation without the person or organisation revealing it
5269 themselves, as Simon, EFF and I have done.
</p
>
5271 <p
>In Norway, and in most other countries, there are laws and
5272 regulations limiting how much money one can transfer across the border
5273 without declaring it. There are money laundering, tax and accounting
5274 laws and regulations I would expect to apply to the use of BitCoin.
5275 If the Skolelinux foundation
5276 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
5277 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
5278 normal bank transfers like EFF is doing, how should this be accounted?
5279 Given that it is impossible to know if money can cross the border or
5280 not, should everything or nothing be declared? What exchange rate
5281 should be used when calculating taxes? Would receivers have to pay
5282 income tax if the foundation were to pay Skolelinux contributors in
5283 BitCoin? I have no idea, but it would be interesting to know.
</p
>
5285 <p
>For a currency to be useful and successful, it must be trusted and
5286 accepted by a lot of users. It must be possible to get easy access to
5287 the currency (as a wage or using currency exchanges), and it must be
5288 easy to spend it. At the moment BitCoin seem fairly easy to get
5289 access to, but there are very few places to spend it. I am not really
5290 a regular user of any of the vendor types currently accepting BitCoin,
5291 so I wonder when my kind of shop would start accepting BitCoins. I
5292 would like to buy electronics, travels and subway tickets, not herbs
5293 and books. :) The currency is young, and this will improve over time
5294 if it become popular, but I suspect regular banks will start to lobby
5295 to get BitCoin declared illegal if it become popular. I
'm sure they
5296 will claim it is helping fund terrorism and money laundering (which
5297 probably would be true, as is any currency in existence), but I
5298 believe the problems should be solved elsewhere and not by blaming
5299 currencies.
</p
>
5301 <p
>The process of creating new BitCoins is called mining, and it is
5302 CPU intensive process that depend on a bit of luck as well (as one is
5303 competing against all the other miners currently spending CPU cycles
5304 to see which one get the next lump of cash). The
"winner
" get
50
5305 BitCoin when this happen. Yesterday I came across the obvious way to
5306 join forces to increase ones changes of getting at least some coins,
5307 by coordinating the work on mining BitCoins across several machines
5308 and people, and sharing the result if one is lucky and get the
50
5310 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
5311 if this sounds interesting. I have not had time to try to set up a
5312 machine to participate there yet, but have seen that running on ones
5313 own for a few days have not yield any BitCoins througth mining
5316 <p
>Update
2010-
12-
15: Found an
<a
5317 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
5318 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
5319 it was interesting to read. The arguments presented seem to be
5320 equally valid for gold, which was used as a currency for many years.
</p
>
5325 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
5326 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
5327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
5328 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
5329 <description><p
>With this weeks lawless
5330 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
5331 attacks
</a
> on Wikileak and
5332 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
5333 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
5334 not be trusted to handle money transactions.
5336 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
5337 Phipps on bitcoin
</a
> reminded me about a project that a friend of
5338 mine mentioned earlier. I decided to follow Simon
's example, and get
5339 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
5340 some help from my friend to get it all running, and he even handed me
5341 some bitcoins to get started. I even donated a few bitcoins to Simon
5342 for helping me remember BitCoin.
</p
>
5344 <p
>So, what is bitcoins, you probably wonder? It is a digital
5345 crypto-currency, decentralised and handled using peer-to-peer
5346 networks. It allows anonymous transactions and prohibits central
5347 control over the transactions, making it impossible for governments
5348 and companies alike to block donations and other transactions. The
5349 source is free software, and while the key dependency wxWidgets
2.9
5350 for the graphical user interface is missing in Debian, the command
5351 line client builds just fine. Hopefully Jonas
5352 <a href=
"http://bugs.debian.org/
578157">will get the package into
5353 Debian
</a
> soon.
</p
>
5355 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
5356 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
5357 bitcoins
</a
> when selling services and goods, and there are even
5358 currency
"stock
" markets where the exchange rate is decided. There
5359 are not many users so far, but the concept seems promising. If you
5360 want to get started and lack a friend with any bitcoins to spare,
5362 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
5363 bitcoin at the time of writing). Use
5364 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
5365 on the current exchange rates.
</p
>
5367 <p
>As an experiment, I have decided to set up bitcoind on one of my
5368 machines. If you want to support my activity, please send Bitcoin
5369 donations to the address
5370 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
5375 <title>Why isn
't Debian Edu using VLC?
</title>
5376 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
5377 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
5378 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
5379 <description><p
>In the latest issue of Linux Journal, the readers choices were
5380 presented, and the winner among the multimedia player were VLC.
5381 Personally, I like VLC, and it is my player of choice when I first try
5382 to play a video file or stream. Only if VLC fail will I drag out
5383 gmplayer to see if it can do better. The reason is mostly the failure
5384 model and trust. When VLC fail, it normally pop up a error message
5385 reporting the problem. When mplayer fail, it normally segfault or
5386 just hangs. The latter failure mode drain my trust in the program.
<p
>
5388 <p
>But even if VLC is my player of choice, we have choosen to use
5389 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
5390 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
5391 plugin to play web videos seamlessly, and the VLC browser plugin is
5392 not very good. For example, it lack in-line control buttons, so there
5393 is no way for the user to pause the video. Also, when I
5394 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
5395 tested the browser plugins
</a
> available in Debian, the VLC plugin
5396 failed on several video pages where mplayer based plugins worked. If
5397 the browser plugin for VLC was as good as the gecko-mediaplayer
5398 package (which uses mplayer), we would switch.
</P
>
5400 <p
>While VLC is a good player, its user interface is slightly
5401 annoying. The most annoying feature is its inconsistent use of
5402 keyboard shortcuts. When the player is in full screen mode, its
5403 shortcuts are different from when it is playing the video in a window.
5404 For example, space only work as pause when in full screen mode. I
5405 wish it had consisten shortcuts and that space also would work when in
5406 window mode. Another nice shortcut in gmplayer is [enter] to restart
5407 the current video. It is very nice when playing short videos from the
5408 web and want to restart it when new people arrive to have a look at
5409 what is going on.
</p
>
5414 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
5415 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
5416 <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>
5417 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
5418 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
5419 upgrade testing of the
5420 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5421 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
5422 This seem like a very good idea, so I adjusted by test scripts and
5423 can now present the updated result from today:
</p
>
5425 <p
>This is for Gnome:
</p
>
5427 <p
>Installed using apt-get, missing with aptitude
</p
>
5429 <blockquote
><p
>
5434 browser-plugin-gnash
5441 freedesktop-sound-theme
5443 gconf-defaults-service
5458 gnome-desktop-environment
5462 gnome-session-canberra
5467 gstreamer0.10-fluendo-mp3
5473 libapache2-mod-dnssd
5476 libaprutil1-dbd-sqlite3
5479 libboost-date-time1.42
.0
5480 libboost-python1.42
.0
5481 libboost-thread1.42
.0
5483 libchamplain-gtk-
0.4-
0
5485 libclutter-gtk-
0.10-
0
5492 libfreerdp-plugins-standard
5507 libgnomepanel2.24-cil
5512 libgtksourceview2.0-common
5513 libmono-addins-gui0.2-cil
5514 libmono-addins0.2-cil
5515 libmono-cairo2.0-cil
5516 libmono-corlib2.0-cil
5517 libmono-i18n-west2.0-cil
5518 libmono-posix2.0-cil
5519 libmono-security2.0-cil
5520 libmono-sharpzip2.84-cil
5521 libmono-system2.0-cil
5524 libndesk-dbus-glib1.0-cil
5525 libndesk-dbus1.0-cil
5535 libtelepathy-farsight0
5544 nautilus-sendto-empathy
5548 python-aptdaemon-gtk
5550 python-beautifulsoup
5565 python-gtksourceview2
5576 python-pkg-resources
5583 python-twisted-conch
5589 python-zope.interface
5594 rhythmbox-plugin-cdrecorder
5601 system-config-printer-udev
5603 telepathy-mission-control-
5
5614 </p
></blockquote
>
5616 <p
>Installed using apt-get, removed with aptitude
</p
>
5618 <blockquote
><p
>
5624 fast-user-switch-applet
5643 libgtksourceview2.0-
0
5645 libsdl1.2debian-alsa
5651 system-config-printer
5656 </p
></blockquote
>
5658 <p
>Installed using aptitude, missing with apt-get
</p
>
5660 <blockquote
><p
>
5661 gstreamer0.10-gnomevfs
5662 </p
></blockquote
>
5664 <p
>Installed using aptitude, removed with apt-get
</p
>
5666 <blockquote
><p
>
5668 </p
></blockquote
>
5670 <p
>This is for KDE:
</p
>
5672 <p
>Installed using apt-get, missing with aptitude
</p
>
5674 <blockquote
><p
>
5676 </p
></blockquote
>
5678 <p
>Installed using apt-get, removed with aptitude
</p
>
5680 <blockquote
><p
>
5683 </p
></blockquote
>
5685 <p
>Installed using aptitude, missing with apt-get
</p
>
5687 <blockquote
><p
>
5701 kdeartwork-emoticons
5703 kdeartwork-theme-icon
5707 kdebase-workspace-bin
5708 kdebase-workspace-data
5722 kscreensaver-xsavers
5737 plasma-dataengines-workspace
5739 plasma-desktopthemes-artwork
5740 plasma-runners-addons
5741 plasma-scriptengine-googlegadgets
5742 plasma-scriptengine-python
5743 plasma-scriptengine-qedje
5744 plasma-scriptengine-ruby
5745 plasma-scriptengine-webkit
5746 plasma-scriptengines
5747 plasma-wallpapers-addons
5748 plasma-widget-folderview
5749 plasma-widget-networkmanagement
5753 xscreensaver-data-extra
5755 xscreensaver-gl-extra
5756 xscreensaver-screensaver-bsod
5757 </p
></blockquote
>
5759 <p
>Installed using aptitude, removed with apt-get
</p
>
5761 <blockquote
><p
>
5763 google-gadgets-common
5781 libggadget-qt-
1.0-
0b
5786 libkonqsidebarplugin4a
5795 libplasma-geolocation-interface4
5797 libplasmagenericshell4
5811 libsmokeknewstuff2-
3
5812 libsmokeknewstuff3-
3
5814 libsmokektexteditor3
5822 libsmokeqtnetwork4-
3
5828 libsmokeqtuitools4-
3
5840 plasma-dataengines-addons
5841 plasma-scriptengine-superkaramba
5842 plasma-widget-lancelot
5843 plasma-widgets-addons
5844 plasma-widgets-workspace
5848 update-notifier-common
5849 </p
></blockquote
>
5851 <p
>Running apt-get autoremove made the results using apt-get and
5852 aptitude a bit more similar, but there are still quite a lott of
5853 differences. I have no idea what packages should be installed after
5854 the upgrade, but hope those that do can have a look.
</p
>
5859 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
5860 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
5861 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
5862 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
5863 <description><p
>Most of the computers in use by the
5864 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
5865 are virtual machines. And they have been Xen machines running on a
5866 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
5867 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
5868 bit harder that it could have been, because we set up the Xen virtual
5869 machines to get the virtual partitions from LVM, which as far as I
5870 know is not supported by KVM. So to migrate, we had to convert
5871 several LVM logical volumes to partitions on a virtual disk file.
</p
>
5874 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
5875 nice recipe
</a
> to do this, and wrote the following script to do the
5876 migration. It uses qemu-img from the qemu package to make the disk
5877 image, parted to partition it, losetup and kpartx to present the disk
5878 image partions as devices, and dd to copy the data. I NFS mounted the
5879 new servers storage area on the old server to do the migration.
</p
>
5885 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5890 if [ -z
"$
1" ] ; then
5891 echo
"Usage: $
0 &lt;hostname
&gt;
"
5897 if [ ! -e /dev/vg_data/$host-disk ] ; then
5898 echo
"error: unable to find LVM volume for $host
"
5902 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5903 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5904 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5905 totalsize=$(( ( $disksize + $swapsize ) ))
5908 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5909 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5911 parted $img mklabel msdos
5912 parted $img mkpart primary linux-swap
0 $disksize
5913 parted $img mkpart primary ext2 $disksize $totalsize
5914 parted $img set
1 boot on
5917 losetup /dev/loop0 $img
5918 kpartx -a /dev/loop0
5920 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5921 fsck.ext3 -f /dev/mapper/loop0p1 || true
5922 mkswap /dev/mapper/loop0p2
5924 kpartx -d /dev/loop0
5925 losetup -d /dev/loop0
5928 <p
>The script is perhaps so simple that it is not copyrightable, but
5929 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5931 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5932 the new disk image attached, installed grub-pc and linux-image-
686 and
5933 set up grub to boot from the disk image. After this, the KVM machines
5934 seem to work just fine.
</p
>
5939 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5940 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5942 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5943 <description><p
>I
'm still running upgrade testing of the
5944 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5945 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5946 status. Here is a short update based on a test I ran
20101118.
</p
>
5948 <p
>I still do not know what a correct migration should look like, so I
5949 report any differences between apt and aptitude and hope someone else
5950 can see if anything should be changed.
</p
>
5952 <p
>This is for Gnome:
</p
>
5954 <p
>Installed using apt-get, missing with aptitude
</p
>
5956 <blockquote
><p
>
5957 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5958 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5959 dmz-cursor-theme empathy empathy-common finger
5960 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5961 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5962 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5963 gnome-cards-data gnome-codec-install gnome-core
5964 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5965 gnome-search-tool gnome-session-canberra gnome-spell
5966 gnome-system-log gnome-themes-extras gnome-themes-more
5967 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5968 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5969 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5970 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5971 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5972 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5973 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5974 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5975 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5976 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5977 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5978 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5979 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5980 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5981 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5982 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5983 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5984 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5985 libmono-security2.0-cil libmono-sharpzip2.84-cil
5986 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5987 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5988 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5989 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5990 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5991 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5992 libxalan2-java libxerces2-java media-player-info mesa-utils
5993 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5994 nautilus-sendto-empathy openoffice.org-writer2latex
5995 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5996 python-aptdaemon python-aptdaemon-gtk python-axiom
5997 python-beautifulsoup python-bugbuddy python-clientform
5998 python-coherence python-configobj python-crypto python-cupshelpers
5999 python-cupsutils python-eggtrayicon python-elementtree
6000 python-epsilon python-evolution python-feedparser python-gdata
6001 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6002 python-gtksourceview2 python-httplib2 python-louie python-mako
6003 python-markupsafe python-mechanize python-nevow python-notify
6004 python-opengl python-openssl python-pam python-pkg-resources
6005 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6006 python-tagpy python-twisted-bin python-twisted-conch
6007 python-twisted-core python-twisted-web python-utidylib python-webkit
6008 python-xdg python-zope.interface remmina remmina-plugin-data
6009 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6010 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6011 software-center svgalibg1 system-config-printer-udev
6012 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6013 totem totem-coherence totem-mozilla totem-plugins
6014 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6016 </p
></blockquote
>
6018 Installed using apt-get, removed with aptitude
6020 <blockquote
><p
>
6021 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6022 epiphany-extensions epiphany-gecko evolution-exchange
6023 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6024 gedit-common gnome-app-install gnome-games gnome-games-data
6025 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6026 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6027 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6028 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6029 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6030 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6031 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6032 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6033 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6034 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6035 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6036 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6037 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6038 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6039 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6040 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6041 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6042 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6043 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6044 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6045 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6046 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6047 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6048 sound-juicer swfdec-gnome system-config-printer totem-common
6049 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6050 </p
></blockquote
>
6052 <p
>Installed using aptitude, missing with apt-get
</p
>
6054 <blockquote
><p
>
6055 gstreamer0.10-gnomevfs
6056 </p
></blockquote
>
6058 <p
>Installed using aptitude, removed with apt-get
</p
>
6060 <blockquote
><p
>
6062 </p
></blockquote
>
6064 <p
>This is for KDE:
</p
>
6066 <p
>Installed using apt-get, missing with aptitude
</p
>
6068 <blockquote
><p
>
6069 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6070 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6071 ghostscript-x git gnome-audio gnugo granatier gs-common
6072 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6073 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6074 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6075 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6076 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6077 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6078 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6079 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6080 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6081 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6082 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6083 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
6084 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6085 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6086 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6087 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6088 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6089 libkrossui4 libmailtools-perl libmime-tools-perl
6090 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6091 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6092 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6093 lirc luatex marble networkstatus noatun-plugins
6094 openoffice.org-writer2latex palapeli palapeli-data parley
6095 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6096 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6097 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6099 </p
></blockquote
>
6101 <p
>Installed using apt-get, removed with aptitude
</p
>
6103 <blockquote
><p
>
6104 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6105 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6106 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6107 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6108 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6109 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6110 kitchensync kiten kjumpingcube klatin klettres klickety klines
6111 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6112 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6113 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6114 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6115 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6116 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6117 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6118 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6119 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6120 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
6121 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
6122 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6123 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
6124 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
6125 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6126 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6127 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6128 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6129 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6130 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6131 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
6132 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
6133 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6134 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6135 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6136 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6137 </p
></blockquote
>
6139 <p
>Installed using aptitude, missing with apt-get
</p
>
6141 <blockquote
><p
>
6142 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6143 kdeartwork kdebase kdebase-apps kdebase-workspace
6144 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6145 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6146 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6147 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6148 xscreensaver-screensaver-bsod
6149 </p
></blockquote
>
6151 <p
>Installed using aptitude, removed with apt-get
</p
>
6153 <blockquote
><p
>
6154 kdebase-bin konq-plugins konqueror
6155 </p
></blockquote
>
6160 <title>Gnash buildbot slave and Debian kfreebsd
</title>
6161 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
6162 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
6163 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
6164 <description><p
>Answering
6165 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
6166 call from the Gnash project
</a
> for
6167 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
6168 current source, I have set up a virtual KVM machine on the Debian
6169 Edu/Skolelinux virtualization host to test the git source on
6170 Debian/Squeeze. I hope this can help the developers in getting new
6171 releases out more often.
</p
>
6173 <p
>As the developers want less main-stream build platforms tested to,
6174 I have considered setting up a
<a
6175 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
6176 machine as well. I have also considered using the kfreebsd
6177 architecture in Debian as a file server in NUUG to get access to the
5
6178 TB zfs volume we currently use to store DV video. Because of this, I
6179 finally got around to do a test installation of Debian/Squeeze with
6180 kfreebsd. Installation went fairly smooth, thought I noticed some
6181 visual glitches in the cdebconf dialogs (black cursor left on the
6182 screen at random locations). Have not gotten very far with the
6183 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6184 fatal problem. Have to spend some more time on it to see if it is
6185 useful as a file server for NUUG. Will try to find time to set up a
6186 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
6191 <title>Debian in
3D
</title>
6192 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
6193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
6194 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
6195 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
6197 <p
>3D printing is just great. I just came across this Debian logo in
6199 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
6200 thingiverse blog
</a
>.
</p
>
6205 <title>Software updates
2010-
10-
24</title>
6206 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
6207 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
6208 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
6209 <description><p
>Some updates.
</p
>
6211 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
6212 raise money for the project is going well. The lower limit of
10
6213 signers was reached in
24 hours, and so far
13 people have signed it.
6214 More signers and more funding is most welcome, and I am really curious
6215 how far we can get before the time limit of December
24 is reached.
6218 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
6219 about what appear to be a great code coverage tool capable of
6220 generating code coverage stats without any changes to the source code.
6222 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
6223 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
6224 It is missing in Debian, but the git source built just fine in Squeeze
6225 after I installed libelf-dev, libdwarf-dev, pkg-config and
6226 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6227 solvable. I hope kcov make it into Debian soon.
</p
>
6229 <p
>Finally found time to wrap up the release notes for
<a
6230 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
6231 new alpha release of Debian Edu
</a
>, and just published the second
6232 alpha test release of the Squeeze based Debian Edu /
6233 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
6234 release. Give it a try if you need a complete linux solution for your
6235 school, including central infrastructure server, workstations, thin
6236 client servers and diskless workstations. A nice touch added
6237 yesterday is RDP support on the thin client servers, for windows
6238 clients to get a Linux desktop on request.
</p
>
6243 <title>Some notes on Flash in Debian and Debian Edu
</title>
6244 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
6245 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
6246 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
6247 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
6248 popularity-contest numbers
</a
>, the adobe-flashplugin package the
6249 second most popular used package that is missing in Debian. The sixth
6250 most popular is flashplayer-mozilla. This is a clear indication that
6251 working flash is important for Debian users. Around
10 percent of the
6252 users submitting data to popcon.debian.org have this package
6253 installed.
</p
>
6255 <p
>In the report written by Lars Risan in August
2008
6256 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
6257 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6258 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
6259 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
6260 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
6261 web sites require Flash to work, and lacking working Flash support in
6262 the web browser and the problems with installing it was perceived as a
6263 good reason to stay with Windows.
</p
>
6265 <p
>I once saw a funny and sad comment in a web forum, where Linux was
6266 said to be the retarded cousin that did not really understand
6267 everything you told him but could work fairly well. This was a
6268 comment regarding the problems Linux have with proprietary formats and
6269 non-standard web pages, and is sad because it exposes a fairly common
6270 understanding of whose fault it is if web pages that only work in for
6271 example Internet Explorer
6 fail to work on Firefox, and funny because
6272 it explain very well how annoying it is for users when Linux
6273 distributions do not work with the documents they receive or the web
6274 pages they want to visit.
</p
>
6276 <p
>This is part of the reason why I believe it is important for Debian
6277 and Debian Edu to have a well working Flash implementation in the
6278 distribution, to get at least popular sites as Youtube and Google
6279 Video to working out of the box. For Squeeze, Debian have the chance
6280 to include the latest version of Gnash that will make this happen, as
6281 the new release
0.8.8 was published a few weeks ago and is resting in
6282 unstable. The new version work with more sites that version
0.8.7.
6283 The Gnash maintainers have asked for a freeze exception, but the
6284 release team have not had time to reply to it yet. I hope they agree
6285 with me that Flash is important for the Debian desktop users, and thus
6286 accept the new package into Squeeze.
</p
>
6291 <title>Circular package dependencies harms apt recovery
</title>
6292 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
6293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
6294 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
6295 <description><p
>I discovered this while doing
6296 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
6297 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
6298 in Debian still got circular dependencies, and it is often claimed
6299 that apt and aptitude should be able to handle this just fine, but
6300 some times these dependency loops causes apt to fail.
</p
>
6302 <p
>An example is from todays
6303 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
6304 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
6305 causes perl-modules to fail to upgrade. The cause is simple. If a
6306 package fail to unpack, then only part of packages with the circular
6307 dependency might end up being unpacked when unpacking aborts, and the
6308 ones already unpacked will fail to configure in the recovery phase
6309 because its dependencies are unavailable.
</p
>
6311 <p
>In this log, the problem manifest itself with this error:
</p
>
6313 <blockquote
><pre
>
6314 dpkg: dependency problems prevent configuration of perl-modules:
6315 perl-modules depends on perl (
>=
5.10.1-
1); however:
6316 Version of perl on system is
5.10.0-
19lenny
2.
6317 dpkg: error processing perl-modules (--configure):
6318 dependency problems - leaving unconfigured
6319 </pre
></blockquote
>
6321 <p
>The perl/perl-modules circular dependency is already
6322 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
6323 hopefully be solved as soon as possible, but it is not the only one,
6324 and each one of these loops in the dependency tree can cause similar
6325 failures. Of course, they only occur when there are bugs in other
6326 packages causing the unpacking to fail, but it is rather nasty when
6327 the failure of one package causes the problem to become worse because
6328 of dependency loops.
</p
>
6331 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
6332 tireless effort by Bill Allombert
</a
>, the number of circular
6334 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
6335 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
6337 <p
>Todays testing also exposed a bug in
6338 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
6339 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
6340 apt-get and aptitude, the latter possibly caused by some circular
6341 dependency. Reported both to BTS to try to get someone to look at
6347 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
6348 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
6349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
6350 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
6351 <description><p
>This is a
6352 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
6354 <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
6356 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
6357 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
6359 <p
>As a step to try to see if it possible to merge the DNS and DHCP
6360 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6361 and dhcp3-server-ldap in Debian use the LDAP server. The two
6362 implementations are quite different in how they use LDAP.
</p
>
6364 To get this information, I started slapd with debugging enabled and
6365 dumped the debug output to a file to get the LDAP searches performed
6366 on a Debian Edu main-server. Here is a summary.
6368 <p
><strong
>powerdns
</strong
></p
>
6370 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
6371 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
6374 <p
>PowerDNS have two modes of operation using LDAP as its backend.
6375 One
"strict
" mode where the forward and reverse DNS lookups are done
6376 using the same LDAP objects, and a
"tree
" mode where the forward and
6377 reverse entries are in two different subtrees in LDAP with a structure
6378 based on the DNS names, as in tjener.intern and
6379 2.2.0.10.in-addr.arpa.
</p
>
6381 <p
>In tree mode, the server is set up to use a LDAP subtree as its
6382 base, and uses a
"base
" scoped search for the DNS name by adding
6383 "dc=tjener,dc=intern,
" to the base with a filter for
6384 "(associateddomain=tjener.intern)
" for the forward entry and
6385 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
6386 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
6387 forward entries, it is looking for attributes named dnsttl, arecord,
6388 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6389 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6390 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6391 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6392 spfrecord and modifytimestamp. For reverse entries it is looking for
6393 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6394 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6395 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6396 ldapsearch commands could look like this:
</p
>
6398 <blockquote
><pre
>
6399 ldapsearch -h ldap \
6400 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6401 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6402 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6403 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6404 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6405 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6407 ldapsearch -h ldap \
6408 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6409 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
6410 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6411 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6412 srvrecord naptrrecord modifytimestamp
6413 </pre
></blockquote
>
6415 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
6416 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6417 example LDAP objects used there. In addition to these objects, the
6418 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6419 also exist.
</p
>
6421 <blockquote
><pre
>
6422 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6424 objectclass: dnsdomain
6425 objectclass: domainrelatedobject
6428 associateddomain: tjener.intern
6430 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6432 objectclass: dnsdomain2
6433 objectclass: domainrelatedobject
6435 ptrrecord: tjener.intern
6436 associateddomain:
2.2.0.10.in-addr.arpa
6437 </pre
></blockquote
>
6439 <p
>In strict mode, the server behaves differently. When looking for
6440 forward DNS entries, it is doing a
"subtree
" scoped search with the
6441 same base as in the tree mode for a object with filter
6442 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
6443 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6444 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6445 naptrrecord and modifytimestamp. For reverse entires it also do a
6446 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
6447 and the requested attributes are associateddomain, dnsttl and
6448 modifytimestamp. In short, in strict mode the objects with ptrrecord
6449 go away, and the arecord attribute in the forward object is used
6452 <p
>The forward and reverse searches can be simulated using ldapsearch
6453 like this:
</p
>
6455 <blockquote
><pre
>
6456 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6457 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
6458 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6459 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6460 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6461 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6463 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6464 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
6465 </pre
></blockquote
>
6467 <p
>In addition to the forward and reverse searches , there is also a
6468 search for SOA records, which behave similar to the forward and
6469 reverse lookups.
</p
>
6471 <p
>A thing to note with the PowerDNS behaviour is that it do not
6472 specify any objectclass names, and instead look for the attributes it
6473 need to generate a DNS reply. This make it able to work with any
6474 objectclass that provide the needed attributes.
</p
>
6476 <p
>The attributes are normally provided in the cosine (RFC
1274) and
6477 dnsdomain2 schemas. The latter is used for reverse entries like
6478 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
6480 <p
>In Debian Edu, we have created DNS objects using the object classes
6481 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6482 attributes) and domainrelatedobject (for associatedDomain). The use
6483 of structural object classes make it impossible to combine these
6484 classes with the object classes used by DHCP.
</p
>
6486 <p
>There are other schemas that could be used too, for example the
6487 dnszone structural object class used by Gosa and bind-sdb for the DNS
6488 attributes combined with the domainrelatedobject object class, but in
6489 this case some unused attributes would have to be included as well
6490 (zonename and relativedomainname).
</p
>
6492 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
6493 mode and not use any of the existing objectclasses (dnsdomain,
6494 dnsdomain2 and dnszone) when one want to combine the DNS information
6495 with DHCP information, and instead create a auxiliary object class
6496 defined something like this (using the attributes defined for
6497 dnsdomain and dnsdomain2 or dnszone):
</p
>
6499 <blockquote
><pre
>
6500 objectclass ( some-oid NAME
'dnsDomainAux
'
6503 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6504 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6505 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6506 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6507 A6Record $ DNAMERecord
6509 </pre
></blockquote
>
6511 <p
>This will allow any object to become a DNS entry when combined with
6512 the domainrelatedobject object class, and allow any entity to include
6513 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
6514 developers asking for their view on this schema and if they are
6515 interested in providing such schema with PowerDNS, and I hope my
6516 message will be accepted into their mailing list soon.
</p
>
6518 <p
><strong
>ISC dhcp
</strong
></p
>
6520 <p
>The DHCP server searches for specific objectclass and requests all
6521 the object attributes, and then uses the attributes it want. This
6522 make it harder to figure out exactly what attributes are used, but
6523 thanks to the working example in Debian Edu I can at least get an idea
6524 what is needed without having to read the source code.
</p
>
6526 <p
>In the DHCP server configuration, the LDAP base to use and the
6527 search filter to use to locate the correct dhcpServer entity is
6528 stored. These are the relevant entries from
6529 /etc/dhcp3/dhcpd.conf:
</p
>
6531 <blockquote
><pre
>
6532 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
6533 ldap-dhcp-server-cn
"dhcp
";
6534 </pre
></blockquote
>
6536 <p
>The DHCP server uses this information to nest all the DHCP
6537 configuration it need. The cn
"dhcp
" is located using the given LDAP
6538 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
6539 search result is this entry:
</p
>
6541 <blockquote
><pre
>
6542 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6545 objectClass: dhcpServer
6546 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6547 </pre
></blockquote
>
6549 <p
>The content of the dhcpServiceDN attribute is next used to locate the
6550 subtree with DHCP configuration. The DHCP configuration subtree base
6551 is located using a base scope search with base
"cn=DHCP
6552 Config,dc=skole,dc=skolelinux,dc=no
" and filter
6553 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
6554 The search result is this entry:
</p
>
6556 <blockquote
><pre
>
6557 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6560 objectClass: dhcpService
6561 objectClass: dhcpOptions
6562 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6563 dhcpStatements: ddns-update-style none
6564 dhcpStatements: authoritative
6565 dhcpOption: smtp-server code
69 = array of ip-address
6566 dhcpOption: www-server code
72 = array of ip-address
6567 dhcpOption: wpad-url code
252 = text
6568 </pre
></blockquote
>
6570 <p
>Next, the entire subtree is processed, one level at the time. When
6571 all the DHCP configuration is loaded, it is ready to receive requests.
6572 The subtree in Debian Edu contain objects with object classes
6573 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6574 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6575 and information about netmasks, dynamic range etc. Leaving out the
6576 details here because it is not relevant for the focus of my
6577 investigation, which is to see if it is possible to merge dns and dhcp
6578 related computer objects.
</p
>
6580 <p
>When a DHCP request come in, LDAP is searched for the MAC address
6581 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
6582 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
6583 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6584 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
6587 <blockquote
><pre
>
6588 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6591 objectClass: dhcpHost
6592 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6593 dhcpStatements: fixed-address hostname
6594 </pre
></blockquote
>
6596 <p
>There is less flexiblity in the way LDAP searches are done here.
6597 The object classes need to have fixed names, and the configuration
6598 need to be stored in a fairly specific LDAP structure. On the
6599 positive side, the invidiual dhcpHost entires can be anywhere without
6600 the DN pointed to by the dhcpServer entries. The latter should make
6601 it possible to group all host entries in a subtree next to the
6602 configuration entries, and this subtree can also be shared with the
6603 DNS server if the schema proposed above is combined with the dhcpHost
6604 structural object class.
6606 <p
><strong
>Conclusion
</strong
></p
>
6608 <p
>The PowerDNS implementation seem to be very flexible when it come
6609 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
6610 come to the the LDAP structure, the
"strict
" mode is very flexible,
6611 allowing DNS objects to be stored anywhere under the base cn specified
6612 in the configuration.
</p
>
6614 <p
>The DHCP implementation on the other hand is very inflexible, both
6615 regarding which LDAP schemas to use and which LDAP structure to use.
6616 I guess one could implement ones own schema, as long as the
6617 objectclasses and attributes have the names used, but this do not
6618 really help when the DHCP subtree need to have a fairly fixed
6619 structure.
</p
>
6621 <p
>Based on the observed behaviour, I suspect a LDAP structure like
6622 this might work for Debian Edu:
</p
>
6624 <blockquote
><pre
>
6626 cn=machine-info (dhcpService) - dhcpServiceDN points here
6627 cn=dhcp (dhcpServer)
6628 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6629 cn=
10.0.2.0 (dhcpSubnet)
6630 cn=group1 (dhcpGroup/dhcpOptions)
6631 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6632 cn=
192.168.0.0 (dhcpSubnet)
6633 cn=group1 (dhcpGroup/dhcpOptions)
6634 ou=machines - PowerDNS base points here
6635 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6636 </pre
></blockquote
>
6638 <P
>This is not tested yet. If the DHCP server require the dhcpHost
6639 entries to be in the dhcpGroup subtrees, the entries can be stored
6640 there instead of a common machines subtree, and the PowerDNS base
6641 would have to be moved one level up to the machine-info subtree.
</p
>
6643 <p
>The combined object under the machines subtree would look something
6644 like this:
</p
>
6646 <blockquote
><pre
>
6647 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6650 objectClass: dhcpHost
6651 objectclass: domainrelatedobject
6652 objectclass: dnsDomainAux
6653 associateddomain: hostname.intern
6654 arecord:
10.11.12.13
6655 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6656 dhcpStatements: fixed-address hostname.intern
6657 </pre
></blockquote
>
6659 </p
>One could even add the LTSP configuration associated with a given
6660 machine, as long as the required attributes are available in a
6661 auxiliary object class.
</p
>
6666 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
6667 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
6668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
6669 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
6670 <description><p
>For a while now, I have wanted to find a way to change the DNS and
6671 DHCP services in Debian Edu to use the same LDAP objects for a given
6672 computer, to avoid the possibility of having a inconsistent state for
6673 a computer in LDAP (as in DHCP but no DNS entry or the other way
6674 around) and make it easier to add computers to LDAP.
</p
>
6676 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
6677 information finally found a solution that seem to work.
</p
>
6679 <p
>The old setup required three LDAP objects for a given computer.
6680 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6681 we switch powerdns to use its strict LDAP method (ldap-method=strict
6682 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6683 merged into one while making it impossible to transfer the reverse map
6684 to a slave DNS server.
</p
>
6686 <p
>If we also replace the object class used to get the DNS related
6687 attributes to one allowing these attributes to be combined with the
6688 dhcphost object class, we can merge the DNS and DHCP entries into one.
6689 I
've written such object class in the dnsdomainaux.schema file (need
6690 proper OIDs, but that is a minor issue), and tested the setup. It
6691 seem to work.
</p
>
6693 <p
>With this test setup in place, we can get away with one LDAP object
6694 for both DNS and DHCP, and even the LTSP configuration I suggested in
6695 an earlier email. The combined LDAP object will look something like
6698 <blockquote
><pre
>
6699 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6701 objectClass: dhcphost
6702 objectclass: domainrelatedobject
6703 objectclass: dnsdomainaux
6704 associateddomain: hostname.intern
6705 arecord:
10.11.12.13
6706 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
6707 dhcpstatements: fixed-address hostname
6709 </pre
></blockquote
>
6711 <p
>The DNS server uses the associateddomain and arecord entries, while
6712 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6713 before asking DNS to resolve the fixed-adddress. LTSP will use
6714 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
6716 <p
>I am not yet sure if I can get the DHCP server to look for its
6717 dhcphost in a different location, to allow us to put the objects
6718 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
6719 that. If I can
't figure out a way to do that, we can still get rid of
6720 the hosts subtree and move all its content into the DHCP Config tree
6721 (which probably should be renamed to be more related to the new
6722 content. I suspect cn=dnsdhcp,ou=services or something like that
6723 might be a good place to put it.
</p
>
6725 <p
>If you want to help out with implementing this for Debian Edu,
6726 please contact us on debian-edu@lists.debian.org.
</p
>
6731 <title>Idea for storing LTSP configuration in LDAP
</title>
6732 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
6733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
6734 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
6735 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
6736 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6737 clients, and that this can be used to fetch configuration from LDAP if
6738 Debian Edu choose to store configuration there.
</p
>
6740 <p
>Armed with this information, I got inspired and wrote a test module
6741 to get configuration from LDAP. The idea is to look up the MAC
6742 address of the client in LDAP, and look for attributes on the form
6743 ltspconfigsetting=value, and use this to export SETTING=value to the
6744 LTSP clients.
</p
>
6746 <p
>The goal is to be able to store the LTSP configuration attributes
6747 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
6748 allowing us to store all information about a computer in one place.
</p
>
6750 <p
>This is a untested draft implementation, and I welcome feedback on
6751 this approach. A real LDAP schema for the ltspClientAux objectclass
6752 need to be written. Comments, suggestions, etc?
</p
>
6754 <blockquote
><pre
>
6755 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6757 # Fetch LTSP client settings from LDAP based on MAC address
6759 # Uses ethernet address as stored in the dhcpHost objectclass using
6760 # the dhcpHWAddress attribute or ethernet address stored in the
6761 # ieee802Device objectclass with the macAddress attribute.
6763 # This module is written to be schema agnostic, and only depend on the
6764 # existence of attribute names.
6766 # The LTSP configuration variables are saved directly using a
6767 # ltspConfig prefix and uppercasing the rest of the attribute name.
6768 # To set the SERVER variable, set the ltspConfigServer attribute.
6770 # Some LDAP schema should be created with all the relevant
6771 # configuration settings. Something like this should work:
6773 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
6776 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6778 LDAPSERVER=$(debian-edu-ldapserver)
6779 if [
"$LDAPSERVER
" ] ; then
6780 LDAPBASE=$(debian-edu-ldapserver -b)
6781 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
6782 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
6783 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
6784 grep
'^ltspConfig
' | while read attr value ; do
6785 # Remove prefix and convert to upper case
6786 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
6787 # bass value on to clients
6788 eval
"$attr=$value; export $attr
"
6792 </pre
></blockquote
>
6794 <p
>I
'm not sure this shell construction will work, because I suspect
6795 the while block might end up in a subshell causing the variables set
6796 there to not show up in ltsp-config, but if that is the case I am sure
6797 the code can be restructured to make sure the variables are passed on.
6798 I expect that can be solved with some testing. :)
</p
>
6800 <p
>If you want to help out with implementing this for Debian Edu,
6801 please contact us on debian-edu@lists.debian.org.
</p
>
6803 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
6804 configuration in LDAP that was created around year
2000 by
6805 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
6806 Xperience, Inc.,
2000</a
>. I found its
6807 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
6808 personal home page over at redhat.com.
</p
>
6813 <title>jXplorer, a very nice LDAP GUI
</title>
6814 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
6815 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
6816 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
6817 <description><p
>Since
6818 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
6819 last post
</a
> about available LDAP tools in Debian, I was told about a
6820 LDAP GUI that is even better than luma. The java application
6821 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
6822 moving LDAP objects and subtrees using drag-and-drop, and can
6823 authenticate using Kerberos. I have only tested the Kerberos
6824 authentication, but do not have a LDAP setup allowing me to rewrite
6825 LDAP with my test user yet. It is
6826 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
6827 Debian
</a
> testing and unstable at the moment. The only problem I
6828 have with it is how it handle errors. If something go wrong, its
6829 non-intuitive behaviour require me to go through some query work list
6830 and remove the failing query. Nothing big, but very annoying.
</p
>
6835 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
6836 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
6837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
6838 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
6839 <description><p
>Here is a short update on my
<a
6840 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
6841 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
6842 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
6843 not reporting the status for KDE, because the upgrade crashes when
6844 aptitude try because of missing conflicts
6845 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
6846 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
6848 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
6849 complete list of the installed packages. Based on this I see these
6850 differences when I did a test run today. As usual, I do not really
6851 know what the correct set of packages would be, but thought it best to
6852 publish the difference.
</p
>
6854 <p
>Installed using apt-get, missing with aptitude
</p
>
6856 <blockquote
><p
>
6857 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
6858 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
6859 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6860 libgtksourceview-common libpt-
1.10.10-plugins-alsa
6861 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6862 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6863 python-
4suite-xml python-eggtrayicon python-gtkhtml2
6864 python-gtkmozembed svgalibg1 xserver-xephyr zip
6865 </p
></blockquote
>
6867 <p
>Installed using apt-get, removed with aptitude
</p
>
6869 <blockquote
><p
>
6870 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6871 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6872 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
6873 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
6874 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
6875 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
6876 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6877 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6878 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6879 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
6880 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
6881 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
6882 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6883 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
6884 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6885 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
6886 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
6887 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6888 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6889 mysql-common swfdec-gnome totem-gstreamer wodim
6890 </p
></blockquote
>
6892 <p
>Installed using aptitude, missing with apt-get
</p
>
6894 <blockquote
><p
>
6895 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6896 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6897 xserver-xorg-input-all xserver-xorg-input-evdev
6898 xserver-xorg-input-kbd xserver-xorg-input-mouse
6899 xserver-xorg-input-synaptics xserver-xorg-video-all
6900 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6901 xserver-xorg-video-chips xserver-xorg-video-cirrus
6902 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6903 xserver-xorg-video-glint xserver-xorg-video-i128
6904 xserver-xorg-video-i740 xserver-xorg-video-mach64
6905 xserver-xorg-video-mga xserver-xorg-video-neomagic
6906 xserver-xorg-video-nouveau xserver-xorg-video-nv
6907 xserver-xorg-video-r128 xserver-xorg-video-radeon
6908 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6909 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6910 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6911 xserver-xorg-video-sis xserver-xorg-video-sisusb
6912 xserver-xorg-video-tdfx xserver-xorg-video-tga
6913 xserver-xorg-video-trident xserver-xorg-video-tseng
6914 xserver-xorg-video-vesa xserver-xorg-video-vmware
6915 xserver-xorg-video-voodoo
6916 </p
></blockquote
>
6918 <p
>Installed using aptitude, removed with apt-get
</p
>
6920 <blockquote
><p
>
6921 deskbar-applet xserver-xorg xserver-xorg-core
6922 xserver-xorg-input-wacom xserver-xorg-video-intel
6923 xserver-xorg-video-openchrome
6924 </p
></blockquote
>
6926 <p
>I was told on IRC that the xorg-xserver package was
6927 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6928 in git
</a
> today to try to get apt-get to not remove xorg completely.
6929 No idea when it hits Squeeze, but when it does I hope it will reduce
6930 the difference somewhat.
6935 <title>LUMA, a very nice LDAP GUI
</title>
6936 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6937 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6938 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6939 <description><p
>The last few days I have been looking into the status of the LDAP
6940 directory in Debian Edu, and in the process I started to miss a GUI
6941 tool to browse the LDAP tree. The only one I was able to find in
6942 Debian/Squeeze and Lenny is
6943 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6944 be a great tool to get a overview of the current LDAP directory
6945 populated by default in Skolelinux. Thanks to it, I have been able to
6946 find empty and obsolete subtrees, misplaced objects and duplicate
6947 objects. It will be installed by default in Debian/Squeeze. If you
6948 are working with LDAP, give it a go. :)
</p
>
6950 <p
>I did notice one problem with it I have not had time to report to
6951 the BTS yet. There is no .desktop file in the package, so the tool do
6952 not show up in the Gnome and KDE menus, but only deep down in in the
6953 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6956 <p
>I have not yet been able to get it to modify the tree yet. I would
6957 like to move objects and remove subtrees directly in the GUI, but have
6958 not found a way to do that with LUMA yet. So in the mean time, I use
6959 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6961 <p
>If you have tips on other GUI tools for LDAP that might be useful
6962 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6964 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6965 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6966 useful GUI alternative. It seem like a good tool, but is unmaintained
6967 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6968 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6973 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6974 <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>
6975 <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>
6976 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6977 <description><p
>A while back, I
6978 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6979 about the fact
</a
> that it is not possible with the provided schemas
6980 for storing DNS and DHCP information in LDAP to combine the two sets
6981 of information into one LDAP object representing a computer.
</p
>
6983 <p
>In the mean time, I discovered that a simple fix would be to make
6984 the dhcpHost object class auxiliary, to allow it to be combined with
6985 the dNSDomain object class, and thus forming one object for one
6986 computer when storing both DHCP and DNS information in LDAP.
</p
>
6988 <p
>If I understand this correctly, it is not safe to do this change
6989 without also changing the assigned number for the object class, and I
6990 do not know enough about LDAP schema design to do that properly for
6991 Debian Edu.
</p
>
6993 <p
>Anyway, for future reference, this is how I believe we could change
6995 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6996 schema
</a
> to solve at least part of the problem with the LDAP schemas
6997 available today from IETF.
</p
>
7000 --- dhcp.schema (revision
65192)
7001 +++ dhcp.schema (working copy)
7003 objectclass (
2.16.840.1.113719.1.203.6.6
7004 NAME
'dhcpHost
'
7005 DESC
'This represents information about a particular client
'
7009 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7010 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7013 <p
>I very much welcome clues on how to do this properly for Debian
7014 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7015 package, and should thus be free to rewrite it as we see fit.
</p
>
7017 <p
>If you want to help out with implementing this for Debian Edu,
7018 please contact us on debian-edu@lists.debian.org.
</p
>
7023 <title>Calling tasksel like the installer, while still getting useful output
</title>
7024 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7026 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7027 <description><p
>A few times I have had the need to simulate the way tasksel
7028 installs packages during the normal debian-installer run. Until now,
7029 I have ended up letting tasksel do the work, with the annoying problem
7030 of not getting any feedback at all when something fails (like a
7031 conffile question from dpkg or a download that fails), using code like
7034 <blockquote
><pre
>
7035 export DEBIAN_FRONTEND=noninteractive
7036 tasksel --new-install
7037 </pre
></blockquote
>
7039 This would invoke tasksel, let its automatic task selection pick the
7040 tasks to install, and continue to install the requested tasks without
7041 any output what so ever.
7043 Recently I revisited this problem while working on the automatic
7044 package upgrade testing, because tasksel would some times hang without
7045 any useful feedback, and I want to see what is going on when it
7046 happen. Then it occured to me, I can parse the output from tasksel
7047 when asked to run in test mode, and use that aptitude command line
7048 printed by tasksel then to simulate the tasksel run. I ended up using
7051 <blockquote
><pre
>
7052 export DEBIAN_FRONTEND=noninteractive
7053 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7055 </pre
></blockquote
>
7057 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7058 --without-recommends -o APT::Install-Recommends=no -y install
7059 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7060 ~pimportant
</tt
>", which will install the gnome desktop task, the
7061 laptop task and all packages with priority standard , required and
7062 important, just like tasksel would have done it during
7063 installation.
</p
>
7065 <p
>A better approach is probably to extend tasksel to be able to
7066 install packages without using debconf-apt-progress, for use cases
7067 like this.
</p
>
7072 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
7073 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
7074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
7075 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
7076 <description><p
>My
7077 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
7078 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
7079 finally made the upgrade logs available from
7080 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
7081 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7082 apt and aptitude, and found their differences interesting. This time
7083 I will only focus on their removal plans.
</p
>
7085 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
7086 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
7087 surprising part is that it want to remove xorg and all
7088 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7089 sure why. When asking aptitude to do the same, it want to remove
129
7090 packages, but most of them are library packages I suspect are no
7091 longer needed. Both of them want to remove bluetooth packages, which
7092 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
7094 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
7095 which seem like a bad idea and xorg the same way as with Gnome. Asking
7096 aptitude for the same, it wants to remove
192 packages, none which are
7097 too surprising.
</p
>
7099 <p
>I guess the removal of xorg during upgrades should be investigated
7100 and avoided, and perhaps others as well. Here are the complete list
7101 of planned removals. The complete logs is available from the URL
7102 above. Note if you want to repeat these tests, that the upgrade test
7103 for kde+apt-get hung in the tasksel setup because of dpkg asking
7104 conffile questions. No idea why. I worked around it by using
7105 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
7108 <p
><b
>apt-get gnome
72</b
>
7109 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
7110 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7111 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
7112 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7113 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7114 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7115 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7116 xserver-xorg-input-kbd xserver-xorg-input-mouse
7117 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7118 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7119 xserver-xorg-video-ati xserver-xorg-video-chips
7120 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7121 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7122 xserver-xorg-video-glint xserver-xorg-video-i128
7123 xserver-xorg-video-i740 xserver-xorg-video-imstt
7124 xserver-xorg-video-intel xserver-xorg-video-mach64
7125 xserver-xorg-video-mga xserver-xorg-video-neomagic
7126 xserver-xorg-video-nsc xserver-xorg-video-nv
7127 xserver-xorg-video-openchrome xserver-xorg-video-r128
7128 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7129 xserver-xorg-video-rendition xserver-xorg-video-s3
7130 xserver-xorg-video-s3virge xserver-xorg-video-savage
7131 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7132 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7133 xserver-xorg-video-tga xserver-xorg-video-trident
7134 xserver-xorg-video-tseng xserver-xorg-video-v4l
7135 xserver-xorg-video-vesa xserver-xorg-video-vga
7136 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
7137 xulrunner-
1.9-gnome-support
</p
>
7139 <p
><b
>aptitude gnome
129</b
>
7141 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
7142 djvulibre-desktop finger gnome-app-install gnome-mount
7143 gnome-network-admin gnome-spell gnome-vfs-obexftp
7144 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7145 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7146 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7147 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
7148 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
7149 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
7150 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
7151 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
7152 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
7153 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
7154 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
7155 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
7156 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7157 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
7158 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
7159 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
7160 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
7161 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
7162 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7163 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7164 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7165 openoffice.org-writer2latex openssl-blacklist p7zip
7166 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
7167 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7168 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7169 swfdec-mozilla totem-gstreamer update-manager wodim
7170 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7171 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7174 <p
><b
>apt-get kde
82</b
>
7176 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7177 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7178 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7179 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7180 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7181 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7182 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7183 xserver-xorg-input-kbd xserver-xorg-input-mouse
7184 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7185 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7186 xserver-xorg-video-ati xserver-xorg-video-chips
7187 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7188 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7189 xserver-xorg-video-glint xserver-xorg-video-i128
7190 xserver-xorg-video-i740 xserver-xorg-video-imstt
7191 xserver-xorg-video-intel xserver-xorg-video-mach64
7192 xserver-xorg-video-mga xserver-xorg-video-neomagic
7193 xserver-xorg-video-nsc xserver-xorg-video-nv
7194 xserver-xorg-video-openchrome xserver-xorg-video-r128
7195 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7196 xserver-xorg-video-rendition xserver-xorg-video-s3
7197 xserver-xorg-video-s3virge xserver-xorg-video-savage
7198 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7199 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7200 xserver-xorg-video-tga xserver-xorg-video-trident
7201 xserver-xorg-video-tseng xserver-xorg-video-v4l
7202 xserver-xorg-video-vesa xserver-xorg-video-vga
7203 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
7205 <p
><b
>aptitude kde
192</b
>
7206 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
7207 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7208 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7209 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7210 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7211 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7212 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7213 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7214 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7215 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7216 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7217 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7218 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7219 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7220 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7221 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7222 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7223 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7224 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
7225 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7226 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7227 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
7228 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7229 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7230 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7231 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7232 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7233 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
7234 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
7235 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7236 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7237 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7238 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7239 texlive-common texlive-doc-base texlive-fonts-recommended
7240 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7241 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7242 xulrunner-
1.9</p
>
7248 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
7249 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
7250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
7251 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
7252 <description><p
>The last few days I have done some upgrade testing in Debian, to
7253 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7254 have been discovered and reported in the process
7255 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
7256 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
7257 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
7258 kdebase-workspace-data), and to get a more regular testing going on, I
7259 am working on a script to automate the test.
</p
>
7261 <p
>The idea is to create a Lenny chroot and use tasksel to install a
7262 Gnome or KDE desktop installation inside the chroot before upgrading
7263 it. To ensure no services are started in the chroot, a policy-rc.d
7264 script is inserted. To make sure tasksel believe it is to install a
7265 desktop on a laptop, the tasksel tests are replaced in the chroot
7266 (only acceptable because this is a throw-away chroot).
</p
>
7268 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7269 currently always fail because udev refuses to upgrade with the kernel
7270 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7271 is created. The bug report
7272 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
7273 this problem do not trigger in a chroot, but I touch the file anyway
7274 to make sure the upgrade go well. Testing on virtual and real
7275 hardware have failed me because of udev so far, and creating this file
7276 do the trick in such settings anyway. This is a
7277 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
7278 issue
</a
> and the current udev behaviour is intended by the udev
7279 maintainer because he lack the resources to rewrite udev to keep
7280 working with old kernels or something like that. I really wish the
7281 udev upstream would keep udev backwards compatible, to avoid such
7282 upgrade problem, but given that they fail to do so, I guess
7283 documenting the way out of this mess is the best option we got for
7284 Debian Squeeze.
</p
>
7286 <p
>Anyway, back to the task at hand, testing upgrades. This test
7287 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
7290 <blockquote
><pre
>
7294 if [
"$
1" ] ; then
7303 exec
&lt; /dev/null
7305 mirror=http://ftp.skolelinux.org/debian
7306 tmpdir=chroot-$from-upgrade-$to-$desktop
7308 debootstrap $from $tmpdir $mirror
7309 chroot $tmpdir aptitude update
7310 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
7314 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7318 mount -t proc proc $tmpdir/proc
7319 # Make sure proc is unmounted also on failure
7320 trap exit_cleanup EXIT INT
7322 chroot $tmpdir aptitude -y install debconf-utils
7324 # Make sure tasksel autoselection trigger. It need the test scripts
7325 # to return the correct answers.
7326 echo tasksel tasksel/desktop multiselect $desktop | \
7327 chroot $tmpdir debconf-set-selections
7329 # Include the desktop and laptop task
7330 for test in desktop laptop ; do
7331 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
7335 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7338 DEBIAN_FRONTEND=noninteractive
7339 DEBIAN_PRIORITY=critical
7340 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7341 chroot $tmpdir tasksel --new-install
7343 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
7344 chroot $tmpdir aptitude update
7345 touch $tmpdir/etc/udev/kernel-upgrade
7346 chroot $tmpdir aptitude -y dist-upgrade
7348 </pre
></blockquote
>
7350 <p
>I suspect it would be useful to test upgrades with both apt-get and
7351 with aptitude, but I have not had time to look at how they behave
7352 differently so far. I hope to get a cron job running to do the test
7353 regularly and post the result on the web. The Gnome upgrade currently
7354 work, while the KDE upgrade fail because of the bug in
7355 kdebase-workspace-data
</p
>
7357 <p
>I am not quite sure what kind of extract from the huge upgrade logs
7358 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
7359 post, so I will refrain from trying. I can report that for Gnome,
7360 aptitude report
760 packages upgraded,
448 newly installed,
129 to
7361 remove and
1 not upgraded and
1024MB need to be downloaded while for
7362 KDE the same numbers are
702 packages upgraded,
507 newly installed,
7363 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
7365 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
7366 is able to migrate to dependency based boot sequencing and parallel
7367 booting without a hitch. Was unsure if there were still bugs with
7368 packages failing to clean up their obsolete init.d script during
7369 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7375 <title>Upstart or sysvinit - as init.d scripts see it
</title>
7376 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
7377 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
7378 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
7379 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
7380 scripts to migrate (some of) their operations to upstart job while
7381 keeping the init.d for hurd and kfreebsd. The packages with such
7382 needs will need a way to get their init.d scripts to behave
7383 differently when used with sysvinit and with upstart. Because of
7384 this, I had a look at the environment variables set when a init.d
7385 script is running under upstart, and when it is not.
</p
>
7387 <p
>With upstart, I notice these environment variables are set when a
7388 script is started from rcS.d/ (ignoring some irrelevant ones like
7391 <blockquote
><pre
>
7397 UPSTART_EVENTS=startup
7399 UPSTART_JOB=rc-sysinit
7400 </pre
></blockquote
>
7402 <p
>With sysvinit, these environment variables are set for the same
7405 <blockquote
><pre
>
7406 INIT_VERSION=sysvinit-
2.88
7411 </pre
></blockquote
>
7413 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
7414 sysvinit are not set by upstart. Not sure if it is intentional or not
7415 to not be compatible with sysvinit in this regard.
</p
>
7417 <p
>For scripts needing to behave differently when upstart is used,
7418 looking for the UPSTART_JOB environment variable seem to be a good
7424 <title>A manual for standards wars...
</title>
7425 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
7426 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
7427 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
7428 <description><p
>Via the
7429 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
7430 of Rob Weir
</a
> I came across the very interesting essay named
7431 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
7432 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
7433 following the standards wars of today.
</p
>
7438 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
7439 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
7440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
7441 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
7442 <description><p
>When using sitesummary at a site to track machines, it is possible
7443 to get a list of the machine types in use thanks to the DMI
7444 information extracted from each machine. The script to do so is
7445 included in the sitesummary package, and here is example output from
7446 the Skolelinux build servers:
</p
>
7448 <blockquote
><pre
>
7449 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7451 Dell Computer Corporation
1
7454 eserver xSeries
345 -[
8670M1X]-
1
7458 </pre
></blockquote
>
7460 <p
>The quality of the report depend on the quality of the DMI tables
7461 provided in each machine. Here there are Intel machines without model
7462 information listed with Intel as vendor and no model, and virtual Xen
7463 machines listed as [no-dmi-info]. One can add -l as a command line
7464 option to list the individual machines.
</p
>
7466 <p
>A larger list is
7467 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
7468 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
7469 provide the basic sitesummary report publicly. In their report there
7470 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
7471 their machines, and as sitesummary is available in both distributions,
7472 it is trivial to get all of them to report to the same central
7473 collector.
</p
>
7478 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
7479 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
7480 <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>
7481 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
7482 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
7483 start at boot when an NVidia video card is used is handled. The
7484 problem seem to be that the nvidia X.org driver uses a long time to
7485 initialize, and this duration is longer than kdm is configured to
7488 <p
>I came across two bugs related to this issue,
7489 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
7490 against initscripts and passed on to nvidia-glx when it became obvious
7491 that the nvidia drivers were involved, and
7492 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
7493 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
7495 <p
>To me, it seem that no-one is interested in actually solving the
7496 problem nvidia video card owners experience and make sure the Debian
7497 distribution work out of the box for these users. The nvidia driver
7498 maintainers expect kdm to be set up to wait longer, while kdm expect
7499 the nvidia driver maintainers to fix the driver to start faster, and
7500 while they wait for each other I guess the users end up switching to a
7501 distribution that work for them. I have no idea what the solution is,
7502 but I am pretty sure that waiting for each other is not it.
</p
>
7504 <p
>I wonder why we end up handling bugs this way.
</p
>
7509 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
7510 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
7511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
7512 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
7513 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
7514 The feature seem to hold up pretty well, but three fairly serious
7515 issues are known and should be solved:
7519 <li
>The wicd package seen to
7520 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
7521 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
7522 parallel booting is enabled. No idea why, but the wicd maintainer
7523 seem to be on the case.
</li
>
7525 <li
>The nvidia X driver seem to
7526 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
7527 triggered more easily when parallel booting is in effect. The
7528 maintainer is on the case.
</li
>
7530 <li
>The sysv-rc package fail to properly enable dependency based boot
7531 sequencing (the shutdown is broken) when old file-rc users
7532 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
7533 sysv-rc. One way to solve it would be for file-rc to create
7534 /etc/init.d/.legacy-bootordering, and another is to try to make
7535 sysv-rc more robust. Will investigate some more and probably upload a
7536 workaround in sysv-rc to help those trying to move from file-rc to
7537 sysv-rc get a working shutdown.
</li
>
7539 </ul
></p
>
7541 <p
>All in all not many surprising issues, and all of them seem
7542 solvable before Squeeze is released. In addition to these there are
7543 some packages with bugs in their dependencies and run level settings,
7544 which I expect will be fixed in a reasonable time span.
</p
>
7546 <p
>If you report any problems with dependencies in init.d scripts to
7547 the BTS, please usertag the report to get it to show up at
7548 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7549 list of usertagged bugs related to this
</a
>.
</p
>
7551 <p
>Update: Correct bug number to file-rc issue.
</p
>
7556 <title>More flexible firmware handling in debian-installer
</title>
7557 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
7558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
7559 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
7560 <description><p
>After a long break from debian-installer development, I finally
7561 found time today to return to the project. Having to spend less time
7562 working dependency based boot in debian, as it is almost complete now,
7563 definitely helped freeing some time.
</p
>
7565 <p
>A while back, I ran into a problem while working on Debian Edu. We
7566 include some firmware packages on the Debian Edu CDs, those needed to
7567 get disk and network controllers working. Without having these
7568 firmware packages available during installation, it is impossible to
7569 install Debian Edu on the given machine, and because our target group
7570 are non-technical people, asking them to provide firmware packages on
7571 an external medium is a support pain. Initially, I expected it to be
7572 enough to include the firmware packages on the CD to get
7573 debian-installer to find and use them. This proved to be wrong.
7574 Next, I hoped it was enough to symlink the relevant firmware packages
7575 to some useful location on the CD (tried /cdrom/ and
7576 /cdrom/firmware/). This also proved to not work, and at this point I
7577 found time to look at the debian-installer code to figure out what was
7578 going to work.
</p
>
7580 <p
>The firmware loading code is in the hw-detect package, and a closer
7581 look revealed that it would only look for firmware packages outside
7582 the installation media, so the CD was never checked for firmware
7583 packages. It would only check USB sticks, floppies and other
7584 "external
" media devices. Today I changed it to also look in the
7585 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7586 solve the problem I ran into with Debian edu. I also changed it to
7587 look in /firmware/, to make sure the installer also find firmware
7588 provided in the initrd when booting the installer via PXE, to allow us
7589 to provide the same feature in the PXE setup included in Debian
7592 <p
>To make sure firmware deb packages with a license questions are not
7593 activated without asking if the license is accepted, I extended
7594 hw-detect to look for preinst scripts in the firmware packages, and
7595 run these before activating the firmware during installation. The
7596 license question is asked using debconf in the preinst, so this should
7597 solve the issue for the firmware packages I have looked at so far.
</p
>
7599 <p
>If you want to discuss the details of these features, please
7600 contact us on debian-boot@lists.debian.org.
</p
>
7605 <title>Parallellized boot is now the default in Debian/unstable
</title>
7606 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
7607 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
7608 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
7609 <description><p
>Since this evening, parallel booting is the default in
7610 Debian/unstable for machines using dependency based boot sequencing.
7611 Apparently the testing of concurrent booting has been wider than
7612 expected, if I am to believe the
7613 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7614 on debian-devel@
</a
>, and I concluded a few days ago to move forward
7615 with the feature this weekend, to give us some time to detect any
7616 remaining problems before Squeeze is frozen. If serious problems are
7617 detected, it is simple to change the default back to sequential boot.
7618 The upload of the new sysvinit package also activate a new upstream
7621 More information about
7622 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7623 based boot sequencing
</a
> is available from the Debian wiki. It is
7624 currently possible to disable parallel booting when one run into
7625 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
7627 <blockquote
><pre
>
7629 </pre
></blockquote
>
7631 <p
>If you report any problems with dependencies in init.d scripts to
7632 the BTS, please usertag the report to get it to show up at
7633 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7634 list of usertagged bugs related to this
</a
>.
</p
>
7639 <title>Sitesummary tip: Listing MAC address of all clients
</title>
7640 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
7641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
7642 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
7643 <description><p
>In the recent Debian Edu versions, the
7644 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
7645 system
</a
> is used to keep track of the machines in the school
7646 network. Each machine will automatically report its status to the
7647 central server after boot and once per night. The network setup is
7648 also reported, and using this information it is possible to get the
7649 MAC address of all network interfaces in the machines. This is useful
7650 to update the DHCP configuration.
</p
>
7652 <p
>To give some idea how to use sitesummary, here is a one-liner to
7653 ist all MAC addresses of all machines reporting to sitesummary. Run
7654 this on the collector host:
</p
>
7656 <blockquote
><pre
>
7657 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
7658 </pre
></blockquote
>
7660 <p
>This will list all MAC addresses assosiated with all machine, one
7661 line per machine and with space between the MAC addresses.
</p
>
7663 <p
>To allow system administrators easier job at adding static DHCP
7664 addresses for hosts, it would be possible to extend this to fetch
7665 machine information from sitesummary and update the DHCP and DNS
7666 tables in LDAP using this information. Such tool is unfortunately not
7667 written yet.
</p
>
7672 <title>systemd, an interesting alternative to upstart
</title>
7673 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
7674 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
7675 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
7676 <description><p
>The last few days a new boot system called
7677 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
7679 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
7681 to the free software world. I have not yet had time to play around
7682 with it, but it seem to be a very interesting alternative to
7683 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
7684 a good alternative for Debian when we are able to switch to an event
7685 based boot system. Tollef is
7686 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
7687 systemd into Debian, and I look forward to seeing how well it work. I
7688 like the fact that systemd handles init.d scripts with dependency
7689 information natively, allowing them to run in parallel where upstart
7690 at the moment do not.
</p
>
7692 <p
>Unfortunately do systemd have the same problem as upstart regarding
7693 platform support. It only work on recent Linux kernels, and also need
7694 some new kernel features enabled to function properly. This means
7695 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7696 system. Not sure how that will be handled if systemd proves to be the
7697 way forward.
</p
>
7699 <p
>In the mean time, based on the
7700 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7701 on debian-devel@
</a
> regarding parallel booting in Debian, I have
7702 decided to enable full parallel booting as the default in Debian as
7703 soon as possible (probably this weekend or early next week), to see if
7704 there are any remaining serious bugs in the init.d dependencies. A
7705 new version of the sysvinit package implementing this change is
7706 already in experimental. If all go well, Squeeze will be released
7707 with parallel booting enabled by default.
</p
>
7712 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
7713 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
7714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
7715 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
7716 <description><p
>These days, the init.d script dependencies in Squeeze are quite
7717 complete, so complete that it is actually possible to run all the
7718 init.d scripts in parallell based on these dependencies. If you want
7719 to test your Squeeze system, make sure
7720 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7721 based boot sequencing
</a
> is enabled, and add this line to
7722 /etc/default/rcS:
</p
>
7724 <blockquote
><pre
>
7725 CONCURRENCY=makefile
7726 </pre
></blockquote
>
7728 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
7729 scripts in parallel using the dependency information stored in
7730 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7731 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7732 to try to start the kdm and gdm scripts as early as possible, and will
7733 start the facilities required by kdm or gdm as early as possible to
7734 make this happen.
</p
>
7736 <p
>Give it a try, and see if you like the result. If some services
7737 fail to start properly, it is most likely because they have incomplete
7738 init.d script dependencies in their startup script (or some of their
7739 dependent scripts have incomplete dependencies). Report bugs and get
7740 the package maintainers to fix it. :)
</p
>
7742 <p
>Running scripts in parallel could be the default in Debian when we
7743 manage to get the init.d script dependencies complete and correct. I
7744 expect we will get there in Squeeze+
1, if we get manage to test and
7745 fix the remaining issues.
</p
>
7747 <p
>If you report any problems with dependencies in init.d scripts to
7748 the BTS, please usertag the report to get it to show up at
7749 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7750 list of usertagged bugs related to this
</a
>.
</p
>
7755 <title>Debian has switched to dependency based boot sequencing
</title>
7756 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
7757 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
7758 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
7759 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
7760 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
7761 have been migrated to using dependency based boot sequencing. This
7762 conclude work me and others have been doing for the last three days.
7763 It feels great to see this finally part of the default Debian
7764 installation. Now we just need to weed out the last few problems that
7765 are bound to show up, to get everything ready for Squeeze.
</p
>
7767 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
7768 fixing the more fundamental problem of handing the event based
7769 non-predictable kernel in the early boot.
</p
>
7774 <title>Taking over sysvinit development
</title>
7775 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
7776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
7777 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
7778 <description><p
>After several years of frustration with the lack of activity from
7779 the existing sysvinit upstream developer, I decided a few weeks ago to
7780 take over the package and become the new upstream. The number of
7781 patches to track for the Debian package was becoming a burden, and the
7782 lack of synchronization between the distribution made it hard to keep
7783 the package up to date.
</p
>
7785 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7786 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
7787 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
7788 and Fedora), based on the patches currently in use in these
7789 distributions. We Debian maintainers plan to move to this tarball as
7790 the new upstream as soon as we find time to do the merge. Since the
7791 new tarball was created, we agreed with Werner at SuSe to make a new
7792 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
7793 development there. The project is registered and currently waiting
7794 for approval by the Savannah administrators, and as soon as it is
7795 approved, we will import the old versions from svn and continue
7796 working on the future release.
</p
>
7798 <p
>It is a bit ironic that this is done now, when some of the involved
7799 distributions are moving to upstart as a syvinit replacement.
</p
>
7804 <title>Debian boots quicker and quicker
</title>
7805 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
7806 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
7807 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
7808 <description><p
>I spent Monday and tuesday this week in London with a lot of the
7809 people involved in the boot system on Debian and Ubuntu, to see if we
7810 could find more ways to speed up the boot system. This was an Ubuntu
7812 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
7813 gathering
</a
>. It was quite productive. We also discussed the future
7814 of boot systems, and ways to handle the increasing number of boot
7815 issues introduced by the Linux kernel becoming more and more
7816 asynchronous and event base. The Ubuntu approach using udev and
7817 upstart might be a good way forward. Time will show.
</p
>
7819 <p
>Anyway, there are a few ways at the moment to speed up the boot
7820 process in Debian. All of these should be applied to get a quick
7825 <li
>Use dash as /bin/sh.
</li
>
7827 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
7828 clock is in UTC.
</li
>
7830 <li
>Install and activate the insserv package to enable
7831 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7832 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
7836 These points are based on the Google summer of code work done by
7837 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
7840 <p
>Support for makefile-style concurrency during boot was uploaded to
7841 unstable yesterday. When we tested it, we were able to cut
6 seconds
7842 from the boot sequence. It depend on very correct dependency
7843 declaration in all init.d scripts, so I expect us to find edge cases
7844 where the dependences in some scripts are slightly wrong when we start
7845 using this.
</p
>
7847 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7848 introduced by Raphael Geissert today, one that could affect the
7849 startup speed as well. Instead of starting some scripts concurrently
7850 from rcS.d/ and another set of scripts from rc2.d/, it would be
7851 possible to run a of them in the same process. A quick way to test
7852 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
7853 insserv
'. Will need to test if that work. :)
</p
>
7858 <title>BSAs påstander om piratkopiering møter motstand
</title>
7859 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
7860 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
7861 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
7862 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
7863 programvareselskapene som Microsoft og Apple, publisert en rapport der
7864 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7865 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7867 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
7868 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
7869 dagene. Et spesielt interessant kommentar fra Sverige,
7870 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
7871 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
7874 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
7875 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7876 företag.
"Man bör nog kanske inte se de här siffrorna som helt
7877 exakta
", säger BSAs Sverigechef John Hugosson.
7880 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
7881 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
7882 piracy figures need a shot of reality
</a
> og
<a
7883 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
7884 Copyright Treaty Work?
</a
></p
>
7886 <p
>Fant lenkene via
<a
7887 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
7888 på Slashdot
</a
>.
</p
>
7893 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
7894 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
7895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
7896 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
7897 <description><p
>Kom over
7898 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
7899 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7900 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7901 jobber til daglig. En rask opptelling forteller meg at vi har
490
7902 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
7903 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7904 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7909 <title>Kryptert harddisk - naturligvis
</title>
7910 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7911 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7912 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7913 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7914 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7915 når en tar tap av arbeidstid, fortrolige dokumenter,
7916 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7917 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7918 til at jeg har kryptert harddisken på både kontormaskinen og min
7919 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7920 komme på avveie, den første informasjon relatert til jobben min ved
7921 Universitetet i Oslo, og den andre relatert til blant annet
7922 foreningsarbeide. Kryptering av diskene gjør at det er lite
7923 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7924 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7925 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7926 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7927 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7928 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7929 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7930 det er gjort slik jeg gjør det er minimale, og gevinstene er
7931 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7932 maskinen reinstalleres og alt er tapt.
</p
>
7934 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7935 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7936 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7937 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7938 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7939 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7940 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7941 betydelige.
</p
>
7946 <title>Two projects that have improved the quality of free software a lot
</title>
7947 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7949 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7950 <description><p
>There are two software projects that have had huge influence on the
7951 quality of free software, and I wanted to mention both in case someone
7952 do not yet know them.
</p
>
7954 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7955 tool to detect and expose errors in the memory handling of programs.
7956 It is easy to use, all one need to do is to run
'valgrind program
',
7957 and it will report any problems on stdout. It is even better if the
7958 program include debug information. With debug information, it is able
7959 to report the source file name and line number where the problem
7960 occurs. It can report things like
'reading past memory block in file
7961 X line N, the memory block was allocated in file Y, line M
', and
7962 'using uninitialised value in control logic
'. This tool has made it
7963 trivial to investigate reproducible crash bugs in programs, and have
7964 reduced the number of this kind of bugs in free software a lot.
7966 <p
>The second one is
7967 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7968 a source code checker. It is able to process the source of a program
7969 and find problems in the logic without running the program. It
7970 started out as the Stanford Checker and became well known when it was
7971 used to find bugs in the Linux kernel. It is now a commercial tool
7972 and the company behind it is running
7973 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7974 free software community, where a lot of free software projects get
7975 their source checked for free. Several thousand defects have been
7976 found and fixed so far. It can find errors like
'lock L taken in file
7977 X line N is never released if exiting in line M
', or
'the code in file
7978 Y lines O to P can never be executed
'. The projects included in the
7979 community service project have managed to get rid of a lot of
7980 reliability problems thanks to Coverity.
</p
>
7982 <p
>I believe tools like this, that are able to automatically find
7983 errors in the source, are vital to improve the quality of software and
7984 make sure we can get rid of the crashing and failing software we are
7985 surrounded by today.
</p
>
7990 <title>No patch is not better than a useless patch
</title>
7991 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7992 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7993 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7994 <description><p
>Julien Blache
7995 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7996 patch is better than a useless patch
</a
>. I completely disagree, as a
7997 patch allow one to discuss a concrete and proposed solution, and also
7998 prove that the issue at hand is important enough for someone to spent
7999 time on fixing it. No patch do not provide any of these positive
8000 properties.
</p
>
8005 <title>Standardize on protocols and formats, not vendors and applications
</title>
8006 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8008 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8009 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8010 very good one to form a long lived computer infrastructure. It is the
8011 simple one, lost by many in todays computer industry: Standardize on
8012 open network protocols and open exchange/storage formats, not applications.
8013 Applications come and go, while protocols and files tend to stay, and
8014 thus one want to make it easy to change application and vendor, while
8015 avoiding conversion costs and locking users to a specific platform or
8016 application.
</p
>
8018 <p
>This approach make it possible to replace the client applications
8019 independently of the server applications. One can even allow users to
8020 use several different applications as long as they handle the selected
8021 protocol and format. In the normal case, only one client application
8022 is recommended and users only get help if they choose to use this
8023 application, but those that want to deviate from the easy path are not
8024 blocked from doing so.
</p
>
8026 <p
>It also allow us to replace the server side without forcing the
8027 users to replace their applications, and thus allow us to select the
8028 best server implementation at any moment, when scale and resouce
8029 requirements change.
</p
>
8031 <p
>I strongly recommend standardizing - on open network protocols and
8032 open formats, but I would never recommend standardizing on a single
8033 application that do not use open network protocol or open formats.
</p
>
8038 <title>Returning from Skolelinux developer gathering
</title>
8039 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8040 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8041 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8042 <description><p
>I
'm sitting on the train going home from this weekends Debian
8043 Edu/Skolelinux development gathering. I got a bit done tuning the
8044 desktop, and looked into the dynamic service location protocol
8045 implementation avahi. It look like it could be useful for us. Almost
8046 30 people participated, and I believe it was a great environment to
8047 get to know the Skolelinux system. Walter Bender, involved in the
8048 development of the Sugar educational platform, presented his stuff and
8049 also helped me improve my OLPC installation. He also showed me that
8050 his Turtle Art application can be used in standalone mode, and we
8051 agreed that I would help getting it packaged for Debian. As a
8052 standalone application it would be great for Debian Edu. We also
8053 tried to get the video conferencing working with two OLPCs, but that
8054 proved to be too hard for us. The application seem to need more work
8055 before it is ready for me. I look forward to getting home and relax
8061 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8062 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8063 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8064 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8065 <description><p
>The state of standardized LDAP schemas on Linux is far from
8066 optimal. There is RFC
2307 documenting one way to store NIS maps in
8067 LDAP, and a modified version of this normally called RFC
2307bis, with
8068 some modifications to be compatible with Active Directory. The RFC
8069 specification handle the content of a lot of system databases, but do
8070 not handle DNS zones and DHCP configuration.
</p
>
8072 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
8073 we would like to store information about users, SMB clients/hosts,
8074 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8075 and LTSP configuration in LDAP. These objects have a lot in common,
8076 but with the current LDAP schemas it is not possible to have one
8077 object per entity. For example, one need to have at least three LDAP
8078 objects for a given computer, one with the SMB related stuff, one with
8079 DNS information and another with DHCP information. The schemas
8080 provided for DNS and DHCP are impossible to combine into one LDAP
8081 object. In addition, it is impossible to implement quick queries for
8082 netgroup membership, because of the way NIS triples are implemented.
8083 It just do not scale. I believe it is time for a few RFC
8084 specifications to cleam up this mess.
</p
>
8086 <p
>I would like to have one LDAP object representing each computer in
8087 the network, and this object can then keep the SMB (ie host key), DHCP
8088 (mac address/name) and DNS (name/IP address) settings in one place.
8089 It need to be efficently stored to make sure it scale well.
</p
>
8091 <p
>I would also like to have a quick way to map from a user or
8092 computer and to the net group this user or computer is a member.
</p
>
8094 <p
>Active Directory have done a better job than unix heads like myself
8095 in this regard, and the unix side need to catch up. Time to start a
8096 new IETF work group?
</p
>
8101 <title>Endelig er Debian Lenny gitt ut
</title>
8102 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
8103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
8104 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
8105 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
8106 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
8107 Et langt steg videre for Debian-prosjektet, og en rekke nye
8108 programpakker blir nå tilgjengelig for de av oss som bruker den
8109 stabile utgaven av Debian. Neste steg er nå å få
8110 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
8111 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
8112 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8113 slippes løs på skolene. Takk til alle debian-utviklerne som har
8114 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8115 bootsekvens tilgjengelig i stabil utgave, vha pakken
8116 <tt
>insserv
</tt
>.
</p
>
8121 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
8122 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
8123 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
8124 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
8125 <description><p
>This weekend we had a small developer gathering for Debian Edu in
8126 Oslo. Most of Saturday was used for the general assemly for the
8127 member organization, but the rest of the weekend I used to tune the
8128 LTSP installation. LTSP now work out of the box on the
10-network.
8129 Acer Aspire One proved to be a very nice thin client, with both
8130 screen, mouse and keybard in a small box. Was working on getting the
8131 diskless workstation setup configured out of the box, but did not
8132 finish it before the weekend was up.
</p
>
8134 <p
>Did not find time to look at the
4 VGA cards in one box we got from
8135 the Brazilian group, so that will have to wait for the next
8136 development gathering. Would love to have the Debian Edu installer
8137 automatically detect and configure a multiseat setup when it find one
8138 of these cards.
</p
>
8143 <title>The sorry state of multimedia browser plugins in Debian
</title>
8144 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
8145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
8146 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
8147 <description><p
>Recently I have spent some time evaluating the multimedia browser
8148 plugins available in Debian Lenny, to see which one we should use by
8149 default in Debian Edu. We need an embedded video playing plugin with
8150 control buttons to pause or stop the video, and capable of streaming
8151 all the multimedia content available on the web. The test results and
8152 notes are available on
8153 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
8154 Debian wiki
</a
>. I was surprised how few of the plugins are able to
8155 fill this need. My personal video player favorite, VLC, has a really
8156 bad plugin which fail on a lot of the test pages. A lot of the MIME
8157 types I would expect to work with any free software player (like
8158 video/ogg), just do not work. And simple formats like the
8159 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
8160 totem and vlc plugins. I hope the situation will improve soon. No
8161 wonder sites use the proprietary Adobe flash to play video.
</p
>
8163 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
8164 be the only one fitting our needs. :/
</p
>