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>Debian APT upgrade without enough free space on the disk...
</title>
11 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
13 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
14 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
15 for a while, and when I need to update it there is not enough free
16 space on the disk for apt to do a normal
'apt upgrade
'. I normally
17 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
18 upgrade only some of the packages in one batch, until the amount of
19 packages to download fall below the amount of free space available.
20 Today, I had about
500 packages to upgrade, and after a while I got
21 tired of trying to install chunks of packages manually. I concluded
22 that I did not have the spare hours required to complete the task, and
23 decided to see if I could automate it. I came up with this small
24 script which I call
'apt-in-chunks
':
</p
>
26 <p
><blockquote
><pre
>
29 # Upgrade packages when the disk is too full to upgrade every
30 # upgradable package in one lump. Fetching packages to upgrade using
31 # apt, and then installing using dpkg, to avoid changing the package
32 # flag for manual/automatic.
37 if [
"$
1" ]; then
38 grep -v
"$
1"
44 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
45 echo
"Upgrading $p
"
47 apt install --download-only -y $p
48 for f in /var/cache/apt/archives/*.deb; do
49 if [ -e
"$f
" ]; then
50 dpkg -i /var/cache/apt/archives/*.deb
55 </pre
></blockquote
></p
>
57 <p
>The script will extract the list of packages to upgrade, try to
58 download the packages needed to upgrade one package, install the
59 downloaded packages using dpkg. The idea is to upgrade packages
60 without changing the APT mark for the package (ie the one recording of
61 the package was manually requested or pulled in as a dependency). To
62 use it, simply run it as root from the command line. If it fail, try
63 'apt install -f
' to clean up the mess and run the script again. This
64 might happen if the new packages conflict with one of the old
65 packages. dpkg is unable to remove, while apt can do this.
</p
>
67 <p
>It take one option, a package to ignore in the list of packages to
68 upgrade. The option to ignore a package is there to be able to skip
69 the packages that are simply too large to unpack. Today this was
70 'ghc
', but I have run into other large packages causing similar
71 problems earlier (like TeX).
</p
>
73 <p
>As usual, if you use Bitcoin and want to show your support of my
74 activities, please send Bitcoin donations to my address
75 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
80 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
81 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
82 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
83 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
84 <description><p
>A new version of the
85 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
86 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
87 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
88 useful. It was uploaded the last few days, and the last update will
89 enter testing tomorrow. See the
90 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
91 notes
</a
> for the list of bug fixes and new features. Version
3.2
92 was announced
6 days ago. We will try to get it into Debian as
95 <p
>More information related to
3D printing is available on the
96 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
97 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
100 <p
>As usual, if you use Bitcoin and want to show your support of my
101 activities, please send Bitcoin donations to my address
102 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
107 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
108 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
110 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
111 <description><p
>After several months of working and waiting, I am happy to report
112 that the nice and user friendly
3D printer slicer software Cura just
113 entered Debian Unstable. It consist of five packages,
114 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
115 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
116 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
117 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
118 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
119 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
120 two, uranium and cura, entered Unstable yesterday. This should make
121 it easier for Debian users to print on at least the Ultimaker class of
122 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
123 make life easier for at least me. :)
</p
>
125 <p
>The work to make this happen was done by Gregor Riepl, and I was
126 happy to assist him in sponsoring the packages. With the introduction
127 of Cura, Debian is up to three
3D printer slicers at your service,
128 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
129 printer, give it a go. :)
</p
>
131 <p
>The
3D printer software is maintained by the
3D printer Debian
132 team, flocking together on the
133 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
135 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
136 IRC channel.
</p
>
138 <p
>The next step for Cura in Debian is to update the cura package to
139 version
3.0.3 and then update the entire set of packages to version
140 3.1.0 which showed up the last few days.
</p
>
145 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
146 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
148 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
149 <description><p
>At my nearby maker space,
150 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
151 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
152 on Windows and MacOS X than Linux, because the software involved had
153 to be manually compiled and set up on Linux while premade packages
154 worked out of the box on Windows and MacOS X. I found this annoying,
155 as the software involved,
156 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
157 and should be trivial to get up and running on Linux if someone took
158 the time to package it for the relevant distributions. I even found
159 <a href=
"https://bugs.debian.org/
706656">a request for adding into
160 Debian
</a
> from
2013, which had seem some activity over the years but
161 never resulted in the software showing up in Debian. So a few days
162 ago I offered my help to try to improve the situation.
</p
>
164 <p
>Now I am very happy to see that all the packages required by a
165 working Cura in Debian are uploaded into Debian and waiting in the NEW
166 queue for the ftpmasters to have a look. You can track the progress
168 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
169 status page for the
3D printer team
</a
>.
</p
>
171 <p
>The uploaded packages are a bit behind upstream, and was uploaded
172 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
173 queue
</a
> while we work up updating the packages to the latest
174 upstream version.
</p
>
176 <p
>On a related note, two competitors for Cura, which I found harder
177 to use and was unable to configure correctly for Ultimaker
2+ in the
178 short time I spent on it, are already in Debian. If you are looking
179 for
3D printer
"slicers
" and want something already available in
181 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
182 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
183 The latter is a fork of the former.
</p
>
185 <p
>As usual, if you use Bitcoin and want to show your support of my
186 activities, please send Bitcoin donations to my address
187 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
192 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
193 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
195 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
196 <description><p
>Every mobile phone announce its existence over radio to the nearby
197 mobile cell towers. And this radio chatter is available for anyone
198 with a radio receiver capable of receiving them. Details about the
199 mobile phones with very good accuracy is of course collected by the
200 phone companies, but this is not the topic of this blog post. The
201 mobile phone radio chatter make it possible to figure out when a cell
202 phone is nearby, as it include the SIM card ID (IMSI). By paying
203 attention over time, one can see when a phone arrive and when it leave
204 an area. I believe it would be nice to make this information more
205 available to the general public, to make more people aware of how
206 their phones are announcing their whereabouts to anyone that care to
209 <p
>I am very happy to report that we managed to get something
210 visualizing this information up and running for
211 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
212 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
213 library. The solution is based on the
214 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
215 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
216 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
217 Sone from the Computer Science department of the University of
218 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
219 IMSIs) as dots in a web browser graph, with lines to the dot
220 representing mobile base station it is talking to. It was working in
221 the lab yesterday, and was moved into place this morning.
</p
>
223 <p
>We set up a fairly powerful desktop machine using Debian
224 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
225 connected and visualize the visible cell phone towers using an
226 <a href=
"https://github.com/marlow925/hopglass
">English version of
227 Hopglass
</a
>. A fairly powerfull machine is needed as the
228 grgsm_livemon_headless processes from
229 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
230 the radio signal to data packages is quite CPU intensive.
</p
>
232 <p
>The frequencies to listen to, are identified using a slightly
233 patched scan-and-livemon (to set the --args values for each receiver),
234 and the Hopglass data is generated using the
235 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
236 in my meshviewer-output branch
</a
>. For some reason we could not get
237 more than four SDRs working. There is also a geographical map trying
238 to show the location of the base stations, but I believe their
239 coordinates are hardcoded to some random location in Germany, I
240 believe. The code should be replaced with code to look up location in
241 a text file, a sqlite database or one of the online databases
243 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
244 issue for the topic
</a
>.
246 <p
>If this sound interesting, visit the stand at the festival!
</p
>
251 <title>Easier recipe to observe the cell phones around you
</title>
252 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
253 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
254 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
255 <description><p
>A little more than a month ago I wrote
256 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
257 to observe the SIM card ID (aka IMSI number) of mobile phones talking
258 to nearby mobile phone base stations using Debian GNU/Linux and a
259 cheap USB software defined radio
</a
>, and thus being able to pinpoint
260 the location of people and equipment (like cars and trains) with an
261 accuracy of a few kilometer. Since then we have worked to make the
262 procedure even simpler, and it is now possible to do this without any
263 manual frequency tuning and without building your own packages.
</p
>
265 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
266 package is now included in Debian testing and unstable, and the
267 IMSI-catcher code no longer require root access to fetch and decode
268 the GSM data collected using gr-gsm.
</p
>
270 <p
>Here is an updated recipe, using packages built by Debian and a git
271 clone of two python scripts:
</p
>
275 <li
>Start with a Debian machine running the Buster version (aka
278 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
279 python-scapy
</tt
>' as root to install required packages.
</li
>
281 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
282 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
284 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
286 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
287 scan-and-livemon
</tt
>' to locate the frequency of nearby base
288 stations and start listening for GSM packages on one of them.
</li
>
290 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
291 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
295 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
296 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
297 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
298 work with RTL
8232 and other similar USB radio receivers you can get
300 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
301 from ebay
</a
>), so for now the solution is to scan using the RTL radio
302 and only use HackRF for fetching GSM data.
</p
>
304 <p
>As far as I can tell, a cell phone only show up on one of the
305 frequencies at the time, so if you are going to track and count every
306 cell phone around you, you need to listen to all the frequencies used.
307 To listen to several frequencies, use the --numrecv argument to
308 scan-and-livemon to use several receivers. Further, I am not sure if
309 phones using
3G or
4G will show as talking GSM to base stations, so
310 this approach might not see all phones around you. I typically see
311 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
313 <p
>I
've tried to run the scanner on a
314 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
315 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
316 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
317 stdout, I am told there it is caused by a buffer overflow between the
318 radio and GNU Radio, caused by the program being unable to read the
319 GSM data fast enough. If you see a stream of
'O
's from the terminal
320 where you started scan-and-livemon, you need a give the process more
321 CPU power. Perhaps someone are able to optimize the code to a point
322 where it become possible to set up RPi3 based GSM sniffers? I tried
323 using Raspbian instead of Debian, but there seem to be something wrong
324 with GNU Radio on raspbian, causing glibc to abort().
</p
>
329 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
330 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
331 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
332 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
333 <description><p
>On friday, I came across an interesting article in the Norwegian
334 web based ICT news magazine digi.no on
335 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
336 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
337 DVB-T software defined radios. The article refered to instructions
338 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
339 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
341 <p
>The instructions said to use Ubuntu, install pip using apt (to
342 bypass apt), use pip to install pybombs (to bypass both apt and pip),
343 and the ask pybombs to fetch and build everything you need from
344 scratch. I wanted to see if I could do the same on the most recent
345 Debian packages, but this did not work because pybombs tried to build
346 stuff that no longer build with the most recent openssl library or
347 some other version skew problem. While trying to get this recipe
348 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
349 and the only piece of software dependency missing in Debian was the
350 gr-gsm package. I also found out that the lead upstream developer of
351 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
352 Debian packages provided in an Ubuntu PPA repository. All I needed to
353 do was to dget the Debian source package and built it.
</p
>
355 <p
>The IMSI collector is a python script listening for packages on the
356 loopback network device and printing to the terminal some specific GSM
357 packages with IMSI numbers in them. The code is fairly short and easy
358 to understand. The reason this work is because gr-gsm include a tool
359 to read GSM data from a software defined radio like a DVB-T USB stick
360 and other software defined radios, decode them and inject them into a
361 network device on your Linux machine (using the loopback device by
362 default). This proved to work just fine, and I
've been testing the
363 collector for a few days now.
</p
>
365 <p
>The updated and simpler recipe is thus to
</p
>
369 <li
>start with a Debian machine running Stretch or newer,
</li
>
371 <li
>build and install the gr-gsm package available from
372 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
374 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
376 <li
>run grgsm_livemon and adjust the frequency until the terminal
377 where it was started is filled with a stream of text (meaning you
378 found a GSM station).
</li
>
380 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
384 <p
>To make it even easier in the future to get this sniffer up and
385 running, I decided to package
386 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
387 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
388 #
871055</a
>), and the package was uploaded into the NEW queue today.
389 Luckily the gnuradio maintainer has promised to help me, as I do not
390 know much about gnuradio stuff yet.
</p
>
392 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
393 commercial tools like
394 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
395 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
396 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
397 Stingray
</a
>, but I hope the existance of cheap alternatives can make
398 more people realise how their whereabouts when carrying a cell phone
399 is easily tracked. Seeing the data flow on the screen, realizing that
400 I live close to a police station and knowing that the police is also
401 wearing cell phones, I wonder how hard it would be for criminals to
402 track the position of the police officers to discover when there are
403 police near by, or for foreign military forces to track the location
404 of the Norwegian military forces, or for anyone to track the location
405 of government officials...
</p
>
407 <p
>It is worth noting that the data reported by the IMSI-catcher
408 script mentioned above is only a fraction of the data broadcasted on
409 the GSM network. It will only collect one frequency at the time,
410 while a typical phone will be using several frequencies, and not all
411 phones will be using the frequencies tracked by the grgsm_livemod
412 program. Also, there is a lot of radio chatter being ignored by the
413 simple_IMSI-catcher script, which would be collected by extending the
414 parser code. I wonder if gr-gsm can be set up to listen to more than
415 one frequency?
</p
>
420 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
421 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
422 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
423 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
424 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
426 <p
>I finally received a copy of the Norwegian Bokmål edition of
427 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
428 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
429 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
430 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
431 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
432 price. The book is also available for download in electronic form as
433 PDF, EPUB and Mobipocket, as can be
434 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
435 as a web page
</a
>.
</p
>
437 <p
>This is the second book I publish (the first was the book
438 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
440 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
441 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
443 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
444 Bokmål
</a
>), and I am very excited to finally wrap up this
446 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
447 for Debian-administratoren
</a
>" will be well received.
</p
>
452 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
453 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
454 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
455 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
456 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
457 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
458 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
459 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
460 på om den fri oversetterløsningen
461 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
462 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
464 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
467 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
468 rolle og muligheter til å håndtere internasjonale utfordringer, som
469 for eksempel flykningekrisen.
</p
>
471 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
474 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
475 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
480 <p
>Dette oversetter Apertium slik:
</p
>
483 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
484 andre aktørar og høve til å handtera internasjonale utfordringar, som
485 til dømes *flykningekrisen.
</p
>
487 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
491 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
492 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
497 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
498 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
499 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
500 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
501 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
502 det er kanskje flisespikking. Det understreker vel bare at det alltid
503 trengs korrekturlesning etter automatisk oversettelse.
</p
>
508 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
509 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
510 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
511 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
512 <description><p
>Over the years, administrating thousand of NFS mounting linux
513 computers at the time, I often needed a way to detect if the machine
514 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
515 file or directory affected by the hang, the process (and possibly the
516 shell) will hang too. So you want to be able to detect this without
517 risking the detection process getting stuck too. It has not been
518 obvious how to do this. When the hang has lasted a while, it is
519 possible to find messages like these in dmesg:
</p
>
521 <p
><blockquote
>
522 nfs: server nfsserver not responding, still trying
523 <br
>nfs: server nfsserver OK
524 </blockquote
></p
>
526 <p
>It is hard to know if the hang is still going on, and it is hard to
527 be sure looking in dmesg is going to work. If there are lots of other
528 messages in dmesg the lines might have rotated out of site before they
529 are noticed.
</p
>
531 <p
>While reading through the nfs client implementation in linux kernel
532 code, I came across some statistics that seem to give a way to detect
533 it. The om_timeouts sunrpc value in the kernel will increase every
534 time the above log entry is inserted into dmesg. And after digging a
535 bit further, I discovered that this value show up in
536 /proc/self/mountstats on Linux.
</p
>
538 <p
>The mountstats content seem to be shared between files using the
539 same file system context, so it is enough to check one of the
540 mountstats files to get the state of the mount point for the machine.
541 I assume this will not show lazy umounted NFS points, nor NFS mount
542 points in a different process context (ie with a different filesystem
543 view), but that does not worry me.
</p
>
545 <p
>The content for a NFS mount point look similar to this:
</p
>
547 <p
><blockquote
><pre
>
549 device /dev/mapper/Debian-var mounted on /var with fstype ext3
550 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
551 opts: rw,vers=
3,rsize=
65536,wsize=
65536,namlen=
255,acregmin=
3,acregmax=
60,acdirmin=
30,acdirmax=
60,soft,nolock,proto=tcp,timeo=
600,retrans=
2,sec=sys,mountaddr=
129.240.3.145,mountvers=
3,mountport=
4048,mountproto=udp,local_lock=all
553 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
554 sec: flavor=
1,pseudoflavor=
1
555 events:
61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
556 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
557 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
558 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
560 NULL:
0 0 0 0 0 0 0 0
561 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
562 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
563 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
564 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
565 READLINK:
125 125 0 20472 18620 0 1112 1118
566 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
567 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
568 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
569 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
570 SYMLINK:
903 903 0 233428 245488 6 5865 5917
571 MKNOD:
80 80 0 20148 21760 0 299 304
572 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
573 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
574 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
575 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
576 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
577 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
578 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
579 FSINFO:
2 2 0 232 328 0 1 1
580 PATHCONF:
1 1 0 116 140 0 0 0
581 COMMIT:
0 0 0 0 0 0 0 0
583 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
585 </pre
></blockquote
></p
>
587 <p
>The key number to look at is the third number in the per-op list.
588 It is the number of NFS timeouts experiences per file system
589 operation. Here
22 write timeouts and
5 access timeouts. If these
590 numbers are increasing, I believe the machine is experiencing NFS
591 hang. Unfortunately the timeout value do not start to increase right
592 away. The NFS operations need to time out first, and this can take a
593 while. The exact timeout value depend on the setup. For example the
594 defaults for TCP and UDP mount points are quite different, and the
595 timeout value is affected by the soft, hard, timeo and retrans NFS
596 mount options.
</p
>
598 <p
>The only way I have been able to get working on Debian and RedHat
599 Enterprise Linux for getting the timeout count is to peek in /proc/.
601 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
602 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
603 command can be used to get these timeout values. But this do not work
604 on Linux, as far as I can tell. I
605 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
606 but have not seen any replies yet.
</p
>
608 <p
>Is there a better way to figure out if a Linux NFS client is
609 experiencing NFS hangs? Is there a way to detect which processes are
610 affected? Is there a way to get the NFS mount going quickly once the
611 network problem causing the NFS hang has been cleared? I would very
612 much welcome some clues, as we regularly run into NFS hangs.
</p
>
617 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
618 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</guid>
620 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
621 <description><p
>For almost a year now, we have been working on making a Norwegian
622 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
623 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
624 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
625 we are working on the proof reading to ensure consistent language and
626 use of correct computer science terms. The plan is to make the book
627 available on paper, as well as in electronic form. For that to
628 happen, the proof reading must be completed and all the figures need
629 to be translated. If you want to help out, get in touch.
</p
>
631 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
633 fresh PDF edition
</a
> in A4 format (the final book will have smaller
634 pages) of the book created every morning is available for
635 proofreading. If you find any errors, please
636 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
637 Weblate and correct the error
</a
>. The
638 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
639 of the translation including figures
</a
> is a useful source for those
640 provide Norwegian bokmål screen shots and figures.
</p
>
645 <title>Unlimited randomness with the ChaosKey?
</title>
646 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
647 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
648 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
649 <description><p
>A few days ago I ordered a small batch of
650 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
651 USB dongle for generating entropy created by Bdale Garbee and Keith
652 Packard. Yesterday it arrived, and I am very happy to report that it
653 work great! According to its designers, to get it to work out of the
654 box, you need the Linux kernel version
4.1 or later. I tested on a
655 Debian Stretch machine (kernel version
4.9), and there it worked just
656 fine, increasing the available entropy very quickly. I wrote a small
657 test oneliner to test. It first print the current entropy level,
658 drain /dev/random, and then print the entropy level for five seconds.
659 Here is the situation without the ChaosKey inserted:
</p
>
661 <blockquote
><pre
>
662 % cat /proc/sys/kernel/random/entropy_avail; \
663 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
664 for n in $(seq
1 5); do \
665 cat /proc/sys/kernel/random/entropy_avail; \
671 28 byte kopiert,
0,
000264565 s,
106 kB/s
678 </pre
></blockquote
>
680 <p
>The entropy level increases by
3-
4 every second. In such case any
681 application requiring random bits (like a HTTPS enabled web server)
682 will halt and wait for more entrpy. And here is the situation with
683 the ChaosKey inserted:
</p
>
685 <blockquote
><pre
>
686 % cat /proc/sys/kernel/random/entropy_avail; \
687 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
688 for n in $(seq
1 5); do \
689 cat /proc/sys/kernel/random/entropy_avail; \
695 104 byte kopiert,
0,
000487647 s,
213 kB/s
702 </pre
></blockquote
>
704 <p
>Quite the difference. :) I bought a few more than I need, in case
705 someone want to buy one here in Norway. :)
</p
>
707 <p
>Update: The dongle was presented at Debconf last year. You might
708 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
709 recording illuminating
</a
>. It explains exactly what the source of
710 randomness is, if you are unable to spot it from the schema drawing
711 available from the ChaosKey web site linked at the start of this blog
717 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
718 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
719 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
720 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
721 <description><p
>Did you ever wonder where the web trafic really flow to reach the
722 web servers, and who own the network equipment it is flowing through?
723 It is possible to get a glimpse of this from using traceroute, but it
724 is hard to find all the details. Many years ago, I wrote a system to
725 map the Norwegian Internet (trying to figure out if our plans for a
726 network game service would get low enough latency, and who we needed
727 to talk to about setting up game servers close to the users. Back
728 then I used traceroute output from many locations (I asked my friends
729 to run a script and send me their traceroute output) to create the
730 graph and the map. The output from traceroute typically look like
734 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
735 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
736 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
737 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
738 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
739 5 he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.627 ms he16-
1-
1.cr2.oslosda310.as2116.net (
195.0.244.48)
3.172 ms he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.857 ms
740 6 ae1.ar8.oslosda310.as2116.net (
195.0.242.39)
0.662 ms
0.637 ms ae0.ar8.oslosda310.as2116.net (
195.0.242.23)
0.622 ms
741 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
745 </pre
></p
>
747 <p
>This show the DNS names and IP addresses of (at least some of the)
748 network equipment involved in getting the data traffic from me to the
749 www.stortinget.no server, and how long it took in milliseconds for a
750 package to reach the equipment and return to me. Three packages are
751 sent, and some times the packages do not follow the same path. This
752 is shown for hop
5, where three different IP addresses replied to the
753 traceroute request.
</p
>
755 <p
>There are many ways to measure trace routes. Other good traceroute
756 implementations I use are traceroute (using ICMP packages) mtr (can do
757 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
758 traceroute and a lot of other capabilities). All of them are easily
759 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
761 <p
>This time around, I wanted to know the geographic location of
762 different route points, to visualize how visiting a web page spread
763 information about the visit to a lot of servers around the globe. The
764 background is that a web site today often will ask the browser to get
765 from many servers the parts (for example HTML, JSON, fonts,
766 JavaScript, CSS, video) required to display the content. This will
767 leak information about the visit to those controlling these servers
768 and anyone able to peek at the data traffic passing by (like your ISP,
769 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
771 <p
>Lets pick an example, the Norwegian parliament web site
772 www.stortinget.no. It is read daily by all members of parliament and
773 their staff, as well as political journalists, activits and many other
774 citizens of Norway. A visit to the www.stortinget.no web site will
775 ask your browser to contact
8 other servers: ajax.googleapis.com,
776 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
777 stats.g.doubleclick.net, www.google-analytics.com,
778 www.googletagmanager.com and www.netigate.se. I extracted this by
779 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
780 Stortinget web page and tell me all the URLs PhantomJS downloaded to
781 render the page (in HAR format using
782 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
783 netsniff example
</a
>. I am very grateful to Gorm for showing me how
784 to do this). My goal is to visualize network traces to all IP
785 addresses behind these DNS names, do show where visitors personal
786 information is spread when visiting the page.
</p
>
788 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
789 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geoip-small.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using GeoIP
"/
></a
></p
>
791 <p
>When I had a look around for options, I could not find any good
792 free software tools to do this, and decided I needed my own traceroute
793 wrapper outputting KML based on locations looked up using GeoIP. KML
794 is easy to work with and easy to generate, and understood by several
795 of the GIS tools I have available. I got good help from by NUUG
796 colleague Anders Einar with this, and the result can be seen in
797 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
798 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
799 free GeoIP databases I could find (and the for-pay databases my
800 friends had access to) is not up to the task. The IP addresses of
801 central Internet infrastructure would typically be placed near the
802 controlling companies main office, and not where the router is really
803 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
804 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
806 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
807 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy-small.png
" alt=
"scapy traceroute graph for URLs used by www.stortinget.no
"/
></a
></p
>
809 <p
>I also had a look at the visual traceroute graph created by
810 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
811 showing IP network ownership (aka AS owner) for the IP address in
813 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
814 graph display a lot of useful information about the traceroute in SVG
815 format
</a
>, and give a good indication on who control the network
816 equipment involved, but it do not include geolocation. This graph
817 make it possible to see the information is made available at least for
818 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
819 3 Communications and NetDNA.
</p
>
821 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
822 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-small.png
" alt=
"example geotraceroute view for www.stortinget.no
"/
></a
></p
>
824 <p
>In the process, I came across the
825 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
826 Salim Gasmi. Its methology of combining guesses based on DNS names,
827 various location databases and finally use latecy times to rule out
828 candidate locations seemed to do a very good job of guessing correct
829 geolocation. But it could only do one trace at the time, did not have
830 a sensor in Norway and did not make the geolocations easily available
831 for postprocessing. So I contacted the developer and asked if he
832 would be willing to share the code (he refused until he had time to
833 clean it up), but he was interested in providing the geolocations in a
834 machine readable format, and willing to set up a sensor in Norway. So
835 since yesterday, it is possible to run traces from Norway in this
836 service thanks to a sensor node set up by
837 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
838 trace in KML format for further processing.
</p
>
840 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
841 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using geotraceroute
"/
></a
></p
>
843 <p
>Here we can see a lot of trafic passes Sweden on its way to
844 Denmark, Germany, Holland and Ireland. Plenty of places where the
845 Snowden confirmations verified the traffic is read by various actors
846 without your best interest as their top priority.
</p
>
848 <p
>Combining KML files is trivial using a text editor, so I could loop
849 over all the hosts behind the urls imported by www.stortinget.no and
850 ask for the KML file from GeoTraceroute, and create a combined KML
851 file with all the traces (unfortunately only one of the IP addresses
852 behind the DNS name is traced this time. To get them all, one would
853 have to request traces using IP number instead of DNS names from
854 GeoTraceroute). That might be the next step in this project.
</p
>
856 <p
>Armed with these tools, I find it a lot easier to figure out where
857 the IP traffic moves and who control the boxes involved in moving it.
858 And every time the link crosses for example the Swedish border, we can
859 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
860 Britain and NSA in USA and cables around the globe. (Hm, what should
861 we tell them? :) Keep that in mind if you ever send anything
862 unencrypted over the Internet.
</p
>
864 <p
>PS: KML files are drawn using
865 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
866 Rublev
<a/
>, as it was less cluttered than the local Linux application
867 Marble. There are heaps of other options too.
</p
>
869 <p
>As usual, if you use Bitcoin and want to show your support of my
870 activities, please send Bitcoin donations to my address
871 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
876 <title>Appstream just learned how to map hardware to packages too!
</title>
877 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
879 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
880 <description><p
>I received a very nice Christmas present today. As my regular
881 readers probably know, I have been working on the
882 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
883 system
</a
> for many years. The goal of the Isenkram system is to make
884 it easier for users to figure out what to install to get a given piece
885 of hardware to work in Debian, and a key part of this system is a way
886 to map hardware to packages. Isenkram have its own mapping database,
887 and also uses data provided by each package using the AppStream
888 metadata format. And today,
889 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
890 Debian learned to look up hardware the same way Isenkram is doing it,
891 ie using fnmatch():
</p
>
894 % appstreamcli what-provides modalias \
895 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
896 Identifier: pymissile [generic]
898 Summary: Control original Striker USB Missile Launcher
900 % appstreamcli what-provides modalias usb:v0694p0002d0000
901 Identifier: libnxt [generic]
903 Summary: utility library for talking to the LEGO Mindstorms NXT brick
906 Identifier: t2n [generic]
908 Summary: Simple command-line tool for Lego NXT
911 Identifier: python-nxt [generic]
913 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
916 Identifier: nbc [generic]
918 Summary: C compiler for LEGO Mindstorms NXT bricks
921 </pre
></p
>
923 <p
>A similar query can be done using the combined AppStream and
924 Isenkram databases using the isenkram-lookup tool:
</p
>
927 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
929 % isenkram-lookup usb:v0694p0002d0000
935 </pre
></p
>
937 <p
>You can find modalias values relevant for your machine using
938 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
940 <p
>If you want to make this system a success and help Debian users
941 make the most of the hardware they have, please
942 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
943 AppStream metadata for your package following the guidelines
</a
>
944 documented in the wiki. So far only
11 packages provide such
945 information, among the several hundred hardware specific packages in
946 Debian. The Isenkram database on the other hand contain
101 packages,
947 mostly related to USB dongles. Most of the packages with hardware
948 mapping in AppStream are LEGO Mindstorms related, because I have, as
949 part of my involvement in
950 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
951 team
</a
> given priority to making sure LEGO users get proposed the
952 complete set of packages in Debian for that particular hardware. The
953 team also got a nice Christmas present today. The
954 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
955 package
</a
> made it into Debian. With this package in place, it is
956 now possible to use the LEGO Mindstorms NXT unit with only free
957 software, as the nxt-firmware package contain the source and firmware
958 binaries for the NXT brick.
</p
>
960 <p
>As usual, if you use Bitcoin and want to show your support of my
961 activities, please send Bitcoin donations to my address
962 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
967 <title>Isenkram updated with a lot more hardware-package mappings
</title>
968 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
969 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
970 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
971 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
972 system
</a
> I wrote two years ago to make it easier in Debian to find
973 and install packages to get your hardware dongles to work, is still
974 going strong. It is a system to look up the hardware present on or
975 connected to the current system, and map the hardware to Debian
976 packages. It can either be done using the tools in isenkram-cli or
977 using the user space daemon in the isenkram package. The latter will
978 notify you, when inserting new hardware, about what packages to
979 install to get the dongle working. It will even provide a button to
980 click on to ask packagekit to install the packages.
</p
>
982 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1001 </pre
></p
>
1003 <p
>It can also list the firware package providing firmware requested
1004 by the load kernel modules, which in my case is an empty list because
1005 I have all the firmware my machine need:
1007 <p
><pre
>
1008 % /usr/sbin/isenkram-autoinstall-firmware -l
1009 info: did not find any firmware files requested by loaded kernel modules. exiting
1011 </pre
></p
>
1013 <p
>The last few days I had a look at several of the around
250
1014 packages in Debian with udev rules. These seem like good candidates
1015 to install when a given hardware dongle is inserted, and I found
1016 several that should be proposed by isenkram. I have not had time to
1017 check all of them, but am happy to report that now there are
97
1018 packages packages mapped to hardware by Isenkram.
11 of these
1019 packages provide hardware mapping using AppStream, while the rest are
1020 listed in the modaliases file provided in isenkram.
</p
>
1022 <p
>These are the packages with hardware mappings at the moment. The
1023 <strong
>marked packages
</strong
> are also announcing their hardware
1024 support using AppStream, for everyone to use:
</p
>
1026 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
1027 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
1028 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
1029 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
1030 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
1031 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1032 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
1033 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1034 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1035 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1036 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
1037 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1038 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
1039 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1040 pcscd, pidgin-blinklight, printer-driver-splix,
1041 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
1042 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1043 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1044 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1045 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1046 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1047 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1048 xserver-xorg-video-vmware, yubikey-personalization and
1049 zd1211-firmware
</p
>
1051 <p
>If you know of other packages, please let me know with a wishlist
1052 bug report against the isenkram-cli package, and ask the package
1054 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
1055 metadata according to the guidelines
</a
> to provide the information
1056 for everyone. In time, I hope to get rid of the isenkram specific
1057 hardware mapping and depend exclusively on AppStream.
</p
>
1059 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
1060 much hardware, and suggest that the package with with any ethernet
1061 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
1062 the details. I hope the maintainer find time to address it soon. In
1063 the mean time I provide an override in isenkram.
</p
>
1068 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
1069 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
1070 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
1071 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
1072 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
1074 <p
>In my early years, I played
1075 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
1076 Elite
</a
> on my PC. I spent many months trading and fighting in
1077 space, and reached the
'elite
' fighting status before I moved on. The
1078 original Elite game was available on Commodore
64 and the IBM PC
1079 edition I played had a
64 KB executable. I am still impressed today
1080 that the authors managed to squeeze both a
3D engine and details about
1081 more than
2000 planet systems across
7 galaxies into a binary so
1084 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
1085 software game Oolite inspired by Elite
</a
> for a while, but did not
1086 really have time to test it properly until a few days ago. It was
1087 great to discover that my old knowledge about trading routes were
1088 still valid. But my fighting and flying abilities were gone, so I had
1089 to retrain to be able to dock on a space station. And I am still not
1090 able to make much resistance when I am attacked by pirates, so I
1091 bougth and mounted the most powerful laser in the rear to be able to
1092 put up at least some resistance while fleeing for my life. :)
</p
>
1094 <p
>When playing Elite in the late eighties, I had to discover
1095 everything on my own, and I had long lists of prices seen on different
1096 planets to be able to decide where to trade what. This time I had the
1098 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1099 where information about each planet is easily available with common
1100 price ranges and suggested trading routes. This improved my ability
1101 to earn money and I have been able to earn enough to buy a lot of
1102 useful equipent in a few days. I believe I originally played for
1103 months before I could get a docking computer, while now I could get it
1104 after less then a week.
</p
>
1106 <p
>If you like science fiction and dreamed of a life as a vagabond in
1107 space, you should try out Oolite. It is available for Linux, MacOSX
1108 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1110 <p
>As usual, if you use Bitcoin and want to show your support of my
1111 activities, please send Bitcoin donations to my address
1112 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1117 <title>Quicker Debian installations using eatmydata
</title>
1118 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1119 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1120 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1121 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1122 installation system, observing how using
1123 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1124 could speed up the installation
</a
> quite a bit. My testing measured
1125 speedup around
20-
40 percent for Debian Edu, where we install around
1126 1000 packages from within the installer. The eatmydata package
1127 provide a way to disable/delay file system flushing. This is a bit
1128 risky in the general case, as files that should be stored on disk will
1129 stay only in memory a bit longer than expected, causing problems if a
1130 machine crashes at an inconvenient time. But for an installation, if
1131 the machine crashes during installation the process is normally
1132 restarted, and avoiding disk operations as much as possible to speed
1133 up the process make perfect sense.
1135 <p
>I added code in the Debian Edu specific installation code to enable
1136 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1137 but did not have time to push it any further. But a few months ago I
1138 picked it up again and worked with the libeatmydata package maintainer
1139 Mattia Rizzolo to make it easier for everyone to get this installation
1140 speedup in Debian. Thanks to our cooperation There is now an
1141 eatmydata-udeb package in Debian testing and unstable, and simply
1142 enabling/installing it in debian-installer (d-i) is enough to get the
1143 quicker installations. It can be enabled using preseeding. The
1144 following untested kernel argument should do the trick:
</p
>
1146 <blockquote
><pre
>
1147 preseed/early_command=
"anna-install eatmydata-udeb
"
1148 </pre
></blockquote
>
1150 <p
>This should ask d-i to install the package inside the d-i
1151 environment early in the installation sequence. Having it installed
1152 in d-i in turn will make sure the relevant scripts are called just
1153 after debootstrap filled /target/ with the freshly installed Debian
1154 system to configure apt to run dpkg with eatmydata. This is enough to
1155 speed up the installation process. There is a proposal to
1156 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1157 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1158 tested its impact.
</p
>
1164 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1165 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1167 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1168 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1169 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1170 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1171 elever over det ganske land skal levere inn hvert år. Det mange ikke
1172 vet er at selv om de kommersielle alternativene
1173 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1174 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1175 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1176 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1177 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1178 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1179 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1180 nynorsk, og få den automatoversatt til det andre skriftspråket.
1181 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1182 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1183 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1184 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1185 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1186 teksten din i webskjemaet der.
1188 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1189 teknologien kan du enten installere pakken
1190 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1191 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1192 api.apertium.org. Se
1193 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1194 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1195 denne teksten som ble skrevet på bokmål over maskinoversatt til
1200 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1201 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1202 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1203 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1204 veit er at sjølv om dei kommersielle alternativa
1205 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1206 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1207 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1208 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1209 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1210 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1211 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1212 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1213 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1214 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1215 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1216 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1217 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1218 teksta di i *webskjemaet der.
1220 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1221 teknologien kan du anten installera pakken
1222 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1223 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1224 *api.*apertium.org. Sjå
1225 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1226 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1227 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1233 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1234 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1236 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1237 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1238 profiler able to run benchmarking experiments on the instrumented
1239 multi-threaded program, finally
1240 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1241 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1243 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1244 blogged about the coz tool
</a
> in August working with upstream to make
1245 it suitable for Debian. There are still issues with clang
1246 compatibility, inline assembly only working x86 and minimized
1247 JavaScript libraries.
</p
>
1249 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1251 <p
><blockquote
>
1252 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1253 </blockquote
></p
>
1255 <p
>This will produce a profile.coz file in the current working
1256 directory with the profiling information. This is then given to a
1257 JavaScript application provided in the package and available from
1258 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1259 To start the local copy, invoke it in a browser like this:
</p
>
1261 <p
><blockquote
>
1262 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1263 </blockquote
></p
>
1265 <p
>See the project home page and the
1266 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1267 ;login: article on Coz
</a
> for more information on how it is
1273 <title>My own self balancing Lego Segway
</title>
1274 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1275 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1276 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1277 <description><p
>A while back I received a Gyro sensor for the NXT
1278 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1279 present. It had been on my wishlist for a while, because I wanted to
1280 build a Segway like balancing lego robot. I had already built
1281 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1282 robot
</a
> with the kids, using the light/color sensor included in the
1283 NXT kit as the balance sensor, but it was not working very well. It
1284 could balance for a while, but was very sensitive to the light
1285 condition in the room and the reflective properties of the surface and
1286 would fall over after a short while. I wanted something more robust,
1288 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1289 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1290 wishlist for some years before it suddenly showed up as a gift from my
1291 loved ones. :)
</p
>
1293 <p
>Unfortunately I have not had time to sit down and play with it
1294 since then. But that changed some days ago, when I was searching for
1295 lego segway information and came across a recipe from HiTechnic for
1297 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1298 HTWay
</a
>, a segway like balancing robot. Build instructions and
1299 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1300 code
</a
> was included, so it was just a question of putting it all
1301 together. And thanks to the great work of many Debian developers, the
1302 compiler needed to build the source for the NXT is already included in
1303 Debian, so I was read to go in less than an hour. The resulting robot
1304 do not look very impressive in its simplicity:
</p
>
1306 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1308 <p
>Because I lack the infrared sensor used to control the robot in the
1309 design from HiTechnic, I had to comment out the last task
1310 (taskControl). I simply placed /* and */ around it get the program
1311 working without that sensor present. Now it balances just fine until
1312 the battery status run low:
</p
>
1314 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1315 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1316 </video
></p
>
1318 <p
>Now we would like to teach it how to follow a line and take remote
1319 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1321 <p
>If you, like me, love LEGO and want to make sure we find the tools
1322 they need to work with LEGO in Debian and all our derivative
1323 distributions like Ubuntu, check out
1324 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1325 project page
</a
> and join the Debian LEGO team. Personally I own a
1326 RCX and NXT controller (no EV3), and would like to make sure the
1327 Debian tools needed to program the systems I own work as they
1333 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1334 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1336 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1337 <description><p
>In July
1338 <a href=
"http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
1339 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1340 the ability to receive SMS messages (aka without a cell phone). It is
1341 time to share some experiences and provide an updated setup.
</p
>
1343 <p
>The Signal app have worked fine for several months now, and I use
1344 it regularly to chat with my loved ones. I had a major snag at the
1345 end of my summer vacation, when the the app completely forgot my
1346 setup, identity and keys. The reason behind this major mess was
1347 running out of disk space. To avoid that ever happening again I have
1348 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1349 roll back to an earlier version if the files are wiped by mistake. I
1350 had to use it once after introducing the git backup. When rolling
1351 back to an earlier version, one need to use the
'reset session
' option
1352 in Signal to get going, and notify the people you talk with about the
1353 problem. I assume there is some sequence number tracking in the
1354 protocol to detect rollback attacks. The git repository is rather big
1355 (
674 MiB so far), but I have not tried to figure out if some of the
1356 content can be added to a .gitignore file due to lack of spare
1359 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1360 make it impossible to send messages using Signal. I could still
1361 receive them, but had to patch the code with a new timestamp to send.
1362 I believe the timeout is added by the developers to force people to
1363 upgrade to the latest version of the app, even when there is no
1364 protocol changes, to reduce the version skew among the user base and
1365 thus try to keep the number of support requests down.
</p
>
1367 <p
>Since my original recipe, the Signal source code changed slightly,
1368 making the old patch fail to apply cleanly. Below is an updated
1369 patch, including the shell wrapper I use to start Signal. The
1370 original version required a new user to locate the JavaScript console
1371 and call a function from there. I got help from a friend with more
1372 JavaScript knowledge than me to modify the code to provide a GUI
1373 button instead. This mean that to get started you just need to run
1374 the wrapper and click the
'Register without mobile phone
' to get going
1375 now. I
've also modified the timeout code to always set it to
90 days
1376 in the future, to avoid having to patch the code regularly.
</p
>
1378 <p
>So, the updated recipe for Debian Jessie:
</p
>
1382 <li
>First, install required packages to get the source code and the
1383 browser you need. Signal only work with Chrome/Chromium, as far as I
1384 know, so you need to install it.
1387 apt install git tor chromium
1388 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1389 </pre
></li
>
1391 <li
>Modify the source code using command listed in the the patch
1392 block below.
</li
>
1394 <li
>Start Signal using the run-signal-app wrapper (for example using
1395 <tt
>`pwd`/run-signal-app
</tt
>).
1397 <li
>Click on the
'Register without mobile phone
', will in a phone
1398 number you can receive calls to the next minute, receive the
1399 verification code and enter it into the form field and press
1400 'Register
'. Note, the phone number you use will be user Signal
1401 username, ie the way others can find you on Signal.
</li
>
1403 <li
>You can now use Signal to contact others. Note, new contacts do
1404 not show up in the contact list until you restart Signal, and there is
1405 no way to assign names to Contacts. There is also no way to create or
1406 update chat groups. I suspect this is because the web app do not have
1407 a associated contact database.
</li
>
1411 <p
>I am still a bit uneasy about using Signal, because of the way its
1412 main author moxie0 reject federation and accept dependencies to major
1413 corporations like Google (part of the code is fetched from Google) and
1414 Amazon (the central coordination point is owned by Amazon). See for
1416 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1417 LibreSignal issue tracker
</a
> for a thread documenting the authors
1418 view on these issues. But the network effect is strong in this case,
1419 and several of the people I want to communicate with already use
1420 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1421 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1422 laptop
</a
>? It already work on Windows and Android, and is included
1423 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1424 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1425 working on Debian Stable.
</p
>
1427 <p
>Anyway, this is the patch I apply to the Signal code to get it
1428 working. It switch to the production servers, disable to timeout,
1429 make registration easier and add the shell wrapper:
</p
>
1432 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1433 diff --git a/js/background.js b/js/background.js
1434 index
24b4c1d.
.579345f
100644
1435 --- a/js/background.js
1436 +++ b/js/background.js
1441 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1442 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1443 var SERVER_PORTS = [
80,
4433,
8443];
1444 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1445 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1446 var messageReceiver;
1447 window.getSocketStatus = function() {
1448 if (messageReceiver) {
1449 diff --git a/js/expire.js b/js/expire.js
1450 index
639aeae..beb91c3
100644
1455 'use strict
';
1456 - var BUILD_EXPIRATION =
0;
1457 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1459 window.extension = window.extension || {};
1461 diff --git a/js/views/install_view.js b/js/views/install_view.js
1462 index
7816f4f.
.1d6233b
100644
1463 --- a/js/views/install_view.js
1464 +++ b/js/views/install_view.js
1467 'click .step1
': this.selectStep.bind(this,
1),
1468 'click .step2
': this.selectStep.bind(this,
2),
1469 -
'click .step3
': this.selectStep.bind(this,
3)
1470 +
'click .step3
': this.selectStep.bind(this,
3),
1471 +
'click .callreg
': function() { extension.install(
'standalone
') },
1474 clearQR: function() {
1475 diff --git a/options.html b/options.html
1476 index dc0f28e.
.8d709f6
100644
1480 &lt;div class=
'nav
'>
1481 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1482 &lt;p
>{{ installTagline }}
&lt;/p
>
1483 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1484 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1485 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1488 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1489 &lt;span class=
'dot step2
'>&lt;/span
>
1490 &lt;span class=
'dot step3
'>&lt;/span
>
1491 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1492 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1498 +userdata=
"`pwd`/userdata
"
1499 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1500 + (cd $userdata
&& git init)
1502 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1504 + --proxy-server=
"socks://localhost:
9050" \
1505 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1507 chmod a+rx run-signal-app
1510 <p
>As usual, if you use Bitcoin and want to show your support of my
1511 activities, please send Bitcoin donations to my address
1512 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1517 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1518 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1519 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1520 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1521 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1522 system
</a
> provide a practical and easy way to figure out which
1523 packages support the hardware in a given machine. The command line
1524 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1525 convenient way to list and install packages relevant for the current
1526 hardware during system installation, both user space packages and
1527 firmware packages. The GUI background daemon on the other hand provide
1528 a pop-up proposing to install packages when a new dongle is inserted
1529 while using the computer. For example, if you plug in a smart card
1530 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1531 that package isn
't already installed, and if you plug in a USB video
1532 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1533 cheese is currently missing. This already work just fine.
</p
>
1535 <p
>But Isenkram depend on a database mapping from hardware IDs to
1536 package names. When I started no such database existed in Debian, so
1537 I made my own data set and included it with the isenkram package and
1538 made isenkram fetch the latest version of this database from git using
1539 http. This way the isenkram users would get updated package proposals
1540 as soon as I learned more about hardware related packages.
</p
>
1542 <p
>The hardware is identified using modalias strings. The modalias
1543 design is from the Linux kernel where most hardware descriptors are
1544 made available as a strings that can be matched using filename style
1545 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1546 identifiers.
</p
>
1548 <p
>The downside to the Isenkram specific database is that there is no
1549 information about relevant distribution / Debian version, making
1550 isenkram propose obsolete packages too. But along came AppStream, a
1551 cross distribution mechanism to store and collect metadata about
1552 software packages. When I heard about the proposal, I contacted the
1553 people involved and suggested to add a hardware matching rule using
1554 modalias strings in the specification, to be able to use AppStream for
1555 mapping hardware to packages. This idea was accepted and AppStream is
1556 now a great way for a package to announce the hardware it support in a
1557 distribution neutral way. I wrote
1558 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1559 recipe on how to add such meta-information
</a
> in a blog post last
1560 December. If you have a hardware related package in Debian, please
1561 announce the relevant hardware IDs using AppStream.
</p
>
1563 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1564 RCX or NXT unit, announce this support using AppStream. The effect is
1565 that when you insert such LEGO robot controller into your Debian
1566 machine, Isenkram will propose to install the packages needed to get
1567 it working. The intention is that this should allow the local user to
1568 start programming his robot controller right away without having to
1569 guess what packages to use or which permissions to fix.
</p
>
1571 <p
>But when I sat down with my son the other day to program our NXT
1572 unit using his Debian Stretch computer, I discovered something
1573 annoying. The local console user (ie my son) did not get access to
1574 the USB device for programming the unit. This used to work, but no
1575 longer in Jessie and Stretch. After some investigation and asking
1576 around on #debian-devel, I discovered that this was because udev had
1577 changed the mechanism used to grant access to local devices. The
1578 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1579 no longer applied, because LDAP users no longer was added to the
1580 plugdev group during login. Michael Biebl told me that this method
1581 was obsolete and the new method used ACLs instead. This was good
1582 news, as the plugdev mechanism is a mess when using a remote user
1583 directory like LDAP. Using ACLs would make sure a user lost device
1584 access when she logged out, even if the user left behind a background
1585 process which would retain the plugdev membership with the ConsoleKit
1586 setup. Armed with this knowledge I moved on to fix the access problem
1587 for the LEGO Mindstorms related packages.
</p
>
1589 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1590 applied directly for a device, or is applied in
1591 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1592 LEGO Mindstorms udev rules did not have a class, I decided to add the
1593 tag directly in the udev rules files included in the packages. Here
1594 is one example. For the nqc C compiler for the RCX, the
1595 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1597 <p
><pre
>
1598 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1599 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1600 </pre
></p
>
1602 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1603 packages using plugdev in their /lib/udev/rules.d/ files should be
1604 changed to use this tag (either directly or indirectly via
1605 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1606 to detect this?
</p
>
1608 <p
>I
've been unable to find good documentation on the uaccess feature.
1609 It is unclear to me if the uaccess tag is an internal implementation
1610 detail like the udev-acl tag used by
1611 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1612 indirect method is the preferred way. Michael
1613 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1614 documentation from the systemd project
</a
> and I hope it will make
1615 this clearer. For now I use the generic classes when they exist and
1616 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1617 directly if no such class exist.
</p
>
1619 <p
>To learn more about the isenkram system, please check out
1620 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1621 blog posts tagged isenkram
</a
>.
</p
>
1623 <p
>To help out making life for LEGO constructors in Debian easier,
1624 please join us on our IRC channel
1625 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1626 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1627 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1628 list is not yet created, but we are working on it. :)
</p
>
1630 <p
>As usual, if you use Bitcoin and want to show your support of my
1631 activities, please send Bitcoin donations to my address
1632 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1637 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1638 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1639 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</guid>
1640 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1641 <description><p
>In April we
1642 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1643 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1644 how to set up and administrate a Debian system. Today I am happy to
1645 report that the first draft is now publicly available. You can find
1646 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1647 Administrator
's Handbook page
</a
> (under Other languages). The first
1648 eight chapters have a first draft translation, and we are working on
1649 proofreading the content. If you want to help out, please start
1651 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1652 hosted weblate project page
</a
>, and get in touch using
1653 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1654 translators mailing list
</a
>. Please also check out
1655 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1656 contributors
</a
>. A good way to contribute is to proofread the text
1657 and update weblate if you find errors.
</p
>
1659 <p
>Our goal is still to make the Norwegian book available on paper as well as
1660 electronic form.
</p
>
1665 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1666 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1667 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1668 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1669 <description><p
>This summer, I read a great article
1670 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1671 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1672 how to profile multi-threaded programs. It presented a system for
1673 profiling software by running experiences in the running program,
1674 testing how run time performance is affected by
"speeding up
" parts of
1675 the code to various degrees compared to a normal run. It does this by
1676 slowing down parallel threads while the
"faster up
" code is running
1677 and measure how this affect processing time. The processing time is
1678 measured using probes inserted into the code, either using progress
1679 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1680 can also measure unmodified code by measuring complete the program
1681 runtime and running the program several times instead.
</p
>
1683 <p
>The project and presentation was so inspiring that I would like to
1684 get the system into Debian. I
1685 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1686 a WNPP request for it
</a
> and contacted upstream to try to make the
1687 system ready for Debian by sending patches. The build process need to
1688 be changed a bit to avoid running
'git clone
' to get dependencies, and
1689 to include the JavaScript web page used to visualize the collected
1690 profiling information included in the source package.
1691 But I expect that should work out fairly soon.
</p
>
1693 <p
>The way the system work is fairly simple. To run an coz experiment
1694 on a binary with debug symbols available, start the program like this:
1696 <p
><blockquote
><pre
>
1697 coz run --- program-to-run
1698 </pre
></blockquote
></p
>
1700 <p
>This will create a text file profile.coz with the instrumentation
1701 information. To show what part of the code affect the performance
1702 most, use a web browser and either point it to
1703 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1704 or use the copy from git (in the gh-pages branch). Check out this web
1705 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
1706 profiling more useful you include
&lt;coz.h
&gt; and insert the
1707 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1708 code, rebuild and run the profiler. This allow coz to do more
1709 targeted experiments.
</p
>
1711 <p
>A video published by ACM
1712 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1713 Coz profiler
</a
> is available from Youtube. There is also a paper
1714 from the
25th Symposium on Operating Systems Principles available
1716 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1717 finding code that counts with causal profiling
</a
>.
</p
>
1719 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1720 for Coz is available from github. It will only build with clang
1722 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1723 feature missing in GCC
</a
>, but I
've submitted
1724 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1725 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1727 <p
>Please get in touch if you, like me, would like to see this piece
1728 of software in Debian. I would very much like some help with the
1729 packaging effort, as I lack the in depth knowledge on how to package
1730 C++ libraries.
</p
>
1735 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1736 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1737 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1738 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1739 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1740 to be a slight challenge. Here is the recipe if I ever need to do it
1741 again. It all started by me wanting to try the recipe to set up
1742 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1743 hardened Android installation
</a
> from the Tor project blog on a
1744 device I had access to. It is a old mobile phone with a broken
1745 microphone The initial idea had been to just
1746 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1747 CyanogenMod on it
</a
>, but did not quite find time to start on it
1748 until a few days ago.
</p
>
1750 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1751 loader (press volume down and power at the same time), (
2) select
1752 'fastboot
' before (
3) connecting the device via USB to a Linux
1753 machine, (
4) request the device identifier token by running
'fastboot
1754 oem get_identifier_token
', (
5) request the device unlocking key using
1755 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1756 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1758 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1759 or newer, and the device I was working on had
2.00.0027. This
1760 apparently can be easily fixed by downloading a Windows program and
1761 running it on your Windows machine, if you accept the terms Microsoft
1762 require you to accept to use Windows - which I do not. So I had to
1763 come up with a different approach. I got a lot of help from AndyCap
1764 on #nuug, and would not have been able to get this working without
1767 <p
>First I needed to extract the hboot firmware from
1768 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1769 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1770 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1771 project named unruu
</a
> using libunshield. The unshield tool did not
1772 recognise the file format, but unruu worked and extracted rom.zip,
1773 containing the new hboot firmware and a text file describing which
1774 devices it would work for.
</p
>
1776 <p
>Next, I needed to get the new firmware into the device. For this I
1777 followed some instructions
1778 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1779 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1780 machine with Debian testing:
</p
>
1782 <p
><pre
>
1783 adb reboot-bootloader
1784 fastboot oem rebootRUU
1785 fastboot flash zip rom.zip
1786 fastboot flash zip rom.zip
1788 </pre
></p
>
1790 <p
>The flash command apparently need to be done twice to take effect,
1791 as the first is just preparations and the second one do the flashing.
1792 The adb command is just to get to the boot loader menu, so turning the
1793 device on while holding volume down and the power button should work
1796 <p
>With the new hboot version in place I could start following the
1797 instructions on the HTC developer web site. I got the device token
1798 like this:
</p
>
1800 <p
><pre
>
1801 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1804 <p
>And once I got the unlock code via email, I could use it like
1807 <p
><pre
>
1808 fastboot flash unlocktoken Unlock_code.bin
1809 </pre
></p
>
1811 <p
>And with that final step in place, the phone was unlocked and I
1812 could start stuffing the software of my own choosing into the device.
1813 So far I only inserted a replacement recovery image to wipe the phone
1814 before I start. We will see what happen next. Perhaps I should
1815 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1820 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1821 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
1822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
1823 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1824 <description><p
>For a while now, I have wanted to test
1825 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1826 said to provide end to end encrypted communication and several of my
1827 friends and family are already using it. As I by choice do not own a
1828 mobile phone, this proved to be harder than expected. And I wanted to
1829 have the source of the client and know that it was the code used on my
1830 machine. But yesterday I managed to get it working. I used the
1831 Github source, compared it to the source in
1832 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1833 Signal Chrome app
</a
> available from the Chrome web store, applied
1834 patches to use the production Signal servers, started the app and
1835 asked for the hidden
"register without a smart phone
" form. Here is
1836 the recipe how I did it.
</p
>
1838 <p
>First, I fetched the Signal desktop source from Github, using
1841 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1844 <p
>Next, I patched the source to use the production servers, to be
1845 able to talk to other Signal users:
</p
>
1848 cat
&lt;
&lt;EOF | patch -p0
1849 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1850 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1851 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1856 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1857 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1858 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1859 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1860 var messageReceiver;
1861 window.getSocketStatus = function() {
1862 if (messageReceiver) {
1863 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1864 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1865 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1868 'use strict
';
1869 - var BUILD_EXPIRATION =
0;
1870 + var BUILD_EXPIRATION =
1474492690000;
1872 window.extension = window.extension || {};
1877 <p
>The first part is changing the servers, and the second is updating
1878 an expiration timestamp. This timestamp need to be updated regularly.
1879 It is set
90 days in the future by the build process (Gruntfile.js).
1880 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1882 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1883 script to launch Signal in Chromium.
</p
>
1890 --proxy-server=
"socks://localhost:
9050" \
1891 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1894 <p
> The script start the app and configure Chromium to use the Tor
1895 SOCKS5 proxy to make sure those controlling the Signal servers (today
1896 Amazon and Whisper Systems) as well as those listening on the lines
1897 will have a harder time location my laptop based on the Signal
1898 connections if they use source IP address.
</p
>
1900 <p
>When the script starts, one need to follow the instructions under
1901 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1902 repository. I right clicked on the Signal window to get up the
1903 Chromium debugging tool, visited the
'Console
' tab and wrote
1904 'extension.install(
"standalone
")
' on the console prompt to get the
1905 registration form. Then I entered by land line phone number and
1906 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1907 repeated the verification code three times. After entering the number
1908 into the verification code field in the form, I could start using
1909 Signal from my laptop.
1911 <p
>As far as I can tell, The Signal app will leak who is talking to
1912 whom and thus who know who to those controlling the central server,
1913 but such leakage is hard to avoid with a centrally controlled server
1914 setup. It is something to keep in mind when using Signal - the
1915 content of your chats are harder to intercept, but the meta data
1916 exposing your contact network is available to people you do not know.
1917 So better than many options, but not great. And sadly the usage is
1918 connected to my land line, thus allowing those controlling the server
1919 to associate it to my home and person. I would prefer it if only
1920 those I knew could tell who I was on Signal. There are options
1921 avoiding such information leakage, but most of my friends are not
1922 using them, so I am stuck with Signal for now.
</p
>
1924 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1926 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1927 and updated recipe for using the Signal app without a mobile
1928 phone
</a
>.
</p
>
1933 <title>The new
"best
" multimedia player in Debian?
</title>
1934 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1936 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1937 <description><p
>When I set out a few weeks ago to figure out
1938 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1939 multimedia player in Debian claimed to support most file formats /
1940 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1941 the various players claimed support for. The range was from
55 to
130
1942 MIME types. I suspect most media formats are supported by all
1943 players, but this is not really reflected in the MimeTypes values in
1944 their desktop files. There are probably also some bogus MIME types
1945 listed, but it is hard to identify which one this is.
</p
>
1947 <p
>Anyway, in the mean time I got in touch with upstream for some of
1948 the players suggesting to add more MIME types to their desktop files,
1949 and decided to spend some time myself improving the situation for my
1950 favorite media player VLC. The fixes for VLC entered Debian unstable
1951 yesterday. The complete list of MIME types can be seen on the
1952 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1953 player MIME type support status
</a
> Debian wiki page.
</p
>
1955 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1956 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1957 kmplayer. I am sure some of the other players desktop files support
1958 several of the formats currently listed as working only with vlc,
1959 toten and parole.
</p
>
1961 <p
>A sad observation is that only
14 MIME types are listed as
1962 supported by all the tested multimedia players in Debian in their
1963 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1964 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1965 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1966 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1967 it sad that video/ogg and video/webm is not supported by all the media
1968 players in Debian. As far as I can tell, all of them can handle both
1974 <title>A program should be able to open its own files on Linux
</title>
1975 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1976 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1977 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1978 <description><p
>Many years ago, when koffice was fresh and with few users, I
1979 decided to test its presentation tool when making the slides for a
1980 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1981 wrote the first draft of the slides, saved the result and went to bed
1982 the day before I would give the talk. The next day I took a plane to
1983 the location where the meeting should take place, and on the plane I
1984 started up koffice again to polish the talk a bit, only to discover
1985 that kpresenter refused to load its own data file. I cursed a bit and
1986 started making the slides again from memory, to have something to
1987 present when I arrived. I tested that the saved files could be
1988 loaded, and the day seemed to be rescued. I continued to polish the
1989 slides until I suddenly discovered that the saved file could no longer
1990 be loaded into kpresenter. In the end I had to rewrite the slides
1991 three times, condensing the content until the talk became shorter and
1992 shorter. After the talk I was able to pinpoint the problem
&ndash;
1993 kpresenter wrote inline images in a way itself could not understand.
1994 Eventually that bug was fixed and kpresenter ended up being a great
1995 program to make slides. The point I
'm trying to make is that we
1996 expect a program to be able to load its own data files, and it is
1997 embarrassing to its developers if it can
't.
</p
>
1999 <p
>Did you ever experience a program failing to load its own data
2000 files from the desktop file browser? It is not a uncommon problem. A
2001 while back I discovered that the screencast recorder
2002 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2003 browser would refuse to open. No video player claimed to understand
2004 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2005 returning the application/ogg MIME type, which no video player I had
2006 installed listed as a MIME type they would understand. I asked for
2007 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2008 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2009 several video players to add video/ogg to their desktop files, to give
2010 the file browser an idea what to do about Ogg Theora files. After a
2011 while, the desktop file browsers in Debian started to handle the
2012 output from gtk-recordmydesktop properly.
</p
>
2014 <p
>But history repeats itself. A few days ago I tested the music
2015 system Rosegarden again, and I discovered that the KDE and xfce file
2016 browsers did not know what to do with the Rosegarden project files
2017 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2018 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2019 included in the next upload. To increase the chance of me remembering
2020 how to fix the problem next time some program fail to load its files
2021 from the file browser, here are some notes on how to fix it.
</p
>
2023 <p
>The file browsers in Debian in general operates on MIME types.
2024 There are two sources for the MIME type of a given file. The output from
2025 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
2026 shared MIME type registry (under /usr/share/mime/). The file MIME
2027 type is mapped to programs supporting the MIME type, and this
2028 information is collected from
2029 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
2030 desktop files
</a
> available in /usr/share/applications/. If there is
2031 one desktop file claiming support for the MIME type of the file, it is
2032 activated when asking to open a given file. If there are more, one
2033 can normally select which one to use by right-clicking on the file and
2034 selecting the wanted one using
'Open with
' or similar. In general
2035 this work well. But it depend on each program picking a good MIME
2037 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
2038 MIME type registered with IANA
</a
>), file and/or the shared MIME
2039 registry recognizing the file and the desktop file to list the MIME
2040 type in its list of supported MIME types.
</p
>
2042 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
2043 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
2044 Shared MIME database
</a
> look like this:
</p
>
2046 <p
><blockquote
><pre
>
2047 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2048 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
2049 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
2050 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
2051 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
2052 &lt;glob pattern=
"*.rg
"/
&gt;
2053 &lt;/mime-type
&gt;
2054 &lt;/mime-info
&gt;
2055 </pre
></blockquote
></p
>
2057 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
2058 (it is a gzipped XML file). Note, it is much better to use an
2059 official MIME type registered with IANA than it is to make up ones own
2060 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
2062 <p
>The desktop file of the rosegarden program failed to list
2063 audio/x-rosegarden in its list of supported MIME types, causing the
2064 file browsers to have no idea what to do with *.rg files:
</p
>
2066 <p
><blockquote
><pre
>
2067 % grep Mime /usr/share/applications/rosegarden.desktop
2068 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2069 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2071 </pre
></blockquote
></p
>
2073 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
2074 MimeType= line.
</p
>
2076 <p
>If you run into a file which fail to open the correct program when
2077 selected from the file browser, please check out the output from
2078 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
2079 MIME type is registered somewhere under /usr/share/mime/ and check
2080 that some desktop file under /usr/share/applications/ is claiming
2081 support for this MIME type. If not, please report a bug to have it
2087 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
2088 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
2089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
2090 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
2091 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
2092 system
</a
> is a user-focused solution in Debian for handling hardware
2093 related packages. The idea is to have a database of mappings between
2094 hardware and packages, and pop up a dialog suggesting for the user to
2095 install the packages to use a given hardware dongle. Some use cases
2096 are when you insert a Yubikey, it proposes to install the software
2097 needed to control it; when you insert a braille reader list it
2098 proposes to install the packages needed to send text to the reader;
2099 and when you insert a ColorHug screen calibrator it suggests to
2100 install the driver for it. The system work well, and even have a few
2101 command line tools to install firmware packages and packages for the
2102 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2104 <p
>The system was initially written using aptdaemon, because I found
2105 good documentation and example code on how to use it. But aptdaemon
2106 is going away and is generally being replaced by
2107 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2108 so Isenkram needed a rewrite. And today, thanks to the great patch
2109 from my college Sunil Mohan Adapa in the FreedomBox project, the
2110 rewrite finally took place. I
've just uploaded a new version of
2111 Isenkram into Debian Unstable with the patch included, and the default
2112 for the background daemon is now to use PackageKit. To check it out,
2113 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2114 and see if it is recognised.
</p
>
2116 <p
>If you want to know what kind of packages isenkram would propose for
2117 the machine it is running on, you can check out the isenkram-lookup
2118 program. This is what it look like on a Thinkpad X230:
</p
>
2120 <p
><blockquote
><pre
>
2136 </pre
></blockquote
></p
>
2138 <p
>The hardware mappings come from several places. The preferred way
2139 is for packages to announce their hardware support using
2140 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2141 cross distribution appstream system
</a
>.
2143 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2144 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2149 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2150 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2152 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2153 <description><p
>Yesterday I updated the
2154 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2155 package in Debian
</a
> with a few patches sent to me by skilled and
2156 enterprising users. There were some nice user and visible changes.
2157 First of all, both desktop menu entries now work. A design flaw in
2158 one of the script made the history graph fail to show up (its PNG was
2159 dumped in ~/.xsession-errors) if no controlling TTY was available.
2160 The script worked when called from the command line, but not when
2161 called from the desktop menu. I changed this to look for a DISPLAY
2162 variable or a TTY before deciding where to draw the graph, and now the
2163 graph window pop up as expected.
</p
>
2165 <p
>The next new feature is a discharge rate estimator in one of the
2166 graphs (the one showing the last few hours). New is also the user of
2167 colours showing charging in blue and discharge in red. The percentages
2168 of this graph is relative to last full charge, not battery design
2171 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2173 <p
>The other graph show the entire history of the collected battery
2174 statistics, comparing it to the design capacity of the battery to
2175 visualise how the battery life time get shorter over time. The red
2176 line in this graph is what the previous graph considers
100 percent:
2178 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2180 <p
>In this graph you can see that I only charge the battery to
80
2181 percent of last full capacity, and how the capacity of the battery is
2182 shrinking. :(
</p
>
2184 <p
>The last new feature is in the collector, which now will handle
2185 more hardware models. On some hardware, Linux power supply
2186 information is stored in /sys/class/power_supply/ACAD/, while the
2187 collector previously only looked in /sys/class/power_supply/AC/. Now
2188 both are checked to figure if there is power connected to the
2191 <p
>If you are interested in how your laptop battery is doing, please
2193 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2194 in Debian unstable, or rebuild it on Jessie to get it working on
2195 Debian stable. :) The upstream source is available from
<a
2196 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2197 Patches are very welcome.
</p
>
2199 <p
>As usual, if you use Bitcoin and want to show your support of my
2200 activities, please send Bitcoin donations to my address
2201 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2206 <title>Debian now with ZFS on Linux included
</title>
2207 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2209 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2210 <description><p
>Today, after many years of hard work from many people,
2211 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2212 Debian. The package status can be seen on
2213 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2214 for zfs-linux
</a
>. and
2215 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2216 team status page
</a
>. If you want to help out, please join us.
2217 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2218 source code
</a
> is available via git on Alioth. It would also be
2219 great if you could help out with
2220 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2221 it is an important piece of the puzzle to get ZFS working.
</p
>
2226 <title>What is the best multimedia player in Debian?
</title>
2227 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2229 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2230 <description><p
><strong
>Where I set out to figure out which multimedia player in
2231 Debian claim support for most file formats.
</strong
></p
>
2233 <p
>A few years ago, I had a look at the media support for Browser
2234 plugins in Debian, to get an idea which plugins to include in Debian
2235 Edu. I created a script to extract the set of supported MIME types
2236 for each plugin, and used this to find out which multimedia browser
2237 plugin supported most file formats / media types.
2238 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2239 result
</a
> can still be seen on the Debian wiki, even though it have
2240 not been updated for a while. But browser plugins are less relevant
2241 these days, so I thought it was time to look at standalone
2244 <p
>A few days ago I was tired of VLC not being listed as a viable
2245 player when I wanted to play videos from the Norwegian National
2246 Broadcasting Company, and decided to investigate why. The cause is a
2247 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2248 desktop file
</a
>. In the process I wrote a script to compare the set
2249 of MIME types announced in the desktop file and the browser plugin,
2250 only to discover that there is quite a large difference between the
2251 two for VLC. This discovery made me dig up the script I used to
2252 compare browser plugins, and adjust it to compare desktop files
2253 instead, to try to figure out which multimedia player in Debian
2254 support most file formats.
</p
>
2256 <p
>The result can be seen on the Debian Wiki, as
2257 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2258 table listing all MIME types supported by one of the packages included
2259 in the table
</a
>, with the package supporting most MIME types being
2260 listed first in the table.
</p
>
2262 </p
>The best multimedia player in Debian? It is totem, followed by
2263 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2264 kmplayer. Time for the other players to update their announced MIME
2270 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2271 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2273 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2274 <description>A friend of mine made me aware of
2275 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2276 handheld computer which will be delivered with Debian preinstalled. I
2277 would love to get one of those for my birthday. :)
</p
>
2279 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2280 plugs and many others connectors, and include a full keyboard and a
5"
2281 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2282 day of battery life time, but I have not seen any independent tests
2283 confirming this. The vendor is still collecting preorders, and the
2284 last I heard last night was that
22 more orders were needed before
2285 production started.
</p
>
2287 <p
>As far as I know, this is the first handheld preinstalled with
2288 Debian. Please let me know if you know of any others. Is it the
2289 first computer being sold with Debian preinstalled?
</p
>
2294 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2295 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2296 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2297 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2298 <description><p
>During this weekends
2299 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2300 squashing party and developer gathering
</a
>, we decided to do our part
2301 to make sure there are good books about Debian available in Norwegian
2302 Bokmål, and got in touch with the people behind the
2303 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2304 project
</a
> to get started. If you want to help out, please start
2306 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2307 hosted weblate project page
</a
>, and get in touch using
2308 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2309 translators mailing list
</a
>. Please also check out
2310 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2311 contributors
</a
>.
</p
>
2313 <p
>The book is already available on paper in English, French and
2314 Japanese, and our goal is to get it available on paper in Norwegian
2315 Bokmål too. In addition to the paper edition, there are also EPUB and
2316 Mobi versions available. And there are incomplete translations
2317 available for many more languages.
</p
>
2322 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2323 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2325 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2326 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2327 packages in Debian, and was quite surprised with what I found. I use
2328 ZFS myself at home, but did not really expect many others to do so.
2329 But I might be wrong.
</p
>
2331 <p
>According to
2332 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2333 results for spl-linux
</a
>, there are
1019 Debian installations, or
2334 0.53% of the population, with the package installed. As far as I know
2335 the only use of the spl-linux package is as a support library for ZFS
2336 on Linux, so I use it here as proxy for measuring the number of ZFS
2337 installation on Linux in Debian. In the kFreeBSD variant of Debian
2338 the ZFS feature is already available, and there
2339 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2340 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2341 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2343 <p
>But even though the Debian project leader Lucas Nussbaum
2344 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2345 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2346 cleared, the package is still not in Debian. The package is again in
2347 the NEW queue. Several uploads have been rejected so far because the
2348 debian/copyright file was incomplete or wrong, but there is no reason
2349 to give up. The current status can be seen on
2350 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2351 team status page
</a
>, and
2352 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2353 source code
</a
> is available on Alioth.
</p
>
2355 <p
>As I want ZFS to be included in next version of Debian to make sure
2356 my home server can function in the future using only official Debian
2357 packages, and the current blocker is to get the debian/copyright file
2358 accepted by the FTP masters in Debian, I decided a while back to try
2359 to help out the team. This was the background for my blog post about
2360 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2361 updating and checking debian/copyright semi-automatically
</a
>, and I
2362 used the techniques I explored there to try to find any errors in the
2363 copyright file. It is not very easy to check every one of the around
2364 2000 files in the source package, but I hope we this time got it
2365 right. If you want to help out, check out the git source and try to
2366 find missing entries in the debian/copyright file.
</p
>
2371 <title>Full battery stats collector is now available in Debian
</title>
2372 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2373 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2374 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2375 <description><p
>Since this morning, the battery-stats package in Debian include an
2376 extended collector that will collect the complete battery history for
2377 later processing and graphing. The original collector store the
2378 battery level as percentage of last full level, while the new
2379 collector also record battery vendor, model, serial number, design
2380 full level, last full level and current battery level. This make it
2381 possible to predict the lifetime of the battery as well as visualise
2382 the energy flow when the battery is charging or discharging.
</p
>
2384 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2385 in the version
0.5.1 package in unstable. Get the new battery level graph
2386 and lifetime prediction by running:
2388 <p
><pre
>
2389 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2390 </pre
></p
>
2392 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2394 <p
>The flow in/out of the battery can be seen by running (no menu
2395 entry yet):
</p
>
2397 <p
><pre
>
2398 /usr/share/battery-stats/battery-stats-graph-flow
2399 </pre
></p
>
2401 <p
>I
'm not quite happy with the way the data is visualised, at least
2402 when there are few data points. The graphs look a bit better with a
2403 few years of data.
</p
>
2405 <p
>A while back one important feature I use in the battery stats
2406 collector broke in Debian. The scripts in
2407 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2408 suspect it happened when Jessie started using systemd, but I do not
2409 know. The issue is reported as
2410 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2411 pm-utils. I managed to work around it by adding an udev rule to call
2412 the collector script every time the power connector is connected and
2413 disconnected. With this fix in place it was finally time to make a
2414 new release of the package, and get it into Debian.
</p
>
2416 <p
>If you are interested in how your laptop battery is doing, please
2418 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2419 in Debian unstable, or rebuild it on Jessie to get it working on
2420 Debian stable. :) The upstream source is available from
2421 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2422 As always, patches are very welcome.
</p
>
2427 <title>Making battery measurements a little easier in Debian
</title>
2428 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2429 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2430 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2431 <description><p
>Back in September, I blogged about
2432 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2433 system I wrote to collect statistics about my laptop battery
</a
>, and
2434 how it showed the decay and death of this battery (now replaced). I
2435 created a simple deb package to handle the collection and graphing,
2436 but did not want to upload it to Debian as there were already
2437 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2438 package in Debian
</a
> that should do the same thing, and I did not see
2439 a point of uploading a competing package when battery-stats could be
2440 fixed instead. I reported a few bugs about its non-function, and
2441 hoped someone would step in and fix it. But no-one did.
</p
>
2443 <p
>I got tired of waiting a few days ago, and took matters in my own
2444 hands. The end result is that I am now the new upstream developer of
2445 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2446 battery-stats in Debian, and the package in Debian unstable is finally
2447 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2448 information provided by the Linux kernel. If you install the
2449 battery-stats package from unstable now, you will be able to get a
2450 graph of the current battery fill level, to get some idea about the
2451 status of the battery. The source package build and work just fine in
2452 Debian testing and stable (and probably oldstable too, but I have not
2453 tested). The default graph you get for that system look like this:
</p
>
2455 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
2457 <p
>My plans for the future is to merge my old scripts into the
2458 battery-stats package, as my old scripts collected a lot more details
2459 about the battery. The scripts are merged into the upstream
2460 battery-stats git repository already, but I am not convinced they work
2461 yet, as I changed a lot of paths along the way. Will have to test a
2462 bit more before I make a new release.
</p
>
2464 <p
>I will also consider changing the file format slightly, as I
2465 suspect the way I combine several values into one field might make it
2466 impossible to know the type of the value when using it for processing
2467 and graphing.
</p
>
2469 <p
>If you would like I would like to keep an close eye on your laptop
2470 battery, check out the battery-stats package in
2471 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2473 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2474 I would love some help to improve the system further.
</p
>
2479 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2480 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2482 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2483 <description><p
>Making packages for Debian requires quite a lot of attention to
2484 details. And one of the details is the content of the
2485 debian/copyright file, which should list all relevant licenses used by
2486 the code in the package in question, preferably in
2487 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2488 readable DEP5 format
</a
>.
</p
>
2490 <p
>For large packages with lots of contributors it is hard to write
2491 and update this file manually, and if you get some detail wrong, the
2492 package is normally rejected by the ftpmasters. So getting it right
2493 the first time around get the package into Debian faster, and save
2494 both you and the ftpmasters some work.. Today, while trying to figure
2495 out what was wrong with
2496 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2497 zfsonlinux copyright file
</a
>, I decided to spend some time on
2498 figuring out the options for doing this job automatically, or at least
2499 semi-automatically.
</p
>
2501 <p
>Lucikly, there are at least two tools available for generating the
2502 file based on the code in the source package,
2503 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2504 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2505 not sure which one of them came first, but both seem to be able to
2506 create a sensible draft file. As far as I can tell, none of them can
2507 be trusted to get the result just right, so the content need to be
2508 polished a bit before the file is OK to upload. I found the debmake
2510 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2511 blog posts from
2014</a
>.
2513 <p
>To generate using debmake, use the -cc option:
2515 <p
><pre
>
2516 debmake -cc
> debian/copyright
2517 </pre
></p
>
2519 <p
>Note there are some problems with python and non-ASCII names, so
2520 this might not be the best option.
</p
>
2522 <p
>The cme option is based on a config parsing library, and I found
2524 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2525 blog post from
2015</a
>. To generate using cme, use the
'update
2526 dpkg-copyright
' option:
2528 <p
><pre
>
2529 cme update dpkg-copyright
2530 </pre
></p
>
2532 <p
>This will create or update debian/copyright. The cme tool seem to
2533 handle UTF-
8 names better than debmake.
</p
>
2535 <p
>When the copyright file is created, I would also like some help to
2536 check if the file is correct. For this I found two good options,
2537 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2538 to focus on license types and file matching, and is able to detect
2539 ineffective blocks in the copyright file. The latter reports missing
2540 copyright holders and years, but was confused by inconsistent license
2541 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2542 fix all issues reported by them before uploading. But I do not know
2543 if the tools and the ftpmasters agree on what is important to fix in a
2544 copyright file, so the package might still be rejected.
</p
>
2546 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2547 will read through the source and try to find all copyright statements.
2548 It is not comparing the result to the content of debian/copyright, but
2549 can be useful when verifying the content of the copyright file.
</p
>
2551 <p
>Are you aware of better tools in Debian to create and update
2552 debian/copyright file. Please let me know, or blog about it on
2553 planet.debian.org.
</p
>
2555 <p
>As usual, if you use Bitcoin and want to show your support of my
2556 activities, please send Bitcoin donations to my address
2557 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2559 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2560 on how to use licensecheck and cdbs to create a draft copyright file
2562 <p
><pre
>
2563 licensecheck --copyright -r `find * -type f` | \
2564 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2565 </pre
></p
>
2567 <p
>He mentioned that he normally check the generated file into the
2568 version control system to make it easier to discover license and
2569 copyright changes in the upstream source. I will try to do the same
2570 with my packages in the future.
</p
>
2572 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2573 against using -quiet for new users, so I removed it from the proposed
2574 command line.
</p
>
2579 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2580 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2581 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2582 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2583 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2584 is taking shape in Debian, and one provided feature is a very
2585 convenient way to tell you which package to install to make a given
2586 firmware file available when the kernel is looking for it. This can
2587 be done using apt-file too, but that is for someone else to blog
2590 <p
>Here is a small recipe to find the package with a given firmware
2591 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2592 picked from the set of firmware announced using appstream in Debian
2593 unstable. In general you would be looking for the firmware requested
2594 by the kernel during kernel module loading. To find the package
2595 providing the example file, do like this:
</p
>
2597 <blockquote
><pre
>
2598 % apt install appstream
2602 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2603 awk
'/Package:/ {print $
2}
'
2606 </pre
></blockquote
>
2608 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2609 appstream wiki
</a
> page to learn how to embed the package metadata in
2610 a way appstream can use.
</p
>
2612 <p
>This same approach can be used to find any package supporting a
2613 given MIME type. This is very useful when you get a file you do not
2614 know how to handle. First find the mime type using
<tt
>file
2615 --mime-type
</tt
>, and next look up the package providing support for
2616 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2617 and you can find all packages handling this type like this:
</p
>
2619 <blockquote
><pre
>
2620 % apt install appstream
2624 % appstreamcli what-provides mimetype image/svg+xml | \
2625 awk
'/Package:/ {print $
2}
'
2647 </pre
></blockquote
>
2649 <p
>I believe the MIME types are fetched from the desktop file for
2650 packages providing appstream metadata.
</p
>
2655 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2656 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2658 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2659 <description><p
>Most people seem not to realise that every time they walk around
2660 with the computerised radio beacon known as a mobile phone their
2661 position is tracked by the phone company and often stored for a long
2662 time (like every time a SMS is received or sent). And if their
2663 computerised radio beacon is capable of running programs (often called
2664 mobile apps) downloaded from the Internet, these programs are often
2665 also capable of tracking their location (if the app requested access
2666 during installation). And when these programs send out information to
2667 central collection points, the location is often included, unless
2668 extra care is taken to not send the location. The provided
2669 information is used by several entities, for good and bad (what is
2670 good and bad, depend on your point of view). What is certain, is that
2671 the private sphere and the right to free movement is challenged and
2672 perhaps even eradicated for those announcing their location this way,
2673 when they share their whereabouts with private and public
2676 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2678 <p
>The phone company logs provide a register of locations to check out
2679 when one want to figure out what the tracked person was doing. It is
2680 unavailable for most of us, but provided to selected government
2681 officials, company staff, those illegally buying information from
2682 unfaithful servants and crackers stealing the information. But the
2683 public information can be collected and analysed, and a free software
2684 tool to do so is called
2685 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2686 discovered it when I read
2687 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2688 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2689 November
2014, and decided to check if it was available in Debian.
2690 The python program was in Debian, but
2691 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2692 Debian
</a
> was completely broken and practically unmaintained. I
2693 uploaded a new version which did not work quite right, but did not
2694 have time to fix it then. This Christmas I decided to finally try to
2695 get Creepy operational in Debian. Now a fixed version is available in
2696 Debian unstable and testing, and almost all Debian specific patches
2698 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2700 <p
>The Creepy program visualises geolocation information fetched from
2701 Twitter, Instagram, Flickr and Google+, and allow one to get a
2702 complete picture of every social media message posted recently in a
2703 given area, or track the movement of a given individual across all
2704 these services. Earlier it was possible to use the search API of at
2705 least some of these services without identifying oneself, but these
2706 days it is impossible. This mean that to use Creepy, you need to
2707 configure it to log in as yourself on these services, and provide
2708 information to them about your search interests. This should be taken
2709 into account when using Creepy, as it will also share information
2710 about yourself with the services.
</p
>
2712 <p
>The picture above show the twitter messages sent from (or at least
2713 geotagged with a position from) the city centre of Oslo, the capital
2714 of Norway. One useful way to use Creepy is to first look at
2715 information tagged with an area of interest, and next look at all the
2716 information provided by one or more individuals who was in the area.
2717 I tested it by checking out which celebrity provide their location in
2718 twitter messages by checkout out who sent twitter messages near a
2719 Norwegian TV station, and next could track their position over time,
2720 making it possible to locate their home and work place, among other
2721 things. A similar technique have been
2722 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2723 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2724 tool to discover lying governments, and a useful tool to help people
2725 understand the value of the private information they provide to the
2728 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2729 it depend on several python modules currently missing in Jessie (at
2730 least python-instagram, python-flickrapi and
2731 python-requests-toolbelt).
</p
>
2733 <p
>(I have uploaded
2734 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2735 screenshots.debian.net
</a
> and licensed it under the same terms as the
2736 Creepy program in Debian.)
</p
>
2741 <title>Always download Debian packages using Tor - the simple recipe
</title>
2742 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2744 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2745 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2746 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2747 that those listening on the Internet lines would have good reason to
2748 believe a computer have a given security hole
</a
> if it download a
2749 security fix from a Debian mirror. This is a good reason to always
2750 use encrypted connections to the Debian mirror, to make sure those
2751 listening do not know which IP address to attack. In August, Richard
2752 Hartmann observed that encryption was not enough, when it was possible
2753 to interfere download size to security patches or the fact that
2754 download took place shortly after a security fix was released, and
2755 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2756 to always use Tor to download packages from the Debian mirror
</a
>. He
2757 was not the first to propose this, as the
2758 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2759 package by Tim Retout already existed to make it easy to convince apt
2760 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2761 aware of that package when I read the blog post from Richard.
</p
>
2763 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2764 sysadmins, and he set up a Tor hidden service on one of the central
2765 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2766 it possible to download packages directly between two tor nodes,
2767 making sure the network traffic always were encrypted.
</p
>
2769 <p
>Here is a short recipe for enabling this on your machine, by
2770 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2771 urls with tor+http and tor+https, and using the hidden service instead
2772 of the official Debian mirror site. I recommend installing
2773 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2774 done in /etc/.
</p
>
2776 <blockquote
><pre
>
2777 apt install apt-transport-tor
2778 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2779 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2780 </pre
></blockquote
>
2782 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2783 the sed commands for these too. The sed command is assuming your are
2784 using the ftp.debian.org Debian mirror. Adjust the command (or just
2785 edit the file manually) to match your mirror.
</p
>
2787 <p
>This work in Debian Jessie and later. Note that tools like
2788 <tt
>apt-file
</tt
> only recently started using the apt transport
2789 system, and do not work with these tor+http URLs. For
2790 <tt
>apt-file
</tt
> you need the version currently in experimental,
2791 which need a recent apt version currently only in unstable. So if you
2792 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2794 <p
>Another advantage from this change is that your machine will start
2795 using Tor regularly and at fairly random intervals (every time you
2796 update the package lists or upgrade or install a new package), thus
2797 masking other Tor traffic done from the same machine. Using Tor will
2798 become normal for the machine in question.
</p
>
2800 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2801 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2802 enabled. It would be great if it was the default on any Debian
2808 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2809 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2810 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2811 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2812 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2813 call the car license plate numbers in those days. I would write the
2814 numbers down in my little book and compare notes with the other kids
2815 to see how many region codes we had seen and if we had seen some
2816 exotic or special region codes and numbers. It was a fun game to pass
2817 time, as we kids have plenty of it.
</p
>
2819 <p
>A few days I came across
2820 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2821 project
</a
>, a free software project to automatically discover and
2822 report license plates in images and video streams, and provide the
2823 "car numbers
" in a machine readable format. I
've been looking for
2824 such system for a while now, because I believe it is a bad idea that the
2825 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2826 number plate recognition
</a
> tool only is available in the hands of
2827 the powerful, and want it to be available also for the powerless to
2828 even the score when it comes to surveillance and sousveillance. I
2829 discovered the developer
2830 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2831 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2832 help him get it into shape to get the package uploaded into the Debian
2835 <p
>Today we finally managed to get the package into shape and uploaded
2836 it into Debian, where it currently
2837 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2838 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2840 <p
>I guess you are wondering why on earth such tool would be useful
2841 for the common folks, ie those not running a large government
2842 surveillance system? Well, I plan to put it in a computer on my bike
2843 and in my car, tracking the cars nearby and allowing me to be notified
2844 when number plates on my watch list are discovered. Another use case
2845 was suggested by a friend of mine, who wanted to set it up at his home
2846 to open the car port automatically when it discovered the plate on his
2847 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2848 capable of placing his license plate number of a piece of cardboard to
2849 open his car port, men replied that it was always unlocked anyway. I
2850 guess for such use case it make sense. I am sure there are other use
2851 cases too, for those with imagination and a vision.
</p
>
2853 <p
>If you want to build your own version of the Debian package, check
2854 out the upstream git source and symlink ./distros/debian to ./debian/
2855 before running
"debuild
" to build the source. Or wait a bit until the
2856 package show up in unstable.
</p
>
2861 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2862 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2863 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2864 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2865 <description><p
>Around three years ago, I created
2866 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2867 system
</a
> to get a more practical solution in Debian for handing
2868 hardware related packages. A GUI system in the isenkram package will
2869 present a pop-up dialog when some hardware dongle supported by
2870 relevant packages in Debian is inserted into the machine. The same
2871 lookup mechanism to detect packages is available as command line
2872 tools in the isenkram-cli package. In addition to mapping hardware,
2873 it will also map kernel firmware files to packages and make it easy to
2874 install needed firmware packages automatically. The key for this
2875 system to work is a good way to map hardware to packages, in other
2876 words, allow packages to announce what hardware they will work
2879 <p
>I started by providing data files in the isenkram source, and
2880 adding code to download the latest version of these data files at run
2881 time, to ensure every user had the most up to date mapping available.
2882 I also added support for storing the mapping in the Packages file in
2883 the apt repositories, but did not push this approach because while I
2884 was trying to figure out how to best store hardware/package mappings,
2885 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2886 appstream system
</a
> was announced. I got in touch and suggested to
2887 add the hardware mapping into that data set to be able to use
2888 appstream as a data source, and this was accepted at least for the
2889 Debian version of appstream.
</p
>
2891 <p
>A few days ago using appstream in Debian for this became possible,
2892 and today I uploaded a new version
0.20 of isenkram adding support for
2893 appstream as a data source for mapping hardware to packages. The only
2894 package so far using appstream to announce its hardware support is my
2895 pymissile package. I got help from Matthias Klumpp with figuring out
2896 how do add the required
2897 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2898 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2899 this content:
</p
>
2901 <blockquote
><pre
>
2902 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2903 &lt;component
&gt;
2904 &lt;id
&gt;pymissile
&lt;/id
&gt;
2905 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2906 &lt;name
&gt;pymissile
&lt;/name
&gt;
2907 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2908 &lt;description
&gt;
2910 Pymissile provides a curses interface to control an original
2911 Marks and Spencer / Striker USB Missile Launcher, as well as a
2912 motion control script to allow a webcamera to control the
2915 &lt;/description
&gt;
2916 &lt;provides
&gt;
2917 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2918 &lt;/provides
&gt;
2919 &lt;/component
&gt;
2920 </pre
></blockquote
>
2922 <p
>The key for isenkram is the component/provides/modalias value,
2923 which is a glob style match rule for hardware specific strings
2924 (modalias strings) provided by the Linux kernel. In this case, it
2925 will map to all USB devices with vendor code
1130 and product code
2928 <p
>Note, it is important that the license of all the metadata files
2929 are compatible to have permissions to aggregate them into archive wide
2930 appstream files. Matthias suggested to use MIT or BSD licenses for
2931 these files. A challenge is figuring out a good id for the data, as
2932 it is supposed to be globally unique and shared across distributions
2933 (in other words, best to coordinate with upstream what to use). But
2934 it can be changed later or, so we went with the package name as
2935 upstream for this project is dormant.
</p
>
2937 <p
>To get the metadata file installed in the correct location for the
2938 mirror update scripts to pick it up and include its content the
2939 appstream data source, the file must be installed in the binary
2940 package under /usr/share/appdata/. I did this by adding the following
2941 line to debian/pymissile.install:
</p
>
2943 <blockquote
><pre
>
2944 debian/pymissile.metainfo.xml usr/share/appdata
2945 </pre
></blockquote
>
2947 <p
>With that in place, the command line tool isenkram-lookup will list
2948 all packages useful on the current computer automatically, and the GUI
2949 pop-up handler will propose to install the package not already
2950 installed if a hardware dongle is inserted into the machine in
2953 <p
>Details of the modalias field in appstream is available from the
2954 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2956 <p
>To locate the modalias values of all hardware present in a machine,
2957 try running this command on the command line:
</p
>
2959 <blockquote
><pre
>
2960 cat $(find /sys/devices/|grep modalias)
2961 </pre
></blockquote
>
2963 <p
>To learn more about the isenkram system, please check out
2964 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2965 blog posts tagged isenkram
</a
>.
</p
>
2970 <title>The GNU General Public License is not magic pixie dust
</title>
2971 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2972 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2973 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2974 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2975 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2976 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2977 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2978 I quote the blog post from Paul in full here with his permission:
<p
>
2982 <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
>
2985 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2987 The first step is to choose a
2988 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2991 The next step is, when someone fails to follow that copyleft license,
2992 <b
>it must be enforced
</b
><br/
>
2994 and its a simple fact of our modern society that such type of
2997 is incredibly expensive to do and incredibly difficult to do.
3000 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3001 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3002 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3003 0x57</a
></small
></p
>
3005 <p
>As the Debian Website
3006 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3007 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3008 imply, public domain and permissively licensed software can lead to
3009 the production of more proprietary software as people discover useful
3010 software, extend it and or incorporate it into their hardware or
3011 software products. Copyleft licenses such as the GNU GPL were created
3012 to close off this avenue to the production of proprietary software but
3013 such licenses are not enough. With the ongoing adoption of Free
3014 Software by individuals and groups, inevitably the community
's
3015 expectations of license compliance are violated, usually out of
3016 ignorance of the way Free Software works, but not always. As Karen
3017 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3018 Freedom
">FaiF
</a
>
3019 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3020 copyleft is nothing if no-one is willing and able to stand up in court
3021 to protect it. The reality of today
's world is that legal
3022 representation is expensive, difficult and time consuming. With
3023 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
3024 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
3025 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
3026 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
3027 of the Linux project, Debian and other groups against GPL violations.
3028 In March the SFC supported a
3029 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
3030 by Christoph Hellwig
</a
> against VMware for refusing to
3031 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
3032 with the GPL
</a
> in relation to their use of parts of the Linux
3033 kernel. Since then two of their sponsors pulled corporate funding and
3035 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
3036 or cancelled their talks
</a
>. As a result they have decided to rely
3037 less on corporate funding and more on the broad community of
3038 individuals who support Free Software and copyleft. So the SFC has
3039 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
3040 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
3041 a community of folks who stand up for copyleft and the GPL by
3042 supporting their work on promoting and supporting copyleft and Free
3045 <p
>If you support Free Software,
3046 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
3047 what the SFC do, agree with their
3048 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
3049 principles
</a
>, are happy about their
3050 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
3051 work on a project that is an SFC
3052 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
3053 just want to stand up for copyleft, please join
3054 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
3055 Allan Webber
</a
>,
3056 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
3058 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
3059 Bacon
</a
>, myself and
3060 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
3062 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
3063 next week your donation will be
3064 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
3065 by an anonymous donor. Please also consider asking your employer to
3066 match your donation or become a sponsor of SFC. Don
't forget to
3067 spread the word about your support for SFC via email, your blog and or
3068 social media accounts.
</p
>
3072 <p
>I agree with Paul on this topic and just signed up as a Supporter
3073 of Software Freedom Conservancy myself. Perhaps you should be a
3074 supporter too?
</p
>
3079 <title>PGP key transition statement for key EE4E02F9
</title>
3080 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
3081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
3082 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
3083 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
3084 set it up properly. I wanted to generate it offline and have it
3085 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
3086 smart card
</a
> for daily use, and learning how to do it and finding
3087 time to sit down with an offline machine almost took forever. But
3088 finally I
've been able to complete the process, and have now moved
3089 from my old GPG key to a new GPG key. See
3090 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
3091 full transition statement, signed with both my old and new key
</a
> for
3092 the details. This is my new key:
</p
>
3095 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
3096 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3097 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3098 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3099 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3100 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3101 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3104 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3105 my old key.
</p
>
3107 <p
>If you signed my old key
3108 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3109 I
'd very much appreciate a signature on my new key, details and
3110 instructions in the transition statement. I m happy to reciprocate if
3111 you have a similarly signed transition statement to present.
</p
>
3116 <title>The life and death of a laptop battery
</title>
3117 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3118 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3119 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3120 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3121 But this do not last. The last few laptops gave me a feeling that
3122 within a year, the life time is just a fraction of what it used to be,
3123 and it slowly become painful to use the laptop without power connected
3124 all the time. Because of this, when I got a new Thinkpad X230 laptop
3125 about two years ago, I decided to monitor its battery state to have
3126 more hard facts when the battery started to fail.
</p
>
3128 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3130 <p
>First I tried to find a sensible Debian package to record the
3131 battery status, assuming that this must be a problem already handled
3132 by someone else. I found
3133 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3134 which collects statistics from the battery, but it was completely
3135 broken. I sent a few suggestions to the maintainer, but decided to
3136 write my own collector as a shell script while I waited for feedback
3138 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3139 blog post about the battery development on a MacBook Air
</a
> I also
3141 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3142 available in Debian.
</p
>
3144 <p
>I started my collector
2013-
07-
15, and it has been collecting
3145 battery stats ever since. Now my
3146 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3147 measurements, from the time the battery was working great until now,
3148 when it is unable to charge above
7% of original capacity. My
3149 collector shell script is quite simple and look like this:
</p
>
3154 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3156 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3157 logfile=/var/log/hjemmenett-battery-status.log
3159 files=
"manufacturer model_name technology serial_number \
3160 energy_full energy_full_design energy_now cycle_count status
"
3162 if [ ! -e
"$logfile
" ] ; then
3164 printf
"timestamp,
"
3166 printf
"%s,
" $f
3169 )
> "$logfile
"
3173 # Print complete message in one echo call, to avoid race condition
3174 # when several log processes run in parallel.
3175 msg=$(printf
"%s,
" $(date +%s); \
3176 for f in $files; do \
3177 printf
"%s,
" $(cat $f); \
3179 echo
"$msg
"
3182 cd /sys/class/power_supply
3185 (cd $bat
&& log_battery
>> "$logfile
")
3189 <p
>The script is called when the power management system detect a
3190 change in the power status (power plug in or out), and when going into
3191 and out of hibernation and suspend. In addition, it collect a value
3192 every
10 minutes. This make it possible for me know when the battery
3193 is discharging, charging and how the maximum charge change over time.
3194 The code for the Debian package
3195 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3196 available on github
</a
>.
</p
>
3198 <p
>The collected log file look like this:
</p
>
3201 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3202 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3204 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3205 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3208 <p
>I wrote a small script to create a graph of the charge development
3209 over time. This graph depicted above show the slow death of my laptop
3212 <p
>But why is this happening? Why are my laptop batteries always
3213 dying in a year or two, while the batteries of space probes and
3214 satellites keep working year after year. If we are to believe
3215 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3216 University
</a
>, the cause is me charging the battery whenever I have a
3217 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3218 all the time, but to stay below
90% of full charge most of the time.
3219 I
've been told that the Tesla electric cars
3220 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3221 the charge of their batteries to
80%
</a
>, with the option to charge to
3222 100% when preparing for a longer trip (not that I would want a car
3223 like Tesla where rights to privacy is abandoned, but that is another
3224 story), which I guess is the option we should have for laptops on
3225 Linux too.
</p
>
3227 <p
>Is there a good and generic way with Linux to tell the battery to
3228 stop charging at
80%, unless requested to charge to
100% once in
3229 preparation for a longer trip? I found
3230 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3231 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3232 80%
</a
>, but could not get it to work (kernel module refused to
3235 <p
>I wonder why the battery capacity was reported to be more than
100%
3236 at the start. I also wonder why the
"full capacity
" increases some
3237 times, and if it is possible to repeat the process to get the battery
3238 back to design capacity. And I wonder if the discharge and charge
3239 speed change over time, or if this stay the same. I did not yet try
3240 to write a tool to calculate the derivative values of the battery
3241 level, but suspect some interesting insights might be learned from
3244 <p
>Update
2015-
09-
24: I got a tip to install the packages
3245 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3246 packages instead of the tp-smapi-dkms package I had tried to use
3247 initially, and use
'tlp setcharge
40 80' to change when charging start
3248 and stop. I
've done so now, but expect my existing battery is toast
3249 and need to be replaced. The proposal is unfortunately Thinkpad
3255 <title>New laptop - some more clues and ideas based on feedback
</title>
3256 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3257 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3258 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3259 <description><p
>Several people contacted me after my previous blog post about my
3260 need for a new laptop, and provided very useful feedback. I wish to
3261 thank every one of these. Several pointed me to the possibility of
3262 fixing my X230, and I am already in the process of getting Lenovo to
3263 do so thanks to the on site, next day support contract covering the
3264 machine. But the battery is almost useless (I expect to replace it
3265 with a non-official battery) and I do not expect the machine to live
3266 for many more years, so it is time to plan its replacement. If I did
3267 not have a support contract, it was suggested to find replacement parts
3268 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3269 might present a language barrier as I do not understand French.
</p
>
3271 <p
>One tip I got was to use the
3272 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3273 compare laptop models. It seem to have more models available than
3274 prisjakt.no. Another tip I got from someone I know have similar
3275 keyboard preferences was that the HP EliteBook
840 keyboard is not
3276 very good, and this matches my experience with earlier EliteBook
3277 keyboards I tested. Because of this, I will not consider it any further.
3279 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3280 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3281 (which is missing from the X240), and is working fairly well with
3282 Debian Sid/Unstable according to
3283 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3284 got on the keyboard quality are not consistent. Some say the keyboard
3285 is good, others say it is ok, while others say it is not very good.
3286 Those with experience from X41 and and X60 agree that the X250
3287 keyboard is not as good as those trusty old laptops, and suggest I
3288 keep and fix my X230 instead of upgrading, or get a used X230 to
3289 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3290 activity and battery status, which is very convenient on my X230. I
'm
3291 also told that the CPU fan is running very often, making it a bit
3292 noisy. In any case, the X250 do not work out of the box with Debian
3293 Stable/Jessie, one of my requirements.
</p
>
3295 <p
>I have also gotten a few vendor proposals, one was
3296 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3297 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3298 The latter look very attractive to me.
</p
>
3300 <p
>Again, thank you all for the very useful feedback. It help a lot
3301 as I keep looking for a replacement.
</p
>
3303 <p
>Update
2015-
07-
06: I was recommended to check out the
3304 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3306 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3307 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3312 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3313 <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>
3314 <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>
3315 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3316 <description><p
>My primary work horse laptop is failing, and will need a
3317 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3318 started flickering yesterday, and I suspect the cause is a broken
3319 cable, as changing the angle of the screen some times get rid of the
3320 flickering.
</p
>
3322 <p
>My requirements have not really changed since I bought it, and is
3324 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3325 described them in
2013</a
>. The last time I bought a laptop, I had
3327 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3328 where I could select at least a few of the requirements (mouse pin,
3329 wifi, weight) and go through the rest manually. Three button mouse
3330 and a good keyboard is not available as an option, and all the three
3331 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3332 G2) lack three mouse buttons). It is also unclear to me how good the
3333 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3334 the keyboard, even if the quality and robustness in the X series have
3335 deteriorated since X41.
</p
>
3337 <p
>I wonder how I can find a sensible laptop when none of the options
3338 seem sensible to me? Are there better services around to search the
3339 set of available laptops for features? Please send me an email if you
3340 have suggestions.
</p
>
3342 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3343 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3344 of endorsed hardware
</a
>, which is useful background information.
</p
>
3349 <title>How to stay with sysvinit in Debian Jessie
</title>
3350 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3351 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3352 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3353 <description><p
>By now, it is well known that Debian Jessie will not be using
3354 sysvinit as its boot system by default. But how can one keep using
3355 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3357 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3358 Schubert
</a
> and
3359 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3362 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3363 keep sysvinit as your boot system, create a file
3364 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3365 you upgrade:
</p
>
3367 <p
><blockquote
><pre
>
3368 Package: systemd-sysv
3369 Pin: release o=Debian
3371 </pre
></blockquote
><p
>
3373 <p
>This file content will tell apt and aptitude to not consider
3374 installing systemd-sysv as part of any installation and upgrade
3375 solution when resolving dependencies, and thus tell it to avoid
3376 systemd as a default boot system. The end result should be that the
3377 upgraded system keep using sysvinit.
</p
>
3379 <p
>If you are installing Jessie for the first time, there is no way to
3380 get sysvinit installed by default (debootstrap used by
3381 debian-installer have no option for this), but one can tell the
3382 installer to switch to sysvinit before the first boot. Either by
3383 using a kernel argument to the installer, or by adding a line to the
3384 preseed file used. First, the kernel command line argument:
3386 <p
><blockquote
><pre
>
3387 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3388 </pre
></blockquote
><p
>
3390 <p
>Next, the line to use in a preseed file:
</p
>
3392 <p
><blockquote
><pre
>
3393 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3394 </pre
></blockquote
><p
>
3396 <p
>One can of course also do this after the first boot by installing
3397 the sysvinit-core package.
</p
>
3399 <p
>I recommend only using sysvinit if you really need it, as the
3400 sysvinit boot sequence in Debian have several hardware specific bugs
3401 on Linux caused by the fact that it is unpredictable when hardware
3402 devices show up during boot. But on the other hand, the new default
3403 boot system still have a few rough edges I hope will be fixed before
3404 Jessie is released.
</p
>
3406 <p
>Update
2014-
11-
26: Inspired by
3407 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3408 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3414 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3415 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3417 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3418 <description><p
>The right to communicate with your friends and family in private,
3419 without anyone snooping, is a right every citicen have in a liberal
3420 democracy. But this right is under serious attack these days.
</p
>
3422 <p
>A while back it occurred to me that one way to make the dragnet
3423 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3424 the whisleblower Snowden) more expensive for Internet email,
3425 is to deliver all email using SMTP via Tor. Such SMTP option would be
3426 a nice addition to the FreedomBox project if we could send email
3427 between FreedomBox machines without leaking metadata about the emails
3428 to the people peeking on the wire. I
3429 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3430 this on the FreedomBox project mailing list in October
</a
> and got a
3431 lot of useful feedback and suggestions. It also became obvious to me
3432 that this was not a novel idea, as the same idea was tested and
3433 documented by Johannes Berg as early as
2006, and both
3434 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3435 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3436 propose a similar method / protocol to pass emails between users.
</p
>
3438 <p
>To implement such system one need to set up a Tor hidden service
3439 providing the SMTP protocol on port
25, and use email addresses
3440 looking like username@hidden-service-name.onion. With such addresses
3441 the connections to port
25 on hidden-service-name.onion using Tor will
3442 go to the correct SMTP server. To do this, one need to configure the
3443 Tor daemon to provide the hidden service and the mail server to accept
3444 emails for this .onion domain. To learn more about Exim configuration
3445 in Debian and test the design provided by Johannes Berg in his FAQ, I
3446 set out yesterday to create a Debian package for making it trivial to
3447 set up such SMTP over Tor service based on Debian. Getting it to work
3448 were fairly easy, and
3449 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3450 source code for the Debian package
</a
> is available from github. I
3451 plan to move it into Debian if further testing prove this to be a
3452 useful approach.
</p
>
3454 <p
>If you want to test this, set up a blank Debian machine without any
3455 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3456 get rid of exim4). Install tor, clone the git repository mentioned
3457 above, build the deb and install it on the machine. Next, run
3458 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3459 the instructions to get the service up and running. Restart tor and
3460 exim when it is done, and test mail delivery using swaks like
3463 <p
><blockquote
><pre
>
3464 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3465 --to fbx@dutlqrrmjhtfa3vp.onion
3466 </pre
></blockquote
></p
>
3468 <p
>This will test the SMTP delivery using tor. Replace the email
3469 address with your own address to test your server. :)
</p
>
3471 <p
>The setup procedure is still to complex, and I hope it can be made
3472 easier and more automatic. Especially the tor setup need more work.
3473 Also, the package include a tor-smtp tool written in C, but its task
3474 should probably be rewritten in some script language to make the deb
3475 architecture independent. It would probably also make the code easier
3476 to review. The tor-smtp tool currently need to listen on a socket for
3477 exim to talk to it and is started using xinetd. It would be better if
3478 no daemon and no socket is needed. I suspect it is possible to get
3479 exim to run a command line tool for delivery instead of talking to a
3480 socket, and hope to figure out how in a future version of this
3483 <p
>Until I wipe my test machine, I can be reached using the
3484 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3485 SMTorP. :)
</p
>
3490 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3491 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3493 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3494 <description><p
>If you ever had to moderate a mailman list, like the ones on
3495 alioth.debian.org, you know the web interface is fairly slow to
3496 operate. First you visit one web page, enter the moderation password
3497 and get a new page shown with a list of all the messages to moderate
3498 and various options for each email address. This take a while for
3499 every list you moderate, and you need to do it regularly to do a good
3500 job as a list moderator. But there is a quick alternative,
3501 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3502 listadmin program
</a
>. It allow you to check lists for new messages
3503 to moderate in a fraction of a second. Here is a test run on two
3504 lists I recently took over:
</p
>
3506 <p
><blockquote
><pre
>
3507 % time listadmin xiph
3508 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3509 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3515 </pre
></blockquote
></p
>
3517 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3518 there are no message in the moderation queue. Every morning I
3519 currently moderate
68 mailman lists, and it normally take around two
3520 minutes. When I took over the two pkg-xiph lists above a few days
3521 ago, there were
400 emails waiting in the moderator queue. It took me
3522 less than
15 minutes to process them all using the listadmin
3525 <p
>If you install
3526 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3527 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3528 with content like this, the moderation task is a breeze:
</p
>
3530 <p
><blockquote
><pre
>
3531 username username@example.org
3534 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3537 adminurl https://{domain}/mailman/admindb/{list}
3538 mailman-list@lists.example.com
3541 other-list@otherserver.example.org
3542 </pre
></blockquote
></p
>
3544 <p
>There are other options to set as well. Check the manual page to
3545 learn the details.
</p
>
3547 <p
>If you are forced to moderate lists on a mailman installation where
3548 the SSL certificate is self signed or not properly signed by a
3549 generally accepted signing authority, you can set a environment
3550 variable when calling listadmin to disable SSL verification:
</p
>
3552 <p
><blockquote
><pre
>
3553 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3554 </pre
></blockquote
></p
>
3556 <p
>If you want to moderate a subset of the lists you take care of, you
3557 can provide an argument to the listadmin script like I do in the
3558 initial screen dump (the xiph argument). Using an argument, only
3559 lists matching the argument string will be processed. This make it
3560 quick to accept messages if you notice the moderation request in your
3563 <p
>Without the listadmin program, I would never be the moderator of
68
3564 mailing lists, as I simply do not have time to spend on that if the
3565 process was any slower. The listadmin program have saved me hours of
3566 time I could spend elsewhere over the years. It truly is nice free
3569 <p
>As usual, if you use Bitcoin and want to show your support of my
3570 activities, please send Bitcoin donations to my address
3571 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3573 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3574 configuration example. Also, I
've been told that the
3575 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3581 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3582 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3584 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3585 <description><p
>When PXE installing laptops with Debian, I often run into the
3586 problem that the WiFi card require some firmware to work properly.
3587 And it has been a pain to fix this using preseeding in Debian.
3588 Normally something more is needed. But thanks to
3589 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3590 package
</a
> and its recent tasksel extension, it has now become easy
3591 to do this using simple preseeding.
</p
>
3593 <p
>The isenkram-cli package provide tasksel tasks which will install
3594 firmware for the hardware found in the machine (actually, requested by
3595 the kernel modules for the hardware). (It can also install user space
3596 programs supporting the hardware detected, but that is not the focus
3597 of this story.)
</p
>
3599 <p
>To get this working in the default installation, two preeseding
3600 values are needed. First, the isenkram-cli package must be installed
3601 into the target chroot (aka the hard drive) before tasksel is executed
3602 in the pkgsel step of the debian-installer system. This is done by
3603 preseeding the base-installer/includes debconf value to include the
3604 isenkram-cli package. The package name is next passed to debootstrap
3605 for installation. With the isenkram-cli package in place, tasksel
3606 will automatically use the isenkram tasks to detect hardware specific
3607 packages for the machine being installed and install them, because
3608 isenkram-cli contain tasksel tasks.
</p
>
3610 <p
>Second, one need to enable the non-free APT repository, because
3611 most firmware unfortunately is non-free. This is done by preseeding
3612 the apt-mirror-setup step. This is unfortunate, but for a lot of
3613 hardware it is the only option in Debian.
</p
>
3615 <p
>The end result is two lines needed in your preseeding file to get
3616 firmware installed automatically by the installer:
</p
>
3618 <p
><blockquote
><pre
>
3619 base-installer base-installer/includes string isenkram-cli
3620 apt-mirror-setup apt-setup/non-free boolean true
3621 </pre
></blockquote
></p
>
3623 <p
>The current version of isenkram-cli in testing/jessie will install
3624 both firmware and user space packages when using this method. It also
3625 do not work well, so use version
0.15 or later. Installing both
3626 firmware and user space packages might give you a bit more than you
3627 want, so I decided to split the tasksel task in two, one for firmware
3628 and one for user space programs. The firmware task is enabled by
3629 default, while the one for user space programs is not. This split is
3630 implemented in the package currently in unstable.
</p
>
3632 <p
>If you decide to give this a go, please let me know (via email) how
3633 this recipe work for you. :)
</p
>
3635 <p
>So, I bet you are wondering, how can this work. First and
3636 foremost, it work because tasksel is modular, and driven by whatever
3637 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3638 isenkram-cli package place two files for tasksel to find. First there
3639 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3641 <p
><blockquote
><pre
>
3642 Task: isenkram-packages
3644 Description: Hardware specific packages (autodetected by isenkram)
3645 Based on the detected hardware various hardware specific packages are
3647 Test-new-install: show show
3649 Packages: for-current-hardware
3651 Task: isenkram-firmware
3653 Description: Hardware specific firmware packages (autodetected by isenkram)
3654 Based on the detected hardware various hardware specific firmware
3655 packages are proposed.
3656 Test-new-install: mark show
3658 Packages: for-current-hardware-firmware
3659 </pre
></blockquote
></p
>
3661 <p
>The key parts are Test-new-install which indicate how the task
3662 should be handled and the Packages line referencing to a script in
3663 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3664 list of packages to install. The for-current-hardware-firmware script
3665 look like this to list relevant firmware for the machine:
3667 <p
><blockquote
><pre
>
3670 PATH=/usr/sbin:$PATH
3672 isenkram-autoinstall-firmware -l
3673 </pre
></blockquote
></p
>
3675 <p
>With those two pieces in place, the firmware is installed by
3676 tasksel during the normal d-i run. :)
</p
>
3678 <p
>If you want to test what tasksel will install when isenkram-cli is
3679 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3680 --new-install
</tt
> to get the list of packages that tasksel would
3683 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3684 pilots in testing this feature, as isenkram is used there now to
3685 install firmware, replacing the earlier scripts.
</p
>
3690 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3691 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3692 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3693 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3694 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3695 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3696 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3697 on a screen normally showing the bread types and prizes:
</p
>
3699 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3701 <p
>If it had booted as it was supposed to, I would never had known
3702 about this hidden Linux installation. It is interesting what
3703 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3708 <title>New lsdvd release version
0.17 is ready
</title>
3709 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3710 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3711 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3712 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3713 got a new set of developers a few weeks ago, after the original
3714 developer decided to step down and pass the project to fresh blood.
3715 This project is now maintained by Petter Reinholdtsen and Steve
3718 <p
>I just wrapped up
3719 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3720 new lsdvd release
</a
>, available in git or from
3721 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3722 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3727 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3728 <li
>Check for garbage in the program chains, which indicate that a track is
3729 non-existant, to work around additional copy protection
</li
>
3730 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3731 <li
>Fix pallete display of first entry
</li
>
3732 <li
>Fix include orders
</li
>
3733 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3734 <li
>Fix the chapter count
</li
>
3735 <li
>Make sure the array size and the array limit used when initialising
3736 the palette size is the same.
</li
>
3737 <li
>Fix array printing.
</li
>
3738 <li
>Correct subsecond calculations.
</li
>
3739 <li
>Add sector information to the output format.
</li
>
3740 <li
>Clean up code to be closer to ANSI C and compile without warnings
3741 with more GCC compiler warnings.
</li
>
3745 <p
>This change bring together patches for lsdvd in use in various
3746 Linux and Unix distributions, as well as patches submitted to the
3747 project the last nine years. Please check it out. :)
</p
>
3752 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3753 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3754 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3755 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3756 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3757 project
</a
> provide a Linux solution for schools, including a
3758 powerful desktop with education software, a central server providing
3759 web pages, user database, user home directories, central login and PXE
3760 boot of both clients without disk and the installation to install Debian
3761 Edu on machines with disk (and a few other services perhaps to small
3762 to mention here). We in the Debian Edu team are currently working on
3763 the Jessie based version, trying to get everything in shape before the
3764 freeze, to avoid having to maintain our own package repository in the
3766 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3767 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3768 work left. Some fatal problems block testing, breaking the installer,
3769 but it is possible to work around these to get anyway. Here is a
3770 recipe on how to get the installation limping along.
</p
>
3772 <p
>First, download the test ISO via
3773 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3774 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3776 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3777 The ISO build was broken on Tuesday, so we do not get a new ISO every
3778 12 hours or so, but thankfully the ISO we already got we are able to
3779 install with some tweaking.
</p
>
3781 <p
>When you get to the Debian Edu profile question, go to tty2
3782 (use Alt-Ctrl-F2), run
</p
>
3784 <p
><blockquote
><pre
>
3785 nano /usr/bin/edu-eatmydata-install
3786 </pre
></blockquote
></p
>
3788 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3789 optimization. Return to the installation, select the profile you want
3790 and continue. Without this change, exim4-config will fail to install
3791 due to a known bug in eatmydata.
</p
>
3793 <p
>When you get the grub question at the end, answer /dev/sda (or if
3794 this do not work, figure out what your correct value would be. All my
3795 test machines need /dev/sda, so I have no advice if it do not fit
3796 your need.
</p
>
3798 <p
>If you installed a profile including a graphical desktop, log in as
3799 root after the initial boot from hard drive, and install the
3800 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3801 or mate. If you want several desktop options, install more than one
3802 metapackage. Once this is done, reboot and you should have a working
3803 graphical login screen. This workaround should no longer be needed
3804 once the education-tasks package version
1.801 enter testing in two
3807 <p
>I believe the ISO build will start working on two days when the new
3808 tasksel package enter testing and Steve McIntyre get a chance to
3809 update the debian-cd git repository. The eatmydata, grub and desktop
3810 issues are already fixed in unstable and testing, and should show up
3811 on the ISO as soon as the ISO build start working again. Well the
3812 eatmydata optimization is really just disabled. The proper fix
3813 require an upload by the eatmydata maintainer applying the patch
3814 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3815 The rest have proper fixes in unstable.
</p
>
3817 <p
>I hope this get you going with the installation testing, as we are
3818 quickly running out of time trying to get our Jessie based
3819 installation ready before the distribution freeze in a month.
</p
>
3824 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3825 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3827 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3828 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3829 to handle my fairly large DVD collection. It is a nice command line
3830 tool to get details about a DVD, like title, tracks, track length,
3831 etc, in XML, Perl or human readable format. But lsdvd have not seen
3832 any new development since
2006 and had a few irritating bugs affecting
3833 its use with some DVDs. Upstream seemed to be dead, and in January I
3834 sent a small probe asking for a version control repository for the
3835 project, without any reply. But I use it regularly and would like to
3836 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3837 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3838 the project admin, and after getting a reply from him explaining that
3839 he was no longer interested in the project, I asked if I could take
3840 over. And yesterday, I became project admin.
</p
>
3842 <p
>I
've been in touch with a Gentoo developer and the Debian
3843 maintainer interested in joining forces to maintain the upstream
3844 project, and I hope we can get a new release out fairly quickly,
3845 collecting the patches spread around on the internet into on place.
3846 I
've added the relevant Debian patches to the freshly created git
3847 repository, and expect the Gentoo patches to make it too. If you got
3848 a DVD collection and care about command line tools, check out
3849 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3850 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3851 list
</a
>. :)
</p
>
3856 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3857 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3858 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3859 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3860 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3861 a lot quicker. When we install more than
2000 packages in
3862 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3863 tasksel in the installer, unpacking the binary packages take forever.
3864 A part of the slow I/O issue was discussed in
3865 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3866 much file system sync-ing done by dpkg, which is the package
3867 responsible for unpacking the binary packages. Other parts (like code
3868 executed by postinst scripts) might also sync to disk during
3869 installation. All this sync-ing to disk do not really make sense to
3870 me. If the machine crash half-way through, I start over, I do not try
3871 to salvage the half installed system. So the failure sync-ing is
3872 supposed to protect against, hardware or system crash, is not really
3873 relevant while the installer is running.
</p
>
3875 <p
>A few days ago, I thought of a way to get rid of all the file
3876 system sync()-ing in a fairly non-intrusive way, without the need to
3877 change the code in several packages. The idea is not new, but I have
3878 not heard anyone propose the approach using dpkg-divert before. It
3879 depend on the small and clever package
3880 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3881 uses LD_PRELOAD to replace the system functions for syncing data to
3882 disk with functions doing nothing, thus allowing programs to live
3883 dangerous while speeding up disk I/O significantly. Instead of
3884 modifying the implementation of dpkg, apt and tasksel (which are the
3885 packages responsible for selecting, fetching and installing packages),
3886 it occurred to me that we could just divert the programs away, replace
3887 them with a simple shell wrapper calling
3888 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3889 Two days ago I decided to test the idea, and wrapped up a simple
3890 implementation for the Debian Edu udeb.
</p
>
3892 <p
>The effect was stunning. In my first test it reduced the running
3893 time of the pkgsel step (installing tasks) from
64 to less than
44
3894 minutes (
20 minutes shaved off the installation) on an old Dell
3895 Latitude D505 machine. I am not quite sure what the optimised time
3896 would have been, as I messed up the testing a bit, causing the debconf
3897 priority to get low enough for two questions to pop up during
3898 installation. As soon as I saw the questions I moved the installation
3899 along, but do not know how long the question were holding up the
3900 installation. I did some more measurements using Debian Edu Jessie,
3901 and got these results. The time measured is the time stamp in
3902 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3903 "pkgsel: finishing up
" lines, if you want to do the same measurement
3904 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3905 timing thus do not depend on how quickly the user handle the tasksel
3908 <p
><table
>
3911 <th
>Machine/setup
</th
>
3912 <th
>Original tasksel
</th
>
3913 <th
>Optimised tasksel
</th
>
3914 <th
>Reduction
</th
>
3918 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3919 <td
>64 min (
07:
46-
08:
50)
</td
>
3920 <td
><44 min (
11:
27-
12:
11)
</td
>
3921 <td
>>20 min
18%
</td
>
3925 <td
>Latitude D505 Roaming LXDE
</td
>
3926 <td
>57 min (
08:
48-
09:
45)
</td
>
3927 <td
>34 min (
07:
43-
08:
17)
</td
>
3928 <td
>23 min
40%
</td
>
3932 <td
>Latitude D505 Minimal
</td
>
3933 <td
>22 min (
10:
37-
10:
59)
</td
>
3934 <td
>11 min (
11:
16-
11:
27)
</td
>
3935 <td
>11 min
50%
</td
>
3939 <td
>Thinkpad X200 Minimal
</td
>
3940 <td
>6 min (
08:
19-
08:
25)
</td
>
3941 <td
>4 min (
08:
04-
08:
08)
</td
>
3942 <td
>2 min
33%
</td
>
3946 <td
>Thinkpad X200 Roaming KDE
</td
>
3947 <td
>19 min (
09:
21-
09:
40)
</td
>
3948 <td
>15 min (
10:
25-
10:
40)
</td
>
3949 <td
>4 min
21%
</td
>
3952 </table
></p
>
3954 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3955 time is spent downloading packages. The connection to the Internet
3956 was
100Mbit/s during testing, so downloading should not be a
3957 significant factor in the measurement. Download typically took a few
3958 seconds to a few minutes, depending on the amount of packages being
3959 installed.
</p
>
3961 <p
>The speedup is implemented by using two hooks in
3962 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3963 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3964 finish-install.d hook to remove the divert at the end of the
3965 installation. I picked the pre-pkgsel.d hook instead of the
3966 post-base-installer.d hook because I test using an ISO without the
3967 eatmydata package included, and the post-base-installer.d hook in
3968 Debian Edu can only operate on packages included in the ISO. The
3969 negative effect of this is that I am unable to activate this
3970 optimization for the kernel installation step in d-i. If the code is
3971 moved to the post-base-installer.d hook, the speedup would be larger
3972 for the entire installation.
</p
>
3974 <p
>I
've implemented this in the
3975 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3976 git repository, and plan to provide the optimization as part of the
3977 Debian Edu installation. If you want to test this yourself, you can
3978 create two files in the installer (or in an udeb). One shell script
3979 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3981 <p
><blockquote
><pre
>
3984 . /usr/share/debconf/confmodule
3986 logger -t my-pkgsel
"info: $*
"
3989 logger -t my-pkgsel
"error: $*
"
3991 override_install() {
3992 apt-install eatmydata || true
3993 if [ -x /target/usr/bin/eatmydata ] ; then
3994 for bin in dpkg apt-get aptitude tasksel ; do
3996 # Test that the file exist and have not been diverted already.
3997 if [ -f /target$file ] ; then
3998 info
"diverting $file using eatmydata
"
3999 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4000 > /target$file.edu
4001 chmod
755 /target$file.edu
4002 in-target dpkg-divert --package debian-edu-config \
4003 --rename --quiet --add $file
4004 ln -sf ./$bin.edu /target$file
4006 error
"unable to divert $file, as it is missing.
"
4010 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4015 </pre
></blockquote
></p
>
4017 <p
>To clean up, another shell script should go into
4018 /usr/lib/finish-install.d/ with code like this:
4020 <p
><blockquote
><pre
>
4022 . /usr/share/debconf/confmodule
4024 logger -t my-finish-install
"error: $@
"
4026 remove_install_override() {
4027 for bin in dpkg apt-get aptitude tasksel ; do
4029 if [ -x /target$file.edu ] ; then
4031 in-target dpkg-divert --package debian-edu-config \
4032 --rename --quiet --remove $file
4035 error
"Missing divert for $file.
"
4038 sync # Flush file buffers before continuing
4041 remove_install_override
4042 </pre
></blockquote
></p
>
4044 <p
>In Debian Edu, I placed both code fragments in a separate script
4045 edu-eatmydata-install and call it from the pre-pkgsel.d and
4046 finish-install.d scripts.
</p
>
4048 <p
>By now you might ask if this change should get into the normal
4049 Debian installer too? I suspect it should, but am not sure the
4050 current debian-installer coordinators find it useful enough. It also
4051 depend on the side effects of the change. I
'm not aware of any, but I
4052 guess we will see if the change is safe after some more testing.
4053 Perhaps there is some package in Debian depending on sync() and
4054 fsync() having effect? Perhaps it should go into its own udeb, to
4055 allow those of us wanting to enable it to do so without affecting
4058 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
4059 will break installation of all programs using gnutls because of
4060 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
4061 eatmydata package in Debian will solve it.
</p
>
4063 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
4064 the optimization work again. And I have discovered that the
4065 dpkg-divert trick is not really needed and implemented a slightly
4066 simpler approach as part of the debian-edu-install package. See
4067 tools/edu-eatmydata-install in the source package.
</p
>
4069 <p
>Update
2014-
11-
11: Unfortunately, a new
4070 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
4071 triggering on i386 made it into testing, and broke this installation
4072 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
4073 request
768893</a
> is accepted, it should be working again.
</p
>
4078 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
4079 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
4080 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
4081 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
4082 <description><p
>Yesterday, I had the pleasure of attending a talk with the
4083 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
4084 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
4085 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
4086 learn that there is a large set of publicly available key servers to
4087 use when looking for peoples public key. So far I have used
4088 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4089 were misbehaving, but those days are ended. The servers I have used
4090 up until yesterday have been slow and some times unavailable. I hope
4091 those problems are gone now.
</p
>
4093 <p
>Behind the round robin DNS entry of the
4094 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
4095 there is a pool of more than
100 keyservers which are checked every
4096 day to ensure they are well connected and up to date. It must be
4097 better than what I have used so far. :)
</p
>
4099 <p
>Yesterdays speaker told me that the service is the default
4100 keyserver provided by the default configuration in GnuPG, but this do
4101 not seem to be used in Debian. Perhaps it should?
</p
>
4103 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4106 <p
><blockquote
><pre
>
4107 keyserver pool.sks-keyservers.net
4108 </pre
></blockquote
></p
>
4110 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4111 entries in DNS. Just for fun, I did just that at work, so now every
4112 user of GnuPG at the University of Oslo should find a OpenGPG
4113 keyserver automatically should their need it:
</p
>
4115 <p
><blockquote
><pre
>
4116 % host -t srv _pgpkey-http._tcp.uio.no
4117 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4119 </pre
></blockquote
></p
>
4121 <p
>Now if only
4122 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4123 HKP lookup protocol
</a
> supported finding signature paths, I would be
4124 very happy. It can look up a given key or search for a user ID, but I
4125 normally do not want that, but to find a trust path from my key to
4126 another key. Given a user ID or key ID, I would like to find (and
4127 download) the keys representing a signature path from my key to the
4128 key in question, to be able to get a trust path between the two keys.
4129 This is as far as I can tell not possible today. Perhaps something
4130 for a future version of the protocol?
</p
>
4135 <title>From English wiki to translated PDF and epub via Docbook
</title>
4136 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4137 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4138 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4139 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4140 project
</a
> provide an instruction manual for teachers, system
4141 administrators and other users that contain useful tips for setting up
4142 and maintaining a Debian Edu installation. This text is about how the
4143 text processing of this manual is handled in the project.
</p
>
4145 <p
>One goal of the project is to provide information in the native
4146 language of its users, and for this we need to handle translations.
4147 But we also want to make sure each language contain the same
4148 information, so for this we need a good way to keep the translations
4149 in sync. And we want it to be easy for our users to improve the
4150 documentation, avoiding the need to learn special formats or tools to
4151 contribute, and the obvious way to do this is to make it possible to
4152 edit the documentation using a web browser. We also want it to be
4153 easy for translators to keep the translation up to date, and give them
4154 help in figuring out what need to be translated. Here is the list of
4155 tools and the process we have found trying to reach all these
4158 <p
>We maintain the authoritative source of our manual in the
4159 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4160 wiki
</a
>, as several wiki pages written in English. It consist of one
4161 front page with references to the different chapters, several pages
4162 for each chapter, and finally one
"collection page
" gluing all the
4163 chapters together into one large web page (aka
4164 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4165 AllInOne page
</a
>). The AllInOne page is the one used for further
4166 processing and translations. Thanks to the fact that the
4167 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4168 wiki.debian.org support exporting pages in
4169 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4170 the list of pages to export using the raw version of the AllInOne
4171 page, loop over each of them to generate a Docbook XML version of the
4172 manual. This process also download images and transform image
4173 references to use the locally downloaded images. The generated
4174 Docbook XML files are slightly broken, so some post-processing is done
4175 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4176 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4177 a handfull of images. The XML file can now be used to generate PDF, HTML
4178 and epub versions of the English manual. This is the basic step of
4179 our process, making PDF (using dblatex), HTML (using xsltproc) and
4180 epub (using dbtoepub) version from Docbook XML, and the resulting files
4181 are placed in the debian-edu-doc-en binary package.
</p
>
4183 <p
>But English documentation is not enough for us. We want translated
4184 documentation too, and we want to make it easy for translators to
4185 track the English original. For this we use the
4186 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4187 which allow us to transform the English Docbook XML file into a
4188 translation file (a .pot file), usable with the normal gettext based
4189 translation tools used by those translating free software. The pot
4190 file is used to create and maintain translation files (several .po
4191 files), which the translations update with the native language
4192 translations of all titles, paragraphs and blocks of text in the
4193 original. The next step is combining the original English Docbook XML
4194 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4195 create a translated Docbook XML file (in this case
4196 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4197 translated, if the translation is not complete) Docbook XML file can
4198 then be used like the original to create a PDF, HTML and epub version
4199 of the documentation.
</p
>
4201 <p
>The translators use different tools to edit the .po files. We
4203 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4204 while some use emacs and vi, others can use web based editors like
4205 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4206 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4207 is where the .po file end up, in our git repository. Updated
4208 translations can either be committed directly to git, or submitted as
4209 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4210 against the debian-edu-doc package
</a
>.
</p
>
4212 <p
>One challenge is images, which both might need to be translated (if
4213 they show translated user applications), and are needed in different
4214 formats when creating PDF and HTML versions (epub is a HTML version in
4215 this regard). For this we transform the original PNG images to the
4216 needed density and format during build, and have a way to provide
4217 translated images by storing translated versions in
4218 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4219 package maintainers know more.
</p
>
4221 <p
>If you wonder what the result look like, we provide
4222 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4223 of the documentation packages on the web
</a
>. See for example the
4224 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4225 PDF version
</a
> or the
4226 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4227 HTML version
</a
>. We do not yet build the epub version by default,
4228 but perhaps it will be done in the future.
</p
>
4230 <p
>To learn more, check out
4231 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4232 debian-edu-doc package
</a
>,
4233 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4234 manual on the wiki
</a
> and
4235 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4236 translation instructions
</a
> in the manual.
</p
>
4241 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4242 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4244 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4245 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4246 related packages relevant for the computer installed automatically.
4247 So I implemented one, using
4248 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4249 package
</a
>. To use it, install the tasksel and isenkram packages and
4250 run tasksel as user root. You should be presented with a new option,
4251 "Hardware specific packages (autodetected by isenkram)
". When you
4252 select it, tasksel will install the packages isenkram claim is fit for
4253 the current hardware, hot pluggable or not.
<p
>
4255 <p
>The implementation is in two files, one is the tasksel menu entry
4256 description, and the other is the script used to extract the list of
4257 packages to install. The first part is in
4258 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4261 <p
><blockquote
><pre
>
4264 Description: Hardware specific packages (autodetected by isenkram)
4265 Based on the detected hardware various hardware specific packages are
4267 Test-new-install: mark show
4269 Packages: for-current-hardware
4270 </pre
></blockquote
></p
>
4272 <p
>The second part is in
4273 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4276 <p
><blockquote
><pre
>
4281 isenkram-autoinstall-firmware -l
4283 </pre
></blockquote
></p
>
4285 <p
>All in all, a very short and simple implementation making it
4286 trivial to install the hardware dependent package we all may want to
4287 have installed on our machines. I
've not been able to find a way to
4288 get tasksel to tell you exactly which packages it plan to install
4289 before doing the installation. So if you are curious or careful,
4290 check the output from the isenkram-* command line tools first.
</p
>
4292 <p
>The information about which packages are handling which hardware is
4293 fetched either from the isenkram package itself in
4294 /usr/share/isenkram/, from git.debian.org or from the APT package
4295 database (using the Modaliases header). The APT package database
4296 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4297 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4298 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4299 the python-apt code (bug
4300 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4301 workaround I was able to get rid of the file descriptor leak and
4302 reduce the memory leak from ~
30 MiB per hardware detection down to
4303 around
2 MiB per hardware detection. It should make the desktop
4304 daemon a lot more useful. The fix is in version
0.7 uploaded to
4305 unstable today.
</p
>
4307 <p
>I believe the current way of mapping hardware to packages in
4308 Isenkram is is a good draft, but in the future I expect isenkram to
4309 use the AppStream data source for this. A proposal for getting proper
4310 AppStream support into Debian is floating around as
4311 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4312 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4313 project
</a
> will take place this summer to improve the situation. I
4314 look forward to seeing the result, and welcome patches for isenkram to
4315 start using the information when it is ready.
</p
>
4317 <p
>If you want your package to map to some specific hardware, either
4318 add a
"Xb-Modaliases
" header to your control file like I did in
4319 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4320 package
</a
> or submit a bug report with the details to the isenkram
4322 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4323 blog posts tagged isenkram
</a
> for details on the notation. I expect
4324 the information will be migrated to AppStream eventually, but for the
4325 moment I got no better place to store it.
</p
>
4330 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4331 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4333 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4334 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4335 project
</a
> is working on providing the software and hardware to make
4336 it easy for non-technical people to host their data and communication
4337 at home, and being able to communicate with their friends and family
4338 encrypted and away from prying eyes. It is still going strong, and
4339 today a major mile stone was reached.
</p
>
4341 <p
>Today, the last of the packages currently used by the project to
4342 created the system images were accepted into Debian Unstable. It was
4343 the freedombox-setup package, which is used to configure the images
4344 during build and on the first boot. Now all one need to get going is
4345 the build code from the freedom-maker git repository and packages from
4346 Debian. And once the freedombox-setup package enter testing, we can
4347 build everything directly from Debian. :)
</p
>
4349 <p
>Some key packages used by Freedombox are
4350 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4351 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4352 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4353 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4354 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4355 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4356 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4357 are plans to integrate more packages into the setup. User
4358 documentation is maintained on the Debian wiki. Please
4359 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4360 the manual
</a
> and help us improve it.
</p
>
4362 <p
>To test for yourself and create boot images with the FreedomBox
4363 setup, run this on a Debian machine using a user with sudo rights to
4364 become root:
</p
>
4366 <p
><pre
>
4367 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4368 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4370 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4372 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4373 </pre
></p
>
4375 <p
>Root access is needed to run debootstrap and mount loopback
4376 devices. See the README in the freedom-maker git repo for more
4377 details on the build. If you do not want all three images, trim the
4378 make line. Note that the virtualbox-image target is not really
4379 virtualbox specific. It create a x86 image usable in kvm, qemu,
4380 vmware and any other x86 virtual machine environment. You might need
4381 the version of vmdebootstrap in Jessie to get the build working, as it
4382 include fixes for a race condition with kpartx.
</p
>
4384 <p
>If you instead want to install using a Debian CD and the preseed
4385 method, boot a Debian Wheezy ISO and use this boot argument to load
4386 the preseed values:
</p
>
4388 <p
><pre
>
4389 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4390 </pre
></p
>
4392 <p
>I have not tested it myself the last few weeks, so I do not know if
4393 it still work.
</p
>
4395 <p
>If you wonder how to help, one task you could look at is using
4396 systemd as the boot system. It will become the default for Linux in
4397 Jessie, so we need to make sure it is usable on the Freedombox. I did
4398 a simple test a few weeks ago, and noticed dnsmasq failed to start
4399 during boot when using systemd. I suspect there are other problems
4400 too. :) To detect problems, there is a test suite included, which can
4401 be run from the plinth web interface.
</p
>
4403 <p
>Give it a go and let us know how it goes on the mailing list, and help
4404 us get the new release published. :) Please join us on
4405 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4406 irc.debian.org)
</a
> and
4407 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4408 mailing list
</a
> if you want to help make this vision come true.
</p
>
4413 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4414 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4415 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4416 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4417 <description><p
>For a while now, I have been looking for a sensible offsite backup
4418 solution for use at home. My requirements are simple, it must be
4419 cheap and locally encrypted (in other words, I keep the encryption
4420 keys, the storage provider do not have access to my private files).
4421 One idea me and my friends had many years ago, before the cloud
4422 storage providers showed up, was to use Google mail as storage,
4423 writing a Linux block device storing blocks as emails in the mail
4424 service provided by Google, and thus get heaps of free space. On top
4425 of this one can add encryption, RAID and volume management to have
4426 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4427 I never found time to implement such system. But the last few weeks I
4428 have looked at a system called
4429 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4430 mounted network backed file system with the features I need.
</p
>
4432 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4433 handling several different storage providers, any with Amazon S3,
4434 Google Drive or OpenStack API. There are heaps of such storage
4435 providers. S3QL can also use a local directory as storage, which
4436 combined with sshfs allow for file storage on any ssh server. S3QL
4437 include support for encryption, compression, de-duplication, snapshots
4438 and immutable file systems, allowing me to mount the remote storage as
4439 a local mount point, look at and use the files as if they were local,
4440 while the content is stored in the cloud as well. This allow me to
4441 have a backup that should survive fire. The file system can not be
4442 shared between several machines at the same time, as only one can
4443 mount it at the time, but any machine with the encryption key and
4444 access to the storage service can mount it if it is unmounted.
</p
>
4446 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4447 package is included already. So to get started, run
<tt
>apt-get
4448 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4449 Greenqloud, after reading their nice recipe on
4450 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4451 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4452 in Iceland more than those in USA when it come to keeping my personal
4453 data safe and private, and thus would rather spend money on a company
4454 in Iceland. Another nice recipe is available from the article
4455 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4456 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4457 Admin magazine. When the provider is picked, figure out how to get
4458 the API key needed to connect to the storage API. With Greencloud,
4459 the key did not show up until I had added payment details to my
4462 <p
>Armed with the API access details, it is time to create the file
4463 system. First, create a new bucket in the cloud. This bucket is the
4464 file system storage area. I picked a bucket name reflecting the
4465 machine that was going to store data there, but any name will do.
4466 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4467 the API login and password, and a locally created password. Store it
4468 all in ~root/.s3ql/authinfo2 like this:
4470 <p
><blockquote
><pre
>
4472 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4473 backend-login: API-login
4474 backend-password: API-password
4475 fs-passphrase: local-password
4476 </pre
></blockquote
></p
>
4478 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4479 but any sensible way to create a fairly random password should do it.
4480 Armed with these details, it is now time to run mkfs, entering the API
4481 details and password to create it:
</p
>
4483 <p
><blockquote
><pre
>
4484 # mkdir -m
700 /var/lib/s3ql-cache
4485 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4486 --ssl s3c://s.greenqloud.com:
443/bucket-name
4487 Enter backend login:
4488 Enter backend password:
4489 Before using S3QL, make sure to read the user
's guide, especially
4490 the
'Important Rules to Avoid Loosing Data
' section.
4491 Enter encryption password:
4492 Confirm encryption password:
4493 Generating random encryption key...
4494 Creating metadata tables...
4504 Compressing and uploading metadata...
4505 Wrote
0.00 MB of compressed metadata.
4506 #
</pre
></blockquote
></p
>
4508 <p
>The next step is mounting the file system to make the storage available.
4510 <p
><blockquote
><pre
>
4511 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4512 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4513 Using
4 upload threads.
4514 Downloading and decompressing metadata...
4524 Mounting filesystem...
4526 Filesystem Size Used Avail Use% Mounted on
4527 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4529 </pre
></blockquote
></p
>
4531 <p
>The file system is now ready for use. I use rsync to store my
4532 backups in it, and as the metadata used by rsync is downloaded at
4533 mount time, no network traffic (and storage cost) is triggered by
4534 running rsync. To unmount, one should not use the normal umount
4535 command, as this will not flush the cache to the cloud storage, but
4536 instead running the umount.s3ql command like this:
4538 <p
><blockquote
><pre
>
4541 </pre
></blockquote
></p
>
4543 <p
>There is a fsck command available to check the file system and
4544 correct any problems detected. This can be used if the local server
4545 crashes while the file system is mounted, to reset the
"already
4546 mounted
" flag. This is what it look like when processing a working
4547 file system:
</p
>
4549 <p
><blockquote
><pre
>
4550 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4551 Using cached metadata.
4552 File system seems clean, checking anyway.
4553 Checking DB integrity...
4554 Creating temporary extra indices...
4555 Checking lost+found...
4556 Checking cached objects...
4557 Checking names (refcounts)...
4558 Checking contents (names)...
4559 Checking contents (inodes)...
4560 Checking contents (parent inodes)...
4561 Checking objects (reference counts)...
4562 Checking objects (backend)...
4563 ..processed
5000 objects so far..
4564 ..processed
10000 objects so far..
4565 ..processed
15000 objects so far..
4566 Checking objects (sizes)...
4567 Checking blocks (referenced objects)...
4568 Checking blocks (refcounts)...
4569 Checking inode-block mapping (blocks)...
4570 Checking inode-block mapping (inodes)...
4571 Checking inodes (refcounts)...
4572 Checking inodes (sizes)...
4573 Checking extended attributes (names)...
4574 Checking extended attributes (inodes)...
4575 Checking symlinks (inodes)...
4576 Checking directory reachability...
4577 Checking unix conventions...
4578 Checking referential integrity...
4579 Dropping temporary indices...
4580 Backing up old metadata...
4590 Compressing and uploading metadata...
4591 Wrote
0.89 MB of compressed metadata.
4593 </pre
></blockquote
></p
>
4595 <p
>Thanks to the cache, working on files that fit in the cache is very
4596 quick, about the same speed as local file access. Uploading large
4597 amount of data is to me limited by the bandwidth out of and into my
4598 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4599 which is very close to my upload speed, and downloading the same
4600 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4601 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4602 network, not the file system code. I do not know what a good cache
4603 size would be, but suspect that the cache should e larger than your
4604 working set.
</p
>
4606 <p
>I mentioned that only one machine can mount the file system at the
4607 time. If another machine try, it is told that the file system is
4610 <p
><blockquote
><pre
>
4611 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4612 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4613 Using
8 upload threads.
4614 Backend reports that fs is still mounted elsewhere, aborting.
4616 </pre
></blockquote
></p
>
4618 <p
>The file content is uploaded when the cache is full, while the
4619 metadata is uploaded once every
24 hour by default. To ensure the
4620 file system content is flushed to the cloud, one can either umount the
4621 file system, or ask S3QL to flush the cache and metadata using
4624 <p
><blockquote
><pre
>
4625 # s3qlctrl upload-meta /s3ql
4626 # s3qlctrl flushcache /s3ql
4628 </pre
></blockquote
></p
>
4630 <p
>If you are curious about how much space your data uses in the
4631 cloud, and how much compression and deduplication cut down on the
4632 storage usage, you can use s3qlstat on the mounted file system to get
4635 <p
><blockquote
><pre
>
4637 Directory entries:
9141
4640 Total data size:
22049.38 MB
4641 After de-duplication:
21955.46 MB (
99.57% of total)
4642 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4643 Database size:
2.39 MB (uncompressed)
4644 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4646 </pre
></blockquote
></p
>
4648 <p
>I mentioned earlier that there are several possible suppliers of
4649 storage. I did not try to locate them all, but am aware of at least
4650 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4651 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4652 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4653 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4654 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4655 accept payment in Bitcoin. Pick one that suit your need. Some of
4656 them provide several GiB of free storage, but the prize models are
4657 quite different and you will have to figure out what suits you
4660 <p
>While researching this blog post, I had a look at research papers
4661 and posters discussing the S3QL file system. There are several, which
4662 told me that the file system is getting a critical check by the
4663 science community and increased my confidence in using it. One nice
4665 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4666 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4667 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4668 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4669 and Pamela Smith. Please have a look.
</p
>
4671 <p
>Given my problems with different file systems earlier, I decided to
4672 check out the mounted S3QL file system to see if it would be usable as
4673 a home directory (in other word, that it provided POSIX semantics when
4674 it come to locking and umask handling etc). Running
4675 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4676 test code to check file system semantics
</a
>, I was happy to discover that
4677 no error was found. So the file system can be used for home
4678 directories, if one chooses to do so.
</p
>
4680 <p
>If you do not want a locally file system, and want something that
4681 work without the Linux fuse file system, I would like to mention the
4682 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4683 provide locally encrypted backup using a command line client. It have
4684 a nicer access control system, where one can split out read and write
4685 access, allowing some systems to write to the backup and others to
4686 only read from it.
</p
>
4688 <p
>As usual, if you use Bitcoin and want to show your support of my
4689 activities, please send Bitcoin donations to my address
4690 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4695 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4696 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4697 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4698 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4699 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4700 project
</a
> is working on providing the software and hardware for
4701 making it easy for non-technical people to host their data and
4702 communication at home, and being able to communicate with their
4703 friends and family encrypted and away from prying eyes. It has been
4704 going on for a while, and is slowly progressing towards a new test
4705 release (
0.2).
</p
>
4707 <p
>And what day could be better than the Pi day to announce that the
4708 new version will provide
"hard drive
" / SD card / USB stick images for
4709 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4710 system), and can also be installed using a Debian installer preseed
4711 file. The Debian based Freedombox is now based on Debian Jessie,
4712 where most of the needed packages used are already present. Only one,
4713 the freedombox-setup package, is missing. To try to build your own
4714 boot image to test the current status, fetch the freedom-maker scripts
4716 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4717 with a user with sudo access to become root:
4720 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4722 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4723 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4725 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4728 <p
>Root access is needed to run debootstrap and mount loopback
4729 devices. See the README for more details on the build. If you do not
4730 want all three images, trim the make line. But note that thanks to
<a
4731 href=
"https://bugs.debian.org/
741407">a race condition in
4732 vmdebootstrap
</a
>, the build might fail without the patch to the
4733 kpartx call.
</p
>
4735 <p
>If you instead want to install using a Debian CD and the preseed
4736 method, boot a Debian Wheezy ISO and use this boot argument to load
4737 the preseed values:
</p
>
4740 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4743 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4744 recently introduced bug in apt in Jessie
</a
>, the installer will
4745 currently hang while setting up APT sources. Killing the
4746 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4747 installation will get the installation going. This affect all
4748 installations in Jessie, and I expect it will be fixed soon.
</p
>
4750 <p
>Give it a go and let us know how it goes on the mailing list, and help
4751 us get the new release published. :) Please join us on
4752 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4753 irc.debian.org)
</a
> and
4754 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4755 mailing list
</a
> if you want to help make this vision come true.
</p
>
4760 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4761 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4763 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4764 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4765 innetgr tools, because I needed them in
4766 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4767 ng-utils, and it has served me well. I placed the project under the
4768 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4769 repository. But many years ago, the CVS repository was dropped (lost,
4770 not migrated to new hardware, not sure), and the project have lacked a
4771 proper home since then.
</p
>
4773 <p
>Last summer, I had a look at the package and made a new release
4774 fixing a irritating crash bug, but was unable to store the changes in
4775 a proper source control system. I applied for a project on
4776 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4777 to follow up on it. Until today. :)
</p
>
4779 <p
>After many hours of cleaning and migration, the ng-utils project
4780 now have a new home, and a git repository with the highlight of the
4781 history of the project. I published all release tarballs and imported
4782 them into the git repository. As the project is really stable and not
4783 expected to gain new features any time soon, I decided to make a new
4784 release and call it
1.0. Visit the new project home on
4785 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4786 if you want to check it out. The new version is also uploaded into
4787 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4792 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4793 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4795 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4796 <description><p
>A few days ago I decided to try to help the Hurd people to get
4797 their changes into sysvinit, to allow them to use the normal sysvinit
4798 boot system instead of their old one. This follow up on the
4799 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4800 Google Summer of Code work
</a
> done last summer by Justus Winter to
4801 get Debian on Hurd working more like Debian on Linux. To get started,
4802 I downloaded a prebuilt hard disk image from
4803 <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
>,
4804 and started it using virt-manager.
</p
>
4806 <p
>The first think I had to do after logging in (root without any
4807 password) was to get the network operational. I followed
4808 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4809 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4810 commands as root to get the machine to accept a IP address from the
4811 kvm internal DHCP server:
</p
>
4813 <p
><blockquote
><pre
>
4814 settrans -fgap /dev/netdde /hurd/netdde
4815 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4816 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4818 </pre
></blockquote
></p
>
4820 <p
>After this, the machine had internet connectivity, and I could
4821 upgrade it and install the sysvinit packages from experimental and
4822 enable it as the default boot system in Hurd.
</p
>
4824 <p
>But before I did that, I set a password on the root user, as ssh is
4825 running on the machine it for ssh login to work a password need to be
4826 set. Also, note that a bug somewhere in openssh on Hurd block
4827 compression from working. Remember to turn that off on the client
4830 <p
>Run these commands as root to upgrade and test the new sysvinit
4833 <p
><blockquote
><pre
>
4834 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4835 deb http://http.debian.net/debian/ experimental main
4838 apt-get dist-upgrade
4839 apt-get install -t experimental initscripts sysv-rc sysvinit \
4840 sysvinit-core sysvinit-utils
4841 update-alternatives --config runsystem
4842 </pre
></blockquote
></p
>
4844 <p
>To reboot after switching boot system, you have to use
4845 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4846 yet a sysvinit process able to receive the signals from the normal
4847 'reboot
' command. After switching to sysvinit as the boot system,
4848 upgrading every package and rebooting, the network come up with DHCP
4849 after boot as it should, and the settrans/pkill hack mentioned at the
4850 start is no longer needed. But for some strange reason, there are no
4851 longer any login prompt in the virtual console, so I logged in using
4854 <p
>Note that there are some race conditions in Hurd making the boot
4855 fail some times. No idea what the cause is, but hope the Hurd porters
4856 figure it out. At least Justus said on IRC (#debian-hurd on
4857 irc.debian.org) that they are aware of the problem. A way to reduce
4858 the impact is to upgrade to the Hurd packages built by Justus by
4859 adding this repository to the machine:
</p
>
4861 <p
><blockquote
><pre
>
4862 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4863 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4865 </pre
></blockquote
></p
>
4867 <p
>At the moment the prebuilt virtual machine get some packages from
4868 http://ftp.debian-ports.org/debian, because some of the packages in
4869 unstable do not yet include the required patches that are lingering in
4870 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4872 <p
><blockquote
><pre
>
4873 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4874 i emacs - GNU Emacs editor (metapackage)
4875 i gdb - GNU Debugger
4876 i hurd-recommended - Miscellaneous translators
4877 i isc-dhcp-client - ISC DHCP client
4878 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4879 i libc-bin - Embedded GNU C Library: Binaries
4880 i libc-dev-bin - Embedded GNU C Library: Development binaries
4881 i libc0.3 - Embedded GNU C Library: Shared libraries
4882 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4883 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4884 i multiarch-support - Transitional package to ensure multiarch compatibilit
4885 i A x11-common - X Window System (X.Org) infrastructure
4886 i xorg - X.Org X Window System
4887 i A xserver-xorg - X.Org X server
4888 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4890 </pre
></blockquote
></p
>
4892 <p
>All in all, testing hurd has been an interesting experience. :)
4893 X.org did not work out of the box and I never took the time to follow
4894 the porters instructions to fix it. This time I was interested in the
4895 command line stuff.
<p
>
4900 <title>New chrpath release
0.16</title>
4901 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4902 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4903 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4904 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4905 find problems in C, C++ and Java code using static source code
4906 analysis. It can detect a lot of different problems, and is very
4907 useful to find memory and locking bugs in the error handling part of
4908 the source. The company behind it provide
4909 <a href=
"https://scan.coverity.com/
">check of free software projects as
4910 a community service
</a
>, and many hundred free software projects are
4911 already checked. A few days ago I decided to have a closer look at
4912 the Coverity system, and discovered that the
4913 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4914 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4915 projects I am involved with was already registered. But these are
4916 fairly big, and I would also like to have a small and easy project to
4917 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4918 checking of the chrpath project
</a
>. It was
4919 added to the checker and discovered seven potential defects. Six of
4920 these were real, mostly resource
"leak
" when the program detected an
4921 error. Nothing serious, as the resources would be released a fraction
4922 of a second later when the program exited because of the error, but it
4923 is nice to do it right in case the source of the program some time in
4924 the future end up in a library. Having fixed all defects and added
4925 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4926 mailing list for the chrpath developers
</a
>, I decided it was time to
4927 publish a new release. These are the release notes:
</p
>
4929 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4933 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4934 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4935 <li
>Mention new project mailing list in the documentation.
</li
>
4940 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4941 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4942 project if something is wrong with the new release. The test suite
4943 did not discover any old errors, so if you find a new one, please also
4944 include a test suite check.
</p
>
4949 <title>New chrpath release
0.15</title>
4950 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4951 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4952 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4953 <description><p
>After many years break from the package and a vain hope that
4954 development would be continued by someone else, I finally pulled my
4955 acts together this morning and wrapped up a new release of chrpath,
4956 the command line tool to modify the rpath and runpath of already
4957 compiled ELF programs. The update was triggered by the persistence of
4958 Isha Vishnoi at IBM, which needed a new config.guess file to get
4959 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4960 is working on. I checked the
4961 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4962 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4963 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4964 packages for interesting patches (failed to find the source from
4965 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4966 These are the release notes:
</p
>
4968 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4972 <li
>Updated config.sub and config.guess from the GNU project to work
4973 with newer architectures. Thanks to isha vishnoi for the heads
4976 <li
>Updated README with current URLs.
</li
>
4978 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4979 Matthias Klose.
</li
>
4981 <li
>Added missing help for -k|--keepgoing option, using patch by
4982 Petr Machata found in Fedora.
</li
>
4984 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4985 .dynamic is a NULL terminated string. Based on patch found in
4986 Fedora credited Axel Thimm and Christian Krause.
</li
>
4991 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4992 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4993 project if something is wrong with the new release. The test suite
4994 did not discover any old errors, so if you find a new one, please also
4995 include a testsuite check.
</p
>
5000 <title>Debian init.d boot script example for rsyslog
</title>
5001 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5003 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5004 <description><p
>If one of the points of switching to a new init system in Debian is
5005 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5006 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5007 init.d scripts at all. Here is an example init.d script, ie a rewrite
5008 of /etc/init.d/rsyslog:
</p
>
5010 <p
><pre
>
5011 #!/lib/init/init-d-script
5014 # Required-Start: $remote_fs $time
5015 # Required-Stop: umountnfs $time
5016 # X-Stop-After: sendsigs
5017 # Default-Start:
2 3 4 5
5018 # Default-Stop:
0 1 6
5019 # Short-Description: enhanced syslogd
5020 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5021 # It is quite compatible to stock sysklogd and can be
5022 # used as a drop-in replacement.
5024 DESC=
"enhanced syslogd
"
5025 DAEMON=/usr/sbin/rsyslogd
5026 </pre
></p
>
5028 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
5029 script was
137 lines, and the above is just
15 lines, most of it meta
5030 info/comments.
</p
>
5032 <p
>How to do this, you ask? Well, one create a new script
5033 /lib/init/init-d-script looking something like this:
5035 <p
><pre
>
5038 # Define LSB log_* functions.
5039 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
5040 # and status_of_proc is working.
5041 . /lib/lsb/init-functions
5044 # Function that starts the daemon/service
5050 #
0 if daemon has been started
5051 #
1 if daemon was already running
5052 #
2 if daemon could not be started
5053 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
5055 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5058 # Add code here, if necessary, that waits for the process to be ready
5059 # to handle requests from services started subsequently which depend
5060 # on this one. As a last resort, sleep for some time.
5064 # Function that stops the daemon/service
5069 #
0 if daemon has been stopped
5070 #
1 if daemon was already stopped
5071 #
2 if daemon could not be stopped
5072 # other if a failure occurred
5073 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
5074 RETVAL=
"$?
"
5075 [
"$RETVAL
" =
2 ]
&& return
2
5076 # Wait for children to finish too if this is a daemon that forks
5077 # and if the daemon is only ever run from this initscript.
5078 # If the above conditions are not satisfied then add some other code
5079 # that waits for the process to drop all resources that could be
5080 # needed by services started subsequently. A last resort is to
5081 # sleep for some time.
5082 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
5083 [
"$?
" =
2 ]
&& return
2
5084 # Many daemons don
't delete their pidfiles when they exit.
5086 return
"$RETVAL
"
5090 # Function that sends a SIGHUP to the daemon/service
5094 # If the daemon can reload its configuration without
5095 # restarting (for example, when it is sent a SIGHUP),
5096 # then implement that here.
5098 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5103 scriptbasename=
"$(basename $
1)
"
5104 echo
"SN: $scriptbasename
"
5105 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5106 script=
"$
1"
5113 NAME=$(basename $DAEMON)
5114 PIDFILE=/var/run/$NAME.pid
5116 # Exit if the package is not installed
5117 #[ -x
"$DAEMON
" ] || exit
0
5119 # Read configuration variable file if it is present
5120 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5122 # Load the VERBOSE setting and other rcS variables
5125 case
"$
1" in
5127 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5129 case
"$?
" in
5130 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5131 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5135 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5137 case
"$?
" in
5138 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5139 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5143 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5145 #reload|force-reload)
5147 # If do_reload() is not implemented then leave this commented out
5148 # and leave
'force-reload
' as an alias for
'restart
'.
5150 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5154 restart|force-reload)
5156 # If the
"reload
" option is implemented then remove the
5157 #
'force-reload
' alias
5159 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5161 case
"$?
" in
5164 case
"$?
" in
5166 1) log_end_msg
1 ;; # Old process is still running
5167 *) log_end_msg
1 ;; # Failed to start
5177 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5183 </pre
></p
>
5185 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5186 lot. I did not really polish the approach, so it might not always
5187 work out of the box, but you get the idea. I did not try very hard to
5188 optimize it nor make it more robust either.
</p
>
5190 <p
>A better argument for switching init system in Debian than reducing
5191 the size of init scripts (which is a good thing to do anyway), is to
5192 get boot system that is able to handle the kernel events sensibly and
5193 robustly, and do not depend on the boot to run sequentially. The boot
5194 and the kernel have not behaved sequentially in years.
</p
>
5199 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5200 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5202 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5203 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5204 remote display access is the preferred solution with oVirt and RedHat
5205 Enterprise Virtualization, and I was sad to discover the other day
5206 that the browser plugin needed to use these systems seamlessly was
5207 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5208 for a package
</a
> was from
2012-
04-
10 with no progress since
5209 2013-
04-
01, so I decided to wrap up a package based on the great work
5210 from Cajus Pollmeier and put it in a collab-maint maintained git
5211 repository to get a package I could use. I would very much like
5212 others to help me maintain the package (or just take over, I do not
5213 mind), but as no-one had volunteered so far, I just uploaded it to
5214 NEW. I hope it will be available in Debian in a few days.
</p
>
5216 <p
>The source is now available from
5217 <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
>
5222 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5223 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5224 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5225 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5226 <description><p
>The
5227 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5228 program is a a very nice system to create virtual machine images. It
5229 create a image file, add a partition table, mount it and run
5230 debootstrap in the mounted directory to create a Debian system on a
5231 stick. Yesterday, I decided to try to teach it how to make images for
5232 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5233 of a plan to simplify the build system for
5234 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5235 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5236 the virtualbox images, but its current build system made multistrap
5237 based system for Dreamplug images, and it is lacking support for
5238 Raspberry Pi.
</p
>
5240 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5241 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5242 code and adjusted it to be able to build armel images on my amd64
5243 Debian laptop. I ended up giving vmdebootstrap five new options,
5244 allowing me to replicate the image creation process I use to make
5245 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5246 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5247 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5248 call debootstrap with --foreign and to copy the handler into the
5249 generated chroot before running the second stage. This allow
5250 vmdebootstrap to create armel images on an amd64 host. Next I added
5251 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5252 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5253 given file system type, allowing me to create an image with a vfat
5254 partition for the /boot/ stuff. I also added a
<tt
>--variant
5255 variant
</tt
> option to allow me to create smaller images without the
5256 Debian base system packages installed. Finally, I added an option
5257 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5258 as a boot loader. It is not needed on the Raspberry Pi and probably
5259 most other non-x86 architectures. The changes were accepted by the
5260 upstream author of vmdebootstrap yesterday and today, and is now
5262 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5263 upstream project page
</a
>.
</p
>
5265 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5266 create a small script (the customize script) to add the non-free
5267 binary blob needed to boot the Raspberry Pi and the APT source
5270 <p
><pre
>
5272 set -e # Exit on first error
5273 rootdir=
"$
1"
5274 cd
"$rootdir
"
5275 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5276 deb http://http.debian.net/debian/ jessie main contrib non-free
5278 # Install non-free binary blob needed to boot Raspberry Pi. This
5279 # install a kernel somewhere too.
5280 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5281 -O $rootdir/usr/bin/rpi-update
5282 chmod a+x $rootdir/usr/bin/rpi-update
5283 mkdir -p $rootdir/lib/modules
5284 touch $rootdir/boot/start.elf
5285 chroot $rootdir rpi-update
5286 </pre
></p
>
5288 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5289 to build the image:
</p
>
5292 sudo ./vmdebootstrap \
5295 --distribution jessie \
5296 --mirror http://http.debian.net/debian \
5305 --root-password raspberry \
5306 --hostname raspberrypi \
5307 --foreign /usr/bin/qemu-arm-static \
5308 --customize `pwd`/customize \
5310 --package git-core \
5311 --package binutils \
5312 --package ca-certificates \
5315 </pre
></p
>
5317 <p
>The list of packages being installed are the ones needed by
5318 rpi-update to make the image bootable on the Raspberry Pi, with the
5319 exception of netbase, which is needed by debootstrap to find
5320 /etc/hosts with the minbase variant. I really wish there was a way to
5321 set up an Raspberry Pi using only packages in the Debian archive, but
5322 that is not possible as far as I know, because it boots from the GPU
5323 using a non-free binary blob.
</p
>
5325 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5326 probably a few others installed. I have not checked the complete
5327 build dependency list.
</p
>
5329 <p
>The resulting image will not use the hardware floating point unit
5330 on the Raspberry PI, because the armel architecture in Debian is not
5331 optimized for that use. So the images created will be a bit slower
5332 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5337 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5338 <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>
5339 <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>
5340 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5341 <description><p
>The last few days I came across a few good causes that should get
5342 wider attention. I recommend signing and donating to each one of
5345 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5346 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5347 Women program which is a Google Summer of Code like initiative to get
5348 more women involved in free software. One debian sponsor has offered
5349 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5350 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5351 hope you will to. :)
</p
>
5353 <p
>And the Electronic Frontier Foundation just announced plans to
5354 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5355 documentaries about the excessive spying
</a
> on every Internet user that
5356 take place these days, and their need to fund the work. I
've already
5357 donated. Are you next?
</p
>
5359 <p
>For my Norwegian audience, the organisation Studentenes og
5360 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5361 statement under the heading
5362 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5363 Access
</a
> for those of us asking for more focus on open access in the
5364 Norwegian government. So far
499 signatures. I hope you will sign it
5370 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5371 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5372 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5373 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5374 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5375 project
</a
> have been going on for a while, and have presented the
5376 vision, ideas and solution several places. Here is a little
5377 collection of videos of talks and presentation of the project.
</p
>
5381 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5382 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5384 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5385 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5387 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5388 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5389 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5390 (Youtube)
</li
>
5392 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5393 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5395 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5396 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5398 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5399 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5400 York City in
2012</a
> (Youtube)
</li
>
5402 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5403 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5404 (Youtube)
</li
>
5406 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5407 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5409 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5410 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5412 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5413 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5414 2013</a
> (Youtube)
</li
>
5418 <p
>A larger list is available from
5419 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5420 Freedombox Wiki
</a
>.
</p
>
5422 <p
>On other news, I am happy to report that Freedombox based on Debian
5423 Jessie is coming along quite well, and soon both Owncloud and using
5424 Tor should be available for testers of the Freedombox solution. :) In
5425 a few weeks I hope everything needed to test it is included in Debian.
5426 The withsqlite package is already in Debian, and the plinth package is
5427 pending in NEW. The third and vital part of that puzzle is the
5428 metapackage/setup framework, which is still pending an upload. Join
5429 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5430 (#freedombox on irc.debian.org)
</a
> and
5431 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5432 mailing list
</a
> if you want to help make this vision come true.
</p
>
5437 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5438 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5440 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5441 <description><p
>I was introduced to the
5442 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5443 in
2010, when Eben Moglen presented his vision about serving the need
5444 of non-technical people to keep their personal information private and
5445 within the legal protection of their own homes. The idea is to give
5446 people back the power over their network and machines, and return
5447 Internet back to its intended peer-to-peer architecture. Instead of
5448 depending on a central service, the Freedombox will give everyone
5449 control over their own basic infrastructure.
</p
>
5451 <p
>I
've intended to join the effort since then, but other tasks have
5452 taken priority. But this summers nasty news about the misuse of trust
5453 and privilege exercised by the
"western
" intelligence gathering
5454 communities increased my eagerness to contribute to a point where I
5455 actually started working on the project a while back.
</p
>
5457 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5458 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5459 create a simple and cheap Debian based appliance that anyone can hook
5460 up in their home and get access to secure and private services and
5461 communication. The initial deployment platform have been the
5462 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5463 which is a piece of hardware I do not own. So to be able to test what
5464 the current Freedombox setup look like, I had to come up with a way to install
5465 it on some hardware I do have access to. I have rewritten the
5466 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5467 image build framework to use .deb packages instead of only copying
5468 setup into the boot images, and thanks to this rewrite I am able to
5469 set up any machine supported by Debian Wheezy as a Freedombox, using
5470 the previously mentioned deb (and a few support debs for packages
5471 missing in Debian).
</p
>
5473 <p
>The current Freedombox setup consist of a set of bootstrapping
5475 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5476 and a administrative web interface
5477 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5478 withsqlite), as well as a privacy enhancing proxy based on
5479 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5480 (freedombox-privoxy). There is also a web/javascript based XMPP
5481 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5482 trying (unsuccessfully so far) to talk to the XMPP server
5483 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5484 web interface is pluggable, and the goal is to use it to enable OpenID
5485 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5486 this is really working yet, see
5487 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5488 project TODO
</a
> for links to GIT repositories. Most of the code is
5489 on github at the moment. The HTTP proxy is operational out of the
5490 box, and the admin web interface can be used to add/remove plinth
5491 users. I
've not been able to do anything else with it so far, but
5492 know there are several branches spread around github and other places
5493 with lots of half baked features.
</p
>
5495 <p
>Anyway, if you want to have a look at the current state, the
5496 following recipes should work to give you a test machine to poke
5499 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5503 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5504 <li
>Boot from it, either as CD or USB stick.
</li
>
5505 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5506 to the Debian installer:
<p
>
5507 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5509 <li
>Answer the few language/region/password questions and pick disk to
5510 install on.
</li
>
5512 <li
>When the installation is finished and the machine have rebooted a
5513 few times, your Freedombox is ready for testing.
</li
>
5517 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5521 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5522 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5523 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5525 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5526 </pre
></li
>
5527 <li
><p
>Run this as root:
</p
>
5529 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5532 apt-get install freedombox-setup
5533 /usr/lib/freedombox/setup
5534 </pre
></li
>
5535 <li
>Reboot into your freshly created Freedombox.
</li
>
5539 <p
>You can test it on other architectures too, but because the
5540 freedombox-privoxy package is binary, it will only work as intended on
5541 the architectures where I have had time to build the binary and put it
5542 in my APT repository. But do not let this stop you. It is only a
5543 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5545 <p
>Note that by default Freedombox is a DHCP server on the
5546 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5547 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5548 disable
</tt
>" as root.
</p
>
5550 <p
>Please let me know if this works for you, or if you have any
5551 problems. We gather on the IRC channel
5552 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5553 irc.debian.org and the
5554 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5555 mailing list
</a
>.
</p
>
5557 <p
>Once you get your freedombox operational, you can visit
5558 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5559 welcome screen (dead end - do not be surprised if you are unable to
5560 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5561 to look at the rest of plinth. The default user is
'admin
' and the
5562 default password is
'secret
'.
</p
>
5567 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5568 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5569 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5570 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5571 <description><p
>Earlier, I reported about
5572 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5573 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5574 told by IBM that the original disk should be thrown away. And as
5575 there no longer was a problem if I bricked the firmware, I decided
5576 today to try to install Intel firmware to replace the Lenovo firmware
5577 currently on the disk.
</p
>
5579 <p
>I searched the Intel site for firmware, and found
5580 <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
>
5581 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5582 according to the site should contain the latest firmware for SSD
5583 disks. I inserted the broken disk in one of my spare laptops and
5584 booted the ISO from a USB stick. The disk was recognized, but the
5585 program claimed the newest firmware already were installed and refused
5586 to insert any Intel firmware. So no change, and the disk is still
5587 unable to handle write load. :( I guess the only way to get them
5588 working would be if Lenovo releases new firmware. No idea how likely
5589 that is. Anyway, just blogging about this test for completeness. I
5590 got a working Samsung disk, and see no point in spending more time on
5591 the broken disks.
</p
>
5596 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5597 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5599 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5600 <description><p
>Today I switched to
5601 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5602 new laptop
</a
>. I
've previously written about the problems I had with
5603 my new Thinkpad X230, which was delivered with an
5604 <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
5605 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5606 sustained writes. My hardware supplier have been very forthcoming in
5607 trying to find a solution, and after first trying with another
5608 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5609 disk instead to fix it once and for all. The Samsung disk survived
5610 the installation of Debian with encrypted disks (filling the disk with
5611 random data during installation killed the first two), and I thus
5612 decided to trust it with my data. I have installed it as a Debian Edu
5613 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5614 server at home using Kerberos and LDAP, and will use it as my work
5615 station from now on.
</p
>
5617 <p
>As this is a solid state disk with no moving parts, I believe the
5618 Debian Wheezy default installation need to be tuned a bit to increase
5619 performance and increase life time of the disk. The Linux kernel and
5620 user space applications do not yet adjust automatically to such
5621 environment. To make it easier for my self, I created a draft Debian
5622 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5623 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5624 for the ssd-setup package
</a
> is available from collab-maint, and it
5625 is set up to adjust the setup of the machine by just installing the
5626 package. If there is any non-SSD disk in the machine, the package
5627 will refuse to install, as I did not try to write any logic to sort
5628 file systems in SSD and non-SSD file systems.
</p
>
5630 <p
>I consider the package a draft, as I am a bit unsure how to best
5631 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5632 where I set up the machine with one large encrypted partition (in
5633 addition to /boot), put LVM on top of this and set up partitions on
5634 top of this again. See the README file in the package source for the
5635 references I used to pick the settings. At the moment these
5636 parameters are tuned:
</p
>
5640 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5641 (adding discard to /etc/crypttab)
</li
>
5643 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5644 this case a cryptsetup partition) by changing issue_discards from
5645 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5647 <li
>Set relatime as a file system option for ext3 and ext4 file
5650 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5651 /etc/fstab.
</li
>
5653 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5655 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5656 cron.daily).
</li
>
5658 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5659 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5663 <p
>During installation, I cancelled the part where the installer fill
5664 the disk with random data, as this would kill the SSD performance for
5665 little gain. My goal with the encrypted file system is to ensure
5666 those stealing my laptop end up with a brick and not a working
5667 computer. I have no hope in keeping the really resourceful people
5668 from getting the data on the disk (see
5669 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5670 Thus I concluded that adding the discard option to crypttab is the
5671 right thing to do.
</p
>
5673 <p
>I considered using the noop I/O scheduler, as several recommended
5674 it for SSD, but others recommended deadline and a benchmark I found
5675 indicated that deadline might be better for interactive use.
</p
>
5677 <p
>I also considered using the
'discard
' file system option for ext3
5678 and ext4, but read that it would give a performance hit ever time a
5679 file is removed, and thought it best to that that slowdown once a day
5680 instead of during my work.
</p
>
5682 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5683 this is already done by Debian Edu.
</p
>
5685 <p
>I have not yet started on the user space tuning. I expect
5686 iceweasel need some tuning, and perhaps other applications too, but
5687 have not yet had time to investigate those parts.
</p
>
5689 <p
>The package should work on Ubuntu too, but I have not yet tested it
5692 <p
>As for the answer to the question in the title of this blog post,
5693 as far as I know, the only solution I know about is to replace the
5694 disk. It might be possible to flash it with Intel firmware instead of
5695 the Lenovo firmware. But I have not tried and did not want to do so
5696 without approval from Lenovo as I wanted to keep the warranty on the
5697 disk until a solution was found and they wanted the broken disks
5703 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5704 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5705 <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>
5706 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5707 <description><p
>A few days ago, I wrote about
5708 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5709 problems I experienced with my new X230 and its SSD disk
</a
>, which
5710 was dying during installation because it is unable to cope with
5711 sustained write. My supplier is in contact with
5712 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5713 replacement disk to try to fix the problem. They decided to send an
5714 identical model, so my hopes for a permanent fix was slim.
</p
>
5716 <p
>Anyway, today I got the replacement disk and tried to install
5717 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5718 same firmware version as the original. This time my hope raised
5719 slightly as the installation progressed, as the original disk used to
5720 die after
4-
7% of the disk was written to, while this time it kept
5721 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5722 died again and I was back on square one. I still do not have a new
5723 laptop with a disk I can trust. I can not live with a disk that might
5724 lock up when I download a new
5725 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5726 other large files. I look forward to hearing from my supplier with
5727 the next proposal from Lenovo.
</p
>
5729 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5730 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5731 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5732 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5733 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5734 P/N
45N8295, P0C38732.
</p
>
5736 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5737 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5738 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5739 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5740 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5741 P/N
45N8295, P0C38732.
</p
>
5743 <p
>The only difference is in the first number (serial number?), ISN,
5744 SA, date and WNPP values. Mentioning all the details here in case
5745 someone is able to use the information to find a way to identify the
5746 failing disk among working ones (if any such working disk actually
5752 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5753 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5754 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5755 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5756 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5757 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5758 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5759 member assosiation NUUG
</a
> and
5760 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5761 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5762 Bitraf
</a
>.
</p
>
5764 <p
>It starts
10:
00 and continue until late evening. Everyone is
5765 welcome, and there is no fee to participate. There is on the other
5766 hand limited space, and only room for
30 people. Please put your name
5767 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5768 wiki page
</a
> if you plan to join us.
</p
>
5773 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5774 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5775 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5776 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5777 <description><p
>Half a year ago, I reported that I had to find a
5778 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5779 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5780 time to spend on it, and it took a while to find a model I believe
5781 will do the job, but two days ago the replacement finally arrived. I
5783 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5784 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5785 a roaming workstation, and it seemed to work flawlessly. But my
5786 second installation with encrypted disk was not as successful. More
5787 on that below.
</p
>
5789 <p
>I had a hard time trying to track down a good laptop, as my most
5790 important requirements (robust and with a good keyboard) are never
5791 listed in the feature list. But I did get good help from the search
5792 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5793 allowed me to limit the list of interesting laptops based on my other
5794 requirements. A bit surprising that SSD disk are not disks according
5795 to that search interface, so I had to drop specifying the number of
5796 disks from my search parameters. I also asked around among friends to
5797 get their impression on keyboards and robustness.
</p
>
5799 <p
>So the new laptop arrived, and it is quite a lot wider than the
5800 X41. I am not quite convinced about the keyboard, as it is
5801 significantly wider than my old keyboard, and I have to stretch my
5802 hand a lot more to reach the edges. But the key response is fairly
5803 good and the individual key shape is fairly easy to handle, so I hope
5804 I will get used to it. My old X40 was starting to fail, and I really
5805 needed a new laptop now. :)
</p
>
5807 <p
>Turning off the touch pad was simple. All it took was a quick
5808 visit to the BIOS during boot it disable it.
</p
>
5810 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5811 lock up during load. And this happen when installing Debian Wheezy
5812 with encrypted disk, while the disk is being filled with random data.
5813 I also tested to install Ubuntu Raring, and it happen there too if I
5814 reenable the code to fill the disk with random data (it is disabled by
5815 default in Ubuntu). And the bug with is already known. It was
5816 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5817 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5818 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5819 kernel developers as
5820 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5821 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5822 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5823 Lenovo forums, both for
5824 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5825 2012-
11-
10</a
> and for
5826 <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
5827 03-
20-
2013</a
>. The problem do not only affect installation. The
5828 reports state that the disk lock up during use if many writes are done
5829 on the disk, so it is much no use to work around the installation
5830 problem and end up with a computer that can lock up at any moment.
5832 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5833 available
</a
> that will lock up the hard drive after running a few
5834 minutes by writing to a file.
</p
>
5836 <p
>I
've contacted my supplier and asked how to handle this, and after
5837 contacting PCHELP Norway (request
01D1FDP) which handle support
5838 requests for Lenovo, his first suggestion was to upgrade the disk
5839 firmware. Unfortunately there is no newer firmware available from
5840 Lenovo, as my disk already have the most recent one (version LF1i). I
5841 hope to hear more from him today and hope the problem can be
5847 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5848 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5849 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5850 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5851 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5852 trusty old Thinkpad X41. Unfortunately I did not have much time to
5853 spend on it, but today the replacement finally arrived. I ended up
5854 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5855 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5856 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5857 this, it is installing what I hope will be a more final installation,
5858 with a encrypted hard drive to ensure any dope head stealing it end up
5859 with an expencive door stop.
</p
>
5861 <p
>I had a hard time trying to track down a good laptop, as my most
5862 important requirements (robust and with a good keyboard) are never
5863 listed in the feature list. But I did get good help from the search
5864 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5865 allowed me to limit the list of interesting laptops based on my other
5866 requirements. A bit surprising that SSD disk are not disks, so I had
5867 to drop number of disks from my search parameters.
</p
>
5869 <p
>I am not quite convinced about the keyboard, as it is significantly
5870 wider than my old keyboard, and I have to stretch my hand a lot more
5871 to reach the edges. But the key response is fairly good and the
5872 individual key shape is fairly easy to handle, so I hope I will get
5873 used to it. My old X40 was starting to fail, and I really needed a
5874 new laptop now. :)
</p
>
5876 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5881 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5882 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5883 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5884 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5885 <description><p
>It annoys me when the computer fail to do automatically what it is
5886 perfectly capable of, and I have to do it manually to get things
5887 working. One such task is to find out what firmware packages are
5888 needed to get the hardware on my computer working. Most often this
5889 affect the wifi card, but some times it even affect the RAID
5890 controller or the ethernet card. Today I pushed version
0.4 of the
5891 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5892 including a new script isenkram-autoinstall-firmware handling the
5893 process of asking all the loaded kernel modules what firmware files
5894 they want, find debian packages providing these files and install the
5895 debian packages. Here is a test run on my laptop:
</p
>
5897 <p
><pre
>
5898 # isenkram-autoinstall-firmware
5899 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5900 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5901 info: locating packages with the requested firmware files
5902 info: Updating APT sources after adding non-free APT source
5903 info: trying to install firmware-ipw2x00
5906 Preconfiguring packages ...
5907 Selecting previously deselected package firmware-ipw2x00.
5908 (Reading database ...
259727 files and directories currently installed.)
5909 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5910 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5912 </pre
></p
>
5914 <p
>When all the requested firmware is present, a simple message is
5915 printed instead:
</p
>
5917 <p
><pre
>
5918 # isenkram-autoinstall-firmware
5919 info: did not find any firmware files requested by loaded kernel modules. exiting
5921 </pre
></p
>
5923 <p
>It could use some polish, but it is already working well and saving
5924 me some time when setting up new machines. :)
</p
>
5926 <p
>So, how does it work? It look at the set of currently loaded
5927 kernel modules, and look up each one of them using modinfo, to find
5928 the firmware files listed in the module meta-information. Next, it
5929 download the Contents file from a nearby APT mirror, and search for
5930 the firmware files in this file to locate the package with the
5931 requested firmware file. If the package is in the non-free section, a
5932 non-free APT source is added and the package is installed using
5933 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5936 <p
>I hope someone find time to implement a more polished version of
5937 this script as part of the hw-detect debian-installer module, to
5938 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5939 #
655507</a
>. There really is no need to insert USB sticks with
5940 firmware during a PXE install when the packages already are available
5941 from the nearby Debian mirror.
</p
>
5946 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5947 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5949 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5950 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5951 the screen just turn black when Linux boot, either during installation
5952 or on first boot from the hard disk. I
've seen it once in a while the
5953 last few years, but only recently understood the cause. I
've seen it
5954 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5955 The reason seem to be in the wiring of some laptops. The system to
5956 control the screen background light is inverted, so when Linux try to
5957 turn the brightness fully on, it end up turning it off instead. I do
5958 not know which Linux drivers are affected, but this post is about the
5959 i915 driver used by the
5960 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5961 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5963 <p
>The problem can be worked around two ways. Either by adding
5964 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5965 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5966 option when it load the i915 kernel module. On Debian and Ubuntu, it
5967 can be done by running these commands as root:
</p
>
5970 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5971 update-initramfs -u -k all
5974 <p
>Since March
2012 there is
5975 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5976 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5977 hardware have this problem, and get the driver to invert the
5978 brightness setting automatically. To use it, one need to add a row in
5979 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5980 intel_quirks array
</a
> in the driver source
5981 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5982 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5983 number (vendor number
8086 is assumed) and subdevice vendor and device
5986 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5987 -vvnn
</tt
> for the video card in question:
</p
>
5989 <p
><pre
>
5990 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5991 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5992 (rev
09) (prog-if
00 [VGA controller])
5993 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5994 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5995 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5996 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5997 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5999 Interrupt: pin A routed to IRQ
42
6000 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6001 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6002 Region
4: I/O ports at
4000 [size=
64]
6003 Expansion ROM at
<unassigned
> [disabled]
6004 Capabilities:
<access denied
>
6005 Kernel driver in use: i915
6006 </pre
></p
>
6008 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6010 <p
><pre
>
6011 struct intel_quirk intel_quirks[] = {
6013 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6014 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6017 </pre
></p
>
6019 <p
>According to the kernel module instructions (as seen using
6020 <tt
>modinfo i915
</tt
>), information about hardware needing the
6021 invert_brightness flag should be sent to the
6022 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
6023 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
6024 developers. But my email about the laptop sent
2013-
06-
03 have not
6026 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
6027 web archive for the mailing list
</a
>, so I suspect they do not accept
6028 emails from non-subscribers. Because of this, I sent my patch also to
6029 the Debian bug tracking system instead as
6030 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
6031 sure the patch is not lost.
</p
>
6033 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
6034 with this problem working properly with Linux. If you use Gnome, your
6035 worries should be over at this point. But if you use KDE, there is
6036 something in KDE ignoring the invert_brightness setting and turning on
6037 the screen during login. I
've reported it to Debian as
6038 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
6039 have no idea yet how to figure out exactly what subsystem is doing
6040 this. Perhaps you can help? Perhaps you know what the Gnome
6041 developers did to handle this, and this can give a clue to the KDE
6042 developers? Or you know where in KDE the screen brightness is changed
6043 during login? If so, please update the BTS report (or get in touch if
6044 you do not know how to update BTS).
</p
>
6046 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
6047 acpi_backlight=vendor, to disable ACPI backlight support completely,
6048 as the ACPI information on the machine is trash and it is better to
6049 leave it to the intel video driver to control the screen
6050 backlight.
</p
>
6055 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
6056 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
6057 <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>
6058 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
6059 <description><p
>Two days ago, I asked
6060 <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
6061 I could install Linux on a Packard Bell EasyNote LV computer
6062 preinstalled with Windows
8</a
>. I found a solution, but am horrified
6063 with the obstacles put in the way of Linux users on a laptop with UEFI
6064 and Windows
8.
</p
>
6066 <p
>I never found out if the cause of my problems were the use of UEFI
6067 secure booting or fast boot. I suspect fast boot was the problem,
6068 causing the firmware to boot directly from HD without considering any
6069 key presses and alternative devices, but do not know UEFI settings
6070 enough to tell.
</p
>
6072 <p
>There is no way to install Linux on the machine in question without
6073 opening the box and disconnecting the hard drive! This is as far as I
6074 can tell, the only way to get access to the firmware setup menu
6075 without accepting the Windows
8 license agreement. I am told (and
6076 found description on how to) that it is possible to configure the
6077 firmware setup once booted into Windows
8. But as I believe the terms
6078 of that agreement are completely unacceptable, accepting the license
6079 was never an alternative. I do not enter agreements I do not intend
6080 to follow.
</p
>
6082 <p
>I feared I had to return the laptops and ask for a refund, and
6083 waste many hours on this, but luckily there was a way to get it to
6084 work. But I would not recommend it to anyone planning to run Linux on
6085 it, and I have become sceptical to Windows
8 certified laptops. Is
6086 this the way Linux will be forced out of the market place, by making
6087 it close to impossible for
"normal
" users to install Linux without
6088 accepting the Microsoft Windows license terms? Or at least not
6089 without risking to loose the warranty?
</p
>
6091 <p
>I
've updated the
6092 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
6093 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
6094 do not have to struggle as much as I did to get Linux into the
6097 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6098 Michael Tokarev and others for feedback and ideas.
</p
>
6103 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6104 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6105 <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>
6106 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6107 <description><p
>I
've run into quite a problem the last few days. I bought three
6108 new laptops for my parents and a few others. I bought Packard Bell
6109 Easynote LV to run Kubuntu on and use as their home computer. But I
6110 am completely unable to figure out how to install Linux on it. The
6111 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6112 instead of a BIOS to boot.
</p
>
6114 <p
>The problem is that I am unable to get it to PXE boot, and unable
6115 to get it to boot the Linux installer from my USB stick. I have yet
6116 to try the DVD install, and still hope it will work. when I turn on
6117 the computer, there is no information on what buttons to press to get
6118 the normal boot menu. I expect to get some boot menu to select PXE or
6119 USB stick booting. When booting, it first ask for the language to
6120 use, then for some regional settings, and finally if I will accept the
6121 Windows
8 terms of use. As these terms are completely unacceptable to
6122 me, I have no other choice but to turn off the computer and try again
6123 to get it to boot the Linux installer.
</p
>
6125 <p
>I have gathered my findings so far on a Linlap page about the
6126 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6127 EasyNote LV
</a
> model. If you have any idea how to get Linux
6128 installed on this machine, please get in touch or update that wiki
6129 page. If I can
't find a way to install Linux, I will have to return
6130 the laptop to the seller and find another machine for my parents.
</p
>
6132 <p
>I wonder, is this the way Linux will be forced out of the market
6133 using UEFI and
"secure boot
" by making it impossible to install Linux
6134 on new Laptops?
</p
>
6139 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6140 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6141 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6142 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6143 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6144 an operating system based on Debian intended for use in schools. It
6145 contain a turn-key solution for the computer network provided to
6146 pupils in the primary schools. It provide both the central server,
6147 network boot servers and desktop environments with heaps of
6148 educational software. The project was founded almost
12 years ago,
6149 2001-
07-
02. If you want to support the project, which is in need for
6150 cash to fund developer gatherings and other project related activity,
6151 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6152 donate some money
</a
>.
6154 <p
>A topic that come up again and again on the Debian Edu mailing
6155 lists and elsewhere, is the question on how to transform a Debian or
6156 Ubuntu installation into a Debian Edu installation. It isn
't very
6157 hard, and last week I wrote a script to replicate the steps done by
6158 the Debian Edu installer.
</p
>
6160 <p
>The script,
6161 <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/
>
6162 in the debian-edu-config package, will go through these six steps and
6163 transform an existing Debian Wheezy or Ubuntu (untested) installation
6164 into a Debian Edu Workstation:
</p
>
6168 <li
>Add skolelinux related APT sources.
</li
>
6169 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6170 <li
>Install debian-edu-install to load preseeding values and pull in
6171 our configuration.
</li
>
6172 <li
>Preseed debconf database with profile setup in
6173 /etc/debian-edu/config, and run tasksel to install packages
6174 according to the profile specified in the config above,
6175 overriding some of the Debian automation machinery.
</li
>
6176 <li
>Run debian-edu-cfengine-D installation to configure everything
6177 that could not be done using preseeding.
</li
>
6178 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6182 <p
>There are some steps in the Debian Edu installation that can not be
6183 replicated like this. Disk partitioning and LVM setup, for example.
6184 So this script just assume there is enough disk space to install all
6185 the needed packages.
</p
>
6187 <p
>The script was created to help a Debian Edu student working on
6188 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6189 Debian Edu client, and using it he can take the existing
6190 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6191 transform it into a fully functioning Debian Edu Workstation (or
6192 Roaming Workstation, or whatever :).
</p
>
6194 <p
>The default setting in the script is to create a KDE Workstation.
6195 If a LXDE based Roaming workstation is wanted instead, modify the
6196 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6198 <p
><pre
>
6199 PROFILE=
"Roaming-Workstation
"
6200 DESKTOP=
"lxde
"
6201 </pre
></p
>
6203 <p
>The script could even become useful to set up Debian Edu servers in
6204 the cloud, by starting with a virtual Debian installation at some
6205 virtual hosting service and setting up all the services on first
6211 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6212 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6214 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6215 <description><P
>In January,
6216 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6217 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6218 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6219 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6220 marvellous construction system from Denmark. We also created
6221 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6222 a place to take notes and write down our plans and hopes. And several
6223 people showed up to help. I was very happy to see the effect of my
6224 call. Since the small start, we have a debtags tag
6225 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6226 tag for LEGO related packages, and now count
10 packages related to
6227 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6229 <p
><table
>
6230 <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
>
6231 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6232 <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
>
6233 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6234 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6235 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6236 <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
>
6237 <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
>
6238 <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
>
6239 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6240 </table
></p
>
6242 <p
>Some of these are available in Wheezy, and all but one are
6243 currently available in Jessie/testing. leocad is so far only
6244 available in experimental.
</p
>
6246 <p
>If you care about LEGO in Debian, please join us on IRC and help
6247 adding the rest of the great free software tools available on Linux
6248 for LEGO designers.
</p
>
6253 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6254 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6256 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6257 <description><p
>When I woke up this morning, I was very happy to see that the
6258 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6259 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6260 Debian release, and I expect to move my machines at home over to it fairly
6263 <p
>The new debian release contain heaps of new stuff, and one program
6264 in particular make me very happy to see included. The
6265 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6266 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6267 included for the first time. Alongside similar programs like
6268 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6269 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6270 it allow for visual programming where syntax errors can not happen,
6271 and a friendly programming environment for learning to control the
6272 computer. Scratch will also be included in the next release of Debian
6275 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6276 Edu/Skolelinux release too. The
6277 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6278 alpha release
</a
> went out last week, and the next should soon
6284 <title>Isenkram
0.2 finally in the Debian archive
</title>
6285 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6286 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6287 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6288 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6289 package
</a
> finally made it into the archive, after lingering in NEW
6290 for many months. I uploaded it to the Debian experimental suite
6291 2013-
01-
27, and today it was accepted into the archive.
</p
>
6293 <p
>Isenkram is a system for suggesting to users what packages to
6294 install to work with a pluggable hardware device. The suggestion pop
6295 up when the device is plugged in. For example if a Lego Mindstorm NXT
6296 is inserted, it will suggest to install the program needed to program
6297 the NXT controller. Give it a go, and report bugs and suggestions to
6303 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6304 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6305 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6306 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6307 <description><p
>My
6308 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6309 bitcoin related blog post
</a
> mentioned that the new
6310 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6311 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6312 2013-
01-
19, and have been available in unstable since then. It was
6313 automatically copied to Ubuntu, and is available in their Raring
6314 version too.
</p
>
6316 <p
>But there is a strange problem with the build that block this new
6317 version from being available on the i386 and kfreebsd-i386
6318 architectures. For some strange reason, the autobuilders in Debian
6319 for these architectures fail to run the test suite on these
6320 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6321 We are so far unable to reproduce it when building it manually, and
6322 no-one have been able to propose a fix. If you got an idea what is
6323 failing, please let us know via the BTS.
</p
>
6325 <p
>One feature that is annoying me with of the bitcoin client, because
6326 I often run low on disk space, is the fact that the client will exit
6327 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6328 #
696715</a
>). So make sure you have enough disk space when you run
6331 <p
>As usual, if you use bitcoin and want to show your support of my
6332 activities, please send Bitcoin donations to my address
6333 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6338 <title>Welcome to the world, Isenkram!
</title>
6339 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6341 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6342 <description><p
>Yesterday, I
6343 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6344 for testers
</a
> for my prototype for making Debian better at handling
6345 pluggable hardware devices, which I
6346 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6347 out to create
</a
> earlier this month. Several valuable testers showed
6348 up, and caused me to really want to to open up the development to more
6349 people. But before I did this, I want to come up with a sensible name
6350 for this project. Today I finally decided on a new name, and I have
6351 renamed the project from hw-support-handler to this new name. In the
6352 process, I moved the source to git and made it available as a
6353 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6354 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6355 To fetch and build the latest version of the source, use
</p
>
6358 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6359 cd isenkram
&& git-buildpackage -us -uc
6362 <p
>I have not yet adjusted all files to use the new name yet. If you
6363 want to hack on the source or improve the package, please go ahead.
6364 But please talk to me first on IRC or via email before you do major
6365 changes, to make sure we do not step on each others toes. :)
</p
>
6367 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6368 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6369 stuff, in other words. I
've been told it is the Norwegian variant of
6370 the German word eisenkram, for those that are familiar with that
6373 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6374 instructions, to avoid confusing people with an error from the signing
6377 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6378 clone argument to avoid the need for authentication.
</p
>
6383 <title>First prototype ready making hardware easier to use in Debian
</title>
6384 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6386 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6387 <description><p
>Early this month I set out to try to
6388 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6389 the Debian support for pluggable hardware devices
</a
>. Now my
6390 prototype is working, and it is ready for a larger audience. To test
6392 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6393 from the Debian Edu subversion repository
</a
>, build and install the
6394 package. You might have to log out and in again activate the
6395 autostart script.
</p
>
6397 <p
>The design is simple:
</p
>
6401 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6402 hw-support-handlerd to start when the user log in.
</li
>
6404 <li
>This program listen for kernel events about new hardware (directly
6405 from the kernel like udev does), not using HAL dbus events as I
6406 initially did.
</li
>
6408 <li
>When new hardware is inserted, look up the hardware modalias in
6409 the APT database, a database
6410 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6411 via HTTP
</a
> and a database available as part of the package.
</li
>
6413 <li
>If a package is mapped to the hardware in question, the package
6414 isn
't installed yet and this is the first time the hardware was
6415 plugged in, show a desktop notification suggesting to install the
6416 package or packages.
</li
>
6418 <li
>If the user click on the
'install package now
' button, ask
6419 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6421 <li
>aptdaemon ask for root password or sudo password, and install the
6422 package while showing progress information in a window.
</li
>
6426 <p
>I still need to come up with a better name for the system. Here
6427 are some screen shots showing the prototype in action. First the
6428 notification, then the password request, and finally the request to
6429 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6431 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6432 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6433 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6434 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6435 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6437 <p
>The prototype still need to be improved with longer timeouts, but
6438 is already useful. The database of hardware to package mappings also
6439 need more work. It is currently compatible with the Ubuntu way of
6440 storing such information in the package control file, but could be
6441 changed to use other formats instead or in addition to the current
6442 method. I
've dropped the use of discover for this mapping, as the
6443 modalias approach is more flexible and easier to use on Linux as long
6444 as the Linux kernel expose its modalias strings directly.
</p
>
6446 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6447 here is the command required to check out and build the source: Use
6448 '<tt
>svn checkout
6449 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6450 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6451 devscripts package.
</p
>
6453 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6454 renamed to Isenkram and the source moved from the Debian Edu
6455 subversion repository to a Debian collab-maint git repository. See
6456 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6457 instructions
</a
> for details.
</p
>
6462 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6463 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6464 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6465 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6466 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6467 suddenly in bed. With a quiet whimper, it went completely quiet and
6468 black. The power button was no longer able to turn it on. It was a
6469 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6470 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6471 Compaq I had before that. Now I need to find a replacement. To keep
6472 going during Christmas, I moved the one year old SSD disk to my old
6473 X40 where it fitted (only one I had left that could use it), but it is
6474 not a durable solution.
6476 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6477 got a new one more than
10 years ago. It still holds true.:)
</p
>
6481 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6482 than A4).
</li
>
6483 <li
>Robust, it will be in my backpack every day.
</li
>
6484 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6485 <li
>Long battery life time. Preferable a week.
</li
>
6486 <li
>Internal WIFI network card.
</li
>
6487 <li
>Internal Twisted Pair network card.
</li
>
6488 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6489 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6490 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6492 <li
>Hardware supported by Debian Stable, ie the default kernel and
6493 X.org packages.
</li
>
6494 <li
>Quiet, preferably fan free (or at least not using the fan most of
6499 <p
>You will notice that there are no RAM and CPU requirements in the
6500 list. The reason is simply that the specifications on laptops the
6501 last
10-
15 years have been sufficient for my needs, and I have to look
6502 at other features to choose my laptop. But are there still made as
6503 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6504 robust, and Thinkpads seem to be heading in the wrong direction since
6505 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6506 still be useful.
</p
>
6508 <p
>Perhaps I should rethink my needs, and look for a pad with an
6509 external keyboard? I
'll have to check the
6510 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6511 well-supported laptops, or perhaps just buy one preinstalled from one
6512 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6513 Pre-loaded site
</a
>.
</p
>
6518 <title>How to find a browser plugin supporting a given MIME type
</title>
6519 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6520 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6521 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6522 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6523 install to get support for a given MIME type. Thanks to
6524 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6525 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6526 Unfortunately, not very many packages provide the needed meta
6527 information, Anyway, here is a small script to look up all browser
6528 plugin packages announcing ther MIME support using this specification:
</p
>
6534 def pkgs_handling_mimetype(mimetype):
6539 version = pkg.candidate
6541 version = pkg.installed
6544 record = version.record
6545 if not record.has_key(
'Npp-MimeType
'):
6547 mime_types = record[
'Npp-MimeType
'].split(
',
')
6548 for t in mime_types:
6549 t = t.rstrip().strip()
6551 thepkgs.append(pkg.name)
6553 mimetype =
"audio/ogg
"
6554 if
1 < len(sys.argv):
6555 mimetype = sys.argv[
1]
6556 print
"Browser plugin packages supporting %s:
" % mimetype
6557 for pkg in pkgs_handling_mimetype(mimetype):
6558 print
" %s
" %pkg
6561 <p
>It can be used like this to look up a given MIME type:
</p
>
6564 % ./apt-find-browserplug-for-mimetype
6565 Browser plugin packages supporting audio/ogg:
6567 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6568 Browser plugin packages supporting application/x-shockwave-flash:
6569 browser-plugin-gnash
6573 <p
>In Ubuntu this mechanism is combined with support in the browser
6574 itself to query for plugins and propose to install the needed
6575 packages. It would be great if Debian supported such feature too. Is
6576 anyone working on adding it?
</p
>
6578 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6579 request for icweasel support for this feature is
6580 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6581 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6582 of manpower and wish for a different design is the reason thus feature
6583 is not yet in iceweasel from Debian.
</p
>
6588 <title>What is the most supported MIME type in Debian?
</title>
6589 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6590 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6591 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6592 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6593 proposal to add AppStream information to the Debian archive
</a
>, is a
6594 proposal to make it possible for a Desktop application to propose to
6595 the user some package to install to gain support for a given MIME
6596 type, font, library etc. that is currently missing. With such
6597 mechanism in place, it would be possible for the desktop to
6598 automatically propose and install leocad if some LDraw file is
6599 downloaded by the browser.
</p
>
6601 <p
>To get some idea about the current content of the archive, I decided
6602 to write a simple program to extract all .desktop files from the
6603 Debian archive and look up the claimed MIME support there. The result
6605 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6606 site
</a
>. Using the collected information, it become possible to
6607 answer the question in the title. Here are the
20 most supported MIME
6608 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6609 The complete list is available from the link above.
</p
>
6611 <p
><strong
>Debian Stable:
</strong
></p
>
6615 ----- -----------------------
6631 18 application/x-ogg
6638 <p
><strong
>Debian Testing:
</strong
></p
>
6642 ----- -----------------------
6658 18 application/x-ogg
6665 <p
><strong
>Debian Unstable:
</strong
></p
>
6669 ----- -----------------------
6686 18 application/x-ogg
6692 <p
>I am told that PackageKit can provide an API to access the kind of
6693 information mentioned in DEP-
11. I have not yet had time to look at
6694 it, but hope the PackageKit people in Debian are on top of these
6697 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6698 discovering a typo in my script.
</p
>
6703 <title>Using modalias info to find packages handling my hardware
</title>
6704 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6706 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6707 <description><p
>Yesterday, I wrote about the
6708 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6709 values provided by the Linux kernel
</a
> following my hope for
6710 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6711 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6712 modalias values attached to package names can be used to map packages
6713 to hardware. This allow the system to look up and suggest relevant
6714 packages when I plug in some new hardware into my machine, and replace
6715 discover and discover-data as the database used to map hardware to
6718 <p
>I create a modaliases file with entries like the following,
6719 containing package name, kernel module name (if relevant, otherwise
6720 the package name) and globs matching the relevant hardware
6723 <p
><blockquote
>
6724 Package: package-name
6725 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6726 </blockquote
></p
>
6728 <p
>It is fairly trivial to write code to find the relevant packages
6729 for a given modalias value using this file.
</p
>
6731 <p
>An entry like this would suggest the video and picture application
6732 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6734 <p
><blockquote
>
6736 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6737 </blockquote
></p
>
6739 <p
>An entry like this would suggest the pcmciautils package when a
6740 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6742 <p
><blockquote
>
6743 Package: pcmciautils
6744 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6745 </blockquote
></p
>
6747 <p
>An entry like this would suggest the package colorhug-client when
6748 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6750 <p
><blockquote
>
6751 Package: colorhug-client
6752 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6753 </blockquote
></p
>
6755 <p
>I believe the format is compatible with the format of the Packages
6756 file in the Debian archive. Ubuntu already uses their Packages file
6757 to store their mappings from packages to hardware.
</p
>
6759 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6760 announce the hardware it support in a way my prototype understand.
6761 This allow those publishing packages in an APT source outside the
6762 Debian archive as well as those backporting packages to make sure the
6763 hardware mapping are included in the package meta information. I
've
6764 tested such header in the pymissile package, and its modalias mapping
6765 is working as it should with my prototype. It even made it to Ubuntu
6768 <p
>To test if it was possible to look up supported hardware using only
6769 the shell tools available in the Debian installer, I wrote a shell
6770 implementation of the lookup code. The idea is to create files for
6771 each modalias and let the shell do the matching. Please check out and
6773 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6774 shell script. It run without any extra dependencies and fetch the
6775 hardware mappings from the Debian archive and the subversion
6776 repository where I currently work on my prototype.
</p
>
6778 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6779 install yubikey-personalization:
</p
>
6781 <p
><blockquote
>
6782 % ./hw-support-lookup
6783 <br
>yubikey-personalization
6785 </blockquote
></p
>
6787 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6788 propose to install the pcmciautils package:
</p
>
6790 <p
><blockquote
>
6791 % ./hw-support-lookup
6792 <br
>pcmciautils
6794 </blockquote
></p
>
6796 <p
>If you know of any hardware-package mapping that should be added to
6797 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6798 database
</a
>, please tell me about it.
</p
>
6800 <p
>It could be possible to generate several of the mappings between
6801 packages and hardware. One source would be to look at packages with
6802 kernel modules, ie packages with *.ko files in /lib/modules/, and
6803 extract their modalias information. Another would be to look at
6804 packages with udev rules, ie packages with files in
6805 /lib/udev/rules.d/, and extract their vendor/model information to
6806 generate a modalias matching rule. I have not tested any of these to
6807 see if it work.
</p
>
6809 <p
>If you want to help implementing a system to let us propose what
6810 packages to install when new hardware is plugged into a Debian
6811 machine, please send me an email or talk to me on
6812 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6817 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6818 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6819 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6820 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6821 <description><p
>While looking into how to look up Debian packages based on hardware
6822 information, to find the packages that support a given piece of
6823 hardware, I refreshed my memory regarding modalias values, and decided
6824 to document the details. Here are my findings so far, also available
6826 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6827 Debian Edu subversion repository
</a
>:
6829 <p
><strong
>Modalias decoded
</strong
></p
>
6831 <p
>This document try to explain what the different types of modalias
6832 values stands for. It is in part based on information from
6833 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6834 &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;,
6835 &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
6836 &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;.
6838 <p
>The modalias entries for a given Linux machine can be found using
6839 this shell script:
</p
>
6842 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6845 <p
>The supported modalias globs for a given kernel module can be found
6846 using modinfo:
</p
>
6849 % /sbin/modinfo psmouse | grep alias:
6850 alias: serio:ty05pr*id*ex*
6851 alias: serio:ty01pr*id*ex*
6855 <p
><strong
>PCI subtype
</strong
></p
>
6857 <p
>A typical PCI entry can look like this. This is an Intel Host
6858 Bridge memory controller:
</p
>
6860 <p
><blockquote
>
6861 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6862 </blockquote
></p
>
6864 <p
>This represent these values:
</p
>
6869 sv
00001028 (subvendor)
6870 sd
000001AD (subdevice)
6872 sc
00 (bus subclass)
6876 <p
>The vendor/device values are the same values outputted from
'lspci
6877 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6878 0600. The
0600 class is a host bridge. Other useful bus values are
6879 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6881 <p
>Not sure how to figure out the interface value, nor what it
6884 <p
><strong
>USB subtype
</strong
></p
>
6886 <p
>Some typical USB entries can look like this. This is an internal
6887 USB hub in a laptop:
</p
>
6889 <p
><blockquote
>
6890 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6891 </blockquote
></p
>
6893 <p
>Here is the values included in this alias:
</p
>
6896 v
1D6B (device vendor)
6897 p
0001 (device product)
6899 dc
09 (device class)
6900 dsc
00 (device subclass)
6901 dp
00 (device protocol)
6902 ic
09 (interface class)
6903 isc
00 (interface subclass)
6904 ip
00 (interface protocol)
6907 <p
>The
0900 device class/subclass means hub. Some times the relevant
6908 class is in the interface class section. For a simple USB web camera,
6909 these alias entries show up:
</p
>
6911 <p
><blockquote
>
6912 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6913 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6914 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6915 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6916 </blockquote
></p
>
6918 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6919 camera),
0101 is audio control device and
0102 is audio streaming (aka
6920 microphone). Thus this is a camera with microphone included.
</p
>
6922 <p
><strong
>ACPI subtype
</strong
></p
>
6924 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6925 receiver in a Thinkpad X40:
</p
>
6927 <p
><blockquote
>
6928 acpi:IBM0071:PNP0511:
6929 </blockquote
></p
>
6931 <p
>The values between the colons are IDs.
</p
>
6933 <p
><strong
>DMI subtype
</strong
></p
>
6935 <p
>The DMI table contain lots of information about the computer case
6936 and model. This is an entry for a IBM Thinkpad X40, fetched from
6937 /sys/devices/virtual/dmi/id/modalias:
</p
>
6939 <p
><blockquote
>
6940 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6941 </blockquote
></p
>
6943 <p
>The values present are
</p
>
6946 bvn IBM (BIOS vendor)
6947 bvr
1UETB
6WW(
1.66) (BIOS version)
6948 bd
06/
15/
2005 (BIOS date)
6949 svn IBM (system vendor)
6950 pn
2371H4G (product name)
6951 pvr ThinkPadX40 (product version)
6952 rvn IBM (board vendor)
6953 rn
2371H4G (board name)
6954 rvr NotAvailable (board version)
6955 cvn IBM (chassis vendor)
6956 ct
10 (chassis type)
6957 cvr NotAvailable (chassis version)
6960 <p
>The chassis type
10 is Notebook. Other interesting values can be
6961 found in the dmidecode source:
</p
>
6965 4 Low Profile Desktop
6978 17 Main Server Chassis
6979 18 Expansion Chassis
6981 20 Bus Expansion Chassis
6982 21 Peripheral Chassis
6984 23 Rack Mount Chassis
6993 <p
>The chassis type values are not always accurately set in the DMI
6994 table. For example my home server is a tower, but the DMI modalias
6995 claim it is a desktop.
</p
>
6997 <p
><strong
>SerIO subtype
</strong
></p
>
6999 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7000 test machine:
</p
>
7002 <p
><blockquote
>
7003 serio:ty01pr00id00ex00
7004 </blockquote
></p
>
7006 <p
>The values present are
</p
>
7015 <p
>This type is supported by the psmouse driver. I am not sure what
7016 the valid values are.
</p
>
7018 <p
><strong
>Other subtypes
</strong
></p
>
7020 <p
>There are heaps of other modalias subtypes according to
7021 file2alias.c. There is the rest of the list from that source: amba,
7022 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7023 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7024 vmbus, x86cpu and zorro. I did not spend time documenting all of
7025 these, as they do not seem relevant for my intended use with mapping
7026 hardware to packages when new stuff is inserted during run time.
</p
>
7028 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
7030 <p
>To check which kernel modules provide support for a given modalias,
7031 one can use the following shell script:
</p
>
7034 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
7035 echo
"$id
" ; \
7036 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
7040 <p
>The output can look like this (only the first few entries as the
7041 list is very long on my test machine):
</p
>
7045 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
7047 FATAL: Module acpi:device: not found.
7049 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
7050 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
7051 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
7052 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7053 acpi:IBM0071:PNP0511:
7054 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
7055 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
7056 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
7060 <p
>If you want to help implementing a system to let us propose what
7061 packages to install when new hardware is plugged into a Debian
7062 machine, please send me an email or talk to me on
7063 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7065 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
7066 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
7067 in /sys/ with space in them.
</p
>
7072 <title>Moved the pymissile Debian packaging to collab-maint
</title>
7073 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
7074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
7075 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
7076 <description><p
>As part of my investigation on how to improve the support in Debian
7077 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7078 Launcher and updated the Debian package
7079 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
7080 sure udev will fix the device permissions when it is plugged in. I
7081 also added a
"Modaliases
" header to test it in the Debian archive and
7082 hopefully make the package be proposed by jockey in Ubuntu when a user
7083 plug in his rocket launcher. In the process I moved the source to a
7084 git repository under collab-maint, to make it easier for any DD to
7085 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
7086 is not very active, but the software still work for me even after five
7087 years of relative silence. The new git repository is not listed in
7088 the uploaded package yet, because I want to test the other changes a
7089 bit more before I upload the new version. If you want to check out
7090 the new version with a .desktop file included, visit the
7091 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
7092 view
</a
> or use
"<tt
>git clone
7093 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7098 <title>Lets make hardware dongles easier to use in Debian
</title>
7099 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7101 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7102 <description><p
>One thing that annoys me with Debian and Linux distributions in
7103 general, is that there is a great package management system with the
7104 ability to automatically install software packages by downloading them
7105 from the distribution mirrors, but no way to get it to automatically
7106 install the packages I need to use the hardware I plug into my
7107 machine. Even if the package to use it is easily available from the
7108 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7109 suggest to automatically install the python-nxt, nbc and t2n packages
7110 I need to talk to it. When I plug in a Yubikey, it could propose the
7111 yubikey-personalization package. The information required to do this
7112 is available, but no-one have pulled all the pieces together.
</p
>
7114 <p
>Some years ago, I proposed to
7115 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7116 the discover subsystem to implement this
</a
>. The idea is fairly
7121 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7122 starting when a user log in.
</li
>
7124 <li
>Set this program up to listen for kernel events emitted when new
7125 hardware is inserted into the computer.
</li
>
7127 <li
>When new hardware is inserted, look up the hardware ID in a
7128 database mapping to packages, and take note of any non-installed
7129 packages.
</li
>
7131 <li
>Show a message to the user proposing to install the discovered
7132 package, and make it easy to install it.
</li
>
7136 <p
>I am not sure what the best way to implement this is, but my
7137 initial idea was to use dbus events to discover new hardware, the
7138 discover database to find packages and
7139 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7142 <p
>Yesterday, I found time to try to implement this idea, and the
7143 draft package is now checked into
7144 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7145 Debian Edu subversion repository
</a
>. In the process, I updated the
7146 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7147 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7148 the relevant packages in Debian, and uploaded a new version
7149 2.2013.01.09 to unstable. I also discovered that the current
7150 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7151 package in Debian no longer discovered any USB devices, because
7152 /proc/bus/usb/devices is no longer present. I ported it to use
7153 libusb as a fall back option to get it working. The fixed package
7154 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7155 because of the freeze).
</p
>
7157 <p
>With this prototype in place, I can insert my Yubikey, and get this
7158 desktop notification to show up (only once, the first time it is
7159 inserted):
</p
>
7161 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7163 <p
>For this prototype to be really useful, some way to automatically
7164 install the proposed packages by pressing the
"Please install
7165 program(s)
" button should to be implemented.
</p
>
7167 <p
>If this idea seem useful to you, and you want to help make it
7168 happen, please help me update the discover-data database with mappings
7169 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7170 list the package you would like to have installed when a given
7171 hardware device is inserted into your computer, and report bugs using
7172 reportbug if it isn
't. Or, if you know of a better way to provide
7173 such mapping, please let me know.
</p
>
7175 <p
>This prototype need more work, and there are several questions that
7176 should be considered before it is ready for production use. Is dbus
7177 the correct way to detect new hardware? At the moment I look for HAL
7178 dbus events on the system bus, because that is the events I could see
7179 on my Debian Squeeze KDE desktop. Are there better events to use?
7180 How should the user be notified? Is the desktop notification
7181 mechanism the best option, or should the background daemon raise a
7182 popup instead? How should packages be installed? When should they
7183 not be installed?
</p
>
7185 <p
>If you want to help getting such feature implemented in Debian,
7186 please send me an email. :)
</p
>
7191 <title>New IRC channel for LEGO designers using Debian
</title>
7192 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7194 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7195 <description><p
>During Christmas, I have worked a bit on the Debian support for
7196 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7197 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7198 discovered I had to build all the tools myself because none were
7199 already in Debian Squeeze. If Debian support for LEGO is something
7200 you care about, please join me on the IRC channel
7201 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7202 irc.debian.org). There is a lot that could be done to improve the
7203 Debian support for LEGO designers. For example both CAD software
7204 and Mindstorm compilers are missing. :)
</p
>
7206 <p
>Update
2012-
01-
03: A
7207 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7208 including links to Lego related packages is now available.
</p
>
7213 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7214 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7216 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7217 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7218 year! I hope next year will prove to be a good year.
</p
>
7220 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7221 decentralised
"currency
" that allow people to transfer bitcoins
7222 between each other with minimal overhead, is a very interesting
7223 experiment. And as I wrote a few days ago, the bitcoin situation in
7224 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7225 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7226 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7227 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7228 for one of the ftpmasters to approve the new bitcoin-qt package
7231 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7232 team in Debian, you can easily test the package in Debian Squeeze
7233 using the following steps to get a set of working packages:
</p
>
7235 <blockquote
><pre
>
7236 git clone git://git.debian.org/git/collab-maint/bitcoin
7238 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7239 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7240 </pre
></blockquote
>
7242 <p
>You might have to install some build dependencies as well. The
7243 list of commands should give you two packages, bitcoind and
7244 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7245 client will download the complete set of bitcoin
"blocks
", which need
7246 around
5.6 GiB of data on my machine at the moment. Make sure your
7247 ~/.bitcoin/ directory have lots of spare room if you want to download
7248 all the blocks. The client will warn if the disk is getting full, so
7249 there is not really a problem if you got too little room, but you will
7250 not be able to get all the features out of the client.
</p
>
7252 <p
>As usual, if you use bitcoin and want to show your support of my
7253 activities, please send Bitcoin donations to my address
7254 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7259 <title>A word on bitcoin support in Debian
</title>
7260 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7261 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7262 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7263 <description><p
>It has been a while since I wrote about
7264 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7265 peer-to-peer based crypto-currency, and the reason is simply that I
7266 have been busy elsewhere. But two days ago, I started looking at the
7267 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7268 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7269 is now maintained by a
7270 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7271 people
</a
>, and the grunt work had already been done by this team. We
7272 owe a huge thank you to all these team members. :)
7273 But I was sad to discover that the bitcoin client is missing in
7274 Wheezy. It is only available in Sid (and an outdated client from
7275 backports). The client had several RC bugs registered in BTS blocking
7276 it from entering testing. To try to help the team and improve the
7277 situation, I spent some time providing patches and triaging the bug
7278 reports. I also had a look at the bitcoin package available from Matt
7280 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7281 Ubuntu
</a
>, and moved the useful pieces from that version into the
7282 Debian package.
</p
>
7284 <p
>After checking with the main package maintainer Jonas Smedegaard on
7285 IRC, I pushed several patches into the collab-maint git repository to
7286 improve the package. It now contains fixes for the RC issues (not from
7287 me, but fixed by Scott Howard), build rules for a Qt GUI client
7288 package, konqueror support for the bitcoin: URI and bash completion
7289 setup. As I work on Debian Squeeze, I also created
7290 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7291 patch to backport
</a
> the latest version. Jonas is going to look at
7292 it and try to integrate it into the git repository before uploading a
7293 new version to unstable.
7295 <p
>I would very much like bitcoin to succeed, to get rid of the
7296 centralized control currently exercised in the monetary system. I
7297 find it completely unacceptable that the USA government is collecting
7298 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7299 that the major credit card companies can block legal money
7300 transactions to Wikileaks. But for bitcoin to succeed, more people
7301 need to use bitcoins, and more people need to accept bitcoins when
7302 they sell products and services. Improving the bitcoin support in
7303 Debian is a small step in the right direction, but not enough.
7304 Unfortunately the user experience when browsing the web and wanting to
7305 pay with bitcoin is still not very good. The bitcoin: URI is a step
7306 in the right direction, but need to work in most or every browser in
7307 use. Also the bitcoin-qt client is too heavy to fire up to do a
7308 quick transaction. I believe there are other clients available, but
7309 have not tested them.
</p
>
7312 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7313 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7314 I received
20.15 BTC so far on the address I provided in my blog two
7315 years ago, as can be
7316 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7317 on the blockexplorer service
</a
>. Thank you everyone for your
7318 donation. The blockexplorer service demonstrates quite well that
7319 bitcoin is not quite anonymous and untracked. :) I wonder if the
7320 number of users have gone up since then. If you use bitcoin and want
7321 to show your support of my activity, please send Bitcoin donations to
7322 the same address as last time,
7323 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7328 <title>Git repository for song book for Computer Scientists
</title>
7329 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7330 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7331 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7332 <description><p
>As I
7333 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7334 this summer
</a
>, I have created a Computer Science song book a few
7335 years ago, and today I finally found time to create a public
7336 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7337 repository for the project
</a
>.
</p
>
7339 <p
>If you want to help out, please clone the source and submit patches
7340 to the HTML version. To generate the PDF and PostScript version,
7341 please use prince XML, or let me know about a useful free software
7342 processor capable of creating a good looking PDF from the HTML.
</p
>
7344 <p
>Want to sing? You can still find the song book in HTML, PDF and
7345 PostScript formats at
7346 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7347 Science Songbook
</a
>.
</p
>
7352 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7353 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7354 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7355 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7356 <description><p
>I dag fyller
7357 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7358 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7359 si gratulerer med dagen, Debian!
</p
>
7364 <title>Song book for Computer Scientists
</title>
7365 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7367 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7368 <description><p
>Many years ago, while studying Computer Science at the
7369 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7370 collecting computer related songs for use at parties. The original
7371 version was written in LaTeX, but a few years ago I got help from
7372 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7373 while keeping the ability to create a nice book in PDF format. I have
7374 not had time to maintain the book for a while now, and guess I should
7375 put it up on some public version control repository where others can
7376 help me extend and update the book. If anyone is volunteering to help
7377 me with this, send me an email. Also let me know if there are songs
7378 missing in my book.
</p
>
7380 <p
>I have not mentioned the book on my blog so far, and it occured to
7381 me today that I really should let all my readers share the joys of
7382 singing out load about programming, computers and computer networks.
7383 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7384 12</a
> is about to start (and I am not going). Want to sing? Check
7385 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7386 Computer Science Songbook
</a
>.
7391 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7392 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7393 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7394 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7395 <description><p
>At work we have heaps of servers. I believe the total count is
7396 around
1000 at the moment. To be able to get help from the vendors
7397 when something go wrong, we want to keep the firmware on the servers
7398 up to date. If the firmware isn
't the latest and greatest, the
7399 vendors typically refuse to start debugging any problems until the
7400 firmware is upgraded. So before every reboot, we want to upgrade the
7401 firmware, and we would really like everyone handling servers at the
7402 university to do this themselves when they plan to reboot a machine.
7403 For that to happen we at the unix server admin group need to provide
7404 the tools to do so.
</p
>
7406 <p
>To make firmware upgrading easier, I am working on a script to
7407 fetch and install the latest firmware for the servers we got. Most of
7408 our hardware are from Dell and HP, so I have focused on these servers
7409 so far. This blog post is about the Dell part.
</P
>
7411 <p
>On the Dell FTP site I was lucky enough to find
7412 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7413 with firmware information for all
11th generation servers, listing
7414 which firmware should be used on a given model and where on the FTP
7415 site I can find it. Using a simple perl XML parser I can then
7416 download the shell scripts Dell provides to do firmware upgrades from
7417 within Linux and reboot when all the firmware is primed and ready to
7418 be activated on the first reboot.
</p
>
7420 <p
>This is the Dell related fragment of the perl code I am working on.
7421 Are there anyone working on similar tools for firmware upgrading all
7422 servers at a site? Please get in touch and lets share resources.
</p
>
7424 <p
><pre
>
7428 use File::Temp qw(tempdir);
7430 # Install needed RHEL packages if missing
7432 'XML::Simple
' =
> 'perl-XML-Simple
',
7434 for my $module (keys %rhelmodules) {
7435 eval
"use $module;
";
7437 my $pkg = $rhelmodules{$module};
7438 system(
"yum install -y $pkg
");
7439 eval
"use $module;
";
7443 my $errorsto =
'pere@hungry.com
';
7449 sub run_firmware_script {
7450 my ($opts, $script) = @_;
7452 print STDERR
"fail: missing script name\n
";
7455 print STDERR
"Running $script\n\n
";
7457 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7458 print STDERR
"success: firmware script ran succcessfully\n
";
7460 print STDERR
"fail: firmware script returned error\n
";
7464 sub run_firmware_scripts {
7465 my ($opts, @dirs) = @_;
7466 # Run firmware packages
7467 for my $dir (@dirs) {
7468 print STDERR
"info: Running scripts in $dir\n
";
7469 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7470 while (my $s = readdir $dh) {
7471 next if $s =~ m/^\.\.?/;
7472 run_firmware_script($opts,
"$dir/$s
");
7480 print STDERR
"info: Downloading $url\n
";
7481 system(
"wget --quiet \
"$url\
"");
7486 my $product = `dmidecode -s system-product-name`;
7489 if ($product =~ m/PowerEdge/) {
7491 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7492 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7494 my $tmpdir = tempdir(
7498 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7499 system(
'gunzip Catalog.xml.gz
');
7500 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7501 # -q is quiet, disabling interactivity and reducing console output
7502 my $fwopts =
"-q
";
7504 for my $url (@paths) {
7505 fetch_dell_fw($url);
7507 run_firmware_scripts($fwopts, $tmpdir);
7509 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7510 print STDERR
"error: Please report to $errorsto.\n
";
7514 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7515 print STDERR
"error: Please report to $errorsto.\n
";
7521 my $url =
"ftp://ftp.us.dell.com/$path
";
7525 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7526 # firmware packages to download from Dell. Only work for Linux
7527 # machines and
11th generation Dell servers.
7528 sub fetch_dell_fw_list {
7529 my $filename = shift;
7531 my $product = `dmidecode -s system-product-name`;
7533 my ($mybrand, $mymodel) = split(/\s+/, $product);
7535 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7537 my $xml = XMLin($filename);
7539 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7540 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7541 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7543 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7544 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7546 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7548 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7550 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7553 for my $component (@{$xml-
>{SoftwareComponent}}) {
7554 my $componenttype = $component-
>{ComponentType}-
>{value};
7556 # Drop application packages, only firmware and BIOS
7557 next if
'APAC
' eq $componenttype;
7559 my $cpath = $component-
>{path};
7560 for my $path (@paths) {
7561 if ($cpath =~ m%/$path$%) {
7562 push(@paths, $cpath);
7570 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7571 it could work on other platforms with some tweaking. Anyone know a
7572 index like Catalog.xml is available from HP for HP servers? At the
7573 moment I maintain a similar list manually and it is quickly getting
7579 <title>How is booting into runlevel
1 different from single user boots?
</title>
7580 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7581 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7582 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7583 <description><p
>Wouter Verhelst have some
7584 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7585 comments and opinions
</a
> on my blog post on
7586 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7587 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7588 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7589 default KDE desktop in Debian
</a
>. I only have time to address one
7590 small piece of his comment now, and though it best to address the
7591 misunderstanding he bring forward:
</p
>
7593 <p
><blockquote
>
7594 Currently, a system admin has four options: [...] boot to a
7595 single-user system (by adding
'single
' to the kernel command line;
7596 this runs rcS and rc1 scripts)
7597 </blockquote
></p
>
7599 <p
>This make me believe Wouter believe booting into single user mode
7600 and booting into runlevel
1 is the same. I am not surprised he
7601 believe this, because it would make sense and is a quite sensible
7602 thing to believe. But because the boot in Debian is slightly broken,
7603 runlevel
1 do not work properly and it isn
't the same as single user
7604 mode. I
'll try to explain what is actually happing, but it is a bit
7605 hard to explain.
</p
>
7607 <p
>Single user mode is defined like this in /etc/inittab:
7608 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7609 executed in single user mode is sulogin. Single user mode is a boot
7610 state
"between
" the runlevels, and when booting into single user mode,
7611 only the scripts in /etc/rcS.d/ are executed before the init process
7612 enters the single user state. When switching to runlevel
1, the state
7613 is in fact not ending in runlevel
1, but it passes through runlevel
1
7614 and end up in the single user mode (see /etc/rc1.d/S03single, which
7615 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7616 1. It is confusing that the
'S
' (single user) init mode is not the
7617 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7620 <p
>This summary might make it clearer. When booting for the first
7621 time into single user mode, the following commands are executed:
7622 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7623 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7624 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7625 trying to continue after visiting single user mode. Not all services
7626 are started again as they should, causing the machine to end up in an
7627 unpredicatble state. This is why Debian admins recommend rebooting
7628 after visiting single user mode.
</p
>
7630 <p
>A similar problem with runlevel
1 is caused by the amount of
7631 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7632 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7633 stopped when passing through the scripts in /etc/rc1.d/, and not
7634 started again when switching away from runlevel
1 to the runlevels
7635 2-
5. I believe the problem is best fixed by moving all the scripts
7636 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7637 functioning single user mode during boot.
</p
>
7639 <p
>I have spent several years investigating the Debian boot system,
7640 and discovered this problem a few years ago. I suspect it originates
7641 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7646 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7647 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7648 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7649 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7650 <description><p
>In the Debian boot system, several packages include scripts that
7651 are started from /etc/rcS.d/. In fact, there is a bite more of them
7652 than make sense, and this causes a few problems. What kind of
7653 problems, you might ask. There are at least two problems. The first
7654 is that it is not possible to recover a machine after switching to
7655 runlevel
1. One need to actually reboot to get the machine back to
7656 the expected state. The other is that single user boot will sometimes
7657 run into problems because some of the subsystems are activated before
7658 the root login is presented, causing problems when trying to recover a
7659 machine from a problem in that subsystem. A minor additional point is
7660 that moving more scripts out of rcS.d/ and into the other rc#.d/
7661 directories will increase the amount of scripts that can run in
7662 parallel during boot, and thus decrease the boot time.
</p
>
7664 <p
>So, which scripts should start from rcS.d/. In short, only the
7665 scripts that _have_ to execute before the root login prompt is
7666 presented during a single user boot should go there. Everything else
7667 should go into the numeric runlevels. This means things like
7668 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7669 the numeric runlevels. Today in Debian, there are around
115 init.d
7670 scripts that are started from rcS.d/, and most of them should be moved
7671 out. Do your package have one of them? Please help us make single
7672 user and runlevel
1 better by moving it.
</p
>
7674 <p
>Scripts setting up the screen, keyboard, system partitions
7675 etc. should still be started from rcS.d/, but there is for example no
7676 need to have the network enabled before the single user login prompt
7677 is presented.
</p
>
7679 <p
>As always, things are not so easy to fix as they sound. To keep
7680 Debian systems working while scripts migrate and during upgrades, the
7681 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7682 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7683 and the next ones can only be moved when their dependencies have been
7684 moved first. This migration must be done sequentially while we ensure
7685 that the package system upgrade packages in the right order to keep
7686 the system state correct. This will require some coordination when it
7687 comes to network related packages, but most of the packages with
7688 scripts that should migrate do not have anything in rcS.d/ depending
7689 on them. Some packages have already been updated, like the sudo
7690 package, while others are still left to do. I wish I had time to work
7691 on this myself, but real live constrains make it unlikely that I will
7692 find time to push this forward.
</p
>
7697 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7698 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7700 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7701 <description><p
>While at Debconf11, I have several times during discussions
7702 mentioned the issues I believe should be improved in Debian for its
7703 desktop to be useful for more people. The use case for this is my
7704 parents, which are currently running Kubuntu which solve the
7707 <p
>I suspect these four missing features are not very hard to
7708 implement. After all, they are present in Ubuntu, so if we wanted to
7709 do this in Debian we would have a source.
</p
>
7713 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7714 are new packages available for upgrades, a icon in the KDE status bar
7715 indicate this, and clicking on it will activate the simple upgrade
7716 tool to handle it. I have no problem guiding both of my parents
7717 through the process over the phone. If a kernel reboot is required,
7718 this too is indicated by the status bars and the upgrade tool. Last
7719 time I checked, nothing with the same features was working in KDE in
7722 <li
><strong
>Simple handling of missing Firefox browser
7723 plugins.
</strong
> When the browser encounter a MIME type it do not
7724 currently have a handler for, it will ask the user if the system
7725 should search for a package that would add support for this MIME type,
7726 and if the user say yes, the APT sources will be searched for packages
7727 advertising the MIME type in their control file (visible in the
7728 Packages file in the APT archive). If one or more packages are found,
7729 it is a simple click of the mouse to add support for the missing mime
7730 type. If the package require the user to accept some non-free
7731 license, this is explained to the user. The entire process make it
7732 more clear to the user why something do not work in the browser, and
7733 make the chances higher for the user to blame the web page authors and
7734 not the browser for any missing features.
</li
>
7736 <li
><strong
>Simple handling of missing multimedia codec/format
7737 handlers.
</strong
> When the media players encounter a format or codec
7738 it is not supporting, a dialog pop up asking the user if the system
7739 should search for a package that would add support for it. This
7740 happen with things like MP3, Windows Media or H
.264. The selection
7741 and installation procedure is very similar to the Firefox browser
7742 plugin handling. This is as far as I know implemented using a
7743 gstreamer hook. The end result is that the user easily get access to
7744 the codecs that are present from the APT archives available, while
7745 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7747 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7748 displaying a text/plain file in my Debian browser, it will propose to
7749 start emacs to show it. If I remember correctly, when doing the same
7750 in Kunbutu it show the file as a text file in the browser. At least I
7751 know Opera will show text files within the browser. I much prefer the
7752 latter behaviour.
</li
>
7756 <p
>There are other nice features as well, like the simplified suite
7757 upgrader, but given that I am the one mostly doing the dist-upgrade,
7758 it do not matter much.
</p
>
7760 <p
>I really hope we could get these features in place for the next
7761 Debian release. It would require the coordinated effort of several
7762 maintainers, but would make the end user experience a lot better.
</p
>
7767 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7768 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7769 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7770 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7771 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7772 site is build on Debian/Squeeze, and this platform was chosen because
7773 I am most familiar with Debian (being a Debian Developer for around
10
7774 years) because it is the latest stable Debian release which should get
7775 security support for a few years.
</p
>
7777 <p
>The web service is written in Perl, and depend on some perl modules
7778 that are missing in Debian at the moment. It would be great if these
7779 modules were added to the Debian archive, allowing anyone to set up
7780 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7781 in their own country using only Debian packages. The list of modules
7782 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7783 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7784 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7785 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7786 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7787 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7788 easier in the future.
</p
>
7790 <p
>Thanks to the great tools in Debian, getting the missing modules
7791 installed on my server was a simple call to
'cpan2deb Module::Name
'
7792 and
'dpkg -i
' to install the resulting package. But this leave me
7793 with the responsibility of tracking security problems, which I really
7794 do not have time for.
</p
>
7799 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7800 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7801 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7802 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7803 <description><p
>Here is a small update for my English readers. Most of my blog
7804 posts have been in Norwegian the last few weeks, so here is a short
7805 update in English.
</p
>
7807 <p
>The kids still keep me too busy to get much free software work
7808 done, but I did manage to organise a project to get a Norwegian port
7809 of the British service
7810 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7811 and it has been running for a month now. The entire project has been
7812 organised by me and two others. Around Christmas we gathered sponsors
7813 to fund the development work. In January I drafted a contract with
7814 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7815 and in February the development took place. Most of it involved
7816 converting the source to use GPS coordinates instead of British
7817 easting/northing, and the resulting code should be a lot easier to get
7818 running in any country by now. The Norwegian
7819 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7820 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7821 source and the source for administrative borders in Norway, and
7822 support for this had to be added/fixed.
</p
>
7824 <p
>The Norwegian version went live March
3th, and we spent the weekend
7825 polishing the system before we announced it March
7th. The system is
7826 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7827 problem reports in a few weeks. Soon we hope to announce the Android
7828 and iPhone versions making it even easier to report problems with the
7829 public infrastructure.
</p
>
7831 <p
>Perhaps something to consider for those of you in countries without
7832 such service?
</p
>
7837 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7838 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7840 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7841 <description><p
>The last few days I have looked at ways to track open security
7842 issues here at my work with the University of Oslo. My idea is that
7843 it should be possible to use the information about security issues
7844 available on the Internet, and check our locally
7845 maintained/distributed software against this information. It should
7846 allow us to verify that no known security issues are forgotten. The
7847 CVE database listing vulnerabilities seem like a great central point,
7848 and by using the package lists from Debian mapped to CVEs provided by
7849 the testing security team, I believed it should be possible to figure
7850 out which security holes were present in our free software
7851 collection.
</p
>
7853 <p
>After reading up on the topic, it became obvious that the first
7854 building block is to be able to name software packages in a unique and
7855 consistent way across data sources. I considered several ways to do
7856 this, for example coming up with my own naming scheme like using URLs
7857 to project home pages or URLs to the Freshmeat entries, or using some
7858 existing naming scheme. And it seem like I am not the first one to
7859 come across this problem, as MITRE already proposed and implemented a
7860 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7861 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7862 software, hardware and other platform components. The CPE ids are
7863 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7864 Vulnerability Database
</a
>, allowing me to look up know security
7865 issues for any CPE name. With this in place, all I need to do is to
7866 locate the CPE id for the software packages we use at the university.
7867 This is fairly trivial (I google for
'cve cpe $package
' and check the
7868 NVD entry if a CVE for the package exist).
</p
>
7870 <p
>To give you an example. The GNU gzip source package have the CPE
7871 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7872 check out, one could look up
7873 <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
7874 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7875 The most recent one is
7876 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7877 and at the bottom of the NVD page for this vulnerability the complete
7878 list of affected versions is provided.
</p
>
7880 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7881 for offline processing of issues. Using this dump, I
've written a
7882 small script taking a list of CPEs as input and list all CVEs
7883 affecting the packages represented by these CPEs. One give it CPEs
7884 with version numbers as specified above and get a list of open
7885 security issues out.
</p
>
7887 <p
>Of course for this approach to be useful, the quality of the NVD
7888 information need to be high. For that to happen, I believe as many as
7889 possible need to use and contribute to the NVD database. I notice
7891 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7892 map from CVE to CPE
</a
>, indicating that they are using the CPE
7893 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7895 <p
>To get an idea about the quality for free software, I spent some
7896 time making it possible to compare the CVE database from Debian with
7897 the CVE database in NVD. The result look fairly good, but there are
7898 some inconsistencies in NVD (same software package having several
7899 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7900 Debian believe are affected by a CVE). Hope to find time to improve
7901 the quality of NVD, but that require being able to get in touch with
7902 someone maintaining it. So far my three emails with questions and
7903 corrections have not seen any reply, but I hope contact can be
7904 established soon.
</p
>
7906 <p
>An interesting application for CPEs is cross platform package
7907 mapping. It would be useful to know which packages in for example
7908 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7909 this would be trivial if all linux distributions provided CPE entries
7910 for their packages.
</p
>
7915 <title>Which module is loaded for a given PCI and USB device?
</title>
7916 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7917 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7918 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7919 <description><p
>In the
7920 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7921 package in Debian, there is a script to report useful information
7922 about the running hardware for use when people report missing
7923 information. One part of this script that I find very useful when
7924 debugging hardware problems, is the part mapping loaded kernel module
7925 to the PCI device it claims. It allow me to quickly see if the kernel
7926 module I expect is driving the hardware I am struggling with. To see
7927 the output, make sure discover-data is installed and run
7928 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7929 one of my machines like this:
</p
>
7933 10de:
03eb i2c_nforce2
7936 10de:
03f0 snd_hda_intel
7945 <p
>The code in question look like this, slightly modified for
7946 readability and to drop the output to file descriptor
3:
</p
>
7949 if [ -d /sys/bus/pci/devices/ ] ; then
7950 echo loaded pci modules:
7952 cd /sys/bus/pci/devices/
7953 for address in * ; do
7954 if [ -d
"$address/driver/module
" ] ; then
7955 module=`cd $address/driver/module ; pwd -P | xargs basename`
7956 if grep -q
"^$module
" /proc/modules ; then
7957 address=$(echo $address |sed s/
0000://)
7958 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7959 echo
"$id $module
"
7968 <p
>Similar code could be used to extract USB device module
7972 if [ -d /sys/bus/usb/devices/ ] ; then
7973 echo loaded usb modules:
7975 cd /sys/bus/usb/devices/
7976 for address in * ; do
7977 if [ -d
"$address/driver/module
" ] ; then
7978 module=`cd $address/driver/module ; pwd -P | xargs basename`
7979 if grep -q
"^$module
" /proc/modules ; then
7980 address=$(echo $address |sed s/
0000://)
7981 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7982 if [
"$id
" ] ; then
7983 echo
"$id $module
"
7993 <p
>This might perhaps be something to include in other tools as
7999 <title>How to test if a laptop is working with Linux
</title>
8000 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8001 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8002 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8003 <description><p
>The last few days I have spent at work here at the
<a
8004 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8005 batch of computers will work with Linux. Every year for the last few
8006 years the university have organised shared bid of a few thousand
8007 computers, and this year HP won the bid. Two different desktops and
8008 five different laptops are on the list this year. We in the UNIX
8009 group want to know which one of these computers work well with RHEL
8010 and Ubuntu, the two Linux distributions we currently handle at the
8011 university.
</p
>
8013 <p
>My test method is simple, and I share it here to get feedback and
8014 perhaps inspire others to test hardware as well. To test, I PXE
8015 install the OS version of choice, and log in as my normal user and run
8016 a few applications and plug in selected pieces of hardware. When
8017 something fail, I make a note about this in the test matrix and move
8018 on. If I have some spare time I try to report the bug to the OS
8019 vendor, but as I only have the machines for a short time, I rarely
8020 have the time to do this for all the problems I find.
</p
>
8022 <p
>Anyway, to get to the point of this post. Here is the simple tests
8023 I perform on a new model.
</p
>
8027 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
8028 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8029 RHEL5 and Debian Edu/Squeeze.
</li
>
8031 <li
>Is X.org working? If the graphical login screen show up after
8032 installation, X.org is working.
</li
>
8034 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
8035 package mesa-utils on Ubuntu) and writing down the frames per second
8036 reported by the program.
</li
>
8038 <li
>Is sound working? With Gnome and KDE, a sound is played when
8039 logging in, and if I can hear this the test is successful. If there
8040 are several audio exits on the machine, I try them all and check if
8041 the Gnome/KDE audio mixer can control where to send the sound. I
8042 normally test this by playing
8043 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
8044 video
</a
> in Firefox/Iceweasel.
</li
>
8046 <li
>Is the USB subsystem working? I test this by plugging in a USB
8047 memory stick and see if Gnome/KDE notices this.
</li
>
8049 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
8050 I have lying around, and see if Gnome/KDE notices this.
</li
>
8052 <li
>Is any built in camera working? Test using cheese, and see if a
8053 picture from the v4l device show up.
</li
>
8055 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8056 any bluetooth devices are discovered. In my office, I normally see a
8059 <li
>For laptops, is the SD or Compaq Flash reader working. I have
8060 memory modules lying around, and stick them in and see if Gnome/KDE
8061 notice this.
</li
>
8063 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
8064 special button work, and if the laptop continue to work after
8067 <li
>For laptops, is the extra buttons working, like audio level,
8068 adjusting background light, switching on/off external video output,
8069 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8070 laptop to laptop, so I just write down which are working and which are
8073 <li
>Some laptops have smart card readers, finger print readers,
8074 acceleration sensors etc. I rarely test these, as I do not know how
8075 to quickly test if they are working or not, so I only document their
8076 existence.
</li
>
8080 <p
>By now I suspect you are really curious what the test results are
8081 for the HP machines I am testing. I
'm not done yet, so I will report
8082 the test results later. For now I can report that HP
8100 Elite work
8083 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
8084 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
8085 can see, I have most machines left to test. One interesting
8086 observation is that Ubuntu Lucid has almost twice the frame rate than
8087 RHEL6 with glxgears. No idea why.
</p
>
8092 <title>Some thoughts on BitCoins
</title>
8093 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
8094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
8095 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
8096 <description><p
>As I continue to explore
8097 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8098 what properties the system have, and how it will be affected by laws
8099 and regulations here in Norway. Here are some random notes.
</p
>
8101 <p
>One interesting thing to note is that since the transactions are
8102 verified using a peer to peer network, all details about a transaction
8103 is known to everyone. This means that if a BitCoin address has been
8104 published like I did with mine in my initial post about BitCoin, it is
8105 possible for everyone to see how many BitCoins have been transfered to
8106 that address. There is even a web service to look at the details for
8107 all transactions. There I can see that my address
8108 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8109 have received
16.06 Bitcoin, the
8110 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8111 address of Simon Phipps have received
181.97 BitCoin and the address
8112 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8113 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8114 every one of you that donated bitcoins to support my activity. The
8115 fact that anyone can see how much money was transfered to a given
8116 address make it more obvious why the BitCoin community recommend to
8117 generate and hand out a new address for each transaction. I
'm told
8118 there is no way to track which addresses belong to a given person or
8119 organisation without the person or organisation revealing it
8120 themselves, as Simon, EFF and I have done.
</p
>
8122 <p
>In Norway, and in most other countries, there are laws and
8123 regulations limiting how much money one can transfer across the border
8124 without declaring it. There are money laundering, tax and accounting
8125 laws and regulations I would expect to apply to the use of BitCoin.
8126 If the Skolelinux foundation
8127 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8128 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8129 normal bank transfers like EFF is doing, how should this be accounted?
8130 Given that it is impossible to know if money can cross the border or
8131 not, should everything or nothing be declared? What exchange rate
8132 should be used when calculating taxes? Would receivers have to pay
8133 income tax if the foundation were to pay Skolelinux contributors in
8134 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8136 <p
>For a currency to be useful and successful, it must be trusted and
8137 accepted by a lot of users. It must be possible to get easy access to
8138 the currency (as a wage or using currency exchanges), and it must be
8139 easy to spend it. At the moment BitCoin seem fairly easy to get
8140 access to, but there are very few places to spend it. I am not really
8141 a regular user of any of the vendor types currently accepting BitCoin,
8142 so I wonder when my kind of shop would start accepting BitCoins. I
8143 would like to buy electronics, travels and subway tickets, not herbs
8144 and books. :) The currency is young, and this will improve over time
8145 if it become popular, but I suspect regular banks will start to lobby
8146 to get BitCoin declared illegal if it become popular. I
'm sure they
8147 will claim it is helping fund terrorism and money laundering (which
8148 probably would be true, as is any currency in existence), but I
8149 believe the problems should be solved elsewhere and not by blaming
8150 currencies.
</p
>
8152 <p
>The process of creating new BitCoins is called mining, and it is
8153 CPU intensive process that depend on a bit of luck as well (as one is
8154 competing against all the other miners currently spending CPU cycles
8155 to see which one get the next lump of cash). The
"winner
" get
50
8156 BitCoin when this happen. Yesterday I came across the obvious way to
8157 join forces to increase ones changes of getting at least some coins,
8158 by coordinating the work on mining BitCoins across several machines
8159 and people, and sharing the result if one is lucky and get the
50
8161 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8162 if this sounds interesting. I have not had time to try to set up a
8163 machine to participate there yet, but have seen that running on ones
8164 own for a few days have not yield any BitCoins througth mining
8167 <p
>Update
2010-
12-
15: Found an
<a
8168 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8169 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8170 it was interesting to read. The arguments presented seem to be
8171 equally valid for gold, which was used as a currency for many years.
</p
>
8176 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8177 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8179 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8180 <description><p
>With this weeks lawless
8181 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8182 attacks
</a
> on Wikileak and
8183 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8184 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8185 not be trusted to handle money transactions.
8187 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8188 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8189 mine mentioned earlier. I decided to follow Simon
's example, and get
8190 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8191 some help from my friend to get it all running, and he even handed me
8192 some bitcoins to get started. I even donated a few bitcoins to Simon
8193 for helping me remember BitCoin.
</p
>
8195 <p
>So, what is bitcoins, you probably wonder? It is a digital
8196 crypto-currency, decentralised and handled using peer-to-peer
8197 networks. It allows anonymous transactions and prohibits central
8198 control over the transactions, making it impossible for governments
8199 and companies alike to block donations and other transactions. The
8200 source is free software, and while the key dependency wxWidgets
2.9
8201 for the graphical user interface is missing in Debian, the command
8202 line client builds just fine. Hopefully Jonas
8203 <a href=
"http://bugs.debian.org/
578157">will get the package into
8204 Debian
</a
> soon.
</p
>
8206 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8207 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8208 bitcoins
</a
> when selling services and goods, and there are even
8209 currency
"stock
" markets where the exchange rate is decided. There
8210 are not many users so far, but the concept seems promising. If you
8211 want to get started and lack a friend with any bitcoins to spare,
8213 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8214 bitcoin at the time of writing). Use
8215 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8216 on the current exchange rates.
</p
>
8218 <p
>As an experiment, I have decided to set up bitcoind on one of my
8219 machines. If you want to support my activity, please send Bitcoin
8220 donations to the address
8221 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8226 <title>Why isn
't Debian Edu using VLC?
</title>
8227 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8229 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8230 <description><p
>In the latest issue of Linux Journal, the readers choices were
8231 presented, and the winner among the multimedia player were VLC.
8232 Personally, I like VLC, and it is my player of choice when I first try
8233 to play a video file or stream. Only if VLC fail will I drag out
8234 gmplayer to see if it can do better. The reason is mostly the failure
8235 model and trust. When VLC fail, it normally pop up a error message
8236 reporting the problem. When mplayer fail, it normally segfault or
8237 just hangs. The latter failure mode drain my trust in the program.
<p
>
8239 <p
>But even if VLC is my player of choice, we have choosen to use
8240 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8241 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8242 plugin to play web videos seamlessly, and the VLC browser plugin is
8243 not very good. For example, it lack in-line control buttons, so there
8244 is no way for the user to pause the video. Also, when I
8245 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8246 tested the browser plugins
</a
> available in Debian, the VLC plugin
8247 failed on several video pages where mplayer based plugins worked. If
8248 the browser plugin for VLC was as good as the gecko-mediaplayer
8249 package (which uses mplayer), we would switch.
</P
>
8251 <p
>While VLC is a good player, its user interface is slightly
8252 annoying. The most annoying feature is its inconsistent use of
8253 keyboard shortcuts. When the player is in full screen mode, its
8254 shortcuts are different from when it is playing the video in a window.
8255 For example, space only work as pause when in full screen mode. I
8256 wish it had consisten shortcuts and that space also would work when in
8257 window mode. Another nice shortcut in gmplayer is [enter] to restart
8258 the current video. It is very nice when playing short videos from the
8259 web and want to restart it when new people arrive to have a look at
8260 what is going on.
</p
>
8265 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8266 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8267 <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>
8268 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8269 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8270 upgrade testing of the
8271 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8272 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8273 This seem like a very good idea, so I adjusted by test scripts and
8274 can now present the updated result from today:
</p
>
8276 <p
>This is for Gnome:
</p
>
8278 <p
>Installed using apt-get, missing with aptitude
</p
>
8280 <blockquote
><p
>
8285 browser-plugin-gnash
8292 freedesktop-sound-theme
8294 gconf-defaults-service
8309 gnome-desktop-environment
8313 gnome-session-canberra
8318 gstreamer0.10-fluendo-mp3
8324 libapache2-mod-dnssd
8327 libaprutil1-dbd-sqlite3
8330 libboost-date-time1.42
.0
8331 libboost-python1.42
.0
8332 libboost-thread1.42
.0
8334 libchamplain-gtk-
0.4-
0
8336 libclutter-gtk-
0.10-
0
8343 libfreerdp-plugins-standard
8358 libgnomepanel2.24-cil
8363 libgtksourceview2.0-common
8364 libmono-addins-gui0.2-cil
8365 libmono-addins0.2-cil
8366 libmono-cairo2.0-cil
8367 libmono-corlib2.0-cil
8368 libmono-i18n-west2.0-cil
8369 libmono-posix2.0-cil
8370 libmono-security2.0-cil
8371 libmono-sharpzip2.84-cil
8372 libmono-system2.0-cil
8375 libndesk-dbus-glib1.0-cil
8376 libndesk-dbus1.0-cil
8386 libtelepathy-farsight0
8395 nautilus-sendto-empathy
8399 python-aptdaemon-gtk
8401 python-beautifulsoup
8416 python-gtksourceview2
8427 python-pkg-resources
8434 python-twisted-conch
8440 python-zope.interface
8445 rhythmbox-plugin-cdrecorder
8452 system-config-printer-udev
8454 telepathy-mission-control-
5
8465 </p
></blockquote
>
8467 <p
>Installed using apt-get, removed with aptitude
</p
>
8469 <blockquote
><p
>
8475 fast-user-switch-applet
8494 libgtksourceview2.0-
0
8496 libsdl1.2debian-alsa
8502 system-config-printer
8507 </p
></blockquote
>
8509 <p
>Installed using aptitude, missing with apt-get
</p
>
8511 <blockquote
><p
>
8512 gstreamer0.10-gnomevfs
8513 </p
></blockquote
>
8515 <p
>Installed using aptitude, removed with apt-get
</p
>
8517 <blockquote
><p
>
8519 </p
></blockquote
>
8521 <p
>This is for KDE:
</p
>
8523 <p
>Installed using apt-get, missing with aptitude
</p
>
8525 <blockquote
><p
>
8527 </p
></blockquote
>
8529 <p
>Installed using apt-get, removed with aptitude
</p
>
8531 <blockquote
><p
>
8534 </p
></blockquote
>
8536 <p
>Installed using aptitude, missing with apt-get
</p
>
8538 <blockquote
><p
>
8552 kdeartwork-emoticons
8554 kdeartwork-theme-icon
8558 kdebase-workspace-bin
8559 kdebase-workspace-data
8573 kscreensaver-xsavers
8588 plasma-dataengines-workspace
8590 plasma-desktopthemes-artwork
8591 plasma-runners-addons
8592 plasma-scriptengine-googlegadgets
8593 plasma-scriptengine-python
8594 plasma-scriptengine-qedje
8595 plasma-scriptengine-ruby
8596 plasma-scriptengine-webkit
8597 plasma-scriptengines
8598 plasma-wallpapers-addons
8599 plasma-widget-folderview
8600 plasma-widget-networkmanagement
8604 xscreensaver-data-extra
8606 xscreensaver-gl-extra
8607 xscreensaver-screensaver-bsod
8608 </p
></blockquote
>
8610 <p
>Installed using aptitude, removed with apt-get
</p
>
8612 <blockquote
><p
>
8614 google-gadgets-common
8632 libggadget-qt-
1.0-
0b
8637 libkonqsidebarplugin4a
8646 libplasma-geolocation-interface4
8648 libplasmagenericshell4
8662 libsmokeknewstuff2-
3
8663 libsmokeknewstuff3-
3
8665 libsmokektexteditor3
8673 libsmokeqtnetwork4-
3
8679 libsmokeqtuitools4-
3
8691 plasma-dataengines-addons
8692 plasma-scriptengine-superkaramba
8693 plasma-widget-lancelot
8694 plasma-widgets-addons
8695 plasma-widgets-workspace
8699 update-notifier-common
8700 </p
></blockquote
>
8702 <p
>Running apt-get autoremove made the results using apt-get and
8703 aptitude a bit more similar, but there are still quite a lott of
8704 differences. I have no idea what packages should be installed after
8705 the upgrade, but hope those that do can have a look.
</p
>
8710 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8711 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8712 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8713 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8714 <description><p
>Most of the computers in use by the
8715 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8716 are virtual machines. And they have been Xen machines running on a
8717 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8718 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8719 bit harder that it could have been, because we set up the Xen virtual
8720 machines to get the virtual partitions from LVM, which as far as I
8721 know is not supported by KVM. So to migrate, we had to convert
8722 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8725 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8726 nice recipe
</a
> to do this, and wrote the following script to do the
8727 migration. It uses qemu-img from the qemu package to make the disk
8728 image, parted to partition it, losetup and kpartx to present the disk
8729 image partions as devices, and dd to copy the data. I NFS mounted the
8730 new servers storage area on the old server to do the migration.
</p
>
8736 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8741 if [ -z
"$
1" ] ; then
8742 echo
"Usage: $
0 &lt;hostname
&gt;
"
8748 if [ ! -e /dev/vg_data/$host-disk ] ; then
8749 echo
"error: unable to find LVM volume for $host
"
8753 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8754 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8755 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8756 totalsize=$(( ( $disksize + $swapsize ) ))
8759 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8760 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8762 parted $img mklabel msdos
8763 parted $img mkpart primary linux-swap
0 $disksize
8764 parted $img mkpart primary ext2 $disksize $totalsize
8765 parted $img set
1 boot on
8768 losetup /dev/loop0 $img
8769 kpartx -a /dev/loop0
8771 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8772 fsck.ext3 -f /dev/mapper/loop0p1 || true
8773 mkswap /dev/mapper/loop0p2
8775 kpartx -d /dev/loop0
8776 losetup -d /dev/loop0
8779 <p
>The script is perhaps so simple that it is not copyrightable, but
8780 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8782 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8783 the new disk image attached, installed grub-pc and linux-image-
686 and
8784 set up grub to boot from the disk image. After this, the KVM machines
8785 seem to work just fine.
</p
>
8790 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8791 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8792 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8793 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8794 <description><p
>I
'm still running upgrade testing of the
8795 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8796 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8797 status. Here is a short update based on a test I ran
20101118.
</p
>
8799 <p
>I still do not know what a correct migration should look like, so I
8800 report any differences between apt and aptitude and hope someone else
8801 can see if anything should be changed.
</p
>
8803 <p
>This is for Gnome:
</p
>
8805 <p
>Installed using apt-get, missing with aptitude
</p
>
8807 <blockquote
><p
>
8808 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8809 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8810 dmz-cursor-theme empathy empathy-common finger
8811 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8812 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8813 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8814 gnome-cards-data gnome-codec-install gnome-core
8815 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8816 gnome-search-tool gnome-session-canberra gnome-spell
8817 gnome-system-log gnome-themes-extras gnome-themes-more
8818 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8819 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8820 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8821 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8822 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8823 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8824 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8825 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8826 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8827 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8828 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8829 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8830 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8831 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8832 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8833 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8834 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8835 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8836 libmono-security2.0-cil libmono-sharpzip2.84-cil
8837 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8838 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8839 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8840 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8841 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8842 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8843 libxalan2-java libxerces2-java media-player-info mesa-utils
8844 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8845 nautilus-sendto-empathy openoffice.org-writer2latex
8846 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8847 python-aptdaemon python-aptdaemon-gtk python-axiom
8848 python-beautifulsoup python-bugbuddy python-clientform
8849 python-coherence python-configobj python-crypto python-cupshelpers
8850 python-cupsutils python-eggtrayicon python-elementtree
8851 python-epsilon python-evolution python-feedparser python-gdata
8852 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8853 python-gtksourceview2 python-httplib2 python-louie python-mako
8854 python-markupsafe python-mechanize python-nevow python-notify
8855 python-opengl python-openssl python-pam python-pkg-resources
8856 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8857 python-tagpy python-twisted-bin python-twisted-conch
8858 python-twisted-core python-twisted-web python-utidylib python-webkit
8859 python-xdg python-zope.interface remmina remmina-plugin-data
8860 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8861 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8862 software-center svgalibg1 system-config-printer-udev
8863 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8864 totem totem-coherence totem-mozilla totem-plugins
8865 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8867 </p
></blockquote
>
8869 Installed using apt-get, removed with aptitude
8871 <blockquote
><p
>
8872 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8873 epiphany-extensions epiphany-gecko evolution-exchange
8874 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8875 gedit-common gnome-app-install gnome-games gnome-games-data
8876 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8877 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8878 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8879 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8880 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8881 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8882 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8883 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8884 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8885 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8886 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8887 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8888 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8889 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8890 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8891 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8892 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8893 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8894 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8895 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8896 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8897 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8898 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8899 sound-juicer swfdec-gnome system-config-printer totem-common
8900 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8901 </p
></blockquote
>
8903 <p
>Installed using aptitude, missing with apt-get
</p
>
8905 <blockquote
><p
>
8906 gstreamer0.10-gnomevfs
8907 </p
></blockquote
>
8909 <p
>Installed using aptitude, removed with apt-get
</p
>
8911 <blockquote
><p
>
8913 </p
></blockquote
>
8915 <p
>This is for KDE:
</p
>
8917 <p
>Installed using apt-get, missing with aptitude
</p
>
8919 <blockquote
><p
>
8920 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8921 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8922 ghostscript-x git gnome-audio gnugo granatier gs-common
8923 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8924 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8925 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8926 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8927 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8928 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8929 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8930 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8931 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8932 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8933 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8934 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8935 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8936 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8937 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8938 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8939 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8940 libkrossui4 libmailtools-perl libmime-tools-perl
8941 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8942 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8943 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8944 lirc luatex marble networkstatus noatun-plugins
8945 openoffice.org-writer2latex palapeli palapeli-data parley
8946 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8947 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8948 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8950 </p
></blockquote
>
8952 <p
>Installed using apt-get, removed with aptitude
</p
>
8954 <blockquote
><p
>
8955 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8956 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8957 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8958 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8959 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8960 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8961 kitchensync kiten kjumpingcube klatin klettres klickety klines
8962 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8963 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8964 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8965 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8966 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8967 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8968 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8969 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8970 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8971 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8972 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8973 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8974 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8975 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8976 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8977 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8978 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8979 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8980 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8981 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8982 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8983 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8984 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8985 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8986 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8987 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8988 </p
></blockquote
>
8990 <p
>Installed using aptitude, missing with apt-get
</p
>
8992 <blockquote
><p
>
8993 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8994 kdeartwork kdebase kdebase-apps kdebase-workspace
8995 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8996 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8997 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8998 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8999 xscreensaver-screensaver-bsod
9000 </p
></blockquote
>
9002 <p
>Installed using aptitude, removed with apt-get
</p
>
9004 <blockquote
><p
>
9005 kdebase-bin konq-plugins konqueror
9006 </p
></blockquote
>
9011 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9012 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9013 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9014 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9015 <description><p
>Answering
9016 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9017 call from the Gnash project
</a
> for
9018 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9019 current source, I have set up a virtual KVM machine on the Debian
9020 Edu/Skolelinux virtualization host to test the git source on
9021 Debian/Squeeze. I hope this can help the developers in getting new
9022 releases out more often.
</p
>
9024 <p
>As the developers want less main-stream build platforms tested to,
9025 I have considered setting up a
<a
9026 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
9027 machine as well. I have also considered using the kfreebsd
9028 architecture in Debian as a file server in NUUG to get access to the
5
9029 TB zfs volume we currently use to store DV video. Because of this, I
9030 finally got around to do a test installation of Debian/Squeeze with
9031 kfreebsd. Installation went fairly smooth, thought I noticed some
9032 visual glitches in the cdebconf dialogs (black cursor left on the
9033 screen at random locations). Have not gotten very far with the
9034 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9035 fatal problem. Have to spend some more time on it to see if it is
9036 useful as a file server for NUUG. Will try to find time to set up a
9037 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
9042 <title>Debian in
3D
</title>
9043 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
9044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
9045 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
9046 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
9048 <p
>3D printing is just great. I just came across this Debian logo in
9050 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
9051 thingiverse blog
</a
>.
</p
>
9056 <title>Software updates
2010-
10-
24</title>
9057 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
9058 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
9059 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
9060 <description><p
>Some updates.
</p
>
9062 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
9063 raise money for the project is going well. The lower limit of
10
9064 signers was reached in
24 hours, and so far
13 people have signed it.
9065 More signers and more funding is most welcome, and I am really curious
9066 how far we can get before the time limit of December
24 is reached.
9069 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
9070 about what appear to be a great code coverage tool capable of
9071 generating code coverage stats without any changes to the source code.
9073 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
9074 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
9075 It is missing in Debian, but the git source built just fine in Squeeze
9076 after I installed libelf-dev, libdwarf-dev, pkg-config and
9077 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9078 solvable. I hope kcov make it into Debian soon.
</p
>
9080 <p
>Finally found time to wrap up the release notes for
<a
9081 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
9082 new alpha release of Debian Edu
</a
>, and just published the second
9083 alpha test release of the Squeeze based Debian Edu /
9084 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
9085 release. Give it a try if you need a complete linux solution for your
9086 school, including central infrastructure server, workstations, thin
9087 client servers and diskless workstations. A nice touch added
9088 yesterday is RDP support on the thin client servers, for windows
9089 clients to get a Linux desktop on request.
</p
>
9094 <title>Some notes on Flash in Debian and Debian Edu
</title>
9095 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
9096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9097 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9098 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9099 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9100 second most popular used package that is missing in Debian. The sixth
9101 most popular is flashplayer-mozilla. This is a clear indication that
9102 working flash is important for Debian users. Around
10 percent of the
9103 users submitting data to popcon.debian.org have this package
9104 installed.
</p
>
9106 <p
>In the report written by Lars Risan in August
2008
9107 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9108 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9109 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9110 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9111 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9112 web sites require Flash to work, and lacking working Flash support in
9113 the web browser and the problems with installing it was perceived as a
9114 good reason to stay with Windows.
</p
>
9116 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9117 said to be the retarded cousin that did not really understand
9118 everything you told him but could work fairly well. This was a
9119 comment regarding the problems Linux have with proprietary formats and
9120 non-standard web pages, and is sad because it exposes a fairly common
9121 understanding of whose fault it is if web pages that only work in for
9122 example Internet Explorer
6 fail to work on Firefox, and funny because
9123 it explain very well how annoying it is for users when Linux
9124 distributions do not work with the documents they receive or the web
9125 pages they want to visit.
</p
>
9127 <p
>This is part of the reason why I believe it is important for Debian
9128 and Debian Edu to have a well working Flash implementation in the
9129 distribution, to get at least popular sites as Youtube and Google
9130 Video to working out of the box. For Squeeze, Debian have the chance
9131 to include the latest version of Gnash that will make this happen, as
9132 the new release
0.8.8 was published a few weeks ago and is resting in
9133 unstable. The new version work with more sites that version
0.8.7.
9134 The Gnash maintainers have asked for a freeze exception, but the
9135 release team have not had time to reply to it yet. I hope they agree
9136 with me that Flash is important for the Debian desktop users, and thus
9137 accept the new package into Squeeze.
</p
>
9142 <title>Circular package dependencies harms apt recovery
</title>
9143 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9145 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9146 <description><p
>I discovered this while doing
9147 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9148 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9149 in Debian still got circular dependencies, and it is often claimed
9150 that apt and aptitude should be able to handle this just fine, but
9151 some times these dependency loops causes apt to fail.
</p
>
9153 <p
>An example is from todays
9154 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9155 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9156 causes perl-modules to fail to upgrade. The cause is simple. If a
9157 package fail to unpack, then only part of packages with the circular
9158 dependency might end up being unpacked when unpacking aborts, and the
9159 ones already unpacked will fail to configure in the recovery phase
9160 because its dependencies are unavailable.
</p
>
9162 <p
>In this log, the problem manifest itself with this error:
</p
>
9164 <blockquote
><pre
>
9165 dpkg: dependency problems prevent configuration of perl-modules:
9166 perl-modules depends on perl (
>=
5.10.1-
1); however:
9167 Version of perl on system is
5.10.0-
19lenny
2.
9168 dpkg: error processing perl-modules (--configure):
9169 dependency problems - leaving unconfigured
9170 </pre
></blockquote
>
9172 <p
>The perl/perl-modules circular dependency is already
9173 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9174 hopefully be solved as soon as possible, but it is not the only one,
9175 and each one of these loops in the dependency tree can cause similar
9176 failures. Of course, they only occur when there are bugs in other
9177 packages causing the unpacking to fail, but it is rather nasty when
9178 the failure of one package causes the problem to become worse because
9179 of dependency loops.
</p
>
9182 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9183 tireless effort by Bill Allombert
</a
>, the number of circular
9185 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9186 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9188 <p
>Todays testing also exposed a bug in
9189 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9190 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9191 apt-get and aptitude, the latter possibly caused by some circular
9192 dependency. Reported both to BTS to try to get someone to look at
9198 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9199 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9201 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9202 <description><p
>This is a
9203 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9205 <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
9207 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9208 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9210 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9211 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9212 and dhcp3-server-ldap in Debian use the LDAP server. The two
9213 implementations are quite different in how they use LDAP.
</p
>
9215 To get this information, I started slapd with debugging enabled and
9216 dumped the debug output to a file to get the LDAP searches performed
9217 on a Debian Edu main-server. Here is a summary.
9219 <p
><strong
>powerdns
</strong
></p
>
9221 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9222 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9225 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9226 One
"strict
" mode where the forward and reverse DNS lookups are done
9227 using the same LDAP objects, and a
"tree
" mode where the forward and
9228 reverse entries are in two different subtrees in LDAP with a structure
9229 based on the DNS names, as in tjener.intern and
9230 2.2.0.10.in-addr.arpa.
</p
>
9232 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9233 base, and uses a
"base
" scoped search for the DNS name by adding
9234 "dc=tjener,dc=intern,
" to the base with a filter for
9235 "(associateddomain=tjener.intern)
" for the forward entry and
9236 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9237 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9238 forward entries, it is looking for attributes named dnsttl, arecord,
9239 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9240 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9241 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9242 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9243 spfrecord and modifytimestamp. For reverse entries it is looking for
9244 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9245 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9246 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9247 ldapsearch commands could look like this:
</p
>
9249 <blockquote
><pre
>
9250 ldapsearch -h ldap \
9251 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9252 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9253 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9254 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9255 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9256 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9258 ldapsearch -h ldap \
9259 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9260 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9261 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9262 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9263 srvrecord naptrrecord modifytimestamp
9264 </pre
></blockquote
>
9266 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9267 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9268 example LDAP objects used there. In addition to these objects, the
9269 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9270 also exist.
</p
>
9272 <blockquote
><pre
>
9273 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9275 objectclass: dnsdomain
9276 objectclass: domainrelatedobject
9279 associateddomain: tjener.intern
9281 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9283 objectclass: dnsdomain2
9284 objectclass: domainrelatedobject
9286 ptrrecord: tjener.intern
9287 associateddomain:
2.2.0.10.in-addr.arpa
9288 </pre
></blockquote
>
9290 <p
>In strict mode, the server behaves differently. When looking for
9291 forward DNS entries, it is doing a
"subtree
" scoped search with the
9292 same base as in the tree mode for a object with filter
9293 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9294 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9295 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9296 naptrrecord and modifytimestamp. For reverse entires it also do a
9297 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9298 and the requested attributes are associateddomain, dnsttl and
9299 modifytimestamp. In short, in strict mode the objects with ptrrecord
9300 go away, and the arecord attribute in the forward object is used
9303 <p
>The forward and reverse searches can be simulated using ldapsearch
9304 like this:
</p
>
9306 <blockquote
><pre
>
9307 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9308 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9309 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9310 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9311 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9312 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9314 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9315 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9316 </pre
></blockquote
>
9318 <p
>In addition to the forward and reverse searches , there is also a
9319 search for SOA records, which behave similar to the forward and
9320 reverse lookups.
</p
>
9322 <p
>A thing to note with the PowerDNS behaviour is that it do not
9323 specify any objectclass names, and instead look for the attributes it
9324 need to generate a DNS reply. This make it able to work with any
9325 objectclass that provide the needed attributes.
</p
>
9327 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9328 dnsdomain2 schemas. The latter is used for reverse entries like
9329 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9331 <p
>In Debian Edu, we have created DNS objects using the object classes
9332 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9333 attributes) and domainrelatedobject (for associatedDomain). The use
9334 of structural object classes make it impossible to combine these
9335 classes with the object classes used by DHCP.
</p
>
9337 <p
>There are other schemas that could be used too, for example the
9338 dnszone structural object class used by Gosa and bind-sdb for the DNS
9339 attributes combined with the domainrelatedobject object class, but in
9340 this case some unused attributes would have to be included as well
9341 (zonename and relativedomainname).
</p
>
9343 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9344 mode and not use any of the existing objectclasses (dnsdomain,
9345 dnsdomain2 and dnszone) when one want to combine the DNS information
9346 with DHCP information, and instead create a auxiliary object class
9347 defined something like this (using the attributes defined for
9348 dnsdomain and dnsdomain2 or dnszone):
</p
>
9350 <blockquote
><pre
>
9351 objectclass ( some-oid NAME
'dnsDomainAux
'
9354 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9355 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9356 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9357 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9358 A6Record $ DNAMERecord
9360 </pre
></blockquote
>
9362 <p
>This will allow any object to become a DNS entry when combined with
9363 the domainrelatedobject object class, and allow any entity to include
9364 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9365 developers asking for their view on this schema and if they are
9366 interested in providing such schema with PowerDNS, and I hope my
9367 message will be accepted into their mailing list soon.
</p
>
9369 <p
><strong
>ISC dhcp
</strong
></p
>
9371 <p
>The DHCP server searches for specific objectclass and requests all
9372 the object attributes, and then uses the attributes it want. This
9373 make it harder to figure out exactly what attributes are used, but
9374 thanks to the working example in Debian Edu I can at least get an idea
9375 what is needed without having to read the source code.
</p
>
9377 <p
>In the DHCP server configuration, the LDAP base to use and the
9378 search filter to use to locate the correct dhcpServer entity is
9379 stored. These are the relevant entries from
9380 /etc/dhcp3/dhcpd.conf:
</p
>
9382 <blockquote
><pre
>
9383 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9384 ldap-dhcp-server-cn
"dhcp
";
9385 </pre
></blockquote
>
9387 <p
>The DHCP server uses this information to nest all the DHCP
9388 configuration it need. The cn
"dhcp
" is located using the given LDAP
9389 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9390 search result is this entry:
</p
>
9392 <blockquote
><pre
>
9393 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9396 objectClass: dhcpServer
9397 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9398 </pre
></blockquote
>
9400 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9401 subtree with DHCP configuration. The DHCP configuration subtree base
9402 is located using a base scope search with base
"cn=DHCP
9403 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9404 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9405 The search result is this entry:
</p
>
9407 <blockquote
><pre
>
9408 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9411 objectClass: dhcpService
9412 objectClass: dhcpOptions
9413 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9414 dhcpStatements: ddns-update-style none
9415 dhcpStatements: authoritative
9416 dhcpOption: smtp-server code
69 = array of ip-address
9417 dhcpOption: www-server code
72 = array of ip-address
9418 dhcpOption: wpad-url code
252 = text
9419 </pre
></blockquote
>
9421 <p
>Next, the entire subtree is processed, one level at the time. When
9422 all the DHCP configuration is loaded, it is ready to receive requests.
9423 The subtree in Debian Edu contain objects with object classes
9424 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9425 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9426 and information about netmasks, dynamic range etc. Leaving out the
9427 details here because it is not relevant for the focus of my
9428 investigation, which is to see if it is possible to merge dns and dhcp
9429 related computer objects.
</p
>
9431 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9432 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9433 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9434 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9435 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9438 <blockquote
><pre
>
9439 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9442 objectClass: dhcpHost
9443 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9444 dhcpStatements: fixed-address hostname
9445 </pre
></blockquote
>
9447 <p
>There is less flexiblity in the way LDAP searches are done here.
9448 The object classes need to have fixed names, and the configuration
9449 need to be stored in a fairly specific LDAP structure. On the
9450 positive side, the invidiual dhcpHost entires can be anywhere without
9451 the DN pointed to by the dhcpServer entries. The latter should make
9452 it possible to group all host entries in a subtree next to the
9453 configuration entries, and this subtree can also be shared with the
9454 DNS server if the schema proposed above is combined with the dhcpHost
9455 structural object class.
9457 <p
><strong
>Conclusion
</strong
></p
>
9459 <p
>The PowerDNS implementation seem to be very flexible when it come
9460 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9461 come to the the LDAP structure, the
"strict
" mode is very flexible,
9462 allowing DNS objects to be stored anywhere under the base cn specified
9463 in the configuration.
</p
>
9465 <p
>The DHCP implementation on the other hand is very inflexible, both
9466 regarding which LDAP schemas to use and which LDAP structure to use.
9467 I guess one could implement ones own schema, as long as the
9468 objectclasses and attributes have the names used, but this do not
9469 really help when the DHCP subtree need to have a fairly fixed
9470 structure.
</p
>
9472 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9473 this might work for Debian Edu:
</p
>
9475 <blockquote
><pre
>
9477 cn=machine-info (dhcpService) - dhcpServiceDN points here
9478 cn=dhcp (dhcpServer)
9479 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9480 cn=
10.0.2.0 (dhcpSubnet)
9481 cn=group1 (dhcpGroup/dhcpOptions)
9482 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9483 cn=
192.168.0.0 (dhcpSubnet)
9484 cn=group1 (dhcpGroup/dhcpOptions)
9485 ou=machines - PowerDNS base points here
9486 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9487 </pre
></blockquote
>
9489 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9490 entries to be in the dhcpGroup subtrees, the entries can be stored
9491 there instead of a common machines subtree, and the PowerDNS base
9492 would have to be moved one level up to the machine-info subtree.
</p
>
9494 <p
>The combined object under the machines subtree would look something
9495 like this:
</p
>
9497 <blockquote
><pre
>
9498 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9501 objectClass: dhcpHost
9502 objectclass: domainrelatedobject
9503 objectclass: dnsDomainAux
9504 associateddomain: hostname.intern
9505 arecord:
10.11.12.13
9506 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9507 dhcpStatements: fixed-address hostname.intern
9508 </pre
></blockquote
>
9510 </p
>One could even add the LTSP configuration associated with a given
9511 machine, as long as the required attributes are available in a
9512 auxiliary object class.
</p
>
9517 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9518 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9519 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9520 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9521 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9522 DHCP services in Debian Edu to use the same LDAP objects for a given
9523 computer, to avoid the possibility of having a inconsistent state for
9524 a computer in LDAP (as in DHCP but no DNS entry or the other way
9525 around) and make it easier to add computers to LDAP.
</p
>
9527 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9528 information finally found a solution that seem to work.
</p
>
9530 <p
>The old setup required three LDAP objects for a given computer.
9531 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9532 we switch powerdns to use its strict LDAP method (ldap-method=strict
9533 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9534 merged into one while making it impossible to transfer the reverse map
9535 to a slave DNS server.
</p
>
9537 <p
>If we also replace the object class used to get the DNS related
9538 attributes to one allowing these attributes to be combined with the
9539 dhcphost object class, we can merge the DNS and DHCP entries into one.
9540 I
've written such object class in the dnsdomainaux.schema file (need
9541 proper OIDs, but that is a minor issue), and tested the setup. It
9542 seem to work.
</p
>
9544 <p
>With this test setup in place, we can get away with one LDAP object
9545 for both DNS and DHCP, and even the LTSP configuration I suggested in
9546 an earlier email. The combined LDAP object will look something like
9549 <blockquote
><pre
>
9550 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9552 objectClass: dhcphost
9553 objectclass: domainrelatedobject
9554 objectclass: dnsdomainaux
9555 associateddomain: hostname.intern
9556 arecord:
10.11.12.13
9557 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9558 dhcpstatements: fixed-address hostname
9560 </pre
></blockquote
>
9562 <p
>The DNS server uses the associateddomain and arecord entries, while
9563 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9564 before asking DNS to resolve the fixed-adddress. LTSP will use
9565 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9567 <p
>I am not yet sure if I can get the DHCP server to look for its
9568 dhcphost in a different location, to allow us to put the objects
9569 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9570 that. If I can
't figure out a way to do that, we can still get rid of
9571 the hosts subtree and move all its content into the DHCP Config tree
9572 (which probably should be renamed to be more related to the new
9573 content. I suspect cn=dnsdhcp,ou=services or something like that
9574 might be a good place to put it.
</p
>
9576 <p
>If you want to help out with implementing this for Debian Edu,
9577 please contact us on debian-edu@lists.debian.org.
</p
>
9582 <title>Idea for storing LTSP configuration in LDAP
</title>
9583 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9584 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9585 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9586 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9587 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9588 clients, and that this can be used to fetch configuration from LDAP if
9589 Debian Edu choose to store configuration there.
</p
>
9591 <p
>Armed with this information, I got inspired and wrote a test module
9592 to get configuration from LDAP. The idea is to look up the MAC
9593 address of the client in LDAP, and look for attributes on the form
9594 ltspconfigsetting=value, and use this to export SETTING=value to the
9595 LTSP clients.
</p
>
9597 <p
>The goal is to be able to store the LTSP configuration attributes
9598 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9599 allowing us to store all information about a computer in one place.
</p
>
9601 <p
>This is a untested draft implementation, and I welcome feedback on
9602 this approach. A real LDAP schema for the ltspClientAux objectclass
9603 need to be written. Comments, suggestions, etc?
</p
>
9605 <blockquote
><pre
>
9606 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9608 # Fetch LTSP client settings from LDAP based on MAC address
9610 # Uses ethernet address as stored in the dhcpHost objectclass using
9611 # the dhcpHWAddress attribute or ethernet address stored in the
9612 # ieee802Device objectclass with the macAddress attribute.
9614 # This module is written to be schema agnostic, and only depend on the
9615 # existence of attribute names.
9617 # The LTSP configuration variables are saved directly using a
9618 # ltspConfig prefix and uppercasing the rest of the attribute name.
9619 # To set the SERVER variable, set the ltspConfigServer attribute.
9621 # Some LDAP schema should be created with all the relevant
9622 # configuration settings. Something like this should work:
9624 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9627 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9629 LDAPSERVER=$(debian-edu-ldapserver)
9630 if [
"$LDAPSERVER
" ] ; then
9631 LDAPBASE=$(debian-edu-ldapserver -b)
9632 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9633 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9634 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9635 grep
'^ltspConfig
' | while read attr value ; do
9636 # Remove prefix and convert to upper case
9637 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9638 # bass value on to clients
9639 eval
"$attr=$value; export $attr
"
9643 </pre
></blockquote
>
9645 <p
>I
'm not sure this shell construction will work, because I suspect
9646 the while block might end up in a subshell causing the variables set
9647 there to not show up in ltsp-config, but if that is the case I am sure
9648 the code can be restructured to make sure the variables are passed on.
9649 I expect that can be solved with some testing. :)
</p
>
9651 <p
>If you want to help out with implementing this for Debian Edu,
9652 please contact us on debian-edu@lists.debian.org.
</p
>
9654 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9655 configuration in LDAP that was created around year
2000 by
9656 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9657 Xperience, Inc.,
2000</a
>. I found its
9658 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9659 personal home page over at redhat.com.
</p
>
9664 <title>jXplorer, a very nice LDAP GUI
</title>
9665 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9667 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9668 <description><p
>Since
9669 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9670 last post
</a
> about available LDAP tools in Debian, I was told about a
9671 LDAP GUI that is even better than luma. The java application
9672 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9673 moving LDAP objects and subtrees using drag-and-drop, and can
9674 authenticate using Kerberos. I have only tested the Kerberos
9675 authentication, but do not have a LDAP setup allowing me to rewrite
9676 LDAP with my test user yet. It is
9677 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9678 Debian
</a
> testing and unstable at the moment. The only problem I
9679 have with it is how it handle errors. If something go wrong, its
9680 non-intuitive behaviour require me to go through some query work list
9681 and remove the failing query. Nothing big, but very annoying.
</p
>
9686 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9687 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9688 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9689 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9690 <description><p
>Here is a short update on my
<a
9691 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9692 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9693 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9694 not reporting the status for KDE, because the upgrade crashes when
9695 aptitude try because of missing conflicts
9696 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9697 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9699 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9700 complete list of the installed packages. Based on this I see these
9701 differences when I did a test run today. As usual, I do not really
9702 know what the correct set of packages would be, but thought it best to
9703 publish the difference.
</p
>
9705 <p
>Installed using apt-get, missing with aptitude
</p
>
9707 <blockquote
><p
>
9708 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9709 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9710 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9711 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9712 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9713 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9714 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9715 python-gtkmozembed svgalibg1 xserver-xephyr zip
9716 </p
></blockquote
>
9718 <p
>Installed using apt-get, removed with aptitude
</p
>
9720 <blockquote
><p
>
9721 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9722 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9723 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9724 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9725 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9726 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9727 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9728 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9729 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9730 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9731 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9732 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9733 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9734 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9735 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9736 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9737 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9738 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9739 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9740 mysql-common swfdec-gnome totem-gstreamer wodim
9741 </p
></blockquote
>
9743 <p
>Installed using aptitude, missing with apt-get
</p
>
9745 <blockquote
><p
>
9746 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9747 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9748 xserver-xorg-input-all xserver-xorg-input-evdev
9749 xserver-xorg-input-kbd xserver-xorg-input-mouse
9750 xserver-xorg-input-synaptics xserver-xorg-video-all
9751 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9752 xserver-xorg-video-chips xserver-xorg-video-cirrus
9753 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9754 xserver-xorg-video-glint xserver-xorg-video-i128
9755 xserver-xorg-video-i740 xserver-xorg-video-mach64
9756 xserver-xorg-video-mga xserver-xorg-video-neomagic
9757 xserver-xorg-video-nouveau xserver-xorg-video-nv
9758 xserver-xorg-video-r128 xserver-xorg-video-radeon
9759 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9760 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9761 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9762 xserver-xorg-video-sis xserver-xorg-video-sisusb
9763 xserver-xorg-video-tdfx xserver-xorg-video-tga
9764 xserver-xorg-video-trident xserver-xorg-video-tseng
9765 xserver-xorg-video-vesa xserver-xorg-video-vmware
9766 xserver-xorg-video-voodoo
9767 </p
></blockquote
>
9769 <p
>Installed using aptitude, removed with apt-get
</p
>
9771 <blockquote
><p
>
9772 deskbar-applet xserver-xorg xserver-xorg-core
9773 xserver-xorg-input-wacom xserver-xorg-video-intel
9774 xserver-xorg-video-openchrome
9775 </p
></blockquote
>
9777 <p
>I was told on IRC that the xorg-xserver package was
9778 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9779 in git
</a
> today to try to get apt-get to not remove xorg completely.
9780 No idea when it hits Squeeze, but when it does I hope it will reduce
9781 the difference somewhat.
9786 <title>LUMA, a very nice LDAP GUI
</title>
9787 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9789 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9790 <description><p
>The last few days I have been looking into the status of the LDAP
9791 directory in Debian Edu, and in the process I started to miss a GUI
9792 tool to browse the LDAP tree. The only one I was able to find in
9793 Debian/Squeeze and Lenny is
9794 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9795 be a great tool to get a overview of the current LDAP directory
9796 populated by default in Skolelinux. Thanks to it, I have been able to
9797 find empty and obsolete subtrees, misplaced objects and duplicate
9798 objects. It will be installed by default in Debian/Squeeze. If you
9799 are working with LDAP, give it a go. :)
</p
>
9801 <p
>I did notice one problem with it I have not had time to report to
9802 the BTS yet. There is no .desktop file in the package, so the tool do
9803 not show up in the Gnome and KDE menus, but only deep down in in the
9804 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9807 <p
>I have not yet been able to get it to modify the tree yet. I would
9808 like to move objects and remove subtrees directly in the GUI, but have
9809 not found a way to do that with LUMA yet. So in the mean time, I use
9810 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9812 <p
>If you have tips on other GUI tools for LDAP that might be useful
9813 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9815 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9816 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9817 useful GUI alternative. It seem like a good tool, but is unmaintained
9818 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9819 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9824 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9825 <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>
9826 <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>
9827 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9828 <description><p
>A while back, I
9829 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9830 about the fact
</a
> that it is not possible with the provided schemas
9831 for storing DNS and DHCP information in LDAP to combine the two sets
9832 of information into one LDAP object representing a computer.
</p
>
9834 <p
>In the mean time, I discovered that a simple fix would be to make
9835 the dhcpHost object class auxiliary, to allow it to be combined with
9836 the dNSDomain object class, and thus forming one object for one
9837 computer when storing both DHCP and DNS information in LDAP.
</p
>
9839 <p
>If I understand this correctly, it is not safe to do this change
9840 without also changing the assigned number for the object class, and I
9841 do not know enough about LDAP schema design to do that properly for
9842 Debian Edu.
</p
>
9844 <p
>Anyway, for future reference, this is how I believe we could change
9846 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9847 schema
</a
> to solve at least part of the problem with the LDAP schemas
9848 available today from IETF.
</p
>
9851 --- dhcp.schema (revision
65192)
9852 +++ dhcp.schema (working copy)
9854 objectclass (
2.16.840.1.113719.1.203.6.6
9855 NAME
'dhcpHost
'
9856 DESC
'This represents information about a particular client
'
9860 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9861 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9864 <p
>I very much welcome clues on how to do this properly for Debian
9865 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9866 package, and should thus be free to rewrite it as we see fit.
</p
>
9868 <p
>If you want to help out with implementing this for Debian Edu,
9869 please contact us on debian-edu@lists.debian.org.
</p
>
9874 <title>Calling tasksel like the installer, while still getting useful output
</title>
9875 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9876 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9877 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9878 <description><p
>A few times I have had the need to simulate the way tasksel
9879 installs packages during the normal debian-installer run. Until now,
9880 I have ended up letting tasksel do the work, with the annoying problem
9881 of not getting any feedback at all when something fails (like a
9882 conffile question from dpkg or a download that fails), using code like
9885 <blockquote
><pre
>
9886 export DEBIAN_FRONTEND=noninteractive
9887 tasksel --new-install
9888 </pre
></blockquote
>
9890 This would invoke tasksel, let its automatic task selection pick the
9891 tasks to install, and continue to install the requested tasks without
9892 any output what so ever.
9894 Recently I revisited this problem while working on the automatic
9895 package upgrade testing, because tasksel would some times hang without
9896 any useful feedback, and I want to see what is going on when it
9897 happen. Then it occured to me, I can parse the output from tasksel
9898 when asked to run in test mode, and use that aptitude command line
9899 printed by tasksel then to simulate the tasksel run. I ended up using
9902 <blockquote
><pre
>
9903 export DEBIAN_FRONTEND=noninteractive
9904 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9906 </pre
></blockquote
>
9908 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9909 --without-recommends -o APT::Install-Recommends=no -y install
9910 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9911 ~pimportant
</tt
>", which will install the gnome desktop task, the
9912 laptop task and all packages with priority standard , required and
9913 important, just like tasksel would have done it during
9914 installation.
</p
>
9916 <p
>A better approach is probably to extend tasksel to be able to
9917 install packages without using debconf-apt-progress, for use cases
9918 like this.
</p
>
9923 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9924 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9926 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9927 <description><p
>My
9928 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9929 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9930 finally made the upgrade logs available from
9931 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9932 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9933 apt and aptitude, and found their differences interesting. This time
9934 I will only focus on their removal plans.
</p
>
9936 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9937 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9938 surprising part is that it want to remove xorg and all
9939 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9940 sure why. When asking aptitude to do the same, it want to remove
129
9941 packages, but most of them are library packages I suspect are no
9942 longer needed. Both of them want to remove bluetooth packages, which
9943 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9945 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9946 which seem like a bad idea and xorg the same way as with Gnome. Asking
9947 aptitude for the same, it wants to remove
192 packages, none which are
9948 too surprising.
</p
>
9950 <p
>I guess the removal of xorg during upgrades should be investigated
9951 and avoided, and perhaps others as well. Here are the complete list
9952 of planned removals. The complete logs is available from the URL
9953 above. Note if you want to repeat these tests, that the upgrade test
9954 for kde+apt-get hung in the tasksel setup because of dpkg asking
9955 conffile questions. No idea why. I worked around it by using
9956 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9959 <p
><b
>apt-get gnome
72</b
>
9960 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9961 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9962 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9963 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9964 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9965 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9966 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9967 xserver-xorg-input-kbd xserver-xorg-input-mouse
9968 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9969 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9970 xserver-xorg-video-ati xserver-xorg-video-chips
9971 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9972 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9973 xserver-xorg-video-glint xserver-xorg-video-i128
9974 xserver-xorg-video-i740 xserver-xorg-video-imstt
9975 xserver-xorg-video-intel xserver-xorg-video-mach64
9976 xserver-xorg-video-mga xserver-xorg-video-neomagic
9977 xserver-xorg-video-nsc xserver-xorg-video-nv
9978 xserver-xorg-video-openchrome xserver-xorg-video-r128
9979 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9980 xserver-xorg-video-rendition xserver-xorg-video-s3
9981 xserver-xorg-video-s3virge xserver-xorg-video-savage
9982 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9983 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9984 xserver-xorg-video-tga xserver-xorg-video-trident
9985 xserver-xorg-video-tseng xserver-xorg-video-v4l
9986 xserver-xorg-video-vesa xserver-xorg-video-vga
9987 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9988 xulrunner-
1.9-gnome-support
</p
>
9990 <p
><b
>aptitude gnome
129</b
>
9992 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9993 djvulibre-desktop finger gnome-app-install gnome-mount
9994 gnome-network-admin gnome-spell gnome-vfs-obexftp
9995 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9996 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9997 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9998 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9999 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10000 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10001 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10002 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10003 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10004 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10005 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10006 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10007 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10008 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10009 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10010 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10011 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10012 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10013 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10014 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10015 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10016 openoffice.org-writer2latex openssl-blacklist p7zip
10017 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10018 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10019 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10020 swfdec-mozilla totem-gstreamer update-manager wodim
10021 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10022 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10025 <p
><b
>apt-get kde
82</b
>
10027 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10028 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10029 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10030 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10031 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10032 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10033 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10034 xserver-xorg-input-kbd xserver-xorg-input-mouse
10035 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10036 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10037 xserver-xorg-video-ati xserver-xorg-video-chips
10038 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10039 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10040 xserver-xorg-video-glint xserver-xorg-video-i128
10041 xserver-xorg-video-i740 xserver-xorg-video-imstt
10042 xserver-xorg-video-intel xserver-xorg-video-mach64
10043 xserver-xorg-video-mga xserver-xorg-video-neomagic
10044 xserver-xorg-video-nsc xserver-xorg-video-nv
10045 xserver-xorg-video-openchrome xserver-xorg-video-r128
10046 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10047 xserver-xorg-video-rendition xserver-xorg-video-s3
10048 xserver-xorg-video-s3virge xserver-xorg-video-savage
10049 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10050 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10051 xserver-xorg-video-tga xserver-xorg-video-trident
10052 xserver-xorg-video-tseng xserver-xorg-video-v4l
10053 xserver-xorg-video-vesa xserver-xorg-video-vga
10054 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
10056 <p
><b
>aptitude kde
192</b
>
10057 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
10058 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10059 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10060 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10061 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10062 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10063 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10064 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10065 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10066 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10067 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10068 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10069 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10070 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10071 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10072 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10073 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10074 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10075 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
10076 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10077 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10078 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
10079 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10080 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10081 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10082 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10083 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10084 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
10085 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
10086 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10087 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10088 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10089 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10090 texlive-common texlive-doc-base texlive-fonts-recommended
10091 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10092 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10093 xulrunner-
1.9</p
>
10099 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10100 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10102 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10103 <description><p
>The last few days I have done some upgrade testing in Debian, to
10104 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10105 have been discovered and reported in the process
10106 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10107 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10108 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10109 kdebase-workspace-data), and to get a more regular testing going on, I
10110 am working on a script to automate the test.
</p
>
10112 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10113 Gnome or KDE desktop installation inside the chroot before upgrading
10114 it. To ensure no services are started in the chroot, a policy-rc.d
10115 script is inserted. To make sure tasksel believe it is to install a
10116 desktop on a laptop, the tasksel tests are replaced in the chroot
10117 (only acceptable because this is a throw-away chroot).
</p
>
10119 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10120 currently always fail because udev refuses to upgrade with the kernel
10121 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10122 is created. The bug report
10123 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10124 this problem do not trigger in a chroot, but I touch the file anyway
10125 to make sure the upgrade go well. Testing on virtual and real
10126 hardware have failed me because of udev so far, and creating this file
10127 do the trick in such settings anyway. This is a
10128 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10129 issue
</a
> and the current udev behaviour is intended by the udev
10130 maintainer because he lack the resources to rewrite udev to keep
10131 working with old kernels or something like that. I really wish the
10132 udev upstream would keep udev backwards compatible, to avoid such
10133 upgrade problem, but given that they fail to do so, I guess
10134 documenting the way out of this mess is the best option we got for
10135 Debian Squeeze.
</p
>
10137 <p
>Anyway, back to the task at hand, testing upgrades. This test
10138 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10141 <blockquote
><pre
>
10145 if [
"$
1" ] ; then
10154 exec
&lt; /dev/null
10156 mirror=http://ftp.skolelinux.org/debian
10157 tmpdir=chroot-$from-upgrade-$to-$desktop
10159 debootstrap $from $tmpdir $mirror
10160 chroot $tmpdir aptitude update
10161 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10165 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10167 umount $tmpdir/proc
10169 mount -t proc proc $tmpdir/proc
10170 # Make sure proc is unmounted also on failure
10171 trap exit_cleanup EXIT INT
10173 chroot $tmpdir aptitude -y install debconf-utils
10175 # Make sure tasksel autoselection trigger. It need the test scripts
10176 # to return the correct answers.
10177 echo tasksel tasksel/desktop multiselect $desktop | \
10178 chroot $tmpdir debconf-set-selections
10180 # Include the desktop and laptop task
10181 for test in desktop laptop ; do
10182 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10186 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10189 DEBIAN_FRONTEND=noninteractive
10190 DEBIAN_PRIORITY=critical
10191 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10192 chroot $tmpdir tasksel --new-install
10194 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10195 chroot $tmpdir aptitude update
10196 touch $tmpdir/etc/udev/kernel-upgrade
10197 chroot $tmpdir aptitude -y dist-upgrade
10199 </pre
></blockquote
>
10201 <p
>I suspect it would be useful to test upgrades with both apt-get and
10202 with aptitude, but I have not had time to look at how they behave
10203 differently so far. I hope to get a cron job running to do the test
10204 regularly and post the result on the web. The Gnome upgrade currently
10205 work, while the KDE upgrade fail because of the bug in
10206 kdebase-workspace-data
</p
>
10208 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10209 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10210 post, so I will refrain from trying. I can report that for Gnome,
10211 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10212 remove and
1 not upgraded and
1024MB need to be downloaded while for
10213 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10214 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10216 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10217 is able to migrate to dependency based boot sequencing and parallel
10218 booting without a hitch. Was unsure if there were still bugs with
10219 packages failing to clean up their obsolete init.d script during
10220 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10221 packages.
</p
>
10226 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10227 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10229 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10230 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10231 scripts to migrate (some of) their operations to upstart job while
10232 keeping the init.d for hurd and kfreebsd. The packages with such
10233 needs will need a way to get their init.d scripts to behave
10234 differently when used with sysvinit and with upstart. Because of
10235 this, I had a look at the environment variables set when a init.d
10236 script is running under upstart, and when it is not.
</p
>
10238 <p
>With upstart, I notice these environment variables are set when a
10239 script is started from rcS.d/ (ignoring some irrelevant ones like
10240 COLUMNS):
</p
>
10242 <blockquote
><pre
>
10248 UPSTART_EVENTS=startup
10250 UPSTART_JOB=rc-sysinit
10251 </pre
></blockquote
>
10253 <p
>With sysvinit, these environment variables are set for the same
10256 <blockquote
><pre
>
10257 INIT_VERSION=sysvinit-
2.88
10262 </pre
></blockquote
>
10264 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10265 sysvinit are not set by upstart. Not sure if it is intentional or not
10266 to not be compatible with sysvinit in this regard.
</p
>
10268 <p
>For scripts needing to behave differently when upstart is used,
10269 looking for the UPSTART_JOB environment variable seem to be a good
10275 <title>A manual for standards wars...
</title>
10276 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10278 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10279 <description><p
>Via the
10280 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10281 of Rob Weir
</a
> I came across the very interesting essay named
10282 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10283 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10284 following the standards wars of today.
</p
>
10289 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10290 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10291 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10292 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10293 <description><p
>When using sitesummary at a site to track machines, it is possible
10294 to get a list of the machine types in use thanks to the DMI
10295 information extracted from each machine. The script to do so is
10296 included in the sitesummary package, and here is example output from
10297 the Skolelinux build servers:
</p
>
10299 <blockquote
><pre
>
10300 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10302 Dell Computer Corporation
1
10305 eserver xSeries
345 -[
8670M1X]-
1
10309 </pre
></blockquote
>
10311 <p
>The quality of the report depend on the quality of the DMI tables
10312 provided in each machine. Here there are Intel machines without model
10313 information listed with Intel as vendor and no model, and virtual Xen
10314 machines listed as [no-dmi-info]. One can add -l as a command line
10315 option to list the individual machines.
</p
>
10317 <p
>A larger list is
10318 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10319 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10320 provide the basic sitesummary report publicly. In their report there
10321 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10322 their machines, and as sitesummary is available in both distributions,
10323 it is trivial to get all of them to report to the same central
10324 collector.
</p
>
10329 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10330 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10331 <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>
10332 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10333 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10334 start at boot when an NVidia video card is used is handled. The
10335 problem seem to be that the nvidia X.org driver uses a long time to
10336 initialize, and this duration is longer than kdm is configured to
10339 <p
>I came across two bugs related to this issue,
10340 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10341 against initscripts and passed on to nvidia-glx when it became obvious
10342 that the nvidia drivers were involved, and
10343 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10344 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10346 <p
>To me, it seem that no-one is interested in actually solving the
10347 problem nvidia video card owners experience and make sure the Debian
10348 distribution work out of the box for these users. The nvidia driver
10349 maintainers expect kdm to be set up to wait longer, while kdm expect
10350 the nvidia driver maintainers to fix the driver to start faster, and
10351 while they wait for each other I guess the users end up switching to a
10352 distribution that work for them. I have no idea what the solution is,
10353 but I am pretty sure that waiting for each other is not it.
</p
>
10355 <p
>I wonder why we end up handling bugs this way.
</p
>
10360 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10361 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10363 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10364 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10365 The feature seem to hold up pretty well, but three fairly serious
10366 issues are known and should be solved:
10368 <p
><ul
>
10370 <li
>The wicd package seen to
10371 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10372 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10373 parallel booting is enabled. No idea why, but the wicd maintainer
10374 seem to be on the case.
</li
>
10376 <li
>The nvidia X driver seem to
10377 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10378 triggered more easily when parallel booting is in effect. The
10379 maintainer is on the case.
</li
>
10381 <li
>The sysv-rc package fail to properly enable dependency based boot
10382 sequencing (the shutdown is broken) when old file-rc users
10383 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10384 sysv-rc. One way to solve it would be for file-rc to create
10385 /etc/init.d/.legacy-bootordering, and another is to try to make
10386 sysv-rc more robust. Will investigate some more and probably upload a
10387 workaround in sysv-rc to help those trying to move from file-rc to
10388 sysv-rc get a working shutdown.
</li
>
10390 </ul
></p
>
10392 <p
>All in all not many surprising issues, and all of them seem
10393 solvable before Squeeze is released. In addition to these there are
10394 some packages with bugs in their dependencies and run level settings,
10395 which I expect will be fixed in a reasonable time span.
</p
>
10397 <p
>If you report any problems with dependencies in init.d scripts to
10398 the BTS, please usertag the report to get it to show up at
10399 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10400 list of usertagged bugs related to this
</a
>.
</p
>
10402 <p
>Update: Correct bug number to file-rc issue.
</p
>
10407 <title>More flexible firmware handling in debian-installer
</title>
10408 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10410 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10411 <description><p
>After a long break from debian-installer development, I finally
10412 found time today to return to the project. Having to spend less time
10413 working dependency based boot in debian, as it is almost complete now,
10414 definitely helped freeing some time.
</p
>
10416 <p
>A while back, I ran into a problem while working on Debian Edu. We
10417 include some firmware packages on the Debian Edu CDs, those needed to
10418 get disk and network controllers working. Without having these
10419 firmware packages available during installation, it is impossible to
10420 install Debian Edu on the given machine, and because our target group
10421 are non-technical people, asking them to provide firmware packages on
10422 an external medium is a support pain. Initially, I expected it to be
10423 enough to include the firmware packages on the CD to get
10424 debian-installer to find and use them. This proved to be wrong.
10425 Next, I hoped it was enough to symlink the relevant firmware packages
10426 to some useful location on the CD (tried /cdrom/ and
10427 /cdrom/firmware/). This also proved to not work, and at this point I
10428 found time to look at the debian-installer code to figure out what was
10429 going to work.
</p
>
10431 <p
>The firmware loading code is in the hw-detect package, and a closer
10432 look revealed that it would only look for firmware packages outside
10433 the installation media, so the CD was never checked for firmware
10434 packages. It would only check USB sticks, floppies and other
10435 "external
" media devices. Today I changed it to also look in the
10436 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10437 solve the problem I ran into with Debian edu. I also changed it to
10438 look in /firmware/, to make sure the installer also find firmware
10439 provided in the initrd when booting the installer via PXE, to allow us
10440 to provide the same feature in the PXE setup included in Debian
10443 <p
>To make sure firmware deb packages with a license questions are not
10444 activated without asking if the license is accepted, I extended
10445 hw-detect to look for preinst scripts in the firmware packages, and
10446 run these before activating the firmware during installation. The
10447 license question is asked using debconf in the preinst, so this should
10448 solve the issue for the firmware packages I have looked at so far.
</p
>
10450 <p
>If you want to discuss the details of these features, please
10451 contact us on debian-boot@lists.debian.org.
</p
>
10456 <title>Parallellized boot is now the default in Debian/unstable
</title>
10457 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10459 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10460 <description><p
>Since this evening, parallel booting is the default in
10461 Debian/unstable for machines using dependency based boot sequencing.
10462 Apparently the testing of concurrent booting has been wider than
10463 expected, if I am to believe the
10464 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10465 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10466 with the feature this weekend, to give us some time to detect any
10467 remaining problems before Squeeze is frozen. If serious problems are
10468 detected, it is simple to change the default back to sequential boot.
10469 The upload of the new sysvinit package also activate a new upstream
10472 More information about
10473 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10474 based boot sequencing
</a
> is available from the Debian wiki. It is
10475 currently possible to disable parallel booting when one run into
10476 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10478 <blockquote
><pre
>
10480 </pre
></blockquote
>
10482 <p
>If you report any problems with dependencies in init.d scripts to
10483 the BTS, please usertag the report to get it to show up at
10484 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10485 list of usertagged bugs related to this
</a
>.
</p
>
10490 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10491 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10493 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10494 <description><p
>In the recent Debian Edu versions, the
10495 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10496 system
</a
> is used to keep track of the machines in the school
10497 network. Each machine will automatically report its status to the
10498 central server after boot and once per night. The network setup is
10499 also reported, and using this information it is possible to get the
10500 MAC address of all network interfaces in the machines. This is useful
10501 to update the DHCP configuration.
</p
>
10503 <p
>To give some idea how to use sitesummary, here is a one-liner to
10504 ist all MAC addresses of all machines reporting to sitesummary. Run
10505 this on the collector host:
</p
>
10507 <blockquote
><pre
>
10508 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10509 </pre
></blockquote
>
10511 <p
>This will list all MAC addresses assosiated with all machine, one
10512 line per machine and with space between the MAC addresses.
</p
>
10514 <p
>To allow system administrators easier job at adding static DHCP
10515 addresses for hosts, it would be possible to extend this to fetch
10516 machine information from sitesummary and update the DHCP and DNS
10517 tables in LDAP using this information. Such tool is unfortunately not
10518 written yet.
</p
>
10523 <title>systemd, an interesting alternative to upstart
</title>
10524 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10526 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10527 <description><p
>The last few days a new boot system called
10528 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10530 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10532 to the free software world. I have not yet had time to play around
10533 with it, but it seem to be a very interesting alternative to
10534 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10535 a good alternative for Debian when we are able to switch to an event
10536 based boot system. Tollef is
10537 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10538 systemd into Debian, and I look forward to seeing how well it work. I
10539 like the fact that systemd handles init.d scripts with dependency
10540 information natively, allowing them to run in parallel where upstart
10541 at the moment do not.
</p
>
10543 <p
>Unfortunately do systemd have the same problem as upstart regarding
10544 platform support. It only work on recent Linux kernels, and also need
10545 some new kernel features enabled to function properly. This means
10546 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10547 system. Not sure how that will be handled if systemd proves to be the
10548 way forward.
</p
>
10550 <p
>In the mean time, based on the
10551 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10552 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10553 decided to enable full parallel booting as the default in Debian as
10554 soon as possible (probably this weekend or early next week), to see if
10555 there are any remaining serious bugs in the init.d dependencies. A
10556 new version of the sysvinit package implementing this change is
10557 already in experimental. If all go well, Squeeze will be released
10558 with parallel booting enabled by default.
</p
>
10563 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10564 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10565 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10566 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10567 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10568 complete, so complete that it is actually possible to run all the
10569 init.d scripts in parallell based on these dependencies. If you want
10570 to test your Squeeze system, make sure
10571 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10572 based boot sequencing
</a
> is enabled, and add this line to
10573 /etc/default/rcS:
</p
>
10575 <blockquote
><pre
>
10576 CONCURRENCY=makefile
10577 </pre
></blockquote
>
10579 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10580 scripts in parallel using the dependency information stored in
10581 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10582 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10583 to try to start the kdm and gdm scripts as early as possible, and will
10584 start the facilities required by kdm or gdm as early as possible to
10585 make this happen.
</p
>
10587 <p
>Give it a try, and see if you like the result. If some services
10588 fail to start properly, it is most likely because they have incomplete
10589 init.d script dependencies in their startup script (or some of their
10590 dependent scripts have incomplete dependencies). Report bugs and get
10591 the package maintainers to fix it. :)
</p
>
10593 <p
>Running scripts in parallel could be the default in Debian when we
10594 manage to get the init.d script dependencies complete and correct. I
10595 expect we will get there in Squeeze+
1, if we get manage to test and
10596 fix the remaining issues.
</p
>
10598 <p
>If you report any problems with dependencies in init.d scripts to
10599 the BTS, please usertag the report to get it to show up at
10600 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10601 list of usertagged bugs related to this
</a
>.
</p
>
10606 <title>Debian has switched to dependency based boot sequencing
</title>
10607 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10609 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10610 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10611 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10612 have been migrated to using dependency based boot sequencing. This
10613 conclude work me and others have been doing for the last three days.
10614 It feels great to see this finally part of the default Debian
10615 installation. Now we just need to weed out the last few problems that
10616 are bound to show up, to get everything ready for Squeeze.
</p
>
10618 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10619 fixing the more fundamental problem of handing the event based
10620 non-predictable kernel in the early boot.
</p
>
10625 <title>Taking over sysvinit development
</title>
10626 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10628 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10629 <description><p
>After several years of frustration with the lack of activity from
10630 the existing sysvinit upstream developer, I decided a few weeks ago to
10631 take over the package and become the new upstream. The number of
10632 patches to track for the Debian package was becoming a burden, and the
10633 lack of synchronization between the distribution made it hard to keep
10634 the package up to date.
</p
>
10636 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10637 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10638 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10639 and Fedora), based on the patches currently in use in these
10640 distributions. We Debian maintainers plan to move to this tarball as
10641 the new upstream as soon as we find time to do the merge. Since the
10642 new tarball was created, we agreed with Werner at SuSe to make a new
10643 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10644 development there. The project is registered and currently waiting
10645 for approval by the Savannah administrators, and as soon as it is
10646 approved, we will import the old versions from svn and continue
10647 working on the future release.
</p
>
10649 <p
>It is a bit ironic that this is done now, when some of the involved
10650 distributions are moving to upstart as a syvinit replacement.
</p
>
10655 <title>Debian boots quicker and quicker
</title>
10656 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10658 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10659 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10660 people involved in the boot system on Debian and Ubuntu, to see if we
10661 could find more ways to speed up the boot system. This was an Ubuntu
10663 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10664 gathering
</a
>. It was quite productive. We also discussed the future
10665 of boot systems, and ways to handle the increasing number of boot
10666 issues introduced by the Linux kernel becoming more and more
10667 asynchronous and event base. The Ubuntu approach using udev and
10668 upstart might be a good way forward. Time will show.
</p
>
10670 <p
>Anyway, there are a few ways at the moment to speed up the boot
10671 process in Debian. All of these should be applied to get a quick
10676 <li
>Use dash as /bin/sh.
</li
>
10678 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10679 clock is in UTC.
</li
>
10681 <li
>Install and activate the insserv package to enable
10682 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10683 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10687 These points are based on the Google summer of code work done by
10688 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10689 Villegas
</a
>.
10691 <p
>Support for makefile-style concurrency during boot was uploaded to
10692 unstable yesterday. When we tested it, we were able to cut
6 seconds
10693 from the boot sequence. It depend on very correct dependency
10694 declaration in all init.d scripts, so I expect us to find edge cases
10695 where the dependences in some scripts are slightly wrong when we start
10696 using this.
</p
>
10698 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10699 introduced by Raphael Geissert today, one that could affect the
10700 startup speed as well. Instead of starting some scripts concurrently
10701 from rcS.d/ and another set of scripts from rc2.d/, it would be
10702 possible to run a of them in the same process. A quick way to test
10703 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10704 insserv
'. Will need to test if that work. :)
</p
>
10709 <title>BSAs påstander om piratkopiering møter motstand
</title>
10710 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10711 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10712 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10713 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10714 programvareselskapene som Microsoft og Apple, publisert en rapport der
10715 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10716 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10718 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10719 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10720 dagene. Et spesielt interessant kommentar fra Sverige,
10721 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10722 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10725 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10726 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10727 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10728 exakta
", säger BSAs Sverigechef John Hugosson.
10729 </blockquote
>
10731 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10732 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10733 piracy figures need a shot of reality
</a
> og
<a
10734 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10735 Copyright Treaty Work?
</a
></p
>
10737 <p
>Fant lenkene via
<a
10738 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10739 på Slashdot
</a
>.
</p
>
10744 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10745 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10746 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10747 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10748 <description><p
>Kom over
10749 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10750 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10751 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10752 jobber til daglig. En rask opptelling forteller meg at vi har
490
10753 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10754 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10755 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10760 <title>Kryptert harddisk - naturligvis
</title>
10761 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10763 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10764 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10765 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10766 når en tar tap av arbeidstid, fortrolige dokumenter,
10767 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10768 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10769 til at jeg har kryptert harddisken på både kontormaskinen og min
10770 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10771 komme på avveie, den første informasjon relatert til jobben min ved
10772 Universitetet i Oslo, og den andre relatert til blant annet
10773 foreningsarbeide. Kryptering av diskene gjør at det er lite
10774 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10775 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10776 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10777 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10778 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10779 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10780 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10781 det er gjort slik jeg gjør det er minimale, og gevinstene er
10782 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10783 maskinen reinstalleres og alt er tapt.
</p
>
10785 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10786 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10787 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10788 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10789 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10790 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10791 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10792 betydelige.
</p
>
10797 <title>Two projects that have improved the quality of free software a lot
</title>
10798 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10799 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10800 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10801 <description><p
>There are two software projects that have had huge influence on the
10802 quality of free software, and I wanted to mention both in case someone
10803 do not yet know them.
</p
>
10805 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10806 tool to detect and expose errors in the memory handling of programs.
10807 It is easy to use, all one need to do is to run
'valgrind program
',
10808 and it will report any problems on stdout. It is even better if the
10809 program include debug information. With debug information, it is able
10810 to report the source file name and line number where the problem
10811 occurs. It can report things like
'reading past memory block in file
10812 X line N, the memory block was allocated in file Y, line M
', and
10813 'using uninitialised value in control logic
'. This tool has made it
10814 trivial to investigate reproducible crash bugs in programs, and have
10815 reduced the number of this kind of bugs in free software a lot.
10817 <p
>The second one is
10818 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10819 a source code checker. It is able to process the source of a program
10820 and find problems in the logic without running the program. It
10821 started out as the Stanford Checker and became well known when it was
10822 used to find bugs in the Linux kernel. It is now a commercial tool
10823 and the company behind it is running
10824 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10825 free software community, where a lot of free software projects get
10826 their source checked for free. Several thousand defects have been
10827 found and fixed so far. It can find errors like
'lock L taken in file
10828 X line N is never released if exiting in line M
', or
'the code in file
10829 Y lines O to P can never be executed
'. The projects included in the
10830 community service project have managed to get rid of a lot of
10831 reliability problems thanks to Coverity.
</p
>
10833 <p
>I believe tools like this, that are able to automatically find
10834 errors in the source, are vital to improve the quality of software and
10835 make sure we can get rid of the crashing and failing software we are
10836 surrounded by today.
</p
>
10841 <title>No patch is not better than a useless patch
</title>
10842 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10843 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10844 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10845 <description><p
>Julien Blache
10846 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10847 patch is better than a useless patch
</a
>. I completely disagree, as a
10848 patch allow one to discuss a concrete and proposed solution, and also
10849 prove that the issue at hand is important enough for someone to spent
10850 time on fixing it. No patch do not provide any of these positive
10851 properties.
</p
>
10856 <title>Standardize on protocols and formats, not vendors and applications
</title>
10857 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10858 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10859 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10860 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10861 very good one to form a long lived computer infrastructure. It is the
10862 simple one, lost by many in todays computer industry: Standardize on
10863 open network protocols and open exchange/storage formats, not applications.
10864 Applications come and go, while protocols and files tend to stay, and
10865 thus one want to make it easy to change application and vendor, while
10866 avoiding conversion costs and locking users to a specific platform or
10867 application.
</p
>
10869 <p
>This approach make it possible to replace the client applications
10870 independently of the server applications. One can even allow users to
10871 use several different applications as long as they handle the selected
10872 protocol and format. In the normal case, only one client application
10873 is recommended and users only get help if they choose to use this
10874 application, but those that want to deviate from the easy path are not
10875 blocked from doing so.
</p
>
10877 <p
>It also allow us to replace the server side without forcing the
10878 users to replace their applications, and thus allow us to select the
10879 best server implementation at any moment, when scale and resouce
10880 requirements change.
</p
>
10882 <p
>I strongly recommend standardizing - on open network protocols and
10883 open formats, but I would never recommend standardizing on a single
10884 application that do not use open network protocol or open formats.
</p
>
10889 <title>Returning from Skolelinux developer gathering
</title>
10890 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10891 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10892 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10893 <description><p
>I
'm sitting on the train going home from this weekends Debian
10894 Edu/Skolelinux development gathering. I got a bit done tuning the
10895 desktop, and looked into the dynamic service location protocol
10896 implementation avahi. It look like it could be useful for us. Almost
10897 30 people participated, and I believe it was a great environment to
10898 get to know the Skolelinux system. Walter Bender, involved in the
10899 development of the Sugar educational platform, presented his stuff and
10900 also helped me improve my OLPC installation. He also showed me that
10901 his Turtle Art application can be used in standalone mode, and we
10902 agreed that I would help getting it packaged for Debian. As a
10903 standalone application it would be great for Debian Edu. We also
10904 tried to get the video conferencing working with two OLPCs, but that
10905 proved to be too hard for us. The application seem to need more work
10906 before it is ready for me. I look forward to getting home and relax
10912 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10913 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10915 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10916 <description><p
>The state of standardized LDAP schemas on Linux is far from
10917 optimal. There is RFC
2307 documenting one way to store NIS maps in
10918 LDAP, and a modified version of this normally called RFC
2307bis, with
10919 some modifications to be compatible with Active Directory. The RFC
10920 specification handle the content of a lot of system databases, but do
10921 not handle DNS zones and DHCP configuration.
</p
>
10923 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10924 we would like to store information about users, SMB clients/hosts,
10925 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10926 and LTSP configuration in LDAP. These objects have a lot in common,
10927 but with the current LDAP schemas it is not possible to have one
10928 object per entity. For example, one need to have at least three LDAP
10929 objects for a given computer, one with the SMB related stuff, one with
10930 DNS information and another with DHCP information. The schemas
10931 provided for DNS and DHCP are impossible to combine into one LDAP
10932 object. In addition, it is impossible to implement quick queries for
10933 netgroup membership, because of the way NIS triples are implemented.
10934 It just do not scale. I believe it is time for a few RFC
10935 specifications to cleam up this mess.
</p
>
10937 <p
>I would like to have one LDAP object representing each computer in
10938 the network, and this object can then keep the SMB (ie host key), DHCP
10939 (mac address/name) and DNS (name/IP address) settings in one place.
10940 It need to be efficently stored to make sure it scale well.
</p
>
10942 <p
>I would also like to have a quick way to map from a user or
10943 computer and to the net group this user or computer is a member.
</p
>
10945 <p
>Active Directory have done a better job than unix heads like myself
10946 in this regard, and the unix side need to catch up. Time to start a
10947 new IETF work group?
</p
>
10952 <title>Endelig er Debian Lenny gitt ut
</title>
10953 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10954 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10955 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10956 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10957 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10958 Et langt steg videre for Debian-prosjektet, og en rekke nye
10959 programpakker blir nå tilgjengelig for de av oss som bruker den
10960 stabile utgaven av Debian. Neste steg er nå å få
10961 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10962 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10963 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10964 slippes løs på skolene. Takk til alle debian-utviklerne som har
10965 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10966 bootsekvens tilgjengelig i stabil utgave, vha pakken
10967 <tt
>insserv
</tt
>.
</p
>
10972 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10973 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10975 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10976 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10977 Oslo. Most of Saturday was used for the general assemly for the
10978 member organization, but the rest of the weekend I used to tune the
10979 LTSP installation. LTSP now work out of the box on the
10-network.
10980 Acer Aspire One proved to be a very nice thin client, with both
10981 screen, mouse and keybard in a small box. Was working on getting the
10982 diskless workstation setup configured out of the box, but did not
10983 finish it before the weekend was up.
</p
>
10985 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10986 the Brazilian group, so that will have to wait for the next
10987 development gathering. Would love to have the Debian Edu installer
10988 automatically detect and configure a multiseat setup when it find one
10989 of these cards.
</p
>
10994 <title>The sorry state of multimedia browser plugins in Debian
</title>
10995 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10996 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10997 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10998 <description><p
>Recently I have spent some time evaluating the multimedia browser
10999 plugins available in Debian Lenny, to see which one we should use by
11000 default in Debian Edu. We need an embedded video playing plugin with
11001 control buttons to pause or stop the video, and capable of streaming
11002 all the multimedia content available on the web. The test results and
11003 notes are available on
11004 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11005 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11006 fill this need. My personal video player favorite, VLC, has a really
11007 bad plugin which fail on a lot of the test pages. A lot of the MIME
11008 types I would expect to work with any free software player (like
11009 video/ogg), just do not work. And simple formats like the
11010 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11011 totem and vlc plugins. I hope the situation will improve soon. No
11012 wonder sites use the proprietary Adobe flash to play video.
</p
>
11014 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11015 be the only one fitting our needs. :/
</p
>