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>https://people.skolelinux.org/pere/blog/
</link>
10 <title>Speech to text, she APTly whispered, how hard can it be?
</title>
11 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</guid>
13 <pubDate>Sun,
23 Apr
2023 09:
40:
00 +
0200</pubDate>
14 <description><p
>While visiting a convention during Eastern, it occurred to me that
15 it would be great if I could have a digital Dictaphone with
16 transcribing capabilities, providing me with texts to cut-n-paste into
17 stuff I need to write. The background is that long drives often bring
18 up the urge to write on texts I am working on, which of course is out
19 of the question while driving. With the release of
20 <a href=
"https://github.com/openai/whisper/
">OpenAI Whisper
</a
>, this
21 seem to be within reach with Free Software, so I decided to give it a
22 go. OpenAI Whisper is a Linux based neural network system to read in
23 audio files and provide text representation of the speech in that
24 audio recording. It handle multiple languages and according to its
25 creators even can translate into a different language than the spoken
26 one. I have not tested the latter feature. It can either use the CPU
27 or a GPU with CODA support. As far as I can tell, CODA in practice
28 limit that feature to NVidia graphics cards. I have few of those, as
29 they do not work great with free software drivers, and have not tested
30 the GPU option. While looking into the matter, I did discover some
31 work to provide CODA support on non-NVidia GPUs, and some work with
32 the library used by Whisper to port it to other GPUs, but have not
33 spent much time looking into GPU support yet. I
've so far used an old
34 X220 laptop as my test machine, and only transcribed using its
37 <p
>As it from a privacy standpoint is unthinkable to use computers
38 under control of someone else (aka a
"cloud
" service) to transcribe
39 ones thoughts and personal notes, I want to run the transcribing
40 system locally on my own computers. The only sensible approach to me
41 is to make the effort I put into this available for any Linux user and
42 to upload the needed packages into Debian. Looking at Debian Bookworm, I
43 discovered that only three packages were missing,
44 <a href=
"https://bugs.debian.org/
1034307">tiktoken
</a
>,
45 <a href=
"https://bugs.debian.org/
1034144">triton
</a
>, and
46 <a href=
"https://bugs.debian.org/
1034091">openai-whisper
</a
>. For a while
48 <a href=
"https://bugs.debian.org/
1034286">ffmpeg-python
</a
> was
50 <a href=
"https://github.com/kkroening/ffmpeg-python/issues/
760">upstream
51 seem to have vanished
</a
> I found it safer
52 <a href=
"https://github.com/openai/whisper/pull/
1242">to rewrite
53 whisper
</a
> to stop depending on in than to introduce ffmpeg-python
54 into Debian. I decided to place these packages under the umbrella of
55 <a href=
"https://salsa.debian.org/deeplearning-team
">the Debian Deep
56 Learning Team
</a
>, which seem like the best team to look after such
57 packages. Discussing the topic within the group also made me aware
58 that the triton package was already a future dependency of newer
59 versions of the torch package being planned, and would be needed after
60 Bookworm is released.
</p
>
62 <p
>All required code packages have been now waiting in
63 <a href=
"https://ftp-master.debian.org/new.html
">the Debian NEW
64 queue
</a
> since Wednesday, heading for Debian Experimental until
65 Bookworm is released. An unsolved issue is how to handle the neural
66 network models used by Whisper. The default behaviour of Whisper is
67 to require Internet connectivity and download the model requested to
68 <tt
>~/.cache/whisper/
</tt
> on first invocation. This obviously would
69 fail
<a href=
"https://people.debian.org/~bap/dfsg-faq.html
">the
70 deserted island test of free software
</a
> as the Debian packages would
71 be unusable for someone stranded with only the Debian archive and solar
72 powered computer on a deserted island.
</p
>
74 <p
>Because of this, I would love to include the models in the Debian
75 mirror system. This is problematic, as the models are very large
76 files, which would put a heavy strain on the Debian mirror
77 infrastructure around the globe. The strain would be even higher if
78 the models change often, which luckily as far as I can tell they do
79 not. The small model, which according to its creator is most useful
80 for English and in my experience is not doing a great job there
81 either, is
462 MiB (deb is
414 MiB). The medium model, which to me
82 seem to handle English speech fairly well is
1.5 GiB (deb is
1.3 GiB)
83 and the large model is
2.9 GiB (deb is
2.6 GiB). I would assume
84 everyone with enough resources would prefer to use the large model for
85 highest quality. I believe the models themselves would have to go
86 into the non-free part of the Debian archive, as they are not really
87 including any useful source code for updating the models. The
88 "source
", aka the model training set, according to the creators
89 consist of
"680,
000 hours of multilingual and multitask supervised
90 data collected from the web
", which to me reads material with both
91 unknown copyright terms, unavailable to the general public. In other
92 words, the source is not available according to the Debian Free
93 Software Guidelines and the model should be considered non-free.
</p
>
95 <p
>I asked the Debian FTP masters for advice regarding uploading a
96 model package on their IRC channel, and based on the feedback there it
97 is still unclear to me if such package would be accepted into the
98 archive. In any case I wrote build rules for a
99 <a href=
"https://salsa.debian.org/deeplearning-team/openai-whisper-model
">OpenAI
100 Whisper model package
</a
> and
101 <a href=
"https://github.com/openai/whisper/pull/
1257">modified the
102 Whisper code base
</a
> to prefer shared files under
<tt
>/usr/
</tt
> and
103 <tt
>/var/
</tt
> over user specific files in
<tt
>~/.cache/whisper/
</tt
>
104 to be able to use these model packages, to prepare for such
105 possibility. One solution might be to include only one of the models
106 (small or medium, I guess) in the Debian archive, and ask people to
107 download the others from the Internet. Not quite sure what to do
108 here, and advice is most welcome (use the debian-ai mailing list).
</p
>
110 <p
>To make it easier to test the new packages while I wait for them to
111 clear the NEW queue, I created an APT source targeting bookworm. I
112 selected Bookworm instead of Bullseye, even though I know the latter
113 would reach more users, is that some of the required dependencies are
114 missing from Bullseye and I during this phase of testing did not want
115 to backport a lot of packages just to get up and running.
</p
>
117 <p
>Here is a recipe to run as user root if you want to test OpenAI
118 Whisper using Debian packages on your Debian Bookworm installation,
119 first adding the APT repository GPG key to the list of trusted keys,
120 then setting up the APT repository and finally installing the packages
121 and one of the models:
</p
>
124 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
125 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
126 mkdir -p /etc/apt/sources.list.d
127 cat
> /etc/apt/sources.list.d/pere-whisper.list
&lt;
&lt;EOF
128 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
129 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
132 apt install openai-whisper
133 </pre
></p
>
135 <p
>The package work for me, but have not yet been tested on any other
136 computer than my own. With it, I have been able to (badly) transcribe
137 a
2 minute
40 second Norwegian audio clip to test using the small
138 model. This took
11 minutes and around
2.2 GiB of RAM. Transcribing
139 the same file with the medium model gave a accurate text in
77 minutes
140 using around
5.2 GiB of RAM. My test machine had too little memory to
141 test the large model, which I believe require
11 GiB of RAM. In
142 short, this now work for me using Debian packages, and I hope it will
143 for you and everyone else once the packages enter Debian.
</p
>
145 <p
>Now I can start on the audio recording part of this project.
</p
>
147 <p
>As usual, if you use Bitcoin and want to show your support of my
148 activities, please send Bitcoin donations to my address
149 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
154 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software
</title>
155 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</link>
156 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</guid>
157 <pubDate>Fri,
7 Apr
2023 23:
10:
00 +
0200</pubDate>
158 <description><p
>Today I finally found time to track down a useful radio frequency
159 scanner for my software defined radio. Just for fun I tried to locate
160 the radios used in the areas, and a good start would be to scan all
161 the frequencies to see what is in use. I
've tried to find a useful
162 program earlier, but ran out of time before I managed to find a useful
163 tool. This time I was more successful, and after a few false leads I
164 found a description of
165 <a href=
"https://www.kali.org/tools/rtlsdr-scanner/
">rtlsdr-scanner
166 over at the Kali site
</a
>, and was able to track down
167 <a href=
"https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git
">the
168 Kali package git repository
</a
> to build a deb package for the
169 scanner. Sadly the package is missing from the Debian project itself,
170 at least in Debian Bullseye. Two runtime dependencies,
171 <a href=
"https://gitlab.com/kalilinux/packages/python-visvis.git
">python-visvis
</a
>
173 <a href=
"https://gitlab.com/kalilinux/packages/python-rtlsdr.git
">python-rtlsdr
</a
>
174 had to be built and installed separately. Luckily
'<tt
>gbp
175 buildpackage
</tt
>' handled them just fine and no further packages had
176 to be manually built. The end result worked out of the box after
177 installation.
</p
>
179 <p
>My initial scans for FM channels worked just fine, so I knew the
180 scanner was functioning. But when I tried to scan every frequency
181 from
100 to
1000 MHz, the program stopped unexpectedly near the
182 completion. After some debugging I discovered USB software radio I
183 used rejected frequencies above
948 MHz, triggering a unreported
184 exception breaking the scan. Changing the scan to end at
957 worked
185 better. I similarly found the lower limit to be around
15, and ended
186 up with the following full scan:
</p
>
188 <p
><a href=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
" width=
"100%
"></a
></p
>
190 <p
>Saving the scan did not work, but exporting it as a CSV file worked
191 just fine. I ended up with around
477k CVS lines with dB level for
192 the given frequency.
</p
>
194 <p
>The save failure seem to be a missing UTF-
8 encoding issue in the
195 python code. Will see if I can find time to send a patch
196 <a href=
"https://github.com/CdeMills/RTLSDR-Scanner/
">upstream
</a
>
197 later to fix this exception:
</p
>
200 Traceback (most recent call last):
201 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
202 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
203 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
204 handle.write(json.dumps(data, indent=
4))
205 TypeError: a bytes-like object is required, not
'str
'
206 Traceback (most recent call last):
207 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
208 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
209 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
210 handle.write(json.dumps(data, indent=
4))
211 TypeError: a bytes-like object is required, not
'str
'
214 <p
>As usual, if you use Bitcoin and want to show your support of my
215 activities, please send Bitcoin donations to my address
216 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
221 <title>OpenSnitch available in Debian Sid and Bookworm
</title>
222 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</link>
223 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</guid>
224 <pubDate>Sat,
25 Feb
2023 20:
30:
00 +
0100</pubDate>
225 <description><p
>Thanks to the efforts of the OpenSnitch lead developer Gustavo
226 Iñiguez Goya allowing me to sponsor the upload,
227 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
228 application firewall OpenSnitch
</a
> is now available in Debian
229 Testing, soon to become the next stable release of Debian.
</p
>
231 <p
>This is a package which set up a network firewall on one or more
232 machines, which is controlled by a graphical user interface that will
233 ask the user if a program should be allowed to connect to the local
234 network or the Internet. If some background daemon is trying to dial
235 home, it can be blocked from doing so with a simple mouse click, or by
236 default simply by not doing anything when the GUI question dialog pop
237 up. A list of all programs discovered using the network is provided
238 in the GUI, giving the user an overview of how the machine(s) programs
239 use the network.
</p
>
241 <p
>OpenSnitch was uploaded for NEW processing about a month ago, and I
242 had little hope of it getting accepted and shaping up in time for the
243 package freeze, but the Debian ftpmasters proved to be amazingly quick
244 at checking out the package and it was accepted into the archive about
245 week after the first upload. It is now team maintained under the Go
246 language team umbrella. A few fixes to the default setup is only in
247 Sid, and should migrate to Testing/Bookworm in a week.
</p
>
249 <p
>During testing I ran into an
250 <a href=
"https://github.com/evilsocket/opensnitch/issues/
813">issue
251 with Minecraft server broadcasts disappearing
</a
>, which was quickly
252 resolved by the developer with a patch and a proposed configuration
253 change. I
've been told this was caused by the Debian packages default
254 use if /proc/ information to track down kernel status, instead of the
255 newer eBPF module that can be used. The reason is simply that
256 upstream and I have failed to find a way to build the eBPF modules for
257 OpenSnitch without a complete configured Linux kernel source tree,
258 which as far as we can tell is unavailable as a build dependency in
259 Debian. We tried unsuccessfully so far to use the kernel-headers
260 package. It would be great if someone could provide some clues how to
261 build eBPF modules on build daemons in Debian, possibly without the full
262 kernel source.
</p
>
264 <p
>As usual, if you use Bitcoin and want to show your support of my
265 activities, please send Bitcoin donations to my address
266 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
271 <title>Is the desktop recommending your program for opening its files?
</title>
272 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
273 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
274 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
275 <description><p
>Linux desktop systems
276 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
277 standardized
</a
> how programs present themselves to the desktop
278 system. If a package include a .desktop file in
279 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
280 environments will pick up the file and use its content to generate the
281 menu of available programs in the system. A lesser known fact is that
282 a package can also explain to the desktop system how to recognize the
283 files created by the program in question, and use it to open these
284 files on request, for example via a GUI file browser.
</p
>
286 <p
>A while back I ran into a package that did not tell the desktop
287 system how to recognize its files and was not used to open its files
288 in the file browser and fixed it. In the process I wrote a simple
289 debian/tests/ script to ensure the setup keep working. It might be
290 useful for other packages too, to ensure any future version of the
291 package keep handling its own files.
</p
>
293 <p
>For this to work the file format need a useful MIME type that can
294 be used to identify the format. If the file format do not yet have a
295 MIME type, it should define one and preferably also
296 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
297 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
299 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
300 query the database of standardized package information and ensure it
301 return sensible values. It also need the location of an example file
302 for xdg-mime to guess the format of.
</p
>
307 # Author: Petter Reinholdtsen
308 # License: GPL v2 or later at your choice.
310 # Validate the MIME setup, making sure motor types have
311 # application/vnd.openmotor+yaml associated with them and is connected
312 # to the openmotor desktop file.
316 mimetype=
"application/vnd.openmotor+yaml
"
317 testfile=
"test/data/real/o3100/motor.ric
"
318 mydesktopfile=
"openmotor.desktop
"
320 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
322 if [
"$mimetype
" !=
"$filemime
" ] ; then
324 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
326 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
329 desktop=$(xdg-mime query default
"$mimetype
")
331 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
333 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
335 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
341 <p
>It is a simple way to ensure your users are not very surprised when
342 they try to open one of your file formats in their file browser.
</p
>
344 <p
>As usual, if you use Bitcoin and want to show your support of my
345 activities, please send Bitcoin donations to my address
346 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
351 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
352 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
353 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
354 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
355 <description><p
>While reading a
356 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
357 post claiming MacOS X recently started scanning local files and
358 reporting information about them to Apple
</a
>, even on a machine where
359 all such callback features had been disabled, I came across a
360 description of the Little Snitch application for MacOS X. It seemed
361 like a very nice tool to have in the tool box, and I decided to see if
362 something similar was available for Linux.
</p
>
364 <p
>It did not take long to find
365 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
366 package
</a
>, which has been in development since
2017, and now is in
367 version
1.5.0. It has had a
368 <a href=
"https://bugs.debian.org/
909567">request for Debian
369 packaging
</a
> since
2018, but no-one completed the job so far. Just
370 for fun, I decided to see if I could help, and I was very happy to
372 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
373 want a Debian package too
</a
>.
</p
>
375 <p
>After struggling a bit with getting the program to run, figuring
376 out building Go programs (and a little failed detour to look at eBPF
377 builds too - help needed), I am very happy to report that I am
378 sponsoring upstream to maintain the package in Debian, and it has
379 since this morning been waiting in NEW for the ftpmasters to have a
380 look. Perhaps it can get into the archive in time for the Bookworm
383 <p
>As usual, if you use Bitcoin and want to show your support of my
384 activities, please send Bitcoin donations to my address
385 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
390 <title>LinuxCNC MQTT publisher component
</title>
391 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
392 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
393 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
394 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
395 video from Andreas Schiffler
</a
> the other day, where he set up
396 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
397 information to the MQTT broker IBM Bluemix. As I also use MQTT for
398 graphing, it occured to me that a generic MQTT LinuxCNC component
399 would be useful and I set out to implement it. Today I got the first
400 draft limping along and submitted as
401 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
402 LinuxCNC project
</a
>.
</p
>
404 <p
>The simple part was setting up the MQTT publishing code in Python.
405 I already have set up other parts submitting data to my Mosquito MQTT
406 broker, so I could reuse that code. Writing a LinuxCNC component in
407 Python as new to me, but using existing examples in the code
408 repository and the extensive documentation, this was fairly straight
409 forward. The hardest part was creating a automated test for the
410 component to ensure it was working. Testing it in a simulated
411 LinuxCNC machine proved very useful, as I discovered features I needed
412 that I had not thought of yet, and adjusted the code quite a bit to
413 make it easier to test without a operational MQTT broker
416 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
417 pins I should collect and publish by default (in other words, the
418 default set of information pieces published), and how to get the
419 machine name from the LinuxCNC INI file. The latter is a minor
420 detail, but I expect it would be useful in a setup with several
421 machines available. I am hoping for feedback from the experienced
422 LinuxCNC developers and users, to make the component even better
423 before it can go into the mainland LinuxCNC code base.
</p
>
425 <p
>Since I started on the MQTT component, I came across
426 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
427 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
428 controlled by a Raspberry Pi, and it occured to me that it would
429 be useful for such use cases if LinuxCNC also provided a REST API for
430 querying its status. I hope to start on such component once the MQTT
431 component is working well.
</p
>
433 <p
>As usual, if you use Bitcoin and want to show your support of my
434 activities, please send Bitcoin donations to my address
435 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
440 <title>ONVIF IP camera management tool finally in Debian
</title>
441 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
442 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
443 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
444 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
445 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
446 specification
</a
>. There is finally a nice command line and GUI tool
447 in Debian to manage ONVIF IP cameras. After working with upstream for
448 a few months and sponsoring the upload, I am very happy to report that
449 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
450 entered Debian Sid last night.
</p
>
452 <p
>The package provide a C library to communicate with such cameras, a
453 command line tool to locate and update settings of (like password) the
454 cameras and a GUI tool to configure and control the units as well as
455 preview the video from the camera. Libonvif is available on Both
456 Linux and Windows and the GUI tool uses the Qt library. The main
457 competitors are non-free software, while libonvif is GNU GPL licensed.
458 I am very glad Debian users in the future can control their cameras
459 using a free software system provided by Debian. But the ONVIF world
460 is full of slightly broken firmware, where the cameras pretend to
461 follow the ONVIF specification but fail to set some configuration
462 values or refuse to provide video to more than one recipient at the
463 time, and the onvif project is quite young and might take a while
464 before it completely work with your camera. Upstream seem eager to
465 improve the library, so handling any broken camera might be just
<a
466 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
468 <p
>The package just cleared NEW, and need a new source only upload
469 before it can enter testing. This will happen in the next few
472 <p
>As usual, if you use Bitcoin and want to show your support of my
473 activities, please send Bitcoin donations to my address
474 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
479 <title>Managing and using ONVIF IP cameras with Linux
</title>
480 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
481 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
482 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
483 <description><p
>Recently I have been looking at how to control and collect data
484 from a handful IP cameras using Linux. I both wanted to change their
485 settings and to make their imagery available via a free software
486 service under my control. Here is a summary of the tools I found.
</p
>
488 <p
>First I had to identify the cameras and their protocols. As far as
489 I could tell, they were using some SOAP looking protocol and their
490 internal web server seem to only work with Microsoft Internet Explorer
491 with some proprietary binary plugin, which in these days of course is
492 a security disaster and also made it impossible for me to use the
493 camera web interface. Luckily I discovered that the SOAP looking
494 protocol is actually following
<a href=
"https://www.onvif.org/
">the
495 ONVIF specification
</a
>, which seem to be supported by a lot of IP
496 cameras these days.
</p
>
498 <p
>Once the protocol was identified, I was able to find what appear to
499 be the most popular way to configure ONVIF cameras, the free software
501 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
502 Manager
</a
>. Lacking any other options at the time, I tried
503 unsuccessfully to get it running using Wine, but was missing a dotnet
504 40 library and I found no way around it to run it on Linux.
</p
>
506 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
507 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
508 Device Tool
</a
>. I did not like its terms of use, so did not spend
509 much time on it.
</p
>
511 <p
>To collect the video and make it available in a web interface, I
512 found the Zoneminder tool in Debian. A recent version was able to
513 automatically detect and configure ONVIF devices, so I could use it to
514 set up motion detection in and collection of the camera output. I had
515 initial problems getting the ONVIF autodetection to work, as both
516 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
517 the inter-tab communication
</a
> being used by the Zoneminder web
518 pages, but managed to get konqueror to work. Apparently the
"Enhanced
519 Tracking Protection
" in Firefox cause the problem. I ended up
520 upgrading to the Bookworm edition of Zoneminder in the process to try
521 to fix the issue, and believe the problem might be solved now.
</p
>
523 <p
>In the process I came across the nice Linux GUI tool
524 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
525 allowing me to preview the camera output and validate the login
526 passwords required. Sadly its author has grown tired of maintaining
527 the software, so it might not see any future updates. Which is sad,
528 as the viewer is sightly unstable and the picture tend to lock up.
529 Note, this lockup might be due to limitations in the cameras and not
530 the viewer implementation. I suspect the camera is only able to
531 provide pictures to one client at the time, and the Zoneminder feed
532 might interfere with the GUI viewer. I have
533 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
534 included in Debian
</a
>.
</p
>
536 <p
>Finally, I found what appear to be very nice Linux free software
537 replacement for the Windows tool, named
538 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
539 provide a C library to talk to ONVIF devices as well as a command line
540 and GUI tool using the library. Using the GUI tool I was able to change
541 the admin passwords and update other settings of the cameras. I have
542 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
543 included in Debian
</a
>.
</p
>
545 <p
>As usual, if you use Bitcoin and want to show your support of my
546 activities, please send Bitcoin donations to my address
547 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
549 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
550 this text, I got several suggestions for more free software Linux
551 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
552 ONVIF python library
</a
> (already
553 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
554 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
555 fork
</a
> using a different SOAP dependency. There is also
556 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
557 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
558 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
559 two are not included in Debian either. I have not tested any of these
565 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
566 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
567 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
568 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
569 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
571 <p
>(The picture is of the previous edition.)
</p
>
573 <p
>Almost two years after the previous Norwegian Bokmål translation of
574 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
575 Handbook
</a
>" was published, a new edition is finally being prepared. The
576 english text is updated, and it is time to start working on the
577 translations. Around
37 percent of the strings have been updated, one
578 way or another, and the translations starting from a complete Debian Buster
579 edition now need to bring their translation up from
63% to
100%. The
580 complete book is licensed using a Creative Commons license, and has
581 been published in several languages over the years. The translations
582 are done by volunteers to bring Linux in their native tongue. The
583 last time I checked, it complete text was available in English,
584 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
585 In addition, work has been started for Arabic (Morocco), Catalan,
586 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
587 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
588 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
590 <p
>The translation is conducted on
591 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
592 hosted weblate project page
</a
>. Prospective translators are
593 recommeded to subscribe to
594 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
595 translators mailing list
</a
> and should also check out
596 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
597 contributors
</a
>.
</p
>
599 <p
>I am one of the Norwegian Bokmål translators of this book, and we
600 have just started. Your contribution is most welcome.
</p
>
602 <p
>As usual, if you use Bitcoin and want to show your support of my
603 activities, please send Bitcoin donations to my address
604 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
609 <title>Automatic LinuxCNC servo PID tuning?
</title>
610 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
611 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
612 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
613 <description><p
>While working on a CNC with servo motors controlled by the
614 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
615 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
616 controller
</a
>, I recently had to learn how to tune the collection of values
617 that control such mathematical machinery that a PID controller is. It
618 proved to be a lot harder than I hoped, and I still have not succeeded
619 in getting the Z PID controller to successfully defy gravity, nor X
620 and Y to move accurately and reliably. But while climbing up this
621 rather steep learning curve, I discovered that some motor control
622 systems are able to tune their PID controllers. I got the impression
623 from the documentation that LinuxCNC were not. This proved to be not
626 <p
>The LinuxCNC
627 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
628 component
</a
> is the recommended PID controller to use. It uses eight
629 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
630 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
631 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
632 state, and all of these need to have a sensible value for the
633 controller to behave properly. Note, there are even more values
634 involved, theser are just the most important ones. In my case I need
635 the X, Y and Z axes to follow the requested path with little error.
636 This has proved quite a challenge for someone who have never tuned a
637 PID controller before, but there is at least some help to be found.
639 <p
>I discovered that included in LinuxCNC was this old PID component
640 at_pid claiming to have auto tuning capabilities. Sadly it had been
641 neglected since
2011, and could not be used as a plug in replacement
642 for the default pid component. One would have to rewriting the
643 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
644 to quickly test auto tuning to see if it did a better job than me at
645 figuring out good P, I and D values to use.
</p
>
647 <p
>I decided to have a look if the situation could be improved. This
648 involved trying to understand the code and history of the pid and
649 at_pid components. Apparently they had a common ancestor, as code
650 structure, comments and variable names were quite close to each other.
651 Sadly this was not reflected in the git history, making it hard to
652 figure out what really happened. My guess is that the author of
653 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
655 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
656 rewrote it to follow the structure he wished pid.c to have, then added
657 support for auto tuning and finally got it included into the LinuxCNC
658 repository. The restructuring and lack of early history made it
659 harder to figure out which part of the code were relevant to the auto
660 tuning, and which part of the code needed to be updated to work the
661 same way as the current pid.c implementation. I started by trying to
662 isolate relevant changes in pid.c, and applying them to at_pid.c. My
663 aim was to make sure the at_pid component could replace the pid
664 component with a simple change in the HAL setup loadrt line, without
665 having to
"rewire
" the rest of the HAL configuration. After a few
666 hours following this approach, I had learned quite a lot about the
667 code structure of both components, while concluding I was heading down
668 the wrong rabbit hole, and should get back to the surface and find a
669 different path.
</p
>
671 <p
>For the second attempt, I decided to throw away all the PID control
672 related part of the original at_pid.c, and instead isolate and lift
673 the auto tuning part of the code and inject it into a copy of pid.c.
674 This ensured compatibility with the current pid component, while
675 adding auto tuning as a run time option. To make it easier to identify
676 the relevant parts in the future, I wrapped all the auto tuning code
677 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
678 pid component by default, as that part of the code is identical. The
679 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
680 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
682 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
683 component. The most important ones are
<tt
>tune-effort
</tt
>,
684 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
685 back, and see what the auto tuning code will do. I do not know the
686 mathematical foundation of the at_pid algorithm, but from observation
687 I can tell that the algorithm will, when enabled, produce a square
688 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
689 of the PID controller. This can be seen using the HAL Scope provided
690 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
691 to the motor controller, which in turn is translated into motor speed.
692 So at_pid will ask the motor to move the axis back and forth. The
693 number of cycles in the pattern is controlled by the
694 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
695 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
696 change the direction of a physical object instantly (as in going
697 directly from a positive voltage to the equivalent negative voltage)
698 do not change velocity instantly, and it take some time for the object
699 to slow down and move in the opposite direction. This result in a
700 more smooth movement wave form, as the axis in question were vibrating
701 back and forth. When the axis reached the target speed in the
702 opposing direction, the auto tuner change direction again. After
703 several of these changes, the average time delay between the
'peaks
'
704 and
'valleys
' of this movement graph is then used to calculate
705 proposed values for Pgain, Igain and Dgain, and insert them into the
706 HAL model to use by the pid controller. The auto tuned settings are
707 not great, but htye work a lot better than the values I had been able
708 to cook up on my own, at least for the horizontal X and Y axis. But I
709 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
710 controllers error out if the voltage change too quickly. I
've been
711 less lucky with the Z axis, which is moving a heavy object up and
712 down, and seem to confuse the algorithm. The Z axis movement became a
713 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
714 gravitational drag, but I will have to work a lot more on the Z axis
715 PID values.
</p
>
717 <p
>Armed with this knowledge, it is time to look at how to do the
718 tuning. Lets say the HAL configuration in question load the PID
719 component for X, Y and Z like this:
</p
>
721 <blockquote
><pre
>
722 loadrt pid names=pid.x,pid.y,pid.z
723 </pre
></blockquote
>
725 <p
>Armed with the new and improved at_pid component, the new line will
726 look like this:
</p
>
728 <blockquote
><pre
>
729 loadrt at_pid names=pid.x,pid.y,pid.z
730 </pre
></blockquote
>
732 <p
>The rest of the HAL setup can stay the same. This work because the
733 components are referenced by name. If the component had used count=
3
734 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
736 <p
>To start tuning the X axis, move the axis to the middle of its
737 range, to make sure it do not hit anything when it start moving back
738 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
739 output range. I used
0.1 as my initial value. Next, assign
1 to the
740 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
741 part and feed
0 to the output pin, which in my case initially caused a
742 lot of drift. In my case it proved to be a good idea with X and Y to
743 tune the motor driver to make sure
0 voltage stopped the motor
744 rotation. On the other hand, for the Z axis this proved to be a bad
745 idea, so it will depend on your setup. It might help to set the
746 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
747 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
748 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
749 your axis will vibrate for a few seconds and when it is done, new
750 values for Pgain, Igain and Dgain will be active. To test them,
751 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
752 machine to suddenly jerk as it bring the axis back to its commanded
753 position, which it might have drifted away from during tuning. To
754 summarize with some halcmd lines:
</p
>
756 <blockquote
><pre
>
757 setp pid.x.tune-effort
0.1
758 setp pid.x.tune-mode
1
759 setp pid.x.tune-start
1
760 # wait for the tuning to complete
761 setp pid.x.tune-mode
0
762 </pre
></blockquote
>
764 <p
>After doing this task quite a few times while trying to figure out
765 how to properly tune the PID controllers on the machine in, I decided
766 to figure out if this process could be automated, and wrote a script
767 to do the entire tuning process from power on. The end result will
768 ensure the machine is powered on and ready to run, home all axis if it
769 is not already done, check that the extra tuning pins are available,
770 move the axis to its mid point, run the auto tuning and re-enable the
771 pid controller when it is done. It can be run several times. Check
773 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
774 script on github if you want to learn how it is done.
</p
>
776 <p
>My hope is that this little adventure can inspire someone who know
777 more about motor PID controller tuning can implement even better
778 algorithms for automatic PID tuning in LinuxCNC, making life easier
779 for both me and all the others that want to use LinuxCNC but lack the
780 in depth knowledge needed to tune PID controllers well.
</p
>
782 <p
>As usual, if you use Bitcoin and want to show your support of my
783 activities, please send Bitcoin donations to my address
784 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
789 <title>LinuxCNC translators life just got a bit easier
</title>
790 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
791 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
792 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
793 <description><p
>Back in oktober last year, when I started looking at the
794 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
795 proposed to change the documentation build system make life easier for
796 translators. The original system consisted of independently written
797 documentation files for each language, with no automated way to track
798 changes done in other translations and no help for the translators to
799 know how much was left to translated. By using
800 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
801 files from the English documentation, this can be improved. A small
802 team of LinuxCNC contributors got together and today our labour
803 finally payed off. Since a few hours ago, it is now possible to
804 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
805 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
807 <p
>The effort to migrate the documentation to use po4a has been both
808 slow and frustrating. I am very happy we finally made it.
</p
>
810 <p
>As usual, if you use Bitcoin and want to show your support of my
811 activities, please send Bitcoin donations to my address
812 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
817 <title>geteltorito make CD firmware upgrades a breeze
</title>
818 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
819 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
820 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
821 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
822 located the firmware download page from Lenovo (which annoyingly do
823 not allow access via Tor, forcing me to hand them more personal
824 information that I would like). The
825 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
826 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
827 when all I got available is a USB memory stick. I tried booting the
828 ISO as a USB stick, but this did not work. But genisoimage came to
829 the rescue.
</p
>
831 <P
>The geteltorito program in
832 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
833 package
</a
> is able to convert the bootable ISO image to a bootable
834 USB stick using a simple command line recipe, which I then can write
835 to the most recently inserted USB stick:
</p
>
837 <blockquote
><pre
>
838 geteltorito -o usbstick.img lenovo-firmware.iso
839 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
840 </pre
></blockquote
>
842 <p
>This USB stick booted the firmware upgrader just fine, and in a few
843 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
848 <title>Run your industrial metal working machine using Debian?
</title>
849 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
850 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
851 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
852 <description><p
>After many months of hard work by the good people involved in
853 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
854 system was accepted Sunday
855 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
856 Once it was available from Debian, I was surprised to discover from
857 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
858 popularity-contest numbers
</a
> that people have been reporting its use
859 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
860 be a good place to check out, but sadly is not working when visiting
863 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
864 Wikipedia quote is in place?
</p
>
867 "LinuxCNC is a software system for numerical control of
868 machines such as milling machines, lathes, plasma cutters, routers,
869 cutting machines, robots and hexapods. It can control up to
9 axes or
870 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
871 several GUIs suited to specific kinds of usage (touch screen,
872 interactive development).
"
875 <p
>It can even control
3D printers. And even though the Wikipedia
876 page indicate that it can only work with hard real time kernel
877 features, it can also work with the user space soft real time features
878 provided by the Debian kernel.
879 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
880 available from Github. The last few months I
've been involved in the
881 translation setup for the program and documentation. Translators are
883 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
884 effort
</a
> using Weblate.
</p
>
886 <p
>As usual, if you use Bitcoin and want to show your support of my
887 activities, please send Bitcoin donations to my address
888 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
893 <title>Debian still an excellent choice for Lego builders
</title>
894 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
895 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
896 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
897 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
898 the packages under the team umbrella has been updated to fix
899 packaging, lintian issues and BTS reports. In addition, a new and
900 inspiring team member appeared on both the
901 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
902 Team mailing list
</a
> and
903 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
904 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
905 Mindstorms programming, check out the
906 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
907 see what Debian can offer the Lego enthusiast.
</p
>
909 <p
>Patches has been sent upstream, causing new upstream releases, one
910 even the first one in more than ten years, and old upstreams was
911 released with new ones. There are still a lot of work left, and the
912 team welcome more members to help us make sure Debian is the Linux
913 distribution of choice for Lego builders. If you want to contribute,
914 join us in the IRC channel and become part of
915 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
916 Salsa
</a
>.
</p
>
918 <p
>As usual, if you use Bitcoin and want to show your support of my
919 activities, please send Bitcoin donations to my address
920 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
925 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
926 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
927 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
928 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
929 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
930 Debian Administrator
's Handbook
</a
> is available in six languages now.
931 I am not sure which one of these are completely proof read, but the
932 complete book is available in these languages:
936 <li
>English
</li
>
937 <li
>Norwegian Bokmål
</li
>
938 <li
>German
</li
>
939 <li
>Indonesian
</li
>
940 <li
>Brazil Portuguese
</li
>
941 <li
>Spanish
</li
>
945 <p
>This is the list of languages more than
70% complete, in other
946 words with not too much left to do:
</p
>
950 <li
>Chinese (Simplified) -
90%
</li
>
951 <li
>French -
79%
</li
>
952 <li
>Italian -
79%
</li
>
953 <li
>Japanese -
77%
</li
>
954 <li
>Arabic (Morocco) -
75%
</li
>
955 <li
>Persian -
71%
</li
>
959 <p
>I wonder how long it will take to bring these to
100%.
</p
>
961 <p
>Then there is the list of languages about halfway done:
</p
>
965 <li
>Russian -
63%
</li
>
966 <li
>Swedish -
53%
</li
>
967 <li
>Chinese (Traditional) -
46%
</li
>
968 <li
>Catalan -
45%
</li
>
972 <p
>Several are on to a good start:
</p
>
976 <li
>Dutch -
26%
</li
>
977 <li
>Vietnamese -
25%
</li
>
978 <li
>Polish -
23%
</li
>
979 <li
>Czech -
22%
</li
>
980 <li
>Turkish -
18%
</li
>
984 <p
>Finally, there are the ones just getting started:
</p
>
988 <li
>Korean -
4%
</li
>
989 <li
>Croatian -
2%
</li
>
990 <li
>Greek -
2%
</li
>
991 <li
>Danish -
1%
</li
>
992 <li
>Romanian -
1%
</li
>
996 <p
>If you want to help provide a Debian instruction book in your own
998 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
999 to contribute to the translations.
</p
>
1001 <p
>As usual, if you use Bitcoin and want to show your support of my
1002 activities, please send Bitcoin donations to my address
1003 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1008 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
1009 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
1010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
1011 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
1012 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
1013 others, the decentralized communication platform
1014 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
1015 (earlier known as Ring), managed to get
1016 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
1017 into Debian Testing. Several of its dependencies has caused build and
1018 propagation problems, which all seem to be solved now.
</p
>
1020 <p
>In addition to the fact that Jami is decentralized, similar to how
1021 bittorrent is decentralized, I first of all like how it is not
1022 connected to external IDs like phone numbers. This allow me to set up
1023 computers to send me notifications using Jami without having to find
1024 get a phone number for each computer. Automatic notification via Jami
1025 is also made trivial thanks to the provided client side API (as a DBus
1026 service). Here is my bourne shell script demonstrating how to let any
1027 system send a message to any Jami address. It will create a new
1028 identity before sending the message, if no Jami identity exist
1031 <p
><pre
>
1034 # Usage: $
0 <jami-address
> <message
>
1036 # Send
<message
> to
<jami-address
>, create local jami account if
1039 # License: GPL v2 or later at your choice
1040 # Author: Petter Reinholdtsen
1043 if [ -z
"$HOME
" ] ; then
1044 echo
"error: missing \$HOME, required for dbus to work
"
1048 # First, get dbus running if not already running
1049 DBUSLAUNCH=/usr/bin/dbus-launch
1050 PIDFILE=/run/asterisk/dbus-session.pid
1051 if [ -e $PIDFILE ] ; then
1053 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
1054 unset DBUS_SESSION_BUS_ADDRESS
1057 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
1058 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
1059 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
1060 DBUS_SESSION_BUS_PID=$!
1062 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1063 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
1064 echo export DBUS_SESSION_BUS_ADDRESS
1070 part=
"$
1"; shift
1071 op=
"$
1"; shift
1072 dbus-send --session \
1073 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1077 part=
"$
1"; shift
1078 op=
"$
1"; shift
1079 dbus-send --session --print-reply \
1080 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1084 dringopreply ConfigurationManager getAccountList | \
1085 grep string | awk -F
'"' '{print $
2}
' | head -n
1
1088 account=$(firstaccount)
1090 if [ -z
"$account
" ] ; then
1091 echo
"Missing local account, trying to create it
"
1092 dringop ConfigurationManager addAccount \
1093 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
1094 account=$(firstaccount)
1095 if [ -z
"$account
" ] ; then
1096 echo
"unable to create local account
"
1101 # Not using dringopreply to ensure $
2 can contain spaces
1102 dbus-send --print-reply --session \
1103 --dest=cx.ring.Ring \
1104 /cx/ring/Ring/ConfigurationManager \
1105 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1106 string:
"$account
" string:
"$
1" \
1107 dict:string:string:
"text/plain
",
"$
2"
1108 </pre
></p
>
1110 <p
>If you want to check it out yourself, visit the
1111 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
1112 more, and install the latest Jami client from Debian Unstable or
1115 <p
>As usual, if you use Bitcoin and want to show your support of my
1116 activities, please send Bitcoin donations to my address
1117 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1122 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
1123 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
1124 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
1125 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
1126 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
1128 <p
>I am happy to report that we finally made it! Norwegian Bokmål
1129 became the first translation published on paper of the new Buster
1130 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
1131 Administrator
's Handbook
</a
>". The print proof reading copy arrived
1132 some days ago, and it looked good, so now the book is approved for
1133 general distribution. This updated paperback edition
<a
1134 href=
"https://debian-handbook.info/get/#norwegian
">is available from
1135 lulu.com
</a
>. The book is also available for download in electronic
1136 form as PDF, EPUB and Mobipocket, and can also be
1137 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
1139 <p
>I am very happy to wrap up this Creative Common licensed project,
1140 which concludes several months of work by several volunteers. The
1141 number of Linux related books published in Norwegian are few, and I
1142 really hope this one will gain many readers, as it is packed with deep
1143 knowledge on Linux and the Debian ecosystem. The book will be
1144 available for various Internet book stores like Amazon and Barnes
&
1145 Noble soon, but I recommend buying
1146 "<a href=
"https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
9j7qwq.html
">Håndbok
1147 for Debian-administratoren
</a
>" directly from the source at Lulu.
1149 <p
>As usual, if you use Bitcoin and want to show your support of my
1150 activities, please send Bitcoin donations to my address
1151 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1156 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
1157 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
1158 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</guid>
1159 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
1160 <description><p
>Thanks to the good work of several volunteers, the updated edition
1161 of the Norwegian translation for
1162 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1163 Handbook
</a
>" is now almost completed. After many months of proof
1164 reading, I consider the proof reading complete enough for us to move
1165 to the next step, and have asked for the print version to be prepared
1166 and sent of to the print on demand service lulu.com. While it is
1167 still not to late if you find any incorrect translations on
1168 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1169 hosted Weblate service
</a
>, but it will be soon. :) You can check out
1170 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
1171 edition on the web
</a
> until the print edition is ready.
</p
>
1173 <p
>The book will be for sale on lulu.com and various web book stores,
1174 with links available from the web site for the book linked to above.
1175 I hope a lot of readers find it useful.
</p
>
1177 <p
>As usual, if you use Bitcoin and want to show your support of my
1178 activities, please send Bitcoin donations to my address
1179 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1184 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
1185 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
1186 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
1187 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
1188 <description><p
>Three years ago, the first Norwegian Bokmål edition of
1189 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1190 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
1191 new and updated version based on Buster is getting ready. Work on the
1192 updated Norwegian Bokmål edition has been going on for a few months
1193 now, and yesterday, we reached the first mile stone, with
100% of the
1194 texts being translated. A lot of proof reading remains, of course,
1195 but a major step towards a new edition has been taken.
</p
>
1197 <p
>The book is translated by volunteers, and we would love to get some
1198 help with the proof reading. The translation uses
1199 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1200 hosted Weblate service
</a
>, and we welcome everyone to have a look and
1201 submit improvements and suggestions. There is also a proof readers
1202 PDF available on request, get in touch if you want to help out that
1205 <p
>As usual, if you use Bitcoin and want to show your support of my
1206 activities, please send Bitcoin donations to my address
1207 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1212 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
1213 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
1214 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
1215 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
1216 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
1217 User Group
</a
>, I have the pleasure of receiving the
1218 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
1219 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
1220 several times a year. I rarely have time to read all the articles,
1221 but try to at least skim through them all as there is a lot of nice
1222 knowledge passed on there. I even carry the latest issue with me most
1223 of the time to try to get through all the articles when I have a few
1224 spare minutes.
</p
>
1226 <p
>The other day I came across a nice article titled
1227 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
1228 Secure Socket API: TLS as an Operating System Service
</a
>" with a
1229 marvellous idea I hope can make it all the way into the POSIX standard.
1230 The idea is as simple as it is powerful. By introducing a new
1231 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1232 handle setting up TLS connections, one both make it trivial to add TLS
1233 support to any program currently using the POSIX socket API, and gain
1234 system wide control over certificates, TLS versions and encryption
1235 systems used. Instead of doing this:
</p
>
1237 <p
><blockquote
><pre
>
1238 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1239 </pre
></blockquote
></p
>
1241 <p
>the program code would be doing this:
<p
>
1243 <p
><blockquote
><pre
>
1244 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1245 </pre
></blockquote
></p
>
1247 <p
>According to the ;login: article, converting a C program to use TLS
1248 would normally modify only
5-
10 lines in the code, which is amazing
1249 when compared to using for example the OpenSSL API.
</p
>
1251 <p
>The project has set up the
1252 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
1253 web site to spread the idea, and the code for a kernel module and the
1254 associated system daemon is available from two github repositories:
1255 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
1256 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
1257 Unfortunately there is no explicit license information with the code,
1258 so its copyright status is unclear. A
1259 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
1260 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
1262 <p
>I love the idea of extending socket() to gain TLS support, and
1263 understand why it is an advantage to implement this as a kernel module
1264 and system wide service daemon, but can not help to think that it
1265 would be a lot easier to get projects to move to this way of setting
1266 up TLS if it was done with a user space approach where programs
1267 wanting to use this API approach could just link with a wrapper
1270 <p
>I recommend you check out this simple and powerful approach to more
1271 secure network connections. :)
</p
>
1273 <p
>As usual, if you use Bitcoin and want to show your support of my
1274 activities, please send Bitcoin donations to my address
1275 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1280 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
1281 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
1282 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
1283 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
1284 <description><p
>Half a year ago,
1285 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
1286 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
1287 client
</a
>, capable of peer-to-peer encrypted communication. It
1288 handle both messages, audio and video. It uses distributed hash
1289 tables instead of central infrastructure to connect its users to each
1290 other, which in my book is a plus. I mentioned briefly that it could
1291 also work as a SIP client, which came in handy when the higher
1292 educational sector in Norway started to promote Zoom as its video
1293 conferencing solution. I am reluctant to use the official Zoom client
1294 software, due to their
<a href=
"https://zoom.us/terms
">copyright
1295 license clauses
</a
> prohibiting users to reverse engineer (for example
1296 to check the security) and benchmark it, and thus prefer to connect to
1297 Zoom meetings with free software clients.
</p
>
1299 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
1300 password set on the room. The Jami daemon leak memory like crazy
1301 (approximately
1 GiB a minute) when I am connected to the video
1302 conference, so I had to restart the client every
7-
10 minutes, which
1303 is not great. I tried to get other SIP Linux clients to work
1304 without success, so I decided I would have to live with this wart
1305 until someone managed to fix the leak in the dring code base. But
1306 another problem showed up once the rooms were password protected. I
1307 could not get my dial tone signaling through from Jami to Zoom, and
1308 dial tone signaling is used to enter the password when connecting to
1309 Zoom. I tried a lot of different permutations with my Jami and
1310 Asterisk setup to try to figure out why the signaling did not get
1311 through, only to finally discover that the fundamental problem seem to
1312 be that Zoom is simply not able to receive dial tone signaling when
1313 connecting via SIP. There seem to be nothing wrong with the Jami and
1314 Asterisk end, it is simply broken in the Zoom end. I got help from a
1315 very skilled VoIP engineer figuring out this last part. And being a
1316 very skilled engineer, he was also able to locate a solution for me.
1317 Or to be exact, a workaround that solve my initial problem of
1318 connecting to password protected Zoom rooms using Jami.
</p
>
1320 <p
>So, how do you do this, I am sure you are wondering by now. The
1322 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
1323 from Zoom
</a
>, and it is to modify the SIP address to include the room
1324 password. What is most surprising about this is that the
1325 automatically generated email from Zoom with instructions on how to
1326 connect via SIP do not mention this. The SIP address to use normally
1327 consist of the room ID (a number), an @ character and the IP address
1328 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1329 room ID in front of the at sign. The format is
"<tt
>[Meeting
1330 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
1331 can both enter password, control the layout (full screen, active
1332 presence and gallery) and specify the host key to start the meeting.
1333 The full SIP address entered into Jami to provide the password will
1334 then look like this (all using made up numbers):
</p
>
1336 <p
><blockquote
>
1337 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
1338 </blockquote
></p
>
1340 <p
>Now if only jami would reduce its memory usage, I could even
1341 recommend this setup to others. :)
</p
>
1343 <p
>As usual, if you use Bitcoin and want to show your support of my
1344 activities, please send Bitcoin donations to my address
1345 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1350 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
1351 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
1352 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
1353 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
1354 <description><p
>The curiosity got the better of me when
1355 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
1356 reported
</a
> that New Jersey was desperately looking for
1357 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
1358 and a few days later it was reported that
1359 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
1360 tried to locate COBOL programmers
</a
>.
</p
>
1362 <p
>I thus decided to have a look at free software alternatives to
1363 learn COBOL, and had the pleasure to find
1364 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
1365 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
1366 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
1367 transforming COBOL code to C or C++ before giving it to GCC or Visual
1368 Studio to build binaries.
</p
>
1370 <p
>I managed to get in touch with upstream, and was impressed with the
1371 quick response, and also was happy to see a new Debian maintainer
1372 taking over when the original one recently asked to be replaced. A
1373 new Debian upload was done as recently as yesterday.
</p
>
1375 <p
>Using the Debian package, I was able to follow a simple COBOL
1376 introduction and make and run simple COBOL programs. It was fun to
1377 learn a new programming language. If you want to test for yourself,
1378 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
1379 page
</a
> have a few simple examples to get you startet.
</p
>
1381 <p
>As I do not have much experience with COBOL, I do not know how
1382 standard compliant it is, but it claim to pass most tests from COBOL
1383 test suite, which sound good to me. It is nice to know it is possible
1384 to learn COBOL using software without any usage restrictions, and I am
1385 very happy such nice free software project as this is available. If
1386 you as me is curious about COBOL, check it out.
</p
>
1388 <p
>As usual, if you use Bitcoin and want to show your support of my
1389 activities, please send Bitcoin donations to my address
1390 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1395 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
1396 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
1397 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
1398 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
1399 <description><p
>Some years ago, in
2016, I
1400 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
1401 for the first time about
</a
> the Ring peer to peer messaging system.
1402 It would provide messaging without any central server coordinating the
1403 system and without requiring all users to register a phone number or
1404 own a mobile phone. Back then, I could not get it to work, and put it
1405 aside until it had seen more development. A few days ago I decided to
1406 give it another try, and am happy to report that this time I am able
1407 to not only send and receive messages, but also place audio and video
1408 calls. But only if UDP is not blocked into your network.
</p
>
1410 <p
>The Ring system changed name earlier this year to
1411 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
1412 tried doing web search for
'ring
' when I discovered it for the first
1413 time, and can only applaud this change as it is impossible to find
1414 something called Ring among the noise of other uses of that word. Now
1415 you can search for
'jami
' and this client and
1416 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
1417 least on duckduckgo.
</p
>
1419 <p
>Jami will by default encrypt messages as well as audio and video
1420 calls, and try to send them directly between the communicating parties
1421 if possible. If this proves impossible (for example if both ends are
1422 behind NAT), it will use a central SIP TURN server maintained by the
1423 Jami project. Jami can also be a normal SIP client. If the SIP
1424 server is unencrypted, the audio and video calls will also be
1425 unencrypted. This is as far as I know the only case where Jami will
1426 do anything without encryption.
</p
>
1428 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
1429 Android, iOS, and Android TV. It is included in Debian already. Jami
1430 also work for those using F-Droid without any Google connections,
1431 while Signal do not.
1432 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
1433 protocol
</a
> is described in the Ring project wiki. The system uses a
1434 distributed hash table (DHT) system (similar to BitTorrent) running
1435 over UDP. On one of the networks I use, I discovered Jami failed to
1436 work. I tracked this down to the fact that incoming UDP packages
1437 going to ports
1-
49999 were blocked, and the DHT would pick a random
1438 port and end up in the low range most of the time. After talking to
1439 the developers, I solved this by enabling the dhtproxy in the
1440 settings, thus using TCP to talk to a central DHT proxy instead of
1442 peering directly with others. I
've been told the developers are
1443 working on allowing DHT to use TCP to avoid this problem. I also ran
1444 into a problem when trying to talk to the version of Ring included in
1445 Debian Stable (Stretch). Apparently the protocol changed between
1446 beta2 and the current version, making these clients incompatible.
1447 Hopefully the protocol will not be made incompatible in the
1450 <p
>It is worth noting that while looking at Jami and its features, I
1451 came across another communication platform I have not tested yet. The
1452 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
1453 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
1454 become the topic of a future blog post.
</p
>
1456 <p
>As usual, if you use Bitcoin and want to show your support of my
1457 activities, please send Bitcoin donations to my address
1458 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1463 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
1464 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
1465 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
1466 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
1467 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
1468 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
1469 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
1470 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1471 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1472 nye versjonen kom på nyåret, og ble
1473 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
1474 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
1475 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1476 måtte justeres, men ikke noe alvorlig. Har oppdatert
1477 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
1478 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
1480 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1481 å spille for oss som liker slikt. :)
</p
>
1483 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1484 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1486 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
1487 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
1492 <title>Debian now got everything you need to program Micro:bit
</title>
1493 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
1494 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
1495 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
1496 <description><p
>I am amazed and very pleased to discover that since a few days ago,
1497 everything you need to program the
<a href=
"https://microbit.org/
">BBC
1498 micro:bit
</a
> is available from the Debian archive. All this is
1499 thanks to the hard work of Nick Morrott and the Debian python
1500 packaging team. The micro:bit project recommend the mu-editor to
1501 program the microcomputer, as this editor will take care of all the
1502 machinery required to injekt/flash micropython alongside the program
1503 into the micro:bit, as long as the pieces are available.
</p
>
1505 <p
>There are three main pieces involved. The first to enter Debian
1507 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
1508 which was accepted into the archive
2019-
01-
12. The next one was
1509 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
1510 showed up
2019-
01-
13. The final and hardest part to to into the
1512 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
1513 which needed to get its build system and dependencies into Debian
1514 before it was accepted
2019-
01-
20. The last one is already in Debian
1515 Unstable and should enter Debian Testing / Buster in three days. This
1516 all allow any user of the micro:bit to get going by simply running
1517 'apt install mu-editor
' when using Testing or Unstable, and once
1518 Buster is released as stable, all the users of Debian stable will be
1519 catered for.
</p
>
1521 <p
>As a minor final touch, I added rules to
1522 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
1523 package
</a
> for recognizing micro:bit and recommend the mu-editor
1524 package. This make sure any user of the isenkram desktop daemon will
1525 get a popup suggesting to install mu-editor then the USB cable from
1526 the micro:bit is inserted for the first time.
</p
>
1528 <p
>This should make it easier to have fun.
</p
>
1530 <p
>As usual, if you use Bitcoin and want to show your support of my
1531 activities, please send Bitcoin donations to my address
1532 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1537 <title>Learn to program with Minetest on Debian
</title>
1538 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
1539 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
1540 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
1541 <description><p
>A fun way to learn how to program
1542 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
1543 instructions in the book
1544 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
1545 with Minecraft
</a
>", which introduces programming in Python to people
1546 who like to play with Minecraft. The book uses a Python library to
1547 talk to a TCP/IP socket with an API accepting build instructions and
1548 providing information about the current players in a Minecraft world.
1549 The TCP/IP API was first created for the Minecraft implementation for
1550 Raspberry Pi, and has since been ported to some server versions of
1551 Minecraft. The book contain recipes for those using Windows, MacOSX
1552 and Raspian. But a little known fact is that you can follow the same
1553 recipes using the free software construction game
1554 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
1556 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
1557 Minetest module implementing the same API
</a
>, making it possible to
1558 use the Python programs coded to talk to Minecraft with Minetest too.
1560 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
1561 this module
</a
> to Debian two weeks ago, and as soon as it clears the
1562 FTP masters NEW queue, learning to program Python with Minetest on
1563 Debian will be a simple
'apt install
' away. The Debian package is
1564 maintained as part of the Debian Games team, and
1565 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
1566 packaging rules
</a
> are currently located under
'unfinished
' on
1569 <p
>You will most likely need to install several of the Minetest
1570 modules in Debian for the examples included with the library to work
1571 well, as there are several blocks used by the example scripts that are
1572 provided via modules in Minetest. Without the required blocks, a
1573 simple stone block is used instead. My initial testing with a analog
1574 clock did not get gold arms as instructed in the python library, but
1575 instead used stone arms.
</p
>
1577 <p
>I tried to find a way to add the API to the desktop version of
1578 Minecraft, but were unable to find any working recipes. The
1579 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
1580 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
1581 working with a standalone Minecraft server setup. Are there any
1582 options to use with the normal desktop version?
</p
>
1584 <p
>As usual, if you use Bitcoin and want to show your support of my
1585 activities, please send Bitcoin donations to my address
1586 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1591 <title>Time for an official MIME type for patches?
</title>
1592 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
1593 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
1594 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
1595 <description><p
>As part of my involvement in
1596 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
1597 archive API project
</a
>, I
've been importing a fairly large lump of
1598 emails into a test instance of the archive to see how well this would
1599 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
1600 notmuch email database
</a
>, all public emails sent to me via
1601 @lists.debian.org, giving me a set of around
216 000 emails to import.
1602 In the process, I had a look at the various attachments included in
1603 these emails, to figure out what to do with attachments, and noticed
1604 that one of the most common attachment formats do not have
1605 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
1606 official MIME type
</a
> registered with IANA/IETF. The output from
1607 diff, ie the input for patch, is on the top
10 list of formats
1608 included in these emails. At the moment people seem to use either
1609 text/x-patch or text/x-diff, but neither is officially registered. It
1610 would be better if one official MIME type were registered and used
1611 everywhere.
</p
>
1613 <p
>To try to get one official MIME type for these files, I
've brought
1615 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
1616 media-types mailing list
</a
>. If you are interested in discussion
1617 which MIME type to use as the official for patch files, or involved in
1618 making software using a MIME type for patches, perhaps you would like
1619 to join the discussion?
</p
>
1621 <p
>As usual, if you use Bitcoin and want to show your support of my
1622 activities, please send Bitcoin donations to my address
1623 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1628 <title>Automatic Google Drive sync using grive in Debian
</title>
1629 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
1630 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
1631 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
1632 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
1633 rescue the remains, I helped set up automatic sync with Google Drive.
1634 I did not find any sensible Debian package handling this
1635 automatically, so I rebuild the grive2 source from
1636 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
1637 task and added a autostart desktop entry and a small shell script to
1638 run in the background while the user is logged in to do the sync.
1639 Here is a sketch of the setup for future reference.
</p
>
1641 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
1642 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
1643 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
1644 to start the sync when the user log in:
</p
>
1646 <p
><blockquote
><pre
>
1648 Name=Google drive autosync
1650 Exec=/home/user/bin/grive-sync
1651 </pre
></blockquote
></p
>
1653 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
1654 ~/googledrive/ with the files in Google Drive.
</p
>
1656 <p
><blockquote
><pre
>
1661 if [
"$syncpid
" ] ; then
1665 trap cleanup EXIT INT QUIT
1666 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
1669 if ! xhost
>/dev/null
2>&1 ; then
1670 echo
"no DISPLAY, exiting as the user probably logged out
"
1673 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
1674 /usr/lib/grive/grive-sync.sh sync googledrive
1677 done
2>&1 | sed
"s%^%$
0:%
"
1678 </pre
></blockquote
></p
>
1680 <p
>Feel free to use the setup if you want. It can be assumed to be
1681 GNU GPL v2 licensed (or any later version, at your leisure), but I
1682 doubt this code is possible to claim copyright on.
</p
>
1684 <p
>As usual, if you use Bitcoin and want to show your support of my
1685 activities, please send Bitcoin donations to my address
1686 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1691 <title>Using the Kodi API to play Youtube videos
</title>
1692 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
1693 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
1694 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
1695 <description><p
>I continue to explore my Kodi installation, and today I wanted to
1696 tell it to play a youtube URL I received in a chat, without having to
1697 insert search terms using the on-screen keyboard. After searching the
1698 web for API access to the Youtube plugin and testing a bit, I managed
1699 to find a recipe that worked. If you got a kodi instance with its API
1700 available from http://kodihost/jsonrpc, you can try the following to
1701 have check out a nice cover band.
</p
>
1703 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
1704 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
1705 "params
": {
"item
": {
"file
":
1706 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
1707 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
1709 <p
>I
've extended kodi-stream program to take a video source as its
1710 first argument. It can now handle direct video links, youtube links
1711 and
'desktop
' to stream my desktop to Kodi. It is almost like a
1712 Chromecast. :)
</p
>
1714 <p
>As usual, if you use Bitcoin and want to show your support of my
1715 activities, please send Bitcoin donations to my address
1716 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1721 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
1722 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
1723 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
1724 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
1725 <description><p
>For a while now, I have looked for a sensible way to share images
1726 with my family using a self hosted solution, as it is unacceptable to
1727 place images from my personal life under the control of strangers
1728 working for data hoarders like Google or Dropbox. The last few days I
1729 have drafted an approach that might work out, and I would like to
1730 share it with you. I would like to publish images on a server under
1731 my control, and point some Internet connected display units using some
1732 free and open standard to the images I published. As my primary
1733 language is not limited to ASCII, I need to store metadata using
1734 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
1735 of reading a RSS feed with image references (aka using the
1736 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
1737 of such frames. In the end I gave up that approach.
</p
>
1739 <p
>Some months ago, I discovered that
1740 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
1741 read images from a RSS feed, and used it to set up a screen saver on
1742 my home info screen, showing images from the Daily images feed from
1743 NASA. This proved to work well. More recently I discovered that
1744 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
1745 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
1746 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
1747 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
1748 screen saver capable of reading a RSS feed with images and news. For
1749 fun, I used it this summer to test Kodi on my parents TV by hooking up
1750 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1751 screen saver showing selected pictures from my selection.
</p
>
1753 <p
>Armed with motivation and a test photo frame, I set out to generate
1754 a RSS feed for the Kodi instance. I adjusted my
<a
1755 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
1756 /var/www/html/privatepictures/, wrote a small Perl script to extract
1757 title and description metadata from the photo files and generate the
1758 RSS file. I ended up using Perl instead of python, as the
1759 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1760 tags I ended up using, while python3-exif did not. The relevant EXIF
1761 tags only support ASCII, so I had to find better alternatives. XMP
1762 seem to have the support I need.
</p
>
1764 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
1765 use tags that can be easily added/updated using normal free software
1766 photo managing software. I ended up using the tags set using this
1767 exiftool command, as these tags can also be set using digiKam:
</p
>
1769 <blockquote
><pre
>
1770 exiftool -headline=
'The RSS image title
' \
1771 -description=
'The RSS image description.
' \
1772 -subject+=for-family photo.jpeg
1773 </pre
></blockquote
>
1775 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
1776 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
1777 use the keyword/subject
'for-family
' to flag that the photo should be
1778 shared with my family. Images with this keyword set are located and
1779 copied into my Freedombox for the RSS generating script to find.
</p
>
1781 <p
>Are there better ways to do this? Get in touch if you have better
1782 suggestions.
</p
>
1784 <p
>As usual, if you use Bitcoin and want to show your support of my
1785 activities, please send Bitcoin donations to my address
1786 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1791 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
1792 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
1793 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
1794 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
1795 <description><p
>Last night, I wrote
1796 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
1797 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
1798 During the day I received valuable feedback, and thanks to the
1799 suggestions I have been able to rewrite the recipe into a much simpler
1800 approach requiring no setup at all. It is a single script that take
1801 care of it all.
</p
>
1803 <p
>This new script uses GStreamer instead of VLC to capture the
1804 desktop and stream it to Kodi. This fixed the video quality issue I
1805 saw initially. It further removes the need to add a m3u file on the
1806 Kodi machine, as it instead connects to
1807 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
1808 Kodi
</a
> and simply ask Kodi to play from the stream created using
1809 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1810 the script below, run it with the DNS name or IP address of the kodi
1811 server to stream to as the only argument, and watch your screen show
1812 up on the Kodi screen. Note, it depend on multicast on the local
1813 network, so if you need to stream outside the local network, the
1814 script must be modified. Also note, I have no idea if audio work, as
1815 I only care about the picture part.
</p
>
1817 <blockquote
><pre
>
1820 # Stream the Linux desktop view to Kodi. See
1821 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1822 # for backgorund information.
1824 # Make sure the stream is stopped in Kodi and the gstreamer process is
1825 # killed if something go wrong (for example if curl is unable to find the
1826 # kodi server). Do the same when interrupting this script.
1830 params=
"$
3"
1831 curl --silent --header
'Content-Type: application/json
' \
1832 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
1833 "http://$host/jsonrpc
"
1836 if [ -n
"$kodihost
" ] ; then
1837 # Stop the playing when we end
1838 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
1839 jq .result[].playerid)
1840 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
1842 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
1843 kill
"$gstpid
"
1846 trap cleanup EXIT INT
1848 if [ -n
"$
1" ]; then
1859 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
1860 cut -d
" " -f2|head -
1)
1861 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1862 videoconvert ! queue2 ! \
1863 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1864 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1865 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1866 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
1867 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1868 > /dev/null
2>&1 &
1871 # Give stream a second to get going
1874 # Ask kodi to start streaming using its JSON-RPC API
1875 kodicmd
"$kodihost
" Player.Open \
1876 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
1878 # wait for gst to end
1879 wait
"$gstpid
"
1880 </pre
></blockquote
>
1882 <p
>I hope you find the approach useful. I know I do.
</p
>
1884 <p
>As usual, if you use Bitcoin and want to show your support of my
1885 activities, please send Bitcoin donations to my address
1886 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1891 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
1892 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
1893 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
1894 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
1895 <description><p
>PS: See
1896 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
1897 followup post
</a
> for a even better approach.
</p
>
1899 <p
>A while back, I was asked by a friend how to stream the desktop to
1900 my projector connected to Kodi. I sadly had to admit that I had no
1901 idea, as it was a task I never had tried. Since then, I have been
1902 looking for a way to do so, preferable without much extra software to
1903 install on either side. Today I found a way that seem to kind of
1904 work. Not great, but it is a start.
</p
>
1906 <p
>I had a look at several approaches, for example
1907 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
1908 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
1909 local storage enough to store the stream locally. This is not going
1910 to work well for me, lacking enough free space, and it would
1911 impossible for my friend to get working.
</p
>
1913 <p
>Next, it occurred to me that perhaps I could use VLC to create a
1914 video stream that Kodi could play. Preferably using
1915 broadcast/multicast, to avoid having to change any setup on the Kodi
1916 side when starting such stream. Unfortunately, the only recipe I
1917 could find using multicast used the rtp protocol, and this protocol
1918 seem to not be supported by Kodi.
</p
>
1920 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
1921 have to specify the IP address of the streaming machine in both the
1922 sending command and the file on the Kodi server. But it is showing my
1923 desktop, and thus allow us to have a shared look on the big screen at
1924 the programs I work on.
</p
>
1926 <p
>I did not spend much time investigating codeces. I combined the
1927 rtp and rtsp recipes from
1928 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
1929 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
1930 this working on the desktop/streaming end.
</p
>
1932 <blockquote
><pre
>
1933 vlc screen:// --sout \
1934 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
1935 </pre
></blockquote
>
1937 <p
>I ssh-ed into my Kodi box and created a file like this with the
1938 same IP address:
</p
>
1940 <blockquote
><pre
>
1941 echo rtsp://
192.168.11.4:
8080/test.sdp \
1942 > /storage/videos/screenstream.m3u
1943 </pre
></blockquote
>
1945 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
1946 as I can tell the IP must be hardcoded for this to work. In other
1947 words, if someone elses machine is going to do the steaming, you have
1948 to update screenstream.m3u on the Kodi machine and adjust the vlc
1949 recipe. To get started, locate the file in Kodi and select the m3u
1950 file while the VLC stream is running. The desktop then show up in my
1951 big screen. :)
</p
>
1953 <p
>When using the same technique to stream a video file with audio,
1954 the audio quality is really bad. No idea if the problem is package
1955 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1956 enough to tell.
</p
>
1958 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
1959 succestions and reminded me about an important step. The
"screen:
"
1960 input source is only available once the vlc-plugin-access-extra
1961 package is installed on Debian. Without it, you will see this error
1962 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
1963 for details.
" He further found that it is possible to drop some parts
1964 of the VLC command line to reduce the amount of hardcoded information.
1965 It is also useful to consider using cvlc to avoid having the VLC
1966 window in the desktop view. In sum, this give us this command line on
1969 <blockquote
><pre
>
1970 cvlc screen:// --sout \
1971 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
1972 </pre
></blockquote
>
1974 <p
>and this on the Kodi end
<p
>
1976 <blockquote
><pre
>
1977 echo rtsp://
192.168.11.4:
8080/ \
1978 > /storage/videos/screenstream.m3u
1979 </pre
></blockquote
>
1981 <p
>Still bad image quality, though. But I did discover that streaming
1982 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1983 audio quality, so I guess the issue is in the input or transcoding
1984 parts, not the rtsp part. I
've tried to change the vb and ab
1985 parameters to use more bandwidth, but it did not make a
1986 difference.
</p
>
1988 <p
>I further received a suggestion from Einar Haraldseid to try using
1989 gstreamer instead of VLC, and this proved to work great! He also
1990 provided me with the trick to get Kodi to use a multicast stream as
1991 its source. By using this monstrous oneliner, I can stream my desktop
1992 with good video quality in reasonable framerate to the
239.255.0.1
1993 multicast address on port
1234:
1995 <blockquote
><pre
>
1996 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1997 videoconvert ! queue2 ! \
1998 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1999 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
2000 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
2001 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
2002 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
2003 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
2004 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2005 </pre
></blockquote
>
2007 <p
>and this on the Kodi end
<p
>
2009 <blockquote
><pre
>
2010 echo udp://@
239.255.0.1:
1234 \
2011 > /storage/videos/screenstream.m3u
2012 </pre
></blockquote
>
2014 <p
>Note the trick to pick a valid pulseaudio source. It might not
2015 pick the one you need. This approach will of course lead to trouble
2016 if more than one source uses the same multicast port and address.
2017 Note the ttl-mc=
1 setting, which limit the multicast packages to the
2018 local network. If the value is increased, your screen will be
2019 broadcasted further, one network
"hop
" for each increase (read up on
2020 multicast to learn more. :)!
</p
>
2022 <p
>Having cracked how to get Kodi to receive multicast streams, I
2023 could use this VLC command to stream to the same multicast address.
2024 The image quality is way better than the rtsp approach, but gstreamer
2025 seem to be doing a better job.
</p
>
2027 <blockquote
><pre
>
2028 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
2029 </pre
></blockquote
>
2031 <p
>As usual, if you use Bitcoin and want to show your support of my
2032 activities, please send Bitcoin donations to my address
2033 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2038 <title>What is the most supported MIME type in Debian in
2018?
</title>
2039 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
2040 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
2041 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
2042 <description><p
>Five years ago,
2043 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
2044 measured what the most supported MIME type in Debian was
</a
>, by
2045 analysing the desktop files in all packages in the archive. Since
2046 then, the DEP-
11 AppStream system has been put into production, making
2047 the task a lot easier. This made me want to repeat the measurement,
2048 to see how much things changed. Here are the new numbers, for
2049 unstable only this time:
2051 <p
><strong
>Debian Unstable:
</strong
></p
>
2055 ----- -----------------------
2067 30 audio/x-vorbis+ogg
2068 29 image/x-portable-pixmap
2070 27 image/x-portable-bitmap
2072 26 application/x-ogg
2078 <p
>The list was created like this using a sid chroot:
"cat
2079 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
2080 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
2082 <p
>It is interesting to see how image formats have passed text/plain
2083 as the most announced supported MIME type. These days, thanks to the
2084 AppStream system, if you run into a file format you do not know, and
2085 want to figure out which packages support the format, you can find the
2086 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
2087 look up all packages announcing support for this format in their
2088 AppStream metadata (XML or .desktop file) using
"appstreamcli
2089 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
2090 me, want to know which packages support inode/directory, you can get a
2091 list like this:
</p
>
2093 <p
><blockquote
><pre
>
2094 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2101 Package: doublecmd-common
2103 Package: enlightenment
2123 </pre
></blockquote
></p
>
2125 <p
>Using the same method, I can quickly discover that the Sketchup file
2126 format is not yet supported by any package in Debian:
</p
>
2128 <p
><blockquote
><pre
>
2129 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2130 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
2132 </pre
></blockquote
></p
>
2134 <p
>Yesterday I used it to figure out which packages support the STL
3D
2137 <p
><blockquote
><pre
>
2138 % appstreamcli what-provides mimetype application/sla|grep Package
2143 </pre
></blockquote
></p
>
2145 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
2147 <p
>As usual, if you use Bitcoin and want to show your support of my
2148 activities, please send Bitcoin donations to my address
2149 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2154 <title>Debian APT upgrade without enough free space on the disk...
</title>
2155 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
2156 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
2157 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
2158 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2159 for a while, and when I need to update it there is not enough free
2160 space on the disk for apt to do a normal
'apt upgrade
'. I normally
2161 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
2162 upgrade only some of the packages in one batch, until the amount of
2163 packages to download fall below the amount of free space available.
2164 Today, I had about
500 packages to upgrade, and after a while I got
2165 tired of trying to install chunks of packages manually. I concluded
2166 that I did not have the spare hours required to complete the task, and
2167 decided to see if I could automate it. I came up with this small
2168 script which I call
'apt-in-chunks
':
</p
>
2170 <p
><blockquote
><pre
>
2173 # Upgrade packages when the disk is too full to upgrade every
2174 # upgradable package in one lump. Fetching packages to upgrade using
2175 # apt, and then installing using dpkg, to avoid changing the package
2176 # flag for manual/automatic.
2181 if [
"$
1" ]; then
2182 grep -v
"$
1"
2188 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
2189 echo
"Upgrading $p
"
2191 apt install --download-only -y $p
2192 for f in /var/cache/apt/archives/*.deb; do
2193 if [ -e
"$f
" ]; then
2194 dpkg -i /var/cache/apt/archives/*.deb
2199 </pre
></blockquote
></p
>
2201 <p
>The script will extract the list of packages to upgrade, try to
2202 download the packages needed to upgrade one package, install the
2203 downloaded packages using dpkg. The idea is to upgrade packages
2204 without changing the APT mark for the package (ie the one recording of
2205 the package was manually requested or pulled in as a dependency). To
2206 use it, simply run it as root from the command line. If it fail, try
2207 'apt install -f
' to clean up the mess and run the script again. This
2208 might happen if the new packages conflict with one of the old
2209 packages. dpkg is unable to remove, while apt can do this.
</p
>
2211 <p
>It take one option, a package to ignore in the list of packages to
2212 upgrade. The option to ignore a package is there to be able to skip
2213 the packages that are simply too large to unpack. Today this was
2214 'ghc
', but I have run into other large packages causing similar
2215 problems earlier (like TeX).
</p
>
2217 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
2218 alternative ways to handle this. The
"unattended-upgrades
2219 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
2220 each package to upgrade, and then upgrade them in order, smallest set
2221 first. It might be a better option than my above mentioned script.
2222 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
2223 the need for using
"dpkg -i
" in the script above.
</p
>
2225 <p
>As usual, if you use Bitcoin and want to show your support of my
2226 activities, please send Bitcoin donations to my address
2227 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2232 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
2233 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
2234 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
2235 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
2236 <description><p
>A new version of the
2237 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
2238 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
2239 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2240 useful. It was uploaded the last few days, and the last update will
2241 enter testing tomorrow. See the
2242 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
2243 notes
</a
> for the list of bug fixes and new features. Version
3.2
2244 was announced
6 days ago. We will try to get it into Debian as
2247 <p
>More information related to
3D printing is available on the
2248 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
2249 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
2250 in Debian.
</p
>
2252 <p
>As usual, if you use Bitcoin and want to show your support of my
2253 activities, please send Bitcoin donations to my address
2254 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2259 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
2260 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
2261 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
2262 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
2263 <description><p
>After several months of working and waiting, I am happy to report
2264 that the nice and user friendly
3D printer slicer software Cura just
2265 entered Debian Unstable. It consist of five packages,
2266 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
2267 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
2268 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
2269 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
2270 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
2271 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
2272 two, uranium and cura, entered Unstable yesterday. This should make
2273 it easier for Debian users to print on at least the Ultimaker class of
2274 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
2275 make life easier for at least me. :)
</p
>
2277 <p
>The work to make this happen was done by Gregor Riepl, and I was
2278 happy to assist him in sponsoring the packages. With the introduction
2279 of Cura, Debian is up to three
3D printer slicers at your service,
2280 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
2281 printer, give it a go. :)
</p
>
2283 <p
>The
3D printer software is maintained by the
3D printer Debian
2284 team, flocking together on the
2285 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
2286 mailing list and the
2287 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
2288 IRC channel.
</p
>
2290 <p
>The next step for Cura in Debian is to update the cura package to
2291 version
3.0.3 and then update the entire set of packages to version
2292 3.1.0 which showed up the last few days.
</p
>
2297 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
2298 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
2299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
2300 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
2301 <description><p
>At my nearby maker space,
2302 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
2303 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
2304 on Windows and MacOS X than Linux, because the software involved had
2305 to be manually compiled and set up on Linux while premade packages
2306 worked out of the box on Windows and MacOS X. I found this annoying,
2307 as the software involved,
2308 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
2309 and should be trivial to get up and running on Linux if someone took
2310 the time to package it for the relevant distributions. I even found
2311 <a href=
"https://bugs.debian.org/
706656">a request for adding into
2312 Debian
</a
> from
2013, which had seem some activity over the years but
2313 never resulted in the software showing up in Debian. So a few days
2314 ago I offered my help to try to improve the situation.
</p
>
2316 <p
>Now I am very happy to see that all the packages required by a
2317 working Cura in Debian are uploaded into Debian and waiting in the NEW
2318 queue for the ftpmasters to have a look. You can track the progress
2320 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
2321 status page for the
3D printer team
</a
>.
</p
>
2323 <p
>The uploaded packages are a bit behind upstream, and was uploaded
2324 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
2325 queue
</a
> while we work up updating the packages to the latest
2326 upstream version.
</p
>
2328 <p
>On a related note, two competitors for Cura, which I found harder
2329 to use and was unable to configure correctly for Ultimaker
2+ in the
2330 short time I spent on it, are already in Debian. If you are looking
2331 for
3D printer
"slicers
" and want something already available in
2333 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
2334 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
2335 The latter is a fork of the former.
</p
>
2337 <p
>As usual, if you use Bitcoin and want to show your support of my
2338 activities, please send Bitcoin donations to my address
2339 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2344 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
2345 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
2346 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
2347 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
2348 <description><p
>Every mobile phone announce its existence over radio to the nearby
2349 mobile cell towers. And this radio chatter is available for anyone
2350 with a radio receiver capable of receiving them. Details about the
2351 mobile phones with very good accuracy is of course collected by the
2352 phone companies, but this is not the topic of this blog post. The
2353 mobile phone radio chatter make it possible to figure out when a cell
2354 phone is nearby, as it include the SIM card ID (IMSI). By paying
2355 attention over time, one can see when a phone arrive and when it leave
2356 an area. I believe it would be nice to make this information more
2357 available to the general public, to make more people aware of how
2358 their phones are announcing their whereabouts to anyone that care to
2361 <p
>I am very happy to report that we managed to get something
2362 visualizing this information up and running for
2363 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
2364 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2365 library. The solution is based on the
2366 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
2367 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
2368 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
2369 Sone from the Computer Science department of the University of
2370 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
2371 IMSIs) as dots in a web browser graph, with lines to the dot
2372 representing mobile base station it is talking to. It was working in
2373 the lab yesterday, and was moved into place this morning.
</p
>
2375 <p
>We set up a fairly powerful desktop machine using Debian
2376 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2377 connected and visualize the visible cell phone towers using an
2378 <a href=
"https://github.com/marlow925/hopglass
">English version of
2379 Hopglass
</a
>. A fairly powerfull machine is needed as the
2380 grgsm_livemon_headless processes from
2381 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
2382 the radio signal to data packages is quite CPU intensive.
</p
>
2384 <p
>The frequencies to listen to, are identified using a slightly
2385 patched scan-and-livemon (to set the --args values for each receiver),
2386 and the Hopglass data is generated using the
2387 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
2388 in my meshviewer-output branch
</a
>. For some reason we could not get
2389 more than four SDRs working. There is also a geographical map trying
2390 to show the location of the base stations, but I believe their
2391 coordinates are hardcoded to some random location in Germany, I
2392 believe. The code should be replaced with code to look up location in
2393 a text file, a sqlite database or one of the online databases
2395 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
2396 issue for the topic
</a
>.
2398 <p
>If this sound interesting, visit the stand at the festival!
</p
>
2403 <title>Easier recipe to observe the cell phones around you
</title>
2404 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
2405 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
2406 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
2407 <description><p
>A little more than a month ago I wrote
2408 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
2409 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2410 to nearby mobile phone base stations using Debian GNU/Linux and a
2411 cheap USB software defined radio
</a
>, and thus being able to pinpoint
2412 the location of people and equipment (like cars and trains) with an
2413 accuracy of a few kilometer. Since then we have worked to make the
2414 procedure even simpler, and it is now possible to do this without any
2415 manual frequency tuning and without building your own packages.
</p
>
2417 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
2418 package is now included in Debian testing and unstable, and the
2419 IMSI-catcher code no longer require root access to fetch and decode
2420 the GSM data collected using gr-gsm.
</p
>
2422 <p
>Here is an updated recipe, using packages built by Debian and a git
2423 clone of two python scripts:
</p
>
2427 <li
>Start with a Debian machine running the Buster version (aka
2428 testing).
</li
>
2430 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
2431 python-scapy
</tt
>' as root to install required packages.
</li
>
2433 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
2434 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
2436 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
2438 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2439 scan-and-livemon
</tt
>' to locate the frequency of nearby base
2440 stations and start listening for GSM packages on one of them.
</li
>
2442 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2443 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
2447 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
2448 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
2449 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
2450 work with RTL
8232 and other similar USB radio receivers you can get
2452 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
2453 from ebay
</a
>), so for now the solution is to scan using the RTL radio
2454 and only use HackRF for fetching GSM data.
</p
>
2456 <p
>As far as I can tell, a cell phone only show up on one of the
2457 frequencies at the time, so if you are going to track and count every
2458 cell phone around you, you need to listen to all the frequencies used.
2459 To listen to several frequencies, use the --numrecv argument to
2460 scan-and-livemon to use several receivers. Further, I am not sure if
2461 phones using
3G or
4G will show as talking GSM to base stations, so
2462 this approach might not see all phones around you. I typically see
2463 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
2465 <p
>I
've tried to run the scanner on a
2466 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
2467 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
2468 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
2469 stdout, I am told there it is caused by a buffer overflow between the
2470 radio and GNU Radio, caused by the program being unable to read the
2471 GSM data fast enough. If you see a stream of
'O
's from the terminal
2472 where you started scan-and-livemon, you need a give the process more
2473 CPU power. Perhaps someone are able to optimize the code to a point
2474 where it become possible to set up RPi3 based GSM sniffers? I tried
2475 using Raspbian instead of Debian, but there seem to be something wrong
2476 with GNU Radio on raspbian, causing glibc to abort().
</p
>
2481 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
2482 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
2483 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
2484 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
2485 <description><p
>On friday, I came across an interesting article in the Norwegian
2486 web based ICT news magazine digi.no on
2487 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
2488 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
2489 DVB-T software defined radios. The article refered to instructions
2490 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
2491 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
2493 <p
>The instructions said to use Ubuntu, install pip using apt (to
2494 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2495 and the ask pybombs to fetch and build everything you need from
2496 scratch. I wanted to see if I could do the same on the most recent
2497 Debian packages, but this did not work because pybombs tried to build
2498 stuff that no longer build with the most recent openssl library or
2499 some other version skew problem. While trying to get this recipe
2500 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
2501 and the only piece of software dependency missing in Debian was the
2502 gr-gsm package. I also found out that the lead upstream developer of
2503 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2504 Debian packages provided in an Ubuntu PPA repository. All I needed to
2505 do was to dget the Debian source package and built it.
</p
>
2507 <p
>The IMSI collector is a python script listening for packages on the
2508 loopback network device and printing to the terminal some specific GSM
2509 packages with IMSI numbers in them. The code is fairly short and easy
2510 to understand. The reason this work is because gr-gsm include a tool
2511 to read GSM data from a software defined radio like a DVB-T USB stick
2512 and other software defined radios, decode them and inject them into a
2513 network device on your Linux machine (using the loopback device by
2514 default). This proved to work just fine, and I
've been testing the
2515 collector for a few days now.
</p
>
2517 <p
>The updated and simpler recipe is thus to
</p
>
2521 <li
>start with a Debian machine running Stretch or newer,
</li
>
2523 <li
>build and install the gr-gsm package available from
2524 <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
>
2526 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
2528 <li
>run grgsm_livemon and adjust the frequency until the terminal
2529 where it was started is filled with a stream of text (meaning you
2530 found a GSM station).
</li
>
2532 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
2536 <p
>To make it even easier in the future to get this sniffer up and
2537 running, I decided to package
2538 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
2539 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
2540 #
871055</a
>), and the package was uploaded into the NEW queue today.
2541 Luckily the gnuradio maintainer has promised to help me, as I do not
2542 know much about gnuradio stuff yet.
</p
>
2544 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
2545 commercial tools like
2546 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
2547 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
2548 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
2549 Stingray
</a
>, but I hope the existance of cheap alternatives can make
2550 more people realise how their whereabouts when carrying a cell phone
2551 is easily tracked. Seeing the data flow on the screen, realizing that
2552 I live close to a police station and knowing that the police is also
2553 wearing cell phones, I wonder how hard it would be for criminals to
2554 track the position of the police officers to discover when there are
2555 police near by, or for foreign military forces to track the location
2556 of the Norwegian military forces, or for anyone to track the location
2557 of government officials...
</p
>
2559 <p
>It is worth noting that the data reported by the IMSI-catcher
2560 script mentioned above is only a fraction of the data broadcasted on
2561 the GSM network. It will only collect one frequency at the time,
2562 while a typical phone will be using several frequencies, and not all
2563 phones will be using the frequencies tracked by the grgsm_livemod
2564 program. Also, there is a lot of radio chatter being ignored by the
2565 simple_IMSI-catcher script, which would be collected by extending the
2566 parser code. I wonder if gr-gsm can be set up to listen to more than
2567 one frequency?
</p
>
2572 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
2573 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
2574 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
2575 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
2576 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
2578 <p
>I finally received a copy of the Norwegian Bokmål edition of
2579 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2580 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
2581 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2582 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
2583 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
2584 price. The book is also available for download in electronic form as
2585 PDF, EPUB and Mobipocket, as can be
2586 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
2587 as a web page
</a
>.
</p
>
2589 <p
>This is the second book I publish (the first was the book
2590 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
2592 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
2593 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
2595 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
2596 Bokmål
</a
>), and I am very excited to finally wrap up this
2598 "<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
2599 for Debian-administratoren
</a
>" will be well received.
</p
>
2604 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
2605 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
2606 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
2607 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
2608 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
2609 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
2610 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2611 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2612 på om den fri oversetterløsningen
2613 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
2614 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
2616 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
2619 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2620 rolle og muligheter til å håndtere internasjonale utfordringer, som
2621 for eksempel flykningekrisen.
</p
>
2623 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2624 på temaet:
</p
>
2626 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
2627 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
2632 <p
>Dette oversetter Apertium slik:
</p
>
2635 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2636 andre aktørar og høve til å handtera internasjonale utfordringar, som
2637 til dømes *flykningekrisen.
</p
>
2639 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
2643 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
2644 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
2649 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
2650 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2651 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2652 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
2653 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
2654 det er kanskje flisespikking. Det understreker vel bare at det alltid
2655 trengs korrekturlesning etter automatisk oversettelse.
</p
>
2660 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
2661 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
2662 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
2663 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
2664 <description><p
>Over the years, administrating thousand of NFS mounting linux
2665 computers at the time, I often needed a way to detect if the machine
2666 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
2667 file or directory affected by the hang, the process (and possibly the
2668 shell) will hang too. So you want to be able to detect this without
2669 risking the detection process getting stuck too. It has not been
2670 obvious how to do this. When the hang has lasted a while, it is
2671 possible to find messages like these in dmesg:
</p
>
2673 <p
><blockquote
>
2674 nfs: server nfsserver not responding, still trying
2675 <br
>nfs: server nfsserver OK
2676 </blockquote
></p
>
2678 <p
>It is hard to know if the hang is still going on, and it is hard to
2679 be sure looking in dmesg is going to work. If there are lots of other
2680 messages in dmesg the lines might have rotated out of site before they
2681 are noticed.
</p
>
2683 <p
>While reading through the nfs client implementation in linux kernel
2684 code, I came across some statistics that seem to give a way to detect
2685 it. The om_timeouts sunrpc value in the kernel will increase every
2686 time the above log entry is inserted into dmesg. And after digging a
2687 bit further, I discovered that this value show up in
2688 /proc/self/mountstats on Linux.
</p
>
2690 <p
>The mountstats content seem to be shared between files using the
2691 same file system context, so it is enough to check one of the
2692 mountstats files to get the state of the mount point for the machine.
2693 I assume this will not show lazy umounted NFS points, nor NFS mount
2694 points in a different process context (ie with a different filesystem
2695 view), but that does not worry me.
</p
>
2697 <p
>The content for a NFS mount point look similar to this:
</p
>
2699 <p
><blockquote
><pre
>
2701 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2702 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
2703 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
2705 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
2706 sec: flavor=
1,pseudoflavor=
1
2707 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
2708 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2709 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
2710 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2712 NULL:
0 0 0 0 0 0 0 0
2713 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2714 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
2715 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2716 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2717 READLINK:
125 125 0 20472 18620 0 1112 1118
2718 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2719 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2720 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
2721 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
2722 SYMLINK:
903 903 0 233428 245488 6 5865 5917
2723 MKNOD:
80 80 0 20148 21760 0 299 304
2724 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
2725 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
2726 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
2727 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
2728 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2729 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2730 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
2731 FSINFO:
2 2 0 232 328 0 1 1
2732 PATHCONF:
1 1 0 116 140 0 0 0
2733 COMMIT:
0 0 0 0 0 0 0 0
2735 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2737 </pre
></blockquote
></p
>
2739 <p
>The key number to look at is the third number in the per-op list.
2740 It is the number of NFS timeouts experiences per file system
2741 operation. Here
22 write timeouts and
5 access timeouts. If these
2742 numbers are increasing, I believe the machine is experiencing NFS
2743 hang. Unfortunately the timeout value do not start to increase right
2744 away. The NFS operations need to time out first, and this can take a
2745 while. The exact timeout value depend on the setup. For example the
2746 defaults for TCP and UDP mount points are quite different, and the
2747 timeout value is affected by the soft, hard, timeo and retrans NFS
2748 mount options.
</p
>
2750 <p
>The only way I have been able to get working on Debian and RedHat
2751 Enterprise Linux for getting the timeout count is to peek in /proc/.
2753 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
2754 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
2755 command can be used to get these timeout values. But this do not work
2756 on Linux, as far as I can tell. I
2757 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
2758 but have not seen any replies yet.
</p
>
2760 <p
>Is there a better way to figure out if a Linux NFS client is
2761 experiencing NFS hangs? Is there a way to detect which processes are
2762 affected? Is there a way to get the NFS mount going quickly once the
2763 network problem causing the NFS hang has been cleared? I would very
2764 much welcome some clues, as we regularly run into NFS hangs.
</p
>
2769 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
2770 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
2771 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</guid>
2772 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
2773 <description><p
>For almost a year now, we have been working on making a Norwegian
2774 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
2775 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
2776 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2777 we are working on the proof reading to ensure consistent language and
2778 use of correct computer science terms. The plan is to make the book
2779 available on paper, as well as in electronic form. For that to
2780 happen, the proof reading must be completed and all the figures need
2781 to be translated. If you want to help out, get in touch.
</p
>
2783 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
2785 fresh PDF edition
</a
> in A4 format (the final book will have smaller
2786 pages) of the book created every morning is available for
2787 proofreading. If you find any errors, please
2788 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
2789 Weblate and correct the error
</a
>. The
2790 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
2791 of the translation including figures
</a
> is a useful source for those
2792 provide Norwegian bokmål screen shots and figures.
</p
>
2797 <title>Unlimited randomness with the ChaosKey?
</title>
2798 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
2799 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
2800 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
2801 <description><p
>A few days ago I ordered a small batch of
2802 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
2803 USB dongle for generating entropy created by Bdale Garbee and Keith
2804 Packard. Yesterday it arrived, and I am very happy to report that it
2805 work great! According to its designers, to get it to work out of the
2806 box, you need the Linux kernel version
4.1 or later. I tested on a
2807 Debian Stretch machine (kernel version
4.9), and there it worked just
2808 fine, increasing the available entropy very quickly. I wrote a small
2809 test oneliner to test. It first print the current entropy level,
2810 drain /dev/random, and then print the entropy level for five seconds.
2811 Here is the situation without the ChaosKey inserted:
</p
>
2813 <blockquote
><pre
>
2814 % cat /proc/sys/kernel/random/entropy_avail; \
2815 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2816 for n in $(seq
1 5); do \
2817 cat /proc/sys/kernel/random/entropy_avail; \
2823 28 byte kopiert,
0,
000264565 s,
106 kB/s
2830 </pre
></blockquote
>
2832 <p
>The entropy level increases by
3-
4 every second. In such case any
2833 application requiring random bits (like a HTTPS enabled web server)
2834 will halt and wait for more entrpy. And here is the situation with
2835 the ChaosKey inserted:
</p
>
2837 <blockquote
><pre
>
2838 % cat /proc/sys/kernel/random/entropy_avail; \
2839 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2840 for n in $(seq
1 5); do \
2841 cat /proc/sys/kernel/random/entropy_avail; \
2847 104 byte kopiert,
0,
000487647 s,
213 kB/s
2854 </pre
></blockquote
>
2856 <p
>Quite the difference. :) I bought a few more than I need, in case
2857 someone want to buy one here in Norway. :)
</p
>
2859 <p
>Update: The dongle was presented at Debconf last year. You might
2860 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
2861 recording illuminating
</a
>. It explains exactly what the source of
2862 randomness is, if you are unable to spot it from the schema drawing
2863 available from the ChaosKey web site linked at the start of this blog
2869 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
2870 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
2871 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
2872 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
2873 <description><p
>Did you ever wonder where the web trafic really flow to reach the
2874 web servers, and who own the network equipment it is flowing through?
2875 It is possible to get a glimpse of this from using traceroute, but it
2876 is hard to find all the details. Many years ago, I wrote a system to
2877 map the Norwegian Internet (trying to figure out if our plans for a
2878 network game service would get low enough latency, and who we needed
2879 to talk to about setting up game servers close to the users. Back
2880 then I used traceroute output from many locations (I asked my friends
2881 to run a script and send me their traceroute output) to create the
2882 graph and the map. The output from traceroute typically look like
2885 <p
><pre
>
2886 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
2887 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
2888 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
2889 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
2890 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
2891 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
2892 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
2893 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
2897 </pre
></p
>
2899 <p
>This show the DNS names and IP addresses of (at least some of the)
2900 network equipment involved in getting the data traffic from me to the
2901 www.stortinget.no server, and how long it took in milliseconds for a
2902 package to reach the equipment and return to me. Three packages are
2903 sent, and some times the packages do not follow the same path. This
2904 is shown for hop
5, where three different IP addresses replied to the
2905 traceroute request.
</p
>
2907 <p
>There are many ways to measure trace routes. Other good traceroute
2908 implementations I use are traceroute (using ICMP packages) mtr (can do
2909 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2910 traceroute and a lot of other capabilities). All of them are easily
2911 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
2913 <p
>This time around, I wanted to know the geographic location of
2914 different route points, to visualize how visiting a web page spread
2915 information about the visit to a lot of servers around the globe. The
2916 background is that a web site today often will ask the browser to get
2917 from many servers the parts (for example HTML, JSON, fonts,
2918 JavaScript, CSS, video) required to display the content. This will
2919 leak information about the visit to those controlling these servers
2920 and anyone able to peek at the data traffic passing by (like your ISP,
2921 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
2923 <p
>Lets pick an example, the Norwegian parliament web site
2924 www.stortinget.no. It is read daily by all members of parliament and
2925 their staff, as well as political journalists, activits and many other
2926 citizens of Norway. A visit to the www.stortinget.no web site will
2927 ask your browser to contact
8 other servers: ajax.googleapis.com,
2928 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2929 stats.g.doubleclick.net, www.google-analytics.com,
2930 www.googletagmanager.com and www.netigate.se. I extracted this by
2931 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
2932 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2933 render the page (in HAR format using
2934 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
2935 netsniff example
</a
>. I am very grateful to Gorm for showing me how
2936 to do this). My goal is to visualize network traces to all IP
2937 addresses behind these DNS names, do show where visitors personal
2938 information is spread when visiting the page.
</p
>
2940 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
2941 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
>
2943 <p
>When I had a look around for options, I could not find any good
2944 free software tools to do this, and decided I needed my own traceroute
2945 wrapper outputting KML based on locations looked up using GeoIP. KML
2946 is easy to work with and easy to generate, and understood by several
2947 of the GIS tools I have available. I got good help from by NUUG
2948 colleague Anders Einar with this, and the result can be seen in
2949 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
2950 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
2951 free GeoIP databases I could find (and the for-pay databases my
2952 friends had access to) is not up to the task. The IP addresses of
2953 central Internet infrastructure would typically be placed near the
2954 controlling companies main office, and not where the router is really
2955 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
2956 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
2958 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
2959 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
>
2961 <p
>I also had a look at the visual traceroute graph created by
2962 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
2963 showing IP network ownership (aka AS owner) for the IP address in
2965 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
2966 graph display a lot of useful information about the traceroute in SVG
2967 format
</a
>, and give a good indication on who control the network
2968 equipment involved, but it do not include geolocation. This graph
2969 make it possible to see the information is made available at least for
2970 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2971 3 Communications and NetDNA.
</p
>
2973 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
2974 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
>
2976 <p
>In the process, I came across the
2977 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
2978 Salim Gasmi. Its methology of combining guesses based on DNS names,
2979 various location databases and finally use latecy times to rule out
2980 candidate locations seemed to do a very good job of guessing correct
2981 geolocation. But it could only do one trace at the time, did not have
2982 a sensor in Norway and did not make the geolocations easily available
2983 for postprocessing. So I contacted the developer and asked if he
2984 would be willing to share the code (he refused until he had time to
2985 clean it up), but he was interested in providing the geolocations in a
2986 machine readable format, and willing to set up a sensor in Norway. So
2987 since yesterday, it is possible to run traces from Norway in this
2988 service thanks to a sensor node set up by
2989 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
2990 trace in KML format for further processing.
</p
>
2992 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
2993 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
>
2995 <p
>Here we can see a lot of trafic passes Sweden on its way to
2996 Denmark, Germany, Holland and Ireland. Plenty of places where the
2997 Snowden confirmations verified the traffic is read by various actors
2998 without your best interest as their top priority.
</p
>
3000 <p
>Combining KML files is trivial using a text editor, so I could loop
3001 over all the hosts behind the urls imported by www.stortinget.no and
3002 ask for the KML file from GeoTraceroute, and create a combined KML
3003 file with all the traces (unfortunately only one of the IP addresses
3004 behind the DNS name is traced this time. To get them all, one would
3005 have to request traces using IP number instead of DNS names from
3006 GeoTraceroute). That might be the next step in this project.
</p
>
3008 <p
>Armed with these tools, I find it a lot easier to figure out where
3009 the IP traffic moves and who control the boxes involved in moving it.
3010 And every time the link crosses for example the Swedish border, we can
3011 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3012 Britain and NSA in USA and cables around the globe. (Hm, what should
3013 we tell them? :) Keep that in mind if you ever send anything
3014 unencrypted over the Internet.
</p
>
3016 <p
>PS: KML files are drawn using
3017 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
3018 Rublev
<a/
>, as it was less cluttered than the local Linux application
3019 Marble. There are heaps of other options too.
</p
>
3021 <p
>As usual, if you use Bitcoin and want to show your support of my
3022 activities, please send Bitcoin donations to my address
3023 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3028 <title>Appstream just learned how to map hardware to packages too!
</title>
3029 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
3030 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
3031 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
3032 <description><p
>I received a very nice Christmas present today. As my regular
3033 readers probably know, I have been working on the
3034 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
3035 system
</a
> for many years. The goal of the Isenkram system is to make
3036 it easier for users to figure out what to install to get a given piece
3037 of hardware to work in Debian, and a key part of this system is a way
3038 to map hardware to packages. Isenkram have its own mapping database,
3039 and also uses data provided by each package using the AppStream
3040 metadata format. And today,
3041 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
3042 Debian learned to look up hardware the same way Isenkram is doing it,
3043 ie using fnmatch():
</p
>
3045 <p
><pre
>
3046 % appstreamcli what-provides modalias \
3047 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3048 Identifier: pymissile [generic]
3050 Summary: Control original Striker USB Missile Launcher
3052 % appstreamcli what-provides modalias usb:v0694p0002d0000
3053 Identifier: libnxt [generic]
3055 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3058 Identifier: t2n [generic]
3060 Summary: Simple command-line tool for Lego NXT
3063 Identifier: python-nxt [generic]
3065 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3068 Identifier: nbc [generic]
3070 Summary: C compiler for LEGO Mindstorms NXT bricks
3073 </pre
></p
>
3075 <p
>A similar query can be done using the combined AppStream and
3076 Isenkram databases using the isenkram-lookup tool:
</p
>
3078 <p
><pre
>
3079 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3081 % isenkram-lookup usb:v0694p0002d0000
3087 </pre
></p
>
3089 <p
>You can find modalias values relevant for your machine using
3090 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
3092 <p
>If you want to make this system a success and help Debian users
3093 make the most of the hardware they have, please
3094 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
3095 AppStream metadata for your package following the guidelines
</a
>
3096 documented in the wiki. So far only
11 packages provide such
3097 information, among the several hundred hardware specific packages in
3098 Debian. The Isenkram database on the other hand contain
101 packages,
3099 mostly related to USB dongles. Most of the packages with hardware
3100 mapping in AppStream are LEGO Mindstorms related, because I have, as
3101 part of my involvement in
3102 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
3103 team
</a
> given priority to making sure LEGO users get proposed the
3104 complete set of packages in Debian for that particular hardware. The
3105 team also got a nice Christmas present today. The
3106 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
3107 package
</a
> made it into Debian. With this package in place, it is
3108 now possible to use the LEGO Mindstorms NXT unit with only free
3109 software, as the nxt-firmware package contain the source and firmware
3110 binaries for the NXT brick.
</p
>
3112 <p
>As usual, if you use Bitcoin and want to show your support of my
3113 activities, please send Bitcoin donations to my address
3114 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3119 <title>Isenkram updated with a lot more hardware-package mappings
</title>
3120 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
3121 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
3122 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
3123 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3124 system
</a
> I wrote two years ago to make it easier in Debian to find
3125 and install packages to get your hardware dongles to work, is still
3126 going strong. It is a system to look up the hardware present on or
3127 connected to the current system, and map the hardware to Debian
3128 packages. It can either be done using the tools in isenkram-cli or
3129 using the user space daemon in the isenkram package. The latter will
3130 notify you, when inserting new hardware, about what packages to
3131 install to get the dongle working. It will even provide a button to
3132 click on to ask packagekit to install the packages.
</p
>
3134 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
3136 <p
><pre
>
3153 </pre
></p
>
3155 <p
>It can also list the firware package providing firmware requested
3156 by the load kernel modules, which in my case is an empty list because
3157 I have all the firmware my machine need:
3159 <p
><pre
>
3160 % /usr/sbin/isenkram-autoinstall-firmware -l
3161 info: did not find any firmware files requested by loaded kernel modules. exiting
3163 </pre
></p
>
3165 <p
>The last few days I had a look at several of the around
250
3166 packages in Debian with udev rules. These seem like good candidates
3167 to install when a given hardware dongle is inserted, and I found
3168 several that should be proposed by isenkram. I have not had time to
3169 check all of them, but am happy to report that now there are
97
3170 packages packages mapped to hardware by Isenkram.
11 of these
3171 packages provide hardware mapping using AppStream, while the rest are
3172 listed in the modaliases file provided in isenkram.
</p
>
3174 <p
>These are the packages with hardware mappings at the moment. The
3175 <strong
>marked packages
</strong
> are also announcing their hardware
3176 support using AppStream, for everyone to use:
</p
>
3178 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
3179 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
3180 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
3181 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
3182 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
3183 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3184 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
3185 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3186 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3187 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3188 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
3189 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3190 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
3191 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3192 pcscd, pidgin-blinklight, printer-driver-splix,
3193 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
3194 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3195 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3196 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3197 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3198 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3199 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3200 xserver-xorg-video-vmware, yubikey-personalization and
3201 zd1211-firmware
</p
>
3203 <p
>If you know of other packages, please let me know with a wishlist
3204 bug report against the isenkram-cli package, and ask the package
3206 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
3207 metadata according to the guidelines
</a
> to provide the information
3208 for everyone. In time, I hope to get rid of the isenkram specific
3209 hardware mapping and depend exclusively on AppStream.
</p
>
3211 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
3212 much hardware, and suggest that the package with with any ethernet
3213 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
3214 the details. I hope the maintainer find time to address it soon. In
3215 the mean time I provide an override in isenkram.
</p
>
3220 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
3221 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
3222 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
3223 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
3224 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
3226 <p
>In my early years, I played
3227 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
3228 Elite
</a
> on my PC. I spent many months trading and fighting in
3229 space, and reached the
'elite
' fighting status before I moved on. The
3230 original Elite game was available on Commodore
64 and the IBM PC
3231 edition I played had a
64 KB executable. I am still impressed today
3232 that the authors managed to squeeze both a
3D engine and details about
3233 more than
2000 planet systems across
7 galaxies into a binary so
3236 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
3237 software game Oolite inspired by Elite
</a
> for a while, but did not
3238 really have time to test it properly until a few days ago. It was
3239 great to discover that my old knowledge about trading routes were
3240 still valid. But my fighting and flying abilities were gone, so I had
3241 to retrain to be able to dock on a space station. And I am still not
3242 able to make much resistance when I am attacked by pirates, so I
3243 bougth and mounted the most powerful laser in the rear to be able to
3244 put up at least some resistance while fleeing for my life. :)
</p
>
3246 <p
>When playing Elite in the late eighties, I had to discover
3247 everything on my own, and I had long lists of prices seen on different
3248 planets to be able to decide where to trade what. This time I had the
3250 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
3251 where information about each planet is easily available with common
3252 price ranges and suggested trading routes. This improved my ability
3253 to earn money and I have been able to earn enough to buy a lot of
3254 useful equipent in a few days. I believe I originally played for
3255 months before I could get a docking computer, while now I could get it
3256 after less then a week.
</p
>
3258 <p
>If you like science fiction and dreamed of a life as a vagabond in
3259 space, you should try out Oolite. It is available for Linux, MacOSX
3260 and Windows, and is included in Debian and derivatives since
2011.
</p
>
3262 <p
>As usual, if you use Bitcoin and want to show your support of my
3263 activities, please send Bitcoin donations to my address
3264 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3269 <title>Quicker Debian installations using eatmydata
</title>
3270 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
3271 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
3272 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
3273 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
3274 installation system, observing how using
3275 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
3276 could speed up the installation
</a
> quite a bit. My testing measured
3277 speedup around
20-
40 percent for Debian Edu, where we install around
3278 1000 packages from within the installer. The eatmydata package
3279 provide a way to disable/delay file system flushing. This is a bit
3280 risky in the general case, as files that should be stored on disk will
3281 stay only in memory a bit longer than expected, causing problems if a
3282 machine crashes at an inconvenient time. But for an installation, if
3283 the machine crashes during installation the process is normally
3284 restarted, and avoiding disk operations as much as possible to speed
3285 up the process make perfect sense.
3287 <p
>I added code in the Debian Edu specific installation code to enable
3288 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
3289 but did not have time to push it any further. But a few months ago I
3290 picked it up again and worked with the libeatmydata package maintainer
3291 Mattia Rizzolo to make it easier for everyone to get this installation
3292 speedup in Debian. Thanks to our cooperation There is now an
3293 eatmydata-udeb package in Debian testing and unstable, and simply
3294 enabling/installing it in debian-installer (d-i) is enough to get the
3295 quicker installations. It can be enabled using preseeding. The
3296 following untested kernel argument should do the trick:
</p
>
3298 <blockquote
><pre
>
3299 preseed/early_command=
"anna-install eatmydata-udeb
"
3300 </pre
></blockquote
>
3302 <p
>This should ask d-i to install the package inside the d-i
3303 environment early in the installation sequence. Having it installed
3304 in d-i in turn will make sure the relevant scripts are called just
3305 after debootstrap filled /target/ with the freshly installed Debian
3306 system to configure apt to run dpkg with eatmydata. This is enough to
3307 speed up the installation process. There is a proposal to
3308 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
3309 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
3310 tested its impact.
</p
>
3316 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
3317 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
3318 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
3319 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
3320 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3321 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3322 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3323 elever over det ganske land skal levere inn hvert år. Det mange ikke
3324 vet er at selv om de kommersielle alternativene
3325 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
3326 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
3327 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3328 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3329 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3330 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3331 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3332 nynorsk, og få den automatoversatt til det andre skriftspråket.
3333 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3334 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3335 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3336 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3337 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
3338 teksten din i webskjemaet der.
3340 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
3341 teknologien kan du enten installere pakken
3342 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
3343 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3344 api.apertium.org. Se
3345 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
3346 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3347 denne teksten som ble skrevet på bokmål over maskinoversatt til
3352 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3353 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3354 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3355 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3356 veit er at sjølv om dei kommersielle alternativa
3357 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
3358 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
3359 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3360 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3361 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3362 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3363 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3364 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3365 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3366 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3367 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3368 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3369 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
3370 teksta di i *webskjemaet der.
3372 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
3373 teknologien kan du anten installera pakken
3374 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
3375 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3376 *api.*apertium.org. Sjå
3377 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
3378 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3379 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3385 <title>Coz profiler for multi-threaded software is now in Debian
</title>
3386 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
3387 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
3388 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
3389 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
3390 profiler able to run benchmarking experiments on the instrumented
3391 multi-threaded program, finally
3392 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
3393 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
3395 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
3396 blogged about the coz tool
</a
> in August working with upstream to make
3397 it suitable for Debian. There are still issues with clang
3398 compatibility, inline assembly only working x86 and minimized
3399 JavaScript libraries.
</p
>
3401 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
3403 <p
><blockquote
>
3404 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
3405 </blockquote
></p
>
3407 <p
>This will produce a profile.coz file in the current working
3408 directory with the profiling information. This is then given to a
3409 JavaScript application provided in the package and available from
3410 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
3411 To start the local copy, invoke it in a browser like this:
</p
>
3413 <p
><blockquote
>
3414 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
3415 </blockquote
></p
>
3417 <p
>See the project home page and the
3418 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
3419 ;login: article on Coz
</a
> for more information on how it is
3425 <title>My own self balancing Lego Segway
</title>
3426 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
3427 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
3428 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
3429 <description><p
>A while back I received a Gyro sensor for the NXT
3430 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
3431 present. It had been on my wishlist for a while, because I wanted to
3432 build a Segway like balancing lego robot. I had already built
3433 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
3434 robot
</a
> with the kids, using the light/color sensor included in the
3435 NXT kit as the balance sensor, but it was not working very well. It
3436 could balance for a while, but was very sensitive to the light
3437 condition in the room and the reflective properties of the surface and
3438 would fall over after a short while. I wanted something more robust,
3440 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
3441 gyro sensor from HiTechnic
</a
> I believed would solve it on my
3442 wishlist for some years before it suddenly showed up as a gift from my
3443 loved ones. :)
</p
>
3445 <p
>Unfortunately I have not had time to sit down and play with it
3446 since then. But that changed some days ago, when I was searching for
3447 lego segway information and came across a recipe from HiTechnic for
3449 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
3450 HTWay
</a
>, a segway like balancing robot. Build instructions and
3451 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
3452 code
</a
> was included, so it was just a question of putting it all
3453 together. And thanks to the great work of many Debian developers, the
3454 compiler needed to build the source for the NXT is already included in
3455 Debian, so I was read to go in less than an hour. The resulting robot
3456 do not look very impressive in its simplicity:
</p
>
3458 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
3460 <p
>Because I lack the infrared sensor used to control the robot in the
3461 design from HiTechnic, I had to comment out the last task
3462 (taskControl). I simply placed /* and */ around it get the program
3463 working without that sensor present. Now it balances just fine until
3464 the battery status run low:
</p
>
3466 <p align=
"center
"><video width=
"70%
" controls=
"true
">
3467 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
3468 </video
></p
>
3470 <p
>Now we would like to teach it how to follow a line and take remote
3471 control instructions using the included Bluetooth receiver in the NXT.
</p
>
3473 <p
>If you, like me, love LEGO and want to make sure we find the tools
3474 they need to work with LEGO in Debian and all our derivative
3475 distributions like Ubuntu, check out
3476 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
3477 project page
</a
> and join the Debian LEGO team. Personally I own a
3478 RCX and NXT controller (no EV3), and would like to make sure the
3479 Debian tools needed to program the systems I own work as they
3485 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
3486 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
3487 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
3488 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
3489 <description><p
>In July
3490 <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
3491 wrote how to get the Signal Chrome/Chromium app working
</a
> without
3492 the ability to receive SMS messages (aka without a cell phone). It is
3493 time to share some experiences and provide an updated setup.
</p
>
3495 <p
>The Signal app have worked fine for several months now, and I use
3496 it regularly to chat with my loved ones. I had a major snag at the
3497 end of my summer vacation, when the the app completely forgot my
3498 setup, identity and keys. The reason behind this major mess was
3499 running out of disk space. To avoid that ever happening again I have
3500 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
3501 roll back to an earlier version if the files are wiped by mistake. I
3502 had to use it once after introducing the git backup. When rolling
3503 back to an earlier version, one need to use the
'reset session
' option
3504 in Signal to get going, and notify the people you talk with about the
3505 problem. I assume there is some sequence number tracking in the
3506 protocol to detect rollback attacks. The git repository is rather big
3507 (
674 MiB so far), but I have not tried to figure out if some of the
3508 content can be added to a .gitignore file due to lack of spare
3511 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
3512 make it impossible to send messages using Signal. I could still
3513 receive them, but had to patch the code with a new timestamp to send.
3514 I believe the timeout is added by the developers to force people to
3515 upgrade to the latest version of the app, even when there is no
3516 protocol changes, to reduce the version skew among the user base and
3517 thus try to keep the number of support requests down.
</p
>
3519 <p
>Since my original recipe, the Signal source code changed slightly,
3520 making the old patch fail to apply cleanly. Below is an updated
3521 patch, including the shell wrapper I use to start Signal. The
3522 original version required a new user to locate the JavaScript console
3523 and call a function from there. I got help from a friend with more
3524 JavaScript knowledge than me to modify the code to provide a GUI
3525 button instead. This mean that to get started you just need to run
3526 the wrapper and click the
'Register without mobile phone
' to get going
3527 now. I
've also modified the timeout code to always set it to
90 days
3528 in the future, to avoid having to patch the code regularly.
</p
>
3530 <p
>So, the updated recipe for Debian Jessie:
</p
>
3534 <li
>First, install required packages to get the source code and the
3535 browser you need. Signal only work with Chrome/Chromium, as far as I
3536 know, so you need to install it.
3539 apt install git tor chromium
3540 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3541 </pre
></li
>
3543 <li
>Modify the source code using command listed in the the patch
3544 block below.
</li
>
3546 <li
>Start Signal using the run-signal-app wrapper (for example using
3547 <tt
>`pwd`/run-signal-app
</tt
>).
3549 <li
>Click on the
'Register without mobile phone
', will in a phone
3550 number you can receive calls to the next minute, receive the
3551 verification code and enter it into the form field and press
3552 'Register
'. Note, the phone number you use will be user Signal
3553 username, ie the way others can find you on Signal.
</li
>
3555 <li
>You can now use Signal to contact others. Note, new contacts do
3556 not show up in the contact list until you restart Signal, and there is
3557 no way to assign names to Contacts. There is also no way to create or
3558 update chat groups. I suspect this is because the web app do not have
3559 a associated contact database.
</li
>
3563 <p
>I am still a bit uneasy about using Signal, because of the way its
3564 main author moxie0 reject federation and accept dependencies to major
3565 corporations like Google (part of the code is fetched from Google) and
3566 Amazon (the central coordination point is owned by Amazon). See for
3568 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
3569 LibreSignal issue tracker
</a
> for a thread documenting the authors
3570 view on these issues. But the network effect is strong in this case,
3571 and several of the people I want to communicate with already use
3572 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
3573 once it
<a href=
"https://bugs.debian.org/
830265">work on my
3574 laptop
</a
>? It already work on Windows and Android, and is included
3575 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
3576 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
3577 working on Debian Stable.
</p
>
3579 <p
>Anyway, this is the patch I apply to the Signal code to get it
3580 working. It switch to the production servers, disable to timeout,
3581 make registration easier and add the shell wrapper:
</p
>
3584 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
3585 diff --git a/js/background.js b/js/background.js
3586 index
24b4c1d.
.579345f
100644
3587 --- a/js/background.js
3588 +++ b/js/background.js
3593 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3594 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
3595 var SERVER_PORTS = [
80,
4433,
8443];
3596 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3597 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3598 var messageReceiver;
3599 window.getSocketStatus = function() {
3600 if (messageReceiver) {
3601 diff --git a/js/expire.js b/js/expire.js
3602 index
639aeae..beb91c3
100644
3607 'use strict
';
3608 - var BUILD_EXPIRATION =
0;
3609 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
3611 window.extension = window.extension || {};
3613 diff --git a/js/views/install_view.js b/js/views/install_view.js
3614 index
7816f4f.
.1d6233b
100644
3615 --- a/js/views/install_view.js
3616 +++ b/js/views/install_view.js
3619 'click .step1
': this.selectStep.bind(this,
1),
3620 'click .step2
': this.selectStep.bind(this,
2),
3621 -
'click .step3
': this.selectStep.bind(this,
3)
3622 +
'click .step3
': this.selectStep.bind(this,
3),
3623 +
'click .callreg
': function() { extension.install(
'standalone
') },
3626 clearQR: function() {
3627 diff --git a/options.html b/options.html
3628 index dc0f28e.
.8d709f6
100644
3632 &lt;div class=
'nav
'>
3633 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
3634 &lt;p
>{{ installTagline }}
&lt;/p
>
3635 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
3636 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
3637 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
3640 &lt;span class=
'dot step1 selected
'>&lt;/span
>
3641 &lt;span class=
'dot step2
'>&lt;/span
>
3642 &lt;span class=
'dot step3
'>&lt;/span
>
3643 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
3644 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
3650 +userdata=
"`pwd`/userdata
"
3651 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
3652 + (cd $userdata
&& git init)
3654 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
3656 + --proxy-server=
"socks://localhost:
9050" \
3657 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3659 chmod a+rx run-signal-app
3662 <p
>As usual, if you use Bitcoin and want to show your support of my
3663 activities, please send Bitcoin donations to my address
3664 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3669 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
3670 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
3671 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
3672 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
3673 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3674 system
</a
> provide a practical and easy way to figure out which
3675 packages support the hardware in a given machine. The command line
3676 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
3677 convenient way to list and install packages relevant for the current
3678 hardware during system installation, both user space packages and
3679 firmware packages. The GUI background daemon on the other hand provide
3680 a pop-up proposing to install packages when a new dongle is inserted
3681 while using the computer. For example, if you plug in a smart card
3682 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
3683 that package isn
't already installed, and if you plug in a USB video
3684 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
3685 cheese is currently missing. This already work just fine.
</p
>
3687 <p
>But Isenkram depend on a database mapping from hardware IDs to
3688 package names. When I started no such database existed in Debian, so
3689 I made my own data set and included it with the isenkram package and
3690 made isenkram fetch the latest version of this database from git using
3691 http. This way the isenkram users would get updated package proposals
3692 as soon as I learned more about hardware related packages.
</p
>
3694 <p
>The hardware is identified using modalias strings. The modalias
3695 design is from the Linux kernel where most hardware descriptors are
3696 made available as a strings that can be matched using filename style
3697 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3698 identifiers.
</p
>
3700 <p
>The downside to the Isenkram specific database is that there is no
3701 information about relevant distribution / Debian version, making
3702 isenkram propose obsolete packages too. But along came AppStream, a
3703 cross distribution mechanism to store and collect metadata about
3704 software packages. When I heard about the proposal, I contacted the
3705 people involved and suggested to add a hardware matching rule using
3706 modalias strings in the specification, to be able to use AppStream for
3707 mapping hardware to packages. This idea was accepted and AppStream is
3708 now a great way for a package to announce the hardware it support in a
3709 distribution neutral way. I wrote
3710 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
3711 recipe on how to add such meta-information
</a
> in a blog post last
3712 December. If you have a hardware related package in Debian, please
3713 announce the relevant hardware IDs using AppStream.
</p
>
3715 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
3716 RCX or NXT unit, announce this support using AppStream. The effect is
3717 that when you insert such LEGO robot controller into your Debian
3718 machine, Isenkram will propose to install the packages needed to get
3719 it working. The intention is that this should allow the local user to
3720 start programming his robot controller right away without having to
3721 guess what packages to use or which permissions to fix.
</p
>
3723 <p
>But when I sat down with my son the other day to program our NXT
3724 unit using his Debian Stretch computer, I discovered something
3725 annoying. The local console user (ie my son) did not get access to
3726 the USB device for programming the unit. This used to work, but no
3727 longer in Jessie and Stretch. After some investigation and asking
3728 around on #debian-devel, I discovered that this was because udev had
3729 changed the mechanism used to grant access to local devices. The
3730 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
3731 no longer applied, because LDAP users no longer was added to the
3732 plugdev group during login. Michael Biebl told me that this method
3733 was obsolete and the new method used ACLs instead. This was good
3734 news, as the plugdev mechanism is a mess when using a remote user
3735 directory like LDAP. Using ACLs would make sure a user lost device
3736 access when she logged out, even if the user left behind a background
3737 process which would retain the plugdev membership with the ConsoleKit
3738 setup. Armed with this knowledge I moved on to fix the access problem
3739 for the LEGO Mindstorms related packages.
</p
>
3741 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
3742 applied directly for a device, or is applied in
3743 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
3744 LEGO Mindstorms udev rules did not have a class, I decided to add the
3745 tag directly in the udev rules files included in the packages. Here
3746 is one example. For the nqc C compiler for the RCX, the
3747 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
3749 <p
><pre
>
3750 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
3751 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
3752 </pre
></p
>
3754 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
3755 packages using plugdev in their /lib/udev/rules.d/ files should be
3756 changed to use this tag (either directly or indirectly via
3757 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
3758 to detect this?
</p
>
3760 <p
>I
've been unable to find good documentation on the uaccess feature.
3761 It is unclear to me if the uaccess tag is an internal implementation
3762 detail like the udev-acl tag used by
3763 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
3764 indirect method is the preferred way. Michael
3765 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
3766 documentation from the systemd project
</a
> and I hope it will make
3767 this clearer. For now I use the generic classes when they exist and
3768 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
3769 directly if no such class exist.
</p
>
3771 <p
>To learn more about the isenkram system, please check out
3772 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3773 blog posts tagged isenkram
</a
>.
</p
>
3775 <p
>To help out making life for LEGO constructors in Debian easier,
3776 please join us on our IRC channel
3777 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
3778 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
3779 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
3780 list is not yet created, but we are working on it. :)
</p
>
3782 <p
>As usual, if you use Bitcoin and want to show your support of my
3783 activities, please send Bitcoin donations to my address
3784 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3789 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
3790 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
3791 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</guid>
3792 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
3793 <description><p
>In April we
3794 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
3795 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
3796 how to set up and administrate a Debian system. Today I am happy to
3797 report that the first draft is now publicly available. You can find
3798 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
3799 Administrator
's Handbook page
</a
> (under Other languages). The first
3800 eight chapters have a first draft translation, and we are working on
3801 proofreading the content. If you want to help out, please start
3803 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3804 hosted weblate project page
</a
>, and get in touch using
3805 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3806 translators mailing list
</a
>. Please also check out
3807 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3808 contributors
</a
>. A good way to contribute is to proofread the text
3809 and update weblate if you find errors.
</p
>
3811 <p
>Our goal is still to make the Norwegian book available on paper as well as
3812 electronic form.
</p
>
3817 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
3818 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
3819 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
3820 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
3821 <description><p
>This summer, I read a great article
3822 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
3823 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
3824 how to profile multi-threaded programs. It presented a system for
3825 profiling software by running experiences in the running program,
3826 testing how run time performance is affected by
"speeding up
" parts of
3827 the code to various degrees compared to a normal run. It does this by
3828 slowing down parallel threads while the
"faster up
" code is running
3829 and measure how this affect processing time. The processing time is
3830 measured using probes inserted into the code, either using progress
3831 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3832 can also measure unmodified code by measuring complete the program
3833 runtime and running the program several times instead.
</p
>
3835 <p
>The project and presentation was so inspiring that I would like to
3836 get the system into Debian. I
3837 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
3838 a WNPP request for it
</a
> and contacted upstream to try to make the
3839 system ready for Debian by sending patches. The build process need to
3840 be changed a bit to avoid running
'git clone
' to get dependencies, and
3841 to include the JavaScript web page used to visualize the collected
3842 profiling information included in the source package.
3843 But I expect that should work out fairly soon.
</p
>
3845 <p
>The way the system work is fairly simple. To run an coz experiment
3846 on a binary with debug symbols available, start the program like this:
3848 <p
><blockquote
><pre
>
3849 coz run --- program-to-run
3850 </pre
></blockquote
></p
>
3852 <p
>This will create a text file profile.coz with the instrumentation
3853 information. To show what part of the code affect the performance
3854 most, use a web browser and either point it to
3855 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
3856 or use the copy from git (in the gh-pages branch). Check out this web
3857 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
3858 profiling more useful you include
&lt;coz.h
&gt; and insert the
3859 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3860 code, rebuild and run the profiler. This allow coz to do more
3861 targeted experiments.
</p
>
3863 <p
>A video published by ACM
3864 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
3865 Coz profiler
</a
> is available from Youtube. There is also a paper
3866 from the
25th Symposium on Operating Systems Principles available
3868 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
3869 finding code that counts with causal profiling
</a
>.
</p
>
3871 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
3872 for Coz is available from github. It will only build with clang
3874 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
3875 feature missing in GCC
</a
>, but I
've submitted
3876 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
3877 it
</a
> and hope it will be included in the upstream source soon.
</p
>
3879 <p
>Please get in touch if you, like me, would like to see this piece
3880 of software in Debian. I would very much like some help with the
3881 packaging effort, as I lack the in depth knowledge on how to package
3882 C++ libraries.
</p
>
3887 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
3888 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
3889 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
3890 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
3891 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3892 to be a slight challenge. Here is the recipe if I ever need to do it
3893 again. It all started by me wanting to try the recipe to set up
3894 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
3895 hardened Android installation
</a
> from the Tor project blog on a
3896 device I had access to. It is a old mobile phone with a broken
3897 microphone The initial idea had been to just
3898 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
3899 CyanogenMod on it
</a
>, but did not quite find time to start on it
3900 until a few days ago.
</p
>
3902 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
3903 loader (press volume down and power at the same time), (
2) select
3904 'fastboot
' before (
3) connecting the device via USB to a Linux
3905 machine, (
4) request the device identifier token by running
'fastboot
3906 oem get_identifier_token
', (
5) request the device unlocking key using
3907 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
3908 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
3910 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
3911 or newer, and the device I was working on had
2.00.0027. This
3912 apparently can be easily fixed by downloading a Windows program and
3913 running it on your Windows machine, if you accept the terms Microsoft
3914 require you to accept to use Windows - which I do not. So I had to
3915 come up with a different approach. I got a lot of help from AndyCap
3916 on #nuug, and would not have been able to get this working without
3919 <p
>First I needed to extract the hboot firmware from
3920 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
3921 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
3922 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
3923 project named unruu
</a
> using libunshield. The unshield tool did not
3924 recognise the file format, but unruu worked and extracted rom.zip,
3925 containing the new hboot firmware and a text file describing which
3926 devices it would work for.
</p
>
3928 <p
>Next, I needed to get the new firmware into the device. For this I
3929 followed some instructions
3930 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
3931 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
3932 machine with Debian testing:
</p
>
3934 <p
><pre
>
3935 adb reboot-bootloader
3936 fastboot oem rebootRUU
3937 fastboot flash zip rom.zip
3938 fastboot flash zip rom.zip
3940 </pre
></p
>
3942 <p
>The flash command apparently need to be done twice to take effect,
3943 as the first is just preparations and the second one do the flashing.
3944 The adb command is just to get to the boot loader menu, so turning the
3945 device on while holding volume down and the power button should work
3948 <p
>With the new hboot version in place I could start following the
3949 instructions on the HTC developer web site. I got the device token
3950 like this:
</p
>
3952 <p
><pre
>
3953 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
3956 <p
>And once I got the unlock code via email, I could use it like
3959 <p
><pre
>
3960 fastboot flash unlocktoken Unlock_code.bin
3961 </pre
></p
>
3963 <p
>And with that final step in place, the phone was unlocked and I
3964 could start stuffing the software of my own choosing into the device.
3965 So far I only inserted a replacement recovery image to wipe the phone
3966 before I start. We will see what happen next. Perhaps I should
3967 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
3972 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
3973 <link>https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
3974 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
3975 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
3976 <description><p
>For a while now, I have wanted to test
3977 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
3978 said to provide end to end encrypted communication and several of my
3979 friends and family are already using it. As I by choice do not own a
3980 mobile phone, this proved to be harder than expected. And I wanted to
3981 have the source of the client and know that it was the code used on my
3982 machine. But yesterday I managed to get it working. I used the
3983 Github source, compared it to the source in
3984 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
3985 Signal Chrome app
</a
> available from the Chrome web store, applied
3986 patches to use the production Signal servers, started the app and
3987 asked for the hidden
"register without a smart phone
" form. Here is
3988 the recipe how I did it.
</p
>
3990 <p
>First, I fetched the Signal desktop source from Github, using
3993 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3996 <p
>Next, I patched the source to use the production servers, to be
3997 able to talk to other Signal users:
</p
>
4000 cat
&lt;
&lt;EOF | patch -p0
4001 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
4002 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
4003 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
4008 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
4009 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
4010 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
4011 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
4012 var messageReceiver;
4013 window.getSocketStatus = function() {
4014 if (messageReceiver) {
4015 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
4016 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
4017 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
4020 'use strict
';
4021 - var BUILD_EXPIRATION =
0;
4022 + var BUILD_EXPIRATION =
1474492690000;
4024 window.extension = window.extension || {};
4029 <p
>The first part is changing the servers, and the second is updating
4030 an expiration timestamp. This timestamp need to be updated regularly.
4031 It is set
90 days in the future by the build process (Gruntfile.js).
4032 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
4034 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
4035 script to launch Signal in Chromium.
</p
>
4042 --proxy-server=
"socks://localhost:
9050" \
4043 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4046 <p
> The script start the app and configure Chromium to use the Tor
4047 SOCKS5 proxy to make sure those controlling the Signal servers (today
4048 Amazon and Whisper Systems) as well as those listening on the lines
4049 will have a harder time location my laptop based on the Signal
4050 connections if they use source IP address.
</p
>
4052 <p
>When the script starts, one need to follow the instructions under
4053 "Standalone Registration
" in the CONTRIBUTING.md file in the git
4054 repository. I right clicked on the Signal window to get up the
4055 Chromium debugging tool, visited the
'Console
' tab and wrote
4056 'extension.install(
"standalone
")
' on the console prompt to get the
4057 registration form. Then I entered by land line phone number and
4058 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
4059 repeated the verification code three times. After entering the number
4060 into the verification code field in the form, I could start using
4061 Signal from my laptop.
4063 <p
>As far as I can tell, The Signal app will leak who is talking to
4064 whom and thus who know who to those controlling the central server,
4065 but such leakage is hard to avoid with a centrally controlled server
4066 setup. It is something to keep in mind when using Signal - the
4067 content of your chats are harder to intercept, but the meta data
4068 exposing your contact network is available to people you do not know.
4069 So better than many options, but not great. And sadly the usage is
4070 connected to my land line, thus allowing those controlling the server
4071 to associate it to my home and person. I would prefer it if only
4072 those I knew could tell who I was on Signal. There are options
4073 avoiding such information leakage, but most of my friends are not
4074 using them, so I am stuck with Signal for now.
</p
>
4076 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
4078 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
4079 and updated recipe for using the Signal app without a mobile
4080 phone
</a
>.
</p
>
4085 <title>The new
"best
" multimedia player in Debian?
</title>
4086 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
4087 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
4088 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
4089 <description><p
>When I set out a few weeks ago to figure out
4090 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
4091 multimedia player in Debian claimed to support most file formats /
4092 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
4093 the various players claimed support for. The range was from
55 to
130
4094 MIME types. I suspect most media formats are supported by all
4095 players, but this is not really reflected in the MimeTypes values in
4096 their desktop files. There are probably also some bogus MIME types
4097 listed, but it is hard to identify which one this is.
</p
>
4099 <p
>Anyway, in the mean time I got in touch with upstream for some of
4100 the players suggesting to add more MIME types to their desktop files,
4101 and decided to spend some time myself improving the situation for my
4102 favorite media player VLC. The fixes for VLC entered Debian unstable
4103 yesterday. The complete list of MIME types can be seen on the
4104 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
4105 player MIME type support status
</a
> Debian wiki page.
</p
>
4107 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
4108 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4109 kmplayer. I am sure some of the other players desktop files support
4110 several of the formats currently listed as working only with vlc,
4111 toten and parole.
</p
>
4113 <p
>A sad observation is that only
14 MIME types are listed as
4114 supported by all the tested multimedia players in Debian in their
4115 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4116 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4117 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4118 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4119 it sad that video/ogg and video/webm is not supported by all the media
4120 players in Debian. As far as I can tell, all of them can handle both
4126 <title>A program should be able to open its own files on Linux
</title>
4127 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
4128 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
4129 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
4130 <description><p
>Many years ago, when koffice was fresh and with few users, I
4131 decided to test its presentation tool when making the slides for a
4132 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4133 wrote the first draft of the slides, saved the result and went to bed
4134 the day before I would give the talk. The next day I took a plane to
4135 the location where the meeting should take place, and on the plane I
4136 started up koffice again to polish the talk a bit, only to discover
4137 that kpresenter refused to load its own data file. I cursed a bit and
4138 started making the slides again from memory, to have something to
4139 present when I arrived. I tested that the saved files could be
4140 loaded, and the day seemed to be rescued. I continued to polish the
4141 slides until I suddenly discovered that the saved file could no longer
4142 be loaded into kpresenter. In the end I had to rewrite the slides
4143 three times, condensing the content until the talk became shorter and
4144 shorter. After the talk I was able to pinpoint the problem
&ndash;
4145 kpresenter wrote inline images in a way itself could not understand.
4146 Eventually that bug was fixed and kpresenter ended up being a great
4147 program to make slides. The point I
'm trying to make is that we
4148 expect a program to be able to load its own data files, and it is
4149 embarrassing to its developers if it can
't.
</p
>
4151 <p
>Did you ever experience a program failing to load its own data
4152 files from the desktop file browser? It is not a uncommon problem. A
4153 while back I discovered that the screencast recorder
4154 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4155 browser would refuse to open. No video player claimed to understand
4156 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
4157 returning the application/ogg MIME type, which no video player I had
4158 installed listed as a MIME type they would understand. I asked for
4159 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
4160 behavour
</a
> and use the MIME type video/ogg instead. I also asked
4161 several video players to add video/ogg to their desktop files, to give
4162 the file browser an idea what to do about Ogg Theora files. After a
4163 while, the desktop file browsers in Debian started to handle the
4164 output from gtk-recordmydesktop properly.
</p
>
4166 <p
>But history repeats itself. A few days ago I tested the music
4167 system Rosegarden again, and I discovered that the KDE and xfce file
4168 browsers did not know what to do with the Rosegarden project files
4169 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
4170 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
4171 included in the next upload. To increase the chance of me remembering
4172 how to fix the problem next time some program fail to load its files
4173 from the file browser, here are some notes on how to fix it.
</p
>
4175 <p
>The file browsers in Debian in general operates on MIME types.
4176 There are two sources for the MIME type of a given file. The output from
4177 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
4178 shared MIME type registry (under /usr/share/mime/). The file MIME
4179 type is mapped to programs supporting the MIME type, and this
4180 information is collected from
4181 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
4182 desktop files
</a
> available in /usr/share/applications/. If there is
4183 one desktop file claiming support for the MIME type of the file, it is
4184 activated when asking to open a given file. If there are more, one
4185 can normally select which one to use by right-clicking on the file and
4186 selecting the wanted one using
'Open with
' or similar. In general
4187 this work well. But it depend on each program picking a good MIME
4189 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
4190 MIME type registered with IANA
</a
>), file and/or the shared MIME
4191 registry recognizing the file and the desktop file to list the MIME
4192 type in its list of supported MIME types.
</p
>
4194 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
4195 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
4196 Shared MIME database
</a
> look like this:
</p
>
4198 <p
><blockquote
><pre
>
4199 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4200 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
4201 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
4202 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
4203 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
4204 &lt;glob pattern=
"*.rg
"/
&gt;
4205 &lt;/mime-type
&gt;
4206 &lt;/mime-info
&gt;
4207 </pre
></blockquote
></p
>
4209 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
4210 (it is a gzipped XML file). Note, it is much better to use an
4211 official MIME type registered with IANA than it is to make up ones own
4212 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
4214 <p
>The desktop file of the rosegarden program failed to list
4215 audio/x-rosegarden in its list of supported MIME types, causing the
4216 file browsers to have no idea what to do with *.rg files:
</p
>
4218 <p
><blockquote
><pre
>
4219 % grep Mime /usr/share/applications/rosegarden.desktop
4220 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4221 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4223 </pre
></blockquote
></p
>
4225 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
4226 MimeType= line.
</p
>
4228 <p
>If you run into a file which fail to open the correct program when
4229 selected from the file browser, please check out the output from
4230 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
4231 MIME type is registered somewhere under /usr/share/mime/ and check
4232 that some desktop file under /usr/share/applications/ is claiming
4233 support for this MIME type. If not, please report a bug to have it
4239 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
4240 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
4241 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
4242 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
4243 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
4244 system
</a
> is a user-focused solution in Debian for handling hardware
4245 related packages. The idea is to have a database of mappings between
4246 hardware and packages, and pop up a dialog suggesting for the user to
4247 install the packages to use a given hardware dongle. Some use cases
4248 are when you insert a Yubikey, it proposes to install the software
4249 needed to control it; when you insert a braille reader list it
4250 proposes to install the packages needed to send text to the reader;
4251 and when you insert a ColorHug screen calibrator it suggests to
4252 install the driver for it. The system work well, and even have a few
4253 command line tools to install firmware packages and packages for the
4254 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
4256 <p
>The system was initially written using aptdaemon, because I found
4257 good documentation and example code on how to use it. But aptdaemon
4258 is going away and is generally being replaced by
4259 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
4260 so Isenkram needed a rewrite. And today, thanks to the great patch
4261 from my college Sunil Mohan Adapa in the FreedomBox project, the
4262 rewrite finally took place. I
've just uploaded a new version of
4263 Isenkram into Debian Unstable with the patch included, and the default
4264 for the background daemon is now to use PackageKit. To check it out,
4265 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
4266 and see if it is recognised.
</p
>
4268 <p
>If you want to know what kind of packages isenkram would propose for
4269 the machine it is running on, you can check out the isenkram-lookup
4270 program. This is what it look like on a Thinkpad X230:
</p
>
4272 <p
><blockquote
><pre
>
4288 </pre
></blockquote
></p
>
4290 <p
>The hardware mappings come from several places. The preferred way
4291 is for packages to announce their hardware support using
4292 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
4293 cross distribution appstream system
</a
>.
4295 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
4296 blog posts about isenkram
</a
> to learn how to do that.
</p
>
4301 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
4302 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
4303 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
4304 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
4305 <description><p
>Yesterday I updated the
4306 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
4307 package in Debian
</a
> with a few patches sent to me by skilled and
4308 enterprising users. There were some nice user and visible changes.
4309 First of all, both desktop menu entries now work. A design flaw in
4310 one of the script made the history graph fail to show up (its PNG was
4311 dumped in ~/.xsession-errors) if no controlling TTY was available.
4312 The script worked when called from the command line, but not when
4313 called from the desktop menu. I changed this to look for a DISPLAY
4314 variable or a TTY before deciding where to draw the graph, and now the
4315 graph window pop up as expected.
</p
>
4317 <p
>The next new feature is a discharge rate estimator in one of the
4318 graphs (the one showing the last few hours). New is also the user of
4319 colours showing charging in blue and discharge in red. The percentages
4320 of this graph is relative to last full charge, not battery design
4323 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
4325 <p
>The other graph show the entire history of the collected battery
4326 statistics, comparing it to the design capacity of the battery to
4327 visualise how the battery life time get shorter over time. The red
4328 line in this graph is what the previous graph considers
100 percent:
4330 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
4332 <p
>In this graph you can see that I only charge the battery to
80
4333 percent of last full capacity, and how the capacity of the battery is
4334 shrinking. :(
</p
>
4336 <p
>The last new feature is in the collector, which now will handle
4337 more hardware models. On some hardware, Linux power supply
4338 information is stored in /sys/class/power_supply/ACAD/, while the
4339 collector previously only looked in /sys/class/power_supply/AC/. Now
4340 both are checked to figure if there is power connected to the
4343 <p
>If you are interested in how your laptop battery is doing, please
4345 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4346 in Debian unstable, or rebuild it on Jessie to get it working on
4347 Debian stable. :) The upstream source is available from
<a
4348 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4349 Patches are very welcome.
</p
>
4351 <p
>As usual, if you use Bitcoin and want to show your support of my
4352 activities, please send Bitcoin donations to my address
4353 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4358 <title>Debian now with ZFS on Linux included
</title>
4359 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
4360 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
4361 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
4362 <description><p
>Today, after many years of hard work from many people,
4363 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
4364 Debian. The package status can be seen on
4365 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
4366 for zfs-linux
</a
>. and
4367 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4368 team status page
</a
>. If you want to help out, please join us.
4369 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
4370 source code
</a
> is available via git on Alioth. It would also be
4371 great if you could help out with
4372 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
4373 it is an important piece of the puzzle to get ZFS working.
</p
>
4378 <title>What is the best multimedia player in Debian?
</title>
4379 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
4380 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
4381 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
4382 <description><p
><strong
>Where I set out to figure out which multimedia player in
4383 Debian claim support for most file formats.
</strong
></p
>
4385 <p
>A few years ago, I had a look at the media support for Browser
4386 plugins in Debian, to get an idea which plugins to include in Debian
4387 Edu. I created a script to extract the set of supported MIME types
4388 for each plugin, and used this to find out which multimedia browser
4389 plugin supported most file formats / media types.
4390 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
4391 result
</a
> can still be seen on the Debian wiki, even though it have
4392 not been updated for a while. But browser plugins are less relevant
4393 these days, so I thought it was time to look at standalone
4396 <p
>A few days ago I was tired of VLC not being listed as a viable
4397 player when I wanted to play videos from the Norwegian National
4398 Broadcasting Company, and decided to investigate why. The cause is a
4399 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
4400 desktop file
</a
>. In the process I wrote a script to compare the set
4401 of MIME types announced in the desktop file and the browser plugin,
4402 only to discover that there is quite a large difference between the
4403 two for VLC. This discovery made me dig up the script I used to
4404 compare browser plugins, and adjust it to compare desktop files
4405 instead, to try to figure out which multimedia player in Debian
4406 support most file formats.
</p
>
4408 <p
>The result can be seen on the Debian Wiki, as
4409 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
4410 table listing all MIME types supported by one of the packages included
4411 in the table
</a
>, with the package supporting most MIME types being
4412 listed first in the table.
</p
>
4414 </p
>The best multimedia player in Debian? It is totem, followed by
4415 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4416 kmplayer. Time for the other players to update their announced MIME
4422 <title>The Pyra - handheld computer with Debian preinstalled
</title>
4423 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
4424 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
4425 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
4426 <description>A friend of mine made me aware of
4427 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
4428 handheld computer which will be delivered with Debian preinstalled. I
4429 would love to get one of those for my birthday. :)
</p
>
4431 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4432 plugs and many others connectors, and include a full keyboard and a
5"
4433 LCD touch screen. The
6000mAh battery is claimed to provide a whole
4434 day of battery life time, but I have not seen any independent tests
4435 confirming this. The vendor is still collecting preorders, and the
4436 last I heard last night was that
22 more orders were needed before
4437 production started.
</p
>
4439 <p
>As far as I know, this is the first handheld preinstalled with
4440 Debian. Please let me know if you know of any others. Is it the
4441 first computer being sold with Debian preinstalled?
</p
>
4446 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
4447 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
4448 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
4449 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
4450 <description><p
>During this weekends
4451 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
4452 squashing party and developer gathering
</a
>, we decided to do our part
4453 to make sure there are good books about Debian available in Norwegian
4454 Bokmål, and got in touch with the people behind the
4455 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
4456 project
</a
> to get started. If you want to help out, please start
4458 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4459 hosted weblate project page
</a
>, and get in touch using
4460 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4461 translators mailing list
</a
>. Please also check out
4462 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4463 contributors
</a
>.
</p
>
4465 <p
>The book is already available on paper in English, French and
4466 Japanese, and our goal is to get it available on paper in Norwegian
4467 Bokmål too. In addition to the paper edition, there are also EPUB and
4468 Mobi versions available. And there are incomplete translations
4469 available for many more languages.
</p
>
4474 <title>One in two hundred Debian users using ZFS on Linux?
</title>
4475 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
4476 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
4477 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
4478 <description><p
>Just for fun I had a look at the popcon number of ZFS related
4479 packages in Debian, and was quite surprised with what I found. I use
4480 ZFS myself at home, but did not really expect many others to do so.
4481 But I might be wrong.
</p
>
4483 <p
>According to
4484 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
4485 results for spl-linux
</a
>, there are
1019 Debian installations, or
4486 0.53% of the population, with the package installed. As far as I know
4487 the only use of the spl-linux package is as a support library for ZFS
4488 on Linux, so I use it here as proxy for measuring the number of ZFS
4489 installation on Linux in Debian. In the kFreeBSD variant of Debian
4490 the ZFS feature is already available, and there
4491 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
4492 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
4493 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
4495 <p
>But even though the Debian project leader Lucas Nussbaum
4496 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
4497 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
4498 cleared, the package is still not in Debian. The package is again in
4499 the NEW queue. Several uploads have been rejected so far because the
4500 debian/copyright file was incomplete or wrong, but there is no reason
4501 to give up. The current status can be seen on
4502 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4503 team status page
</a
>, and
4504 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
4505 source code
</a
> is available on Alioth.
</p
>
4507 <p
>As I want ZFS to be included in next version of Debian to make sure
4508 my home server can function in the future using only official Debian
4509 packages, and the current blocker is to get the debian/copyright file
4510 accepted by the FTP masters in Debian, I decided a while back to try
4511 to help out the team. This was the background for my blog post about
4512 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
4513 updating and checking debian/copyright semi-automatically
</a
>, and I
4514 used the techniques I explored there to try to find any errors in the
4515 copyright file. It is not very easy to check every one of the around
4516 2000 files in the source package, but I hope we this time got it
4517 right. If you want to help out, check out the git source and try to
4518 find missing entries in the debian/copyright file.
</p
>
4523 <title>Full battery stats collector is now available in Debian
</title>
4524 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
4525 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
4526 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
4527 <description><p
>Since this morning, the battery-stats package in Debian include an
4528 extended collector that will collect the complete battery history for
4529 later processing and graphing. The original collector store the
4530 battery level as percentage of last full level, while the new
4531 collector also record battery vendor, model, serial number, design
4532 full level, last full level and current battery level. This make it
4533 possible to predict the lifetime of the battery as well as visualise
4534 the energy flow when the battery is charging or discharging.
</p
>
4536 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
4537 in the version
0.5.1 package in unstable. Get the new battery level graph
4538 and lifetime prediction by running:
4540 <p
><pre
>
4541 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4542 </pre
></p
>
4544 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
4546 <p
>The flow in/out of the battery can be seen by running (no menu
4547 entry yet):
</p
>
4549 <p
><pre
>
4550 /usr/share/battery-stats/battery-stats-graph-flow
4551 </pre
></p
>
4553 <p
>I
'm not quite happy with the way the data is visualised, at least
4554 when there are few data points. The graphs look a bit better with a
4555 few years of data.
</p
>
4557 <p
>A while back one important feature I use in the battery stats
4558 collector broke in Debian. The scripts in
4559 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
4560 suspect it happened when Jessie started using systemd, but I do not
4561 know. The issue is reported as
4562 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
4563 pm-utils. I managed to work around it by adding an udev rule to call
4564 the collector script every time the power connector is connected and
4565 disconnected. With this fix in place it was finally time to make a
4566 new release of the package, and get it into Debian.
</p
>
4568 <p
>If you are interested in how your laptop battery is doing, please
4570 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4571 in Debian unstable, or rebuild it on Jessie to get it working on
4572 Debian stable. :) The upstream source is available from
4573 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4574 As always, patches are very welcome.
</p
>
4579 <title>Making battery measurements a little easier in Debian
</title>
4580 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
4581 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
4582 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
4583 <description><p
>Back in September, I blogged about
4584 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
4585 system I wrote to collect statistics about my laptop battery
</a
>, and
4586 how it showed the decay and death of this battery (now replaced). I
4587 created a simple deb package to handle the collection and graphing,
4588 but did not want to upload it to Debian as there were already
4589 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
4590 package in Debian
</a
> that should do the same thing, and I did not see
4591 a point of uploading a competing package when battery-stats could be
4592 fixed instead. I reported a few bugs about its non-function, and
4593 hoped someone would step in and fix it. But no-one did.
</p
>
4595 <p
>I got tired of waiting a few days ago, and took matters in my own
4596 hands. The end result is that I am now the new upstream developer of
4597 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
4598 battery-stats in Debian, and the package in Debian unstable is finally
4599 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
4600 information provided by the Linux kernel. If you install the
4601 battery-stats package from unstable now, you will be able to get a
4602 graph of the current battery fill level, to get some idea about the
4603 status of the battery. The source package build and work just fine in
4604 Debian testing and stable (and probably oldstable too, but I have not
4605 tested). The default graph you get for that system look like this:
</p
>
4607 <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
>
4609 <p
>My plans for the future is to merge my old scripts into the
4610 battery-stats package, as my old scripts collected a lot more details
4611 about the battery. The scripts are merged into the upstream
4612 battery-stats git repository already, but I am not convinced they work
4613 yet, as I changed a lot of paths along the way. Will have to test a
4614 bit more before I make a new release.
</p
>
4616 <p
>I will also consider changing the file format slightly, as I
4617 suspect the way I combine several values into one field might make it
4618 impossible to know the type of the value when using it for processing
4619 and graphing.
</p
>
4621 <p
>If you would like I would like to keep an close eye on your laptop
4622 battery, check out the battery-stats package in
4623 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
4625 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4626 I would love some help to improve the system further.
</p
>
4631 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
4632 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
4633 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
4634 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
4635 <description><p
>Making packages for Debian requires quite a lot of attention to
4636 details. And one of the details is the content of the
4637 debian/copyright file, which should list all relevant licenses used by
4638 the code in the package in question, preferably in
4639 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
4640 readable DEP5 format
</a
>.
</p
>
4642 <p
>For large packages with lots of contributors it is hard to write
4643 and update this file manually, and if you get some detail wrong, the
4644 package is normally rejected by the ftpmasters. So getting it right
4645 the first time around get the package into Debian faster, and save
4646 both you and the ftpmasters some work.. Today, while trying to figure
4647 out what was wrong with
4648 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
4649 zfsonlinux copyright file
</a
>, I decided to spend some time on
4650 figuring out the options for doing this job automatically, or at least
4651 semi-automatically.
</p
>
4653 <p
>Lucikly, there are at least two tools available for generating the
4654 file based on the code in the source package,
4655 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
4656 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
4657 not sure which one of them came first, but both seem to be able to
4658 create a sensible draft file. As far as I can tell, none of them can
4659 be trusted to get the result just right, so the content need to be
4660 polished a bit before the file is OK to upload. I found the debmake
4662 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
4663 blog posts from
2014</a
>.
4665 <p
>To generate using debmake, use the -cc option:
4667 <p
><pre
>
4668 debmake -cc
> debian/copyright
4669 </pre
></p
>
4671 <p
>Note there are some problems with python and non-ASCII names, so
4672 this might not be the best option.
</p
>
4674 <p
>The cme option is based on a config parsing library, and I found
4676 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
4677 blog post from
2015</a
>. To generate using cme, use the
'update
4678 dpkg-copyright
' option:
4680 <p
><pre
>
4681 cme update dpkg-copyright
4682 </pre
></p
>
4684 <p
>This will create or update debian/copyright. The cme tool seem to
4685 handle UTF-
8 names better than debmake.
</p
>
4687 <p
>When the copyright file is created, I would also like some help to
4688 check if the file is correct. For this I found two good options,
4689 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
4690 to focus on license types and file matching, and is able to detect
4691 ineffective blocks in the copyright file. The latter reports missing
4692 copyright holders and years, but was confused by inconsistent license
4693 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
4694 fix all issues reported by them before uploading. But I do not know
4695 if the tools and the ftpmasters agree on what is important to fix in a
4696 copyright file, so the package might still be rejected.
</p
>
4698 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
4699 will read through the source and try to find all copyright statements.
4700 It is not comparing the result to the content of debian/copyright, but
4701 can be useful when verifying the content of the copyright file.
</p
>
4703 <p
>Are you aware of better tools in Debian to create and update
4704 debian/copyright file. Please let me know, or blog about it on
4705 planet.debian.org.
</p
>
4707 <p
>As usual, if you use Bitcoin and want to show your support of my
4708 activities, please send Bitcoin donations to my address
4709 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4711 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
4712 on how to use licensecheck and cdbs to create a draft copyright file
4714 <p
><pre
>
4715 licensecheck --copyright -r `find * -type f` | \
4716 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
4717 </pre
></p
>
4719 <p
>He mentioned that he normally check the generated file into the
4720 version control system to make it easier to discover license and
4721 copyright changes in the upstream source. I will try to do the same
4722 with my packages in the future.
</p
>
4724 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
4725 against using -quiet for new users, so I removed it from the proposed
4726 command line.
</p
>
4731 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
4732 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
4733 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
4734 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
4735 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
4736 is taking shape in Debian, and one provided feature is a very
4737 convenient way to tell you which package to install to make a given
4738 firmware file available when the kernel is looking for it. This can
4739 be done using apt-file too, but that is for someone else to blog
4742 <p
>Here is a small recipe to find the package with a given firmware
4743 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
4744 picked from the set of firmware announced using appstream in Debian
4745 unstable. In general you would be looking for the firmware requested
4746 by the kernel during kernel module loading. To find the package
4747 providing the example file, do like this:
</p
>
4749 <blockquote
><pre
>
4750 % apt install appstream
4754 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
4755 awk
'/Package:/ {print $
2}
'
4758 </pre
></blockquote
>
4760 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
4761 appstream wiki
</a
> page to learn how to embed the package metadata in
4762 a way appstream can use.
</p
>
4764 <p
>This same approach can be used to find any package supporting a
4765 given MIME type. This is very useful when you get a file you do not
4766 know how to handle. First find the mime type using
<tt
>file
4767 --mime-type
</tt
>, and next look up the package providing support for
4768 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4769 and you can find all packages handling this type like this:
</p
>
4771 <blockquote
><pre
>
4772 % apt install appstream
4776 % appstreamcli what-provides mimetype image/svg+xml | \
4777 awk
'/Package:/ {print $
2}
'
4799 </pre
></blockquote
>
4801 <p
>I believe the MIME types are fetched from the desktop file for
4802 packages providing appstream metadata.
</p
>
4807 <title>Creepy, visualise geotagged social media information - nice free software
</title>
4808 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
4809 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
4810 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
4811 <description><p
>Most people seem not to realise that every time they walk around
4812 with the computerised radio beacon known as a mobile phone their
4813 position is tracked by the phone company and often stored for a long
4814 time (like every time a SMS is received or sent). And if their
4815 computerised radio beacon is capable of running programs (often called
4816 mobile apps) downloaded from the Internet, these programs are often
4817 also capable of tracking their location (if the app requested access
4818 during installation). And when these programs send out information to
4819 central collection points, the location is often included, unless
4820 extra care is taken to not send the location. The provided
4821 information is used by several entities, for good and bad (what is
4822 good and bad, depend on your point of view). What is certain, is that
4823 the private sphere and the right to free movement is challenged and
4824 perhaps even eradicated for those announcing their location this way,
4825 when they share their whereabouts with private and public
4828 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
4830 <p
>The phone company logs provide a register of locations to check out
4831 when one want to figure out what the tracked person was doing. It is
4832 unavailable for most of us, but provided to selected government
4833 officials, company staff, those illegally buying information from
4834 unfaithful servants and crackers stealing the information. But the
4835 public information can be collected and analysed, and a free software
4836 tool to do so is called
4837 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
4838 discovered it when I read
4839 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
4840 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
4841 November
2014, and decided to check if it was available in Debian.
4842 The python program was in Debian, but
4843 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
4844 Debian
</a
> was completely broken and practically unmaintained. I
4845 uploaded a new version which did not work quite right, but did not
4846 have time to fix it then. This Christmas I decided to finally try to
4847 get Creepy operational in Debian. Now a fixed version is available in
4848 Debian unstable and testing, and almost all Debian specific patches
4850 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
4852 <p
>The Creepy program visualises geolocation information fetched from
4853 Twitter, Instagram, Flickr and Google+, and allow one to get a
4854 complete picture of every social media message posted recently in a
4855 given area, or track the movement of a given individual across all
4856 these services. Earlier it was possible to use the search API of at
4857 least some of these services without identifying oneself, but these
4858 days it is impossible. This mean that to use Creepy, you need to
4859 configure it to log in as yourself on these services, and provide
4860 information to them about your search interests. This should be taken
4861 into account when using Creepy, as it will also share information
4862 about yourself with the services.
</p
>
4864 <p
>The picture above show the twitter messages sent from (or at least
4865 geotagged with a position from) the city centre of Oslo, the capital
4866 of Norway. One useful way to use Creepy is to first look at
4867 information tagged with an area of interest, and next look at all the
4868 information provided by one or more individuals who was in the area.
4869 I tested it by checking out which celebrity provide their location in
4870 twitter messages by checkout out who sent twitter messages near a
4871 Norwegian TV station, and next could track their position over time,
4872 making it possible to locate their home and work place, among other
4873 things. A similar technique have been
4874 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
4875 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
4876 tool to discover lying governments, and a useful tool to help people
4877 understand the value of the private information they provide to the
4880 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
4881 it depend on several python modules currently missing in Jessie (at
4882 least python-instagram, python-flickrapi and
4883 python-requests-toolbelt).
</p
>
4885 <p
>(I have uploaded
4886 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
4887 screenshots.debian.net
</a
> and licensed it under the same terms as the
4888 Creepy program in Debian.)
</p
>
4893 <title>Always download Debian packages using Tor - the simple recipe
</title>
4894 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
4895 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
4896 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
4897 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
4898 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
4899 that those listening on the Internet lines would have good reason to
4900 believe a computer have a given security hole
</a
> if it download a
4901 security fix from a Debian mirror. This is a good reason to always
4902 use encrypted connections to the Debian mirror, to make sure those
4903 listening do not know which IP address to attack. In August, Richard
4904 Hartmann observed that encryption was not enough, when it was possible
4905 to interfere download size to security patches or the fact that
4906 download took place shortly after a security fix was released, and
4907 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
4908 to always use Tor to download packages from the Debian mirror
</a
>. He
4909 was not the first to propose this, as the
4910 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
4911 package by Tim Retout already existed to make it easy to convince apt
4912 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
4913 aware of that package when I read the blog post from Richard.
</p
>
4915 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
4916 sysadmins, and he set up a Tor hidden service on one of the central
4917 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4918 it possible to download packages directly between two tor nodes,
4919 making sure the network traffic always were encrypted.
</p
>
4921 <p
>Here is a short recipe for enabling this on your machine, by
4922 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
4923 urls with tor+http and tor+https, and using the hidden service instead
4924 of the official Debian mirror site. I recommend installing
4925 <tt
>etckeeper
</tt
> before you start to have a history of the changes
4926 done in /etc/.
</p
>
4928 <blockquote
><pre
>
4929 apt install apt-transport-tor
4930 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
4931 sed -i
's% http% tor+http%
' /etc/apt/sources.list
4932 </pre
></blockquote
>
4934 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
4935 the sed commands for these too. The sed command is assuming your are
4936 using the ftp.debian.org Debian mirror. Adjust the command (or just
4937 edit the file manually) to match your mirror.
</p
>
4939 <p
>This work in Debian Jessie and later. Note that tools like
4940 <tt
>apt-file
</tt
> only recently started using the apt transport
4941 system, and do not work with these tor+http URLs. For
4942 <tt
>apt-file
</tt
> you need the version currently in experimental,
4943 which need a recent apt version currently only in unstable. So if you
4944 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
4946 <p
>Another advantage from this change is that your machine will start
4947 using Tor regularly and at fairly random intervals (every time you
4948 update the package lists or upgrade or install a new package), thus
4949 masking other Tor traffic done from the same machine. Using Tor will
4950 become normal for the machine in question.
</p
>
4952 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
4953 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
4954 enabled. It would be great if it was the default on any Debian
4960 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
4961 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
4962 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
4963 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
4964 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
4965 call the car license plate numbers in those days. I would write the
4966 numbers down in my little book and compare notes with the other kids
4967 to see how many region codes we had seen and if we had seen some
4968 exotic or special region codes and numbers. It was a fun game to pass
4969 time, as we kids have plenty of it.
</p
>
4971 <p
>A few days I came across
4972 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
4973 project
</a
>, a free software project to automatically discover and
4974 report license plates in images and video streams, and provide the
4975 "car numbers
" in a machine readable format. I
've been looking for
4976 such system for a while now, because I believe it is a bad idea that the
4977 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
4978 number plate recognition
</a
> tool only is available in the hands of
4979 the powerful, and want it to be available also for the powerless to
4980 even the score when it comes to surveillance and sousveillance. I
4981 discovered the developer
4982 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
4983 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
4984 help him get it into shape to get the package uploaded into the Debian
4987 <p
>Today we finally managed to get the package into shape and uploaded
4988 it into Debian, where it currently
4989 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
4990 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
4992 <p
>I guess you are wondering why on earth such tool would be useful
4993 for the common folks, ie those not running a large government
4994 surveillance system? Well, I plan to put it in a computer on my bike
4995 and in my car, tracking the cars nearby and allowing me to be notified
4996 when number plates on my watch list are discovered. Another use case
4997 was suggested by a friend of mine, who wanted to set it up at his home
4998 to open the car port automatically when it discovered the plate on his
4999 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5000 capable of placing his license plate number of a piece of cardboard to
5001 open his car port, men replied that it was always unlocked anyway. I
5002 guess for such use case it make sense. I am sure there are other use
5003 cases too, for those with imagination and a vision.
</p
>
5005 <p
>If you want to build your own version of the Debian package, check
5006 out the upstream git source and symlink ./distros/debian to ./debian/
5007 before running
"debuild
" to build the source. Or wait a bit until the
5008 package show up in unstable.
</p
>
5013 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
5014 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
5015 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
5016 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
5017 <description><p
>Around three years ago, I created
5018 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
5019 system
</a
> to get a more practical solution in Debian for handing
5020 hardware related packages. A GUI system in the isenkram package will
5021 present a pop-up dialog when some hardware dongle supported by
5022 relevant packages in Debian is inserted into the machine. The same
5023 lookup mechanism to detect packages is available as command line
5024 tools in the isenkram-cli package. In addition to mapping hardware,
5025 it will also map kernel firmware files to packages and make it easy to
5026 install needed firmware packages automatically. The key for this
5027 system to work is a good way to map hardware to packages, in other
5028 words, allow packages to announce what hardware they will work
5031 <p
>I started by providing data files in the isenkram source, and
5032 adding code to download the latest version of these data files at run
5033 time, to ensure every user had the most up to date mapping available.
5034 I also added support for storing the mapping in the Packages file in
5035 the apt repositories, but did not push this approach because while I
5036 was trying to figure out how to best store hardware/package mappings,
5037 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
5038 appstream system
</a
> was announced. I got in touch and suggested to
5039 add the hardware mapping into that data set to be able to use
5040 appstream as a data source, and this was accepted at least for the
5041 Debian version of appstream.
</p
>
5043 <p
>A few days ago using appstream in Debian for this became possible,
5044 and today I uploaded a new version
0.20 of isenkram adding support for
5045 appstream as a data source for mapping hardware to packages. The only
5046 package so far using appstream to announce its hardware support is my
5047 pymissile package. I got help from Matthias Klumpp with figuring out
5048 how do add the required
5049 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
5050 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
5051 this content:
</p
>
5053 <blockquote
><pre
>
5054 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
5055 &lt;component
&gt;
5056 &lt;id
&gt;pymissile
&lt;/id
&gt;
5057 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
5058 &lt;name
&gt;pymissile
&lt;/name
&gt;
5059 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
5060 &lt;description
&gt;
5062 Pymissile provides a curses interface to control an original
5063 Marks and Spencer / Striker USB Missile Launcher, as well as a
5064 motion control script to allow a webcamera to control the
5067 &lt;/description
&gt;
5068 &lt;provides
&gt;
5069 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
5070 &lt;/provides
&gt;
5071 &lt;/component
&gt;
5072 </pre
></blockquote
>
5074 <p
>The key for isenkram is the component/provides/modalias value,
5075 which is a glob style match rule for hardware specific strings
5076 (modalias strings) provided by the Linux kernel. In this case, it
5077 will map to all USB devices with vendor code
1130 and product code
5080 <p
>Note, it is important that the license of all the metadata files
5081 are compatible to have permissions to aggregate them into archive wide
5082 appstream files. Matthias suggested to use MIT or BSD licenses for
5083 these files. A challenge is figuring out a good id for the data, as
5084 it is supposed to be globally unique and shared across distributions
5085 (in other words, best to coordinate with upstream what to use). But
5086 it can be changed later or, so we went with the package name as
5087 upstream for this project is dormant.
</p
>
5089 <p
>To get the metadata file installed in the correct location for the
5090 mirror update scripts to pick it up and include its content the
5091 appstream data source, the file must be installed in the binary
5092 package under /usr/share/appdata/. I did this by adding the following
5093 line to debian/pymissile.install:
</p
>
5095 <blockquote
><pre
>
5096 debian/pymissile.metainfo.xml usr/share/appdata
5097 </pre
></blockquote
>
5099 <p
>With that in place, the command line tool isenkram-lookup will list
5100 all packages useful on the current computer automatically, and the GUI
5101 pop-up handler will propose to install the package not already
5102 installed if a hardware dongle is inserted into the machine in
5105 <p
>Details of the modalias field in appstream is available from the
5106 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
5108 <p
>To locate the modalias values of all hardware present in a machine,
5109 try running this command on the command line:
</p
>
5111 <blockquote
><pre
>
5112 cat $(find /sys/devices/|grep modalias)
5113 </pre
></blockquote
>
5115 <p
>To learn more about the isenkram system, please check out
5116 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
5117 blog posts tagged isenkram
</a
>.
</p
>
5122 <title>The GNU General Public License is not magic pixie dust
</title>
5123 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
5124 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
5125 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
5126 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
5127 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
5128 GPL is not magic pixie dust
</a
>" explain the importance of making sure
5129 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
5130 I quote the blog post from Paul in full here with his permission:
<p
>
5134 <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
>
5137 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
5139 The first step is to choose a
5140 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
5143 The next step is, when someone fails to follow that copyleft license,
5144 <b
>it must be enforced
</b
><br/
>
5146 and its a simple fact of our modern society that such type of
5149 is incredibly expensive to do and incredibly difficult to do.
5152 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
5153 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
5154 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
5155 0x57</a
></small
></p
>
5157 <p
>As the Debian Website
5158 <a href=
"https://bugs.debian.org/
794116">used
</a
>
5159 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
5160 imply, public domain and permissively licensed software can lead to
5161 the production of more proprietary software as people discover useful
5162 software, extend it and or incorporate it into their hardware or
5163 software products. Copyleft licenses such as the GNU GPL were created
5164 to close off this avenue to the production of proprietary software but
5165 such licenses are not enough. With the ongoing adoption of Free
5166 Software by individuals and groups, inevitably the community
's
5167 expectations of license compliance are violated, usually out of
5168 ignorance of the way Free Software works, but not always. As Karen
5169 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
5170 Freedom
">FaiF
</a
>
5171 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
5172 copyleft is nothing if no-one is willing and able to stand up in court
5173 to protect it. The reality of today
's world is that legal
5174 representation is expensive, difficult and time consuming. With
5175 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
5176 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
5177 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
5178 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
5179 of the Linux project, Debian and other groups against GPL violations.
5180 In March the SFC supported a
5181 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
5182 by Christoph Hellwig
</a
> against VMware for refusing to
5183 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
5184 with the GPL
</a
> in relation to their use of parts of the Linux
5185 kernel. Since then two of their sponsors pulled corporate funding and
5187 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
5188 or cancelled their talks
</a
>. As a result they have decided to rely
5189 less on corporate funding and more on the broad community of
5190 individuals who support Free Software and copyleft. So the SFC has
5191 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
5192 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
5193 a community of folks who stand up for copyleft and the GPL by
5194 supporting their work on promoting and supporting copyleft and Free
5197 <p
>If you support Free Software,
5198 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
5199 what the SFC do, agree with their
5200 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
5201 principles
</a
>, are happy about their
5202 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
5203 work on a project that is an SFC
5204 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
5205 just want to stand up for copyleft, please join
5206 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
5207 Allan Webber
</a
>,
5208 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
5210 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
5211 Bacon
</a
>, myself and
5212 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
5214 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
5215 next week your donation will be
5216 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
5217 by an anonymous donor. Please also consider asking your employer to
5218 match your donation or become a sponsor of SFC. Don
't forget to
5219 spread the word about your support for SFC via email, your blog and or
5220 social media accounts.
</p
>
5224 <p
>I agree with Paul on this topic and just signed up as a Supporter
5225 of Software Freedom Conservancy myself. Perhaps you should be a
5226 supporter too?
</p
>
5231 <title>PGP key transition statement for key EE4E02F9
</title>
5232 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
5233 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
5234 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
5235 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
5236 set it up properly. I wanted to generate it offline and have it
5237 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
5238 smart card
</a
> for daily use, and learning how to do it and finding
5239 time to sit down with an offline machine almost took forever. But
5240 finally I
've been able to complete the process, and have now moved
5241 from my old GPG key to a new GPG key. See
5242 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
5243 full transition statement, signed with both my old and new key
</a
> for
5244 the details. This is my new key:
</p
>
5247 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
5248 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
5249 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
5250 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
5251 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
5252 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
5253 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
5256 <p
>The key can be downloaded from the OpenPGP key servers, signed by
5257 my old key.
</p
>
5259 <p
>If you signed my old key
5260 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
5261 I
'd very much appreciate a signature on my new key, details and
5262 instructions in the transition statement. I m happy to reciprocate if
5263 you have a similarly signed transition statement to present.
</p
>
5268 <title>The life and death of a laptop battery
</title>
5269 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
5270 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
5271 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
5272 <description><p
>When I get a new laptop, the battery life time at the start is OK.
5273 But this do not last. The last few laptops gave me a feeling that
5274 within a year, the life time is just a fraction of what it used to be,
5275 and it slowly become painful to use the laptop without power connected
5276 all the time. Because of this, when I got a new Thinkpad X230 laptop
5277 about two years ago, I decided to monitor its battery state to have
5278 more hard facts when the battery started to fail.
</p
>
5280 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
5282 <p
>First I tried to find a sensible Debian package to record the
5283 battery status, assuming that this must be a problem already handled
5284 by someone else. I found
5285 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
5286 which collects statistics from the battery, but it was completely
5287 broken. I sent a few suggestions to the maintainer, but decided to
5288 write my own collector as a shell script while I waited for feedback
5290 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
5291 blog post about the battery development on a MacBook Air
</a
> I also
5293 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
5294 available in Debian.
</p
>
5296 <p
>I started my collector
2013-
07-
15, and it has been collecting
5297 battery stats ever since. Now my
5298 /var/log/hjemmenett-battery-status.log file contain around
115,
000
5299 measurements, from the time the battery was working great until now,
5300 when it is unable to charge above
7% of original capacity. My
5301 collector shell script is quite simple and look like this:
</p
>
5306 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
5308 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
5309 logfile=/var/log/hjemmenett-battery-status.log
5311 files=
"manufacturer model_name technology serial_number \
5312 energy_full energy_full_design energy_now cycle_count status
"
5314 if [ ! -e
"$logfile
" ] ; then
5316 printf
"timestamp,
"
5318 printf
"%s,
" $f
5321 )
> "$logfile
"
5325 # Print complete message in one echo call, to avoid race condition
5326 # when several log processes run in parallel.
5327 msg=$(printf
"%s,
" $(date +%s); \
5328 for f in $files; do \
5329 printf
"%s,
" $(cat $f); \
5331 echo
"$msg
"
5334 cd /sys/class/power_supply
5337 (cd $bat
&& log_battery
>> "$logfile
")
5341 <p
>The script is called when the power management system detect a
5342 change in the power status (power plug in or out), and when going into
5343 and out of hibernation and suspend. In addition, it collect a value
5344 every
10 minutes. This make it possible for me know when the battery
5345 is discharging, charging and how the maximum charge change over time.
5346 The code for the Debian package
5347 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
5348 available on github
</a
>.
</p
>
5350 <p
>The collected log file look like this:
</p
>
5353 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5354 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
5356 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5357 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5360 <p
>I wrote a small script to create a graph of the charge development
5361 over time. This graph depicted above show the slow death of my laptop
5364 <p
>But why is this happening? Why are my laptop batteries always
5365 dying in a year or two, while the batteries of space probes and
5366 satellites keep working year after year. If we are to believe
5367 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
5368 University
</a
>, the cause is me charging the battery whenever I have a
5369 chance, and the fix is to not charge the Lithium-ion batteries to
100%
5370 all the time, but to stay below
90% of full charge most of the time.
5371 I
've been told that the Tesla electric cars
5372 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
5373 the charge of their batteries to
80%
</a
>, with the option to charge to
5374 100% when preparing for a longer trip (not that I would want a car
5375 like Tesla where rights to privacy is abandoned, but that is another
5376 story), which I guess is the option we should have for laptops on
5377 Linux too.
</p
>
5379 <p
>Is there a good and generic way with Linux to tell the battery to
5380 stop charging at
80%, unless requested to charge to
100% once in
5381 preparation for a longer trip? I found
5382 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
5383 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5384 80%
</a
>, but could not get it to work (kernel module refused to
5387 <p
>I wonder why the battery capacity was reported to be more than
100%
5388 at the start. I also wonder why the
"full capacity
" increases some
5389 times, and if it is possible to repeat the process to get the battery
5390 back to design capacity. And I wonder if the discharge and charge
5391 speed change over time, or if this stay the same. I did not yet try
5392 to write a tool to calculate the derivative values of the battery
5393 level, but suspect some interesting insights might be learned from
5396 <p
>Update
2015-
09-
24: I got a tip to install the packages
5397 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5398 packages instead of the tp-smapi-dkms package I had tried to use
5399 initially, and use
'tlp setcharge
40 80' to change when charging start
5400 and stop. I
've done so now, but expect my existing battery is toast
5401 and need to be replaced. The proposal is unfortunately Thinkpad
5407 <title>New laptop - some more clues and ideas based on feedback
</title>
5408 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
5409 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
5410 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
5411 <description><p
>Several people contacted me after my previous blog post about my
5412 need for a new laptop, and provided very useful feedback. I wish to
5413 thank every one of these. Several pointed me to the possibility of
5414 fixing my X230, and I am already in the process of getting Lenovo to
5415 do so thanks to the on site, next day support contract covering the
5416 machine. But the battery is almost useless (I expect to replace it
5417 with a non-official battery) and I do not expect the machine to live
5418 for many more years, so it is time to plan its replacement. If I did
5419 not have a support contract, it was suggested to find replacement parts
5420 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
5421 might present a language barrier as I do not understand French.
</p
>
5423 <p
>One tip I got was to use the
5424 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
5425 compare laptop models. It seem to have more models available than
5426 prisjakt.no. Another tip I got from someone I know have similar
5427 keyboard preferences was that the HP EliteBook
840 keyboard is not
5428 very good, and this matches my experience with earlier EliteBook
5429 keyboards I tested. Because of this, I will not consider it any further.
5431 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
5432 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5433 (which is missing from the X240), and is working fairly well with
5434 Debian Sid/Unstable according to
5435 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
5436 got on the keyboard quality are not consistent. Some say the keyboard
5437 is good, others say it is ok, while others say it is not very good.
5438 Those with experience from X41 and and X60 agree that the X250
5439 keyboard is not as good as those trusty old laptops, and suggest I
5440 keep and fix my X230 instead of upgrading, or get a used X230 to
5441 replace it. I
'm also told that the X250 lack leds for caps lock, disk
5442 activity and battery status, which is very convenient on my X230. I
'm
5443 also told that the CPU fan is running very often, making it a bit
5444 noisy. In any case, the X250 do not work out of the box with Debian
5445 Stable/Jessie, one of my requirements.
</p
>
5447 <p
>I have also gotten a few vendor proposals, one was
5448 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
5449 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
5450 The latter look very attractive to me.
</p
>
5452 <p
>Again, thank you all for the very useful feedback. It help a lot
5453 as I keep looking for a replacement.
</p
>
5455 <p
>Update
2015-
07-
06: I was recommended to check out the
5456 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
5458 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
5459 thinkpad X models
</a
>, and provide one year warranty.
</p
>
5464 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
5465 <link>https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</link>
5466 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</guid>
5467 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
5468 <description><p
>My primary work horse laptop is failing, and will need a
5469 replacement soon. The left
5 cm of the screen on my Thinkpad X230
5470 started flickering yesterday, and I suspect the cause is a broken
5471 cable, as changing the angle of the screen some times get rid of the
5472 flickering.
</p
>
5474 <p
>My requirements have not really changed since I bought it, and is
5476 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
5477 described them in
2013</a
>. The last time I bought a laptop, I had
5479 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
5480 where I could select at least a few of the requirements (mouse pin,
5481 wifi, weight) and go through the rest manually. Three button mouse
5482 and a good keyboard is not available as an option, and all the three
5483 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
5484 G2) lack three mouse buttons). It is also unclear to me how good the
5485 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5486 the keyboard, even if the quality and robustness in the X series have
5487 deteriorated since X41.
</p
>
5489 <p
>I wonder how I can find a sensible laptop when none of the options
5490 seem sensible to me? Are there better services around to search the
5491 set of available laptops for features? Please send me an email if you
5492 have suggestions.
</p
>
5494 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
5495 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
5496 of endorsed hardware
</a
>, which is useful background information.
</p
>
5501 <title>How to stay with sysvinit in Debian Jessie
</title>
5502 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
5503 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
5504 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
5505 <description><p
>By now, it is well known that Debian Jessie will not be using
5506 sysvinit as its boot system by default. But how can one keep using
5507 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5509 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
5510 Schubert
</a
> and
5511 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
5514 <p
>If you already are using Wheezy and want to upgrade to Jessie and
5515 keep sysvinit as your boot system, create a file
5516 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
5517 you upgrade:
</p
>
5519 <p
><blockquote
><pre
>
5520 Package: systemd-sysv
5521 Pin: release o=Debian
5523 </pre
></blockquote
><p
>
5525 <p
>This file content will tell apt and aptitude to not consider
5526 installing systemd-sysv as part of any installation and upgrade
5527 solution when resolving dependencies, and thus tell it to avoid
5528 systemd as a default boot system. The end result should be that the
5529 upgraded system keep using sysvinit.
</p
>
5531 <p
>If you are installing Jessie for the first time, there is no way to
5532 get sysvinit installed by default (debootstrap used by
5533 debian-installer have no option for this), but one can tell the
5534 installer to switch to sysvinit before the first boot. Either by
5535 using a kernel argument to the installer, or by adding a line to the
5536 preseed file used. First, the kernel command line argument:
5538 <p
><blockquote
><pre
>
5539 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
5540 </pre
></blockquote
><p
>
5542 <p
>Next, the line to use in a preseed file:
</p
>
5544 <p
><blockquote
><pre
>
5545 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5546 </pre
></blockquote
><p
>
5548 <p
>One can of course also do this after the first boot by installing
5549 the sysvinit-core package.
</p
>
5551 <p
>I recommend only using sysvinit if you really need it, as the
5552 sysvinit boot sequence in Debian have several hardware specific bugs
5553 on Linux caused by the fact that it is unpredictable when hardware
5554 devices show up during boot. But on the other hand, the new default
5555 boot system still have a few rough edges I hope will be fixed before
5556 Jessie is released.
</p
>
5558 <p
>Update
2014-
11-
26: Inspired by
5559 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
5560 blog post by Torsten Glaser
</a
>, added --purge to the preseed
5566 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
5567 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
5568 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
5569 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
5570 <description><p
>The right to communicate with your friends and family in private,
5571 without anyone snooping, is a right every citicen have in a liberal
5572 democracy. But this right is under serious attack these days.
</p
>
5574 <p
>A while back it occurred to me that one way to make the dragnet
5575 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5576 the whisleblower Snowden) more expensive for Internet email,
5577 is to deliver all email using SMTP via Tor. Such SMTP option would be
5578 a nice addition to the FreedomBox project if we could send email
5579 between FreedomBox machines without leaking metadata about the emails
5580 to the people peeking on the wire. I
5581 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
5582 this on the FreedomBox project mailing list in October
</a
> and got a
5583 lot of useful feedback and suggestions. It also became obvious to me
5584 that this was not a novel idea, as the same idea was tested and
5585 documented by Johannes Berg as early as
2006, and both
5586 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
5587 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
5588 propose a similar method / protocol to pass emails between users.
</p
>
5590 <p
>To implement such system one need to set up a Tor hidden service
5591 providing the SMTP protocol on port
25, and use email addresses
5592 looking like username@hidden-service-name.onion. With such addresses
5593 the connections to port
25 on hidden-service-name.onion using Tor will
5594 go to the correct SMTP server. To do this, one need to configure the
5595 Tor daemon to provide the hidden service and the mail server to accept
5596 emails for this .onion domain. To learn more about Exim configuration
5597 in Debian and test the design provided by Johannes Berg in his FAQ, I
5598 set out yesterday to create a Debian package for making it trivial to
5599 set up such SMTP over Tor service based on Debian. Getting it to work
5600 were fairly easy, and
5601 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
5602 source code for the Debian package
</a
> is available from github. I
5603 plan to move it into Debian if further testing prove this to be a
5604 useful approach.
</p
>
5606 <p
>If you want to test this, set up a blank Debian machine without any
5607 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
5608 get rid of exim4). Install tor, clone the git repository mentioned
5609 above, build the deb and install it on the machine. Next, run
5610 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
5611 the instructions to get the service up and running. Restart tor and
5612 exim when it is done, and test mail delivery using swaks like
5615 <p
><blockquote
><pre
>
5616 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5617 --to fbx@dutlqrrmjhtfa3vp.onion
5618 </pre
></blockquote
></p
>
5620 <p
>This will test the SMTP delivery using tor. Replace the email
5621 address with your own address to test your server. :)
</p
>
5623 <p
>The setup procedure is still to complex, and I hope it can be made
5624 easier and more automatic. Especially the tor setup need more work.
5625 Also, the package include a tor-smtp tool written in C, but its task
5626 should probably be rewritten in some script language to make the deb
5627 architecture independent. It would probably also make the code easier
5628 to review. The tor-smtp tool currently need to listen on a socket for
5629 exim to talk to it and is started using xinetd. It would be better if
5630 no daemon and no socket is needed. I suspect it is possible to get
5631 exim to run a command line tool for delivery instead of talking to a
5632 socket, and hope to figure out how in a future version of this
5635 <p
>Until I wipe my test machine, I can be reached using the
5636 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
5637 SMTorP. :)
</p
>
5642 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
5643 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
5644 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
5645 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
5646 <description><p
>If you ever had to moderate a mailman list, like the ones on
5647 alioth.debian.org, you know the web interface is fairly slow to
5648 operate. First you visit one web page, enter the moderation password
5649 and get a new page shown with a list of all the messages to moderate
5650 and various options for each email address. This take a while for
5651 every list you moderate, and you need to do it regularly to do a good
5652 job as a list moderator. But there is a quick alternative,
5653 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
5654 listadmin program
</a
>. It allow you to check lists for new messages
5655 to moderate in a fraction of a second. Here is a test run on two
5656 lists I recently took over:
</p
>
5658 <p
><blockquote
><pre
>
5659 % time listadmin xiph
5660 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5661 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5667 </pre
></blockquote
></p
>
5669 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
5670 there are no message in the moderation queue. Every morning I
5671 currently moderate
68 mailman lists, and it normally take around two
5672 minutes. When I took over the two pkg-xiph lists above a few days
5673 ago, there were
400 emails waiting in the moderator queue. It took me
5674 less than
15 minutes to process them all using the listadmin
5677 <p
>If you install
5678 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
5679 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
5680 with content like this, the moderation task is a breeze:
</p
>
5682 <p
><blockquote
><pre
>
5683 username username@example.org
5686 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
5689 adminurl https://{domain}/mailman/admindb/{list}
5690 mailman-list@lists.example.com
5693 other-list@otherserver.example.org
5694 </pre
></blockquote
></p
>
5696 <p
>There are other options to set as well. Check the manual page to
5697 learn the details.
</p
>
5699 <p
>If you are forced to moderate lists on a mailman installation where
5700 the SSL certificate is self signed or not properly signed by a
5701 generally accepted signing authority, you can set a environment
5702 variable when calling listadmin to disable SSL verification:
</p
>
5704 <p
><blockquote
><pre
>
5705 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
5706 </pre
></blockquote
></p
>
5708 <p
>If you want to moderate a subset of the lists you take care of, you
5709 can provide an argument to the listadmin script like I do in the
5710 initial screen dump (the xiph argument). Using an argument, only
5711 lists matching the argument string will be processed. This make it
5712 quick to accept messages if you notice the moderation request in your
5715 <p
>Without the listadmin program, I would never be the moderator of
68
5716 mailing lists, as I simply do not have time to spend on that if the
5717 process was any slower. The listadmin program have saved me hours of
5718 time I could spend elsewhere over the years. It truly is nice free
5721 <p
>As usual, if you use Bitcoin and want to show your support of my
5722 activities, please send Bitcoin donations to my address
5723 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5725 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
5726 configuration example. Also, I
've been told that the
5727 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
5733 <title>Debian Jessie, PXE and automatic firmware installation
</title>
5734 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
5735 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
5736 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
5737 <description><p
>When PXE installing laptops with Debian, I often run into the
5738 problem that the WiFi card require some firmware to work properly.
5739 And it has been a pain to fix this using preseeding in Debian.
5740 Normally something more is needed. But thanks to
5741 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
5742 package
</a
> and its recent tasksel extension, it has now become easy
5743 to do this using simple preseeding.
</p
>
5745 <p
>The isenkram-cli package provide tasksel tasks which will install
5746 firmware for the hardware found in the machine (actually, requested by
5747 the kernel modules for the hardware). (It can also install user space
5748 programs supporting the hardware detected, but that is not the focus
5749 of this story.)
</p
>
5751 <p
>To get this working in the default installation, two preeseding
5752 values are needed. First, the isenkram-cli package must be installed
5753 into the target chroot (aka the hard drive) before tasksel is executed
5754 in the pkgsel step of the debian-installer system. This is done by
5755 preseeding the base-installer/includes debconf value to include the
5756 isenkram-cli package. The package name is next passed to debootstrap
5757 for installation. With the isenkram-cli package in place, tasksel
5758 will automatically use the isenkram tasks to detect hardware specific
5759 packages for the machine being installed and install them, because
5760 isenkram-cli contain tasksel tasks.
</p
>
5762 <p
>Second, one need to enable the non-free APT repository, because
5763 most firmware unfortunately is non-free. This is done by preseeding
5764 the apt-mirror-setup step. This is unfortunate, but for a lot of
5765 hardware it is the only option in Debian.
</p
>
5767 <p
>The end result is two lines needed in your preseeding file to get
5768 firmware installed automatically by the installer:
</p
>
5770 <p
><blockquote
><pre
>
5771 base-installer base-installer/includes string isenkram-cli
5772 apt-mirror-setup apt-setup/non-free boolean true
5773 </pre
></blockquote
></p
>
5775 <p
>The current version of isenkram-cli in testing/jessie will install
5776 both firmware and user space packages when using this method. It also
5777 do not work well, so use version
0.15 or later. Installing both
5778 firmware and user space packages might give you a bit more than you
5779 want, so I decided to split the tasksel task in two, one for firmware
5780 and one for user space programs. The firmware task is enabled by
5781 default, while the one for user space programs is not. This split is
5782 implemented in the package currently in unstable.
</p
>
5784 <p
>If you decide to give this a go, please let me know (via email) how
5785 this recipe work for you. :)
</p
>
5787 <p
>So, I bet you are wondering, how can this work. First and
5788 foremost, it work because tasksel is modular, and driven by whatever
5789 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5790 isenkram-cli package place two files for tasksel to find. First there
5791 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
5793 <p
><blockquote
><pre
>
5794 Task: isenkram-packages
5796 Description: Hardware specific packages (autodetected by isenkram)
5797 Based on the detected hardware various hardware specific packages are
5799 Test-new-install: show show
5801 Packages: for-current-hardware
5803 Task: isenkram-firmware
5805 Description: Hardware specific firmware packages (autodetected by isenkram)
5806 Based on the detected hardware various hardware specific firmware
5807 packages are proposed.
5808 Test-new-install: mark show
5810 Packages: for-current-hardware-firmware
5811 </pre
></blockquote
></p
>
5813 <p
>The key parts are Test-new-install which indicate how the task
5814 should be handled and the Packages line referencing to a script in
5815 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5816 list of packages to install. The for-current-hardware-firmware script
5817 look like this to list relevant firmware for the machine:
5819 <p
><blockquote
><pre
>
5822 PATH=/usr/sbin:$PATH
5824 isenkram-autoinstall-firmware -l
5825 </pre
></blockquote
></p
>
5827 <p
>With those two pieces in place, the firmware is installed by
5828 tasksel during the normal d-i run. :)
</p
>
5830 <p
>If you want to test what tasksel will install when isenkram-cli is
5831 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
5832 --new-install
</tt
> to get the list of packages that tasksel would
5835 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
5836 pilots in testing this feature, as isenkram is used there now to
5837 install firmware, replacing the earlier scripts.
</p
>
5842 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
5843 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
5844 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
5845 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
5846 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
5847 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5848 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
5849 on a screen normally showing the bread types and prizes:
</p
>
5851 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
5853 <p
>If it had booted as it was supposed to, I would never had known
5854 about this hidden Linux installation. It is interesting what
5855 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
5860 <title>New lsdvd release version
0.17 is ready
</title>
5861 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
5862 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
5863 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
5864 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
5865 got a new set of developers a few weeks ago, after the original
5866 developer decided to step down and pass the project to fresh blood.
5867 This project is now maintained by Petter Reinholdtsen and Steve
5870 <p
>I just wrapped up
5871 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
5872 new lsdvd release
</a
>, available in git or from
5873 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
5874 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
5879 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
5880 <li
>Check for garbage in the program chains, which indicate that a track is
5881 non-existant, to work around additional copy protection
</li
>
5882 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
5883 <li
>Fix pallete display of first entry
</li
>
5884 <li
>Fix include orders
</li
>
5885 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
5886 <li
>Fix the chapter count
</li
>
5887 <li
>Make sure the array size and the array limit used when initialising
5888 the palette size is the same.
</li
>
5889 <li
>Fix array printing.
</li
>
5890 <li
>Correct subsecond calculations.
</li
>
5891 <li
>Add sector information to the output format.
</li
>
5892 <li
>Clean up code to be closer to ANSI C and compile without warnings
5893 with more GCC compiler warnings.
</li
>
5897 <p
>This change bring together patches for lsdvd in use in various
5898 Linux and Unix distributions, as well as patches submitted to the
5899 project the last nine years. Please check it out. :)
</p
>
5904 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
5905 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
5906 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
5907 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
5908 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5909 project
</a
> provide a Linux solution for schools, including a
5910 powerful desktop with education software, a central server providing
5911 web pages, user database, user home directories, central login and PXE
5912 boot of both clients without disk and the installation to install Debian
5913 Edu on machines with disk (and a few other services perhaps to small
5914 to mention here). We in the Debian Edu team are currently working on
5915 the Jessie based version, trying to get everything in shape before the
5916 freeze, to avoid having to maintain our own package repository in the
5918 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
5919 status
</a
> can be seen on the Debian wiki, and there is still heaps of
5920 work left. Some fatal problems block testing, breaking the installer,
5921 but it is possible to work around these to get anyway. Here is a
5922 recipe on how to get the installation limping along.
</p
>
5924 <p
>First, download the test ISO via
5925 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
5926 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
5928 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
5929 The ISO build was broken on Tuesday, so we do not get a new ISO every
5930 12 hours or so, but thankfully the ISO we already got we are able to
5931 install with some tweaking.
</p
>
5933 <p
>When you get to the Debian Edu profile question, go to tty2
5934 (use Alt-Ctrl-F2), run
</p
>
5936 <p
><blockquote
><pre
>
5937 nano /usr/bin/edu-eatmydata-install
5938 </pre
></blockquote
></p
>
5940 <p
>and add
'exit
0' as the second line, disabling the eatmydata
5941 optimization. Return to the installation, select the profile you want
5942 and continue. Without this change, exim4-config will fail to install
5943 due to a known bug in eatmydata.
</p
>
5945 <p
>When you get the grub question at the end, answer /dev/sda (or if
5946 this do not work, figure out what your correct value would be. All my
5947 test machines need /dev/sda, so I have no advice if it do not fit
5948 your need.
</p
>
5950 <p
>If you installed a profile including a graphical desktop, log in as
5951 root after the initial boot from hard drive, and install the
5952 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5953 or mate. If you want several desktop options, install more than one
5954 metapackage. Once this is done, reboot and you should have a working
5955 graphical login screen. This workaround should no longer be needed
5956 once the education-tasks package version
1.801 enter testing in two
5959 <p
>I believe the ISO build will start working on two days when the new
5960 tasksel package enter testing and Steve McIntyre get a chance to
5961 update the debian-cd git repository. The eatmydata, grub and desktop
5962 issues are already fixed in unstable and testing, and should show up
5963 on the ISO as soon as the ISO build start working again. Well the
5964 eatmydata optimization is really just disabled. The proper fix
5965 require an upload by the eatmydata maintainer applying the patch
5966 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
5967 The rest have proper fixes in unstable.
</p
>
5969 <p
>I hope this get you going with the installation testing, as we are
5970 quickly running out of time trying to get our Jessie based
5971 installation ready before the distribution freeze in a month.
</p
>
5976 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
5977 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
5978 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
5979 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
5980 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
5981 to handle my fairly large DVD collection. It is a nice command line
5982 tool to get details about a DVD, like title, tracks, track length,
5983 etc, in XML, Perl or human readable format. But lsdvd have not seen
5984 any new development since
2006 and had a few irritating bugs affecting
5985 its use with some DVDs. Upstream seemed to be dead, and in January I
5986 sent a small probe asking for a version control repository for the
5987 project, without any reply. But I use it regularly and would like to
5988 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
5989 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
5990 the project admin, and after getting a reply from him explaining that
5991 he was no longer interested in the project, I asked if I could take
5992 over. And yesterday, I became project admin.
</p
>
5994 <p
>I
've been in touch with a Gentoo developer and the Debian
5995 maintainer interested in joining forces to maintain the upstream
5996 project, and I hope we can get a new release out fairly quickly,
5997 collecting the patches spread around on the internet into on place.
5998 I
've added the relevant Debian patches to the freshly created git
5999 repository, and expect the Gentoo patches to make it too. If you got
6000 a DVD collection and care about command line tools, check out
6001 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
6002 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
6003 list
</a
>. :)
</p
>
6008 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
6009 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
6010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
6011 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
6012 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
6013 a lot quicker. When we install more than
2000 packages in
6014 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
6015 tasksel in the installer, unpacking the binary packages take forever.
6016 A part of the slow I/O issue was discussed in
6017 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
6018 much file system sync-ing done by dpkg, which is the package
6019 responsible for unpacking the binary packages. Other parts (like code
6020 executed by postinst scripts) might also sync to disk during
6021 installation. All this sync-ing to disk do not really make sense to
6022 me. If the machine crash half-way through, I start over, I do not try
6023 to salvage the half installed system. So the failure sync-ing is
6024 supposed to protect against, hardware or system crash, is not really
6025 relevant while the installer is running.
</p
>
6027 <p
>A few days ago, I thought of a way to get rid of all the file
6028 system sync()-ing in a fairly non-intrusive way, without the need to
6029 change the code in several packages. The idea is not new, but I have
6030 not heard anyone propose the approach using dpkg-divert before. It
6031 depend on the small and clever package
6032 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
6033 uses LD_PRELOAD to replace the system functions for syncing data to
6034 disk with functions doing nothing, thus allowing programs to live
6035 dangerous while speeding up disk I/O significantly. Instead of
6036 modifying the implementation of dpkg, apt and tasksel (which are the
6037 packages responsible for selecting, fetching and installing packages),
6038 it occurred to me that we could just divert the programs away, replace
6039 them with a simple shell wrapper calling
6040 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
6041 Two days ago I decided to test the idea, and wrapped up a simple
6042 implementation for the Debian Edu udeb.
</p
>
6044 <p
>The effect was stunning. In my first test it reduced the running
6045 time of the pkgsel step (installing tasks) from
64 to less than
44
6046 minutes (
20 minutes shaved off the installation) on an old Dell
6047 Latitude D505 machine. I am not quite sure what the optimised time
6048 would have been, as I messed up the testing a bit, causing the debconf
6049 priority to get low enough for two questions to pop up during
6050 installation. As soon as I saw the questions I moved the installation
6051 along, but do not know how long the question were holding up the
6052 installation. I did some more measurements using Debian Edu Jessie,
6053 and got these results. The time measured is the time stamp in
6054 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
6055 "pkgsel: finishing up
" lines, if you want to do the same measurement
6056 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6057 timing thus do not depend on how quickly the user handle the tasksel
6060 <p
><table
>
6063 <th
>Machine/setup
</th
>
6064 <th
>Original tasksel
</th
>
6065 <th
>Optimised tasksel
</th
>
6066 <th
>Reduction
</th
>
6070 <td
>Latitude D505 Main+LTSP LXDE
</td
>
6071 <td
>64 min (
07:
46-
08:
50)
</td
>
6072 <td
><44 min (
11:
27-
12:
11)
</td
>
6073 <td
>>20 min
18%
</td
>
6077 <td
>Latitude D505 Roaming LXDE
</td
>
6078 <td
>57 min (
08:
48-
09:
45)
</td
>
6079 <td
>34 min (
07:
43-
08:
17)
</td
>
6080 <td
>23 min
40%
</td
>
6084 <td
>Latitude D505 Minimal
</td
>
6085 <td
>22 min (
10:
37-
10:
59)
</td
>
6086 <td
>11 min (
11:
16-
11:
27)
</td
>
6087 <td
>11 min
50%
</td
>
6091 <td
>Thinkpad X200 Minimal
</td
>
6092 <td
>6 min (
08:
19-
08:
25)
</td
>
6093 <td
>4 min (
08:
04-
08:
08)
</td
>
6094 <td
>2 min
33%
</td
>
6098 <td
>Thinkpad X200 Roaming KDE
</td
>
6099 <td
>19 min (
09:
21-
09:
40)
</td
>
6100 <td
>15 min (
10:
25-
10:
40)
</td
>
6101 <td
>4 min
21%
</td
>
6104 </table
></p
>
6106 <p
>The test is done using a netinst ISO on a USB stick, so some of the
6107 time is spent downloading packages. The connection to the Internet
6108 was
100Mbit/s during testing, so downloading should not be a
6109 significant factor in the measurement. Download typically took a few
6110 seconds to a few minutes, depending on the amount of packages being
6111 installed.
</p
>
6113 <p
>The speedup is implemented by using two hooks in
6114 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
6115 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
6116 finish-install.d hook to remove the divert at the end of the
6117 installation. I picked the pre-pkgsel.d hook instead of the
6118 post-base-installer.d hook because I test using an ISO without the
6119 eatmydata package included, and the post-base-installer.d hook in
6120 Debian Edu can only operate on packages included in the ISO. The
6121 negative effect of this is that I am unable to activate this
6122 optimization for the kernel installation step in d-i. If the code is
6123 moved to the post-base-installer.d hook, the speedup would be larger
6124 for the entire installation.
</p
>
6126 <p
>I
've implemented this in the
6127 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
6128 git repository, and plan to provide the optimization as part of the
6129 Debian Edu installation. If you want to test this yourself, you can
6130 create two files in the installer (or in an udeb). One shell script
6131 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
6133 <p
><blockquote
><pre
>
6136 . /usr/share/debconf/confmodule
6138 logger -t my-pkgsel
"info: $*
"
6141 logger -t my-pkgsel
"error: $*
"
6143 override_install() {
6144 apt-install eatmydata || true
6145 if [ -x /target/usr/bin/eatmydata ] ; then
6146 for bin in dpkg apt-get aptitude tasksel ; do
6148 # Test that the file exist and have not been diverted already.
6149 if [ -f /target$file ] ; then
6150 info
"diverting $file using eatmydata
"
6151 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
6152 > /target$file.edu
6153 chmod
755 /target$file.edu
6154 in-target dpkg-divert --package debian-edu-config \
6155 --rename --quiet --add $file
6156 ln -sf ./$bin.edu /target$file
6158 error
"unable to divert $file, as it is missing.
"
6162 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
6167 </pre
></blockquote
></p
>
6169 <p
>To clean up, another shell script should go into
6170 /usr/lib/finish-install.d/ with code like this:
6172 <p
><blockquote
><pre
>
6174 . /usr/share/debconf/confmodule
6176 logger -t my-finish-install
"error: $@
"
6178 remove_install_override() {
6179 for bin in dpkg apt-get aptitude tasksel ; do
6181 if [ -x /target$file.edu ] ; then
6183 in-target dpkg-divert --package debian-edu-config \
6184 --rename --quiet --remove $file
6187 error
"Missing divert for $file.
"
6190 sync # Flush file buffers before continuing
6193 remove_install_override
6194 </pre
></blockquote
></p
>
6196 <p
>In Debian Edu, I placed both code fragments in a separate script
6197 edu-eatmydata-install and call it from the pre-pkgsel.d and
6198 finish-install.d scripts.
</p
>
6200 <p
>By now you might ask if this change should get into the normal
6201 Debian installer too? I suspect it should, but am not sure the
6202 current debian-installer coordinators find it useful enough. It also
6203 depend on the side effects of the change. I
'm not aware of any, but I
6204 guess we will see if the change is safe after some more testing.
6205 Perhaps there is some package in Debian depending on sync() and
6206 fsync() having effect? Perhaps it should go into its own udeb, to
6207 allow those of us wanting to enable it to do so without affecting
6210 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
6211 will break installation of all programs using gnutls because of
6212 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
6213 eatmydata package in Debian will solve it.
</p
>
6215 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
6216 the optimization work again. And I have discovered that the
6217 dpkg-divert trick is not really needed and implemented a slightly
6218 simpler approach as part of the debian-edu-install package. See
6219 tools/edu-eatmydata-install in the source package.
</p
>
6221 <p
>Update
2014-
11-
11: Unfortunately, a new
6222 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
6223 triggering on i386 made it into testing, and broke this installation
6224 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
6225 request
768893</a
> is accepted, it should be working again.
</p
>
6230 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
6231 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
6232 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
6233 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
6234 <description><p
>Yesterday, I had the pleasure of attending a talk with the
6235 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
6236 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
6237 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
6238 learn that there is a large set of publicly available key servers to
6239 use when looking for peoples public key. So far I have used
6240 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6241 were misbehaving, but those days are ended. The servers I have used
6242 up until yesterday have been slow and some times unavailable. I hope
6243 those problems are gone now.
</p
>
6245 <p
>Behind the round robin DNS entry of the
6246 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
6247 there is a pool of more than
100 keyservers which are checked every
6248 day to ensure they are well connected and up to date. It must be
6249 better than what I have used so far. :)
</p
>
6251 <p
>Yesterdays speaker told me that the service is the default
6252 keyserver provided by the default configuration in GnuPG, but this do
6253 not seem to be used in Debian. Perhaps it should?
</p
>
6255 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
6258 <p
><blockquote
><pre
>
6259 keyserver pool.sks-keyservers.net
6260 </pre
></blockquote
></p
>
6262 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
6263 entries in DNS. Just for fun, I did just that at work, so now every
6264 user of GnuPG at the University of Oslo should find a OpenGPG
6265 keyserver automatically should their need it:
</p
>
6267 <p
><blockquote
><pre
>
6268 % host -t srv _pgpkey-http._tcp.uio.no
6269 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
6271 </pre
></blockquote
></p
>
6273 <p
>Now if only
6274 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
6275 HKP lookup protocol
</a
> supported finding signature paths, I would be
6276 very happy. It can look up a given key or search for a user ID, but I
6277 normally do not want that, but to find a trust path from my key to
6278 another key. Given a user ID or key ID, I would like to find (and
6279 download) the keys representing a signature path from my key to the
6280 key in question, to be able to get a trust path between the two keys.
6281 This is as far as I can tell not possible today. Perhaps something
6282 for a future version of the protocol?
</p
>
6287 <title>From English wiki to translated PDF and epub via Docbook
</title>
6288 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
6289 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
6290 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
6291 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6292 project
</a
> provide an instruction manual for teachers, system
6293 administrators and other users that contain useful tips for setting up
6294 and maintaining a Debian Edu installation. This text is about how the
6295 text processing of this manual is handled in the project.
</p
>
6297 <p
>One goal of the project is to provide information in the native
6298 language of its users, and for this we need to handle translations.
6299 But we also want to make sure each language contain the same
6300 information, so for this we need a good way to keep the translations
6301 in sync. And we want it to be easy for our users to improve the
6302 documentation, avoiding the need to learn special formats or tools to
6303 contribute, and the obvious way to do this is to make it possible to
6304 edit the documentation using a web browser. We also want it to be
6305 easy for translators to keep the translation up to date, and give them
6306 help in figuring out what need to be translated. Here is the list of
6307 tools and the process we have found trying to reach all these
6310 <p
>We maintain the authoritative source of our manual in the
6311 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
6312 wiki
</a
>, as several wiki pages written in English. It consist of one
6313 front page with references to the different chapters, several pages
6314 for each chapter, and finally one
"collection page
" gluing all the
6315 chapters together into one large web page (aka
6316 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
6317 AllInOne page
</a
>). The AllInOne page is the one used for further
6318 processing and translations. Thanks to the fact that the
6319 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
6320 wiki.debian.org support exporting pages in
6321 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
6322 the list of pages to export using the raw version of the AllInOne
6323 page, loop over each of them to generate a Docbook XML version of the
6324 manual. This process also download images and transform image
6325 references to use the locally downloaded images. The generated
6326 Docbook XML files are slightly broken, so some post-processing is done
6327 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
6328 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6329 a handfull of images. The XML file can now be used to generate PDF, HTML
6330 and epub versions of the English manual. This is the basic step of
6331 our process, making PDF (using dblatex), HTML (using xsltproc) and
6332 epub (using dbtoepub) version from Docbook XML, and the resulting files
6333 are placed in the debian-edu-doc-en binary package.
</p
>
6335 <p
>But English documentation is not enough for us. We want translated
6336 documentation too, and we want to make it easy for translators to
6337 track the English original. For this we use the
6338 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
6339 which allow us to transform the English Docbook XML file into a
6340 translation file (a .pot file), usable with the normal gettext based
6341 translation tools used by those translating free software. The pot
6342 file is used to create and maintain translation files (several .po
6343 files), which the translations update with the native language
6344 translations of all titles, paragraphs and blocks of text in the
6345 original. The next step is combining the original English Docbook XML
6346 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6347 create a translated Docbook XML file (in this case
6348 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6349 translated, if the translation is not complete) Docbook XML file can
6350 then be used like the original to create a PDF, HTML and epub version
6351 of the documentation.
</p
>
6353 <p
>The translators use different tools to edit the .po files. We
6355 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
6356 while some use emacs and vi, others can use web based editors like
6357 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
6358 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
6359 is where the .po file end up, in our git repository. Updated
6360 translations can either be committed directly to git, or submitted as
6361 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
6362 against the debian-edu-doc package
</a
>.
</p
>
6364 <p
>One challenge is images, which both might need to be translated (if
6365 they show translated user applications), and are needed in different
6366 formats when creating PDF and HTML versions (epub is a HTML version in
6367 this regard). For this we transform the original PNG images to the
6368 needed density and format during build, and have a way to provide
6369 translated images by storing translated versions in
6370 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6371 package maintainers know more.
</p
>
6373 <p
>If you wonder what the result look like, we provide
6374 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
6375 of the documentation packages on the web
</a
>. See for example the
6376 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
6377 PDF version
</a
> or the
6378 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
6379 HTML version
</a
>. We do not yet build the epub version by default,
6380 but perhaps it will be done in the future.
</p
>
6382 <p
>To learn more, check out
6383 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
6384 debian-edu-doc package
</a
>,
6385 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
6386 manual on the wiki
</a
> and
6387 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
6388 translation instructions
</a
> in the manual.
</p
>
6393 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
6394 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
6395 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
6396 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
6397 <description><p
>It would be nice if it was easier in Debian to get all the hardware
6398 related packages relevant for the computer installed automatically.
6399 So I implemented one, using
6400 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
6401 package
</a
>. To use it, install the tasksel and isenkram packages and
6402 run tasksel as user root. You should be presented with a new option,
6403 "Hardware specific packages (autodetected by isenkram)
". When you
6404 select it, tasksel will install the packages isenkram claim is fit for
6405 the current hardware, hot pluggable or not.
<p
>
6407 <p
>The implementation is in two files, one is the tasksel menu entry
6408 description, and the other is the script used to extract the list of
6409 packages to install. The first part is in
6410 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
6413 <p
><blockquote
><pre
>
6416 Description: Hardware specific packages (autodetected by isenkram)
6417 Based on the detected hardware various hardware specific packages are
6419 Test-new-install: mark show
6421 Packages: for-current-hardware
6422 </pre
></blockquote
></p
>
6424 <p
>The second part is in
6425 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
6428 <p
><blockquote
><pre
>
6433 isenkram-autoinstall-firmware -l
6435 </pre
></blockquote
></p
>
6437 <p
>All in all, a very short and simple implementation making it
6438 trivial to install the hardware dependent package we all may want to
6439 have installed on our machines. I
've not been able to find a way to
6440 get tasksel to tell you exactly which packages it plan to install
6441 before doing the installation. So if you are curious or careful,
6442 check the output from the isenkram-* command line tools first.
</p
>
6444 <p
>The information about which packages are handling which hardware is
6445 fetched either from the isenkram package itself in
6446 /usr/share/isenkram/, from git.debian.org or from the APT package
6447 database (using the Modaliases header). The APT package database
6448 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6449 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
6450 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
6451 the python-apt code (bug
6452 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
6453 workaround I was able to get rid of the file descriptor leak and
6454 reduce the memory leak from ~
30 MiB per hardware detection down to
6455 around
2 MiB per hardware detection. It should make the desktop
6456 daemon a lot more useful. The fix is in version
0.7 uploaded to
6457 unstable today.
</p
>
6459 <p
>I believe the current way of mapping hardware to packages in
6460 Isenkram is is a good draft, but in the future I expect isenkram to
6461 use the AppStream data source for this. A proposal for getting proper
6462 AppStream support into Debian is floating around as
6463 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
6464 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
6465 project
</a
> will take place this summer to improve the situation. I
6466 look forward to seeing the result, and welcome patches for isenkram to
6467 start using the information when it is ready.
</p
>
6469 <p
>If you want your package to map to some specific hardware, either
6470 add a
"Xb-Modaliases
" header to your control file like I did in
6471 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
6472 package
</a
> or submit a bug report with the details to the isenkram
6474 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
6475 blog posts tagged isenkram
</a
> for details on the notation. I expect
6476 the information will be migrated to AppStream eventually, but for the
6477 moment I got no better place to store it.
</p
>
6482 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
6483 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
6484 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
6485 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
6486 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6487 project
</a
> is working on providing the software and hardware to make
6488 it easy for non-technical people to host their data and communication
6489 at home, and being able to communicate with their friends and family
6490 encrypted and away from prying eyes. It is still going strong, and
6491 today a major mile stone was reached.
</p
>
6493 <p
>Today, the last of the packages currently used by the project to
6494 created the system images were accepted into Debian Unstable. It was
6495 the freedombox-setup package, which is used to configure the images
6496 during build and on the first boot. Now all one need to get going is
6497 the build code from the freedom-maker git repository and packages from
6498 Debian. And once the freedombox-setup package enter testing, we can
6499 build everything directly from Debian. :)
</p
>
6501 <p
>Some key packages used by Freedombox are
6502 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
6503 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
6504 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
6505 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
6506 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
6507 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
6508 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
6509 are plans to integrate more packages into the setup. User
6510 documentation is maintained on the Debian wiki. Please
6511 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
6512 the manual
</a
> and help us improve it.
</p
>
6514 <p
>To test for yourself and create boot images with the FreedomBox
6515 setup, run this on a Debian machine using a user with sudo rights to
6516 become root:
</p
>
6518 <p
><pre
>
6519 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6520 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6522 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6524 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6525 </pre
></p
>
6527 <p
>Root access is needed to run debootstrap and mount loopback
6528 devices. See the README in the freedom-maker git repo for more
6529 details on the build. If you do not want all three images, trim the
6530 make line. Note that the virtualbox-image target is not really
6531 virtualbox specific. It create a x86 image usable in kvm, qemu,
6532 vmware and any other x86 virtual machine environment. You might need
6533 the version of vmdebootstrap in Jessie to get the build working, as it
6534 include fixes for a race condition with kpartx.
</p
>
6536 <p
>If you instead want to install using a Debian CD and the preseed
6537 method, boot a Debian Wheezy ISO and use this boot argument to load
6538 the preseed values:
</p
>
6540 <p
><pre
>
6541 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6542 </pre
></p
>
6544 <p
>I have not tested it myself the last few weeks, so I do not know if
6545 it still work.
</p
>
6547 <p
>If you wonder how to help, one task you could look at is using
6548 systemd as the boot system. It will become the default for Linux in
6549 Jessie, so we need to make sure it is usable on the Freedombox. I did
6550 a simple test a few weeks ago, and noticed dnsmasq failed to start
6551 during boot when using systemd. I suspect there are other problems
6552 too. :) To detect problems, there is a test suite included, which can
6553 be run from the plinth web interface.
</p
>
6555 <p
>Give it a go and let us know how it goes on the mailing list, and help
6556 us get the new release published. :) Please join us on
6557 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6558 irc.debian.org)
</a
> and
6559 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6560 mailing list
</a
> if you want to help make this vision come true.
</p
>
6565 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
6566 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
6567 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
6568 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
6569 <description><p
>For a while now, I have been looking for a sensible offsite backup
6570 solution for use at home. My requirements are simple, it must be
6571 cheap and locally encrypted (in other words, I keep the encryption
6572 keys, the storage provider do not have access to my private files).
6573 One idea me and my friends had many years ago, before the cloud
6574 storage providers showed up, was to use Google mail as storage,
6575 writing a Linux block device storing blocks as emails in the mail
6576 service provided by Google, and thus get heaps of free space. On top
6577 of this one can add encryption, RAID and volume management to have
6578 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6579 I never found time to implement such system. But the last few weeks I
6580 have looked at a system called
6581 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
6582 mounted network backed file system with the features I need.
</p
>
6584 <p
>S3QL is a fuse file system with a local cache and cloud storage,
6585 handling several different storage providers, any with Amazon S3,
6586 Google Drive or OpenStack API. There are heaps of such storage
6587 providers. S3QL can also use a local directory as storage, which
6588 combined with sshfs allow for file storage on any ssh server. S3QL
6589 include support for encryption, compression, de-duplication, snapshots
6590 and immutable file systems, allowing me to mount the remote storage as
6591 a local mount point, look at and use the files as if they were local,
6592 while the content is stored in the cloud as well. This allow me to
6593 have a backup that should survive fire. The file system can not be
6594 shared between several machines at the same time, as only one can
6595 mount it at the time, but any machine with the encryption key and
6596 access to the storage service can mount it if it is unmounted.
</p
>
6598 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
6599 package is included already. So to get started, run
<tt
>apt-get
6600 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
6601 Greenqloud, after reading their nice recipe on
6602 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
6603 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
6604 in Iceland more than those in USA when it come to keeping my personal
6605 data safe and private, and thus would rather spend money on a company
6606 in Iceland. Another nice recipe is available from the article
6607 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
6608 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
6609 Admin magazine. When the provider is picked, figure out how to get
6610 the API key needed to connect to the storage API. With Greencloud,
6611 the key did not show up until I had added payment details to my
6614 <p
>Armed with the API access details, it is time to create the file
6615 system. First, create a new bucket in the cloud. This bucket is the
6616 file system storage area. I picked a bucket name reflecting the
6617 machine that was going to store data there, but any name will do.
6618 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
6619 the API login and password, and a locally created password. Store it
6620 all in ~root/.s3ql/authinfo2 like this:
6622 <p
><blockquote
><pre
>
6624 storage-url: s3c://s.greenqloud.com:
443/bucket-name
6625 backend-login: API-login
6626 backend-password: API-password
6627 fs-passphrase: local-password
6628 </pre
></blockquote
></p
>
6630 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
6631 but any sensible way to create a fairly random password should do it.
6632 Armed with these details, it is now time to run mkfs, entering the API
6633 details and password to create it:
</p
>
6635 <p
><blockquote
><pre
>
6636 # mkdir -m
700 /var/lib/s3ql-cache
6637 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6638 --ssl s3c://s.greenqloud.com:
443/bucket-name
6639 Enter backend login:
6640 Enter backend password:
6641 Before using S3QL, make sure to read the user
's guide, especially
6642 the
'Important Rules to Avoid Loosing Data
' section.
6643 Enter encryption password:
6644 Confirm encryption password:
6645 Generating random encryption key...
6646 Creating metadata tables...
6656 Compressing and uploading metadata...
6657 Wrote
0.00 MB of compressed metadata.
6658 #
</pre
></blockquote
></p
>
6660 <p
>The next step is mounting the file system to make the storage available.
6662 <p
><blockquote
><pre
>
6663 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6664 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6665 Using
4 upload threads.
6666 Downloading and decompressing metadata...
6676 Mounting filesystem...
6678 Filesystem Size Used Avail Use% Mounted on
6679 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
6681 </pre
></blockquote
></p
>
6683 <p
>The file system is now ready for use. I use rsync to store my
6684 backups in it, and as the metadata used by rsync is downloaded at
6685 mount time, no network traffic (and storage cost) is triggered by
6686 running rsync. To unmount, one should not use the normal umount
6687 command, as this will not flush the cache to the cloud storage, but
6688 instead running the umount.s3ql command like this:
6690 <p
><blockquote
><pre
>
6693 </pre
></blockquote
></p
>
6695 <p
>There is a fsck command available to check the file system and
6696 correct any problems detected. This can be used if the local server
6697 crashes while the file system is mounted, to reset the
"already
6698 mounted
" flag. This is what it look like when processing a working
6699 file system:
</p
>
6701 <p
><blockquote
><pre
>
6702 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
6703 Using cached metadata.
6704 File system seems clean, checking anyway.
6705 Checking DB integrity...
6706 Creating temporary extra indices...
6707 Checking lost+found...
6708 Checking cached objects...
6709 Checking names (refcounts)...
6710 Checking contents (names)...
6711 Checking contents (inodes)...
6712 Checking contents (parent inodes)...
6713 Checking objects (reference counts)...
6714 Checking objects (backend)...
6715 ..processed
5000 objects so far..
6716 ..processed
10000 objects so far..
6717 ..processed
15000 objects so far..
6718 Checking objects (sizes)...
6719 Checking blocks (referenced objects)...
6720 Checking blocks (refcounts)...
6721 Checking inode-block mapping (blocks)...
6722 Checking inode-block mapping (inodes)...
6723 Checking inodes (refcounts)...
6724 Checking inodes (sizes)...
6725 Checking extended attributes (names)...
6726 Checking extended attributes (inodes)...
6727 Checking symlinks (inodes)...
6728 Checking directory reachability...
6729 Checking unix conventions...
6730 Checking referential integrity...
6731 Dropping temporary indices...
6732 Backing up old metadata...
6742 Compressing and uploading metadata...
6743 Wrote
0.89 MB of compressed metadata.
6745 </pre
></blockquote
></p
>
6747 <p
>Thanks to the cache, working on files that fit in the cache is very
6748 quick, about the same speed as local file access. Uploading large
6749 amount of data is to me limited by the bandwidth out of and into my
6750 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
6751 which is very close to my upload speed, and downloading the same
6752 Debian installation ISO gave me
610 kiB/s, close to my download speed.
6753 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
6754 network, not the file system code. I do not know what a good cache
6755 size would be, but suspect that the cache should e larger than your
6756 working set.
</p
>
6758 <p
>I mentioned that only one machine can mount the file system at the
6759 time. If another machine try, it is told that the file system is
6762 <p
><blockquote
><pre
>
6763 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6764 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6765 Using
8 upload threads.
6766 Backend reports that fs is still mounted elsewhere, aborting.
6768 </pre
></blockquote
></p
>
6770 <p
>The file content is uploaded when the cache is full, while the
6771 metadata is uploaded once every
24 hour by default. To ensure the
6772 file system content is flushed to the cloud, one can either umount the
6773 file system, or ask S3QL to flush the cache and metadata using
6776 <p
><blockquote
><pre
>
6777 # s3qlctrl upload-meta /s3ql
6778 # s3qlctrl flushcache /s3ql
6780 </pre
></blockquote
></p
>
6782 <p
>If you are curious about how much space your data uses in the
6783 cloud, and how much compression and deduplication cut down on the
6784 storage usage, you can use s3qlstat on the mounted file system to get
6787 <p
><blockquote
><pre
>
6789 Directory entries:
9141
6792 Total data size:
22049.38 MB
6793 After de-duplication:
21955.46 MB (
99.57% of total)
6794 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
6795 Database size:
2.39 MB (uncompressed)
6796 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6798 </pre
></blockquote
></p
>
6800 <p
>I mentioned earlier that there are several possible suppliers of
6801 storage. I did not try to locate them all, but am aware of at least
6802 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
6803 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
6804 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
6805 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
6806 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
6807 accept payment in Bitcoin. Pick one that suit your need. Some of
6808 them provide several GiB of free storage, but the prize models are
6809 quite different and you will have to figure out what suits you
6812 <p
>While researching this blog post, I had a look at research papers
6813 and posters discussing the S3QL file system. There are several, which
6814 told me that the file system is getting a critical check by the
6815 science community and increased my confidence in using it. One nice
6817 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
6818 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6819 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
6820 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6821 and Pamela Smith. Please have a look.
</p
>
6823 <p
>Given my problems with different file systems earlier, I decided to
6824 check out the mounted S3QL file system to see if it would be usable as
6825 a home directory (in other word, that it provided POSIX semantics when
6826 it come to locking and umask handling etc). Running
6827 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
6828 test code to check file system semantics
</a
>, I was happy to discover that
6829 no error was found. So the file system can be used for home
6830 directories, if one chooses to do so.
</p
>
6832 <p
>If you do not want a locally file system, and want something that
6833 work without the Linux fuse file system, I would like to mention the
6834 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
6835 provide locally encrypted backup using a command line client. It have
6836 a nicer access control system, where one can split out read and write
6837 access, allowing some systems to write to the backup and others to
6838 only read from it.
</p
>
6840 <p
>As usual, if you use Bitcoin and want to show your support of my
6841 activities, please send Bitcoin donations to my address
6842 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6847 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
6848 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
6849 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
6850 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
6851 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6852 project
</a
> is working on providing the software and hardware for
6853 making it easy for non-technical people to host their data and
6854 communication at home, and being able to communicate with their
6855 friends and family encrypted and away from prying eyes. It has been
6856 going on for a while, and is slowly progressing towards a new test
6857 release (
0.2).
</p
>
6859 <p
>And what day could be better than the Pi day to announce that the
6860 new version will provide
"hard drive
" / SD card / USB stick images for
6861 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6862 system), and can also be installed using a Debian installer preseed
6863 file. The Debian based Freedombox is now based on Debian Jessie,
6864 where most of the needed packages used are already present. Only one,
6865 the freedombox-setup package, is missing. To try to build your own
6866 boot image to test the current status, fetch the freedom-maker scripts
6868 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
6869 with a user with sudo access to become root:
6872 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6874 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6875 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6877 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6880 <p
>Root access is needed to run debootstrap and mount loopback
6881 devices. See the README for more details on the build. If you do not
6882 want all three images, trim the make line. But note that thanks to
<a
6883 href=
"https://bugs.debian.org/
741407">a race condition in
6884 vmdebootstrap
</a
>, the build might fail without the patch to the
6885 kpartx call.
</p
>
6887 <p
>If you instead want to install using a Debian CD and the preseed
6888 method, boot a Debian Wheezy ISO and use this boot argument to load
6889 the preseed values:
</p
>
6892 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6895 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
6896 recently introduced bug in apt in Jessie
</a
>, the installer will
6897 currently hang while setting up APT sources. Killing the
6898 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
6899 installation will get the installation going. This affect all
6900 installations in Jessie, and I expect it will be fixed soon.
</p
>
6902 <p
>Give it a go and let us know how it goes on the mailing list, and help
6903 us get the new release published. :) Please join us on
6904 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6905 irc.debian.org)
</a
> and
6906 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6907 mailing list
</a
> if you want to help make this vision come true.
</p
>
6912 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
6913 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
6914 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
6915 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
6916 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
6917 innetgr tools, because I needed them in
6918 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
6919 ng-utils, and it has served me well. I placed the project under the
6920 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
6921 repository. But many years ago, the CVS repository was dropped (lost,
6922 not migrated to new hardware, not sure), and the project have lacked a
6923 proper home since then.
</p
>
6925 <p
>Last summer, I had a look at the package and made a new release
6926 fixing a irritating crash bug, but was unable to store the changes in
6927 a proper source control system. I applied for a project on
6928 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
6929 to follow up on it. Until today. :)
</p
>
6931 <p
>After many hours of cleaning and migration, the ng-utils project
6932 now have a new home, and a git repository with the highlight of the
6933 history of the project. I published all release tarballs and imported
6934 them into the git repository. As the project is really stable and not
6935 expected to gain new features any time soon, I decided to make a new
6936 release and call it
1.0. Visit the new project home on
6937 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
6938 if you want to check it out. The new version is also uploaded into
6939 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
6944 <title>Testing sysvinit from experimental in Debian Hurd
</title>
6945 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
6946 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
6947 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
6948 <description><p
>A few days ago I decided to try to help the Hurd people to get
6949 their changes into sysvinit, to allow them to use the normal sysvinit
6950 boot system instead of their old one. This follow up on the
6951 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
6952 Google Summer of Code work
</a
> done last summer by Justus Winter to
6953 get Debian on Hurd working more like Debian on Linux. To get started,
6954 I downloaded a prebuilt hard disk image from
6955 <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
>,
6956 and started it using virt-manager.
</p
>
6958 <p
>The first think I had to do after logging in (root without any
6959 password) was to get the network operational. I followed
6960 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
6961 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
6962 commands as root to get the machine to accept a IP address from the
6963 kvm internal DHCP server:
</p
>
6965 <p
><blockquote
><pre
>
6966 settrans -fgap /dev/netdde /hurd/netdde
6967 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
6968 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
6970 </pre
></blockquote
></p
>
6972 <p
>After this, the machine had internet connectivity, and I could
6973 upgrade it and install the sysvinit packages from experimental and
6974 enable it as the default boot system in Hurd.
</p
>
6976 <p
>But before I did that, I set a password on the root user, as ssh is
6977 running on the machine it for ssh login to work a password need to be
6978 set. Also, note that a bug somewhere in openssh on Hurd block
6979 compression from working. Remember to turn that off on the client
6982 <p
>Run these commands as root to upgrade and test the new sysvinit
6985 <p
><blockquote
><pre
>
6986 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
6987 deb http://http.debian.net/debian/ experimental main
6990 apt-get dist-upgrade
6991 apt-get install -t experimental initscripts sysv-rc sysvinit \
6992 sysvinit-core sysvinit-utils
6993 update-alternatives --config runsystem
6994 </pre
></blockquote
></p
>
6996 <p
>To reboot after switching boot system, you have to use
6997 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
6998 yet a sysvinit process able to receive the signals from the normal
6999 'reboot
' command. After switching to sysvinit as the boot system,
7000 upgrading every package and rebooting, the network come up with DHCP
7001 after boot as it should, and the settrans/pkill hack mentioned at the
7002 start is no longer needed. But for some strange reason, there are no
7003 longer any login prompt in the virtual console, so I logged in using
7006 <p
>Note that there are some race conditions in Hurd making the boot
7007 fail some times. No idea what the cause is, but hope the Hurd porters
7008 figure it out. At least Justus said on IRC (#debian-hurd on
7009 irc.debian.org) that they are aware of the problem. A way to reduce
7010 the impact is to upgrade to the Hurd packages built by Justus by
7011 adding this repository to the machine:
</p
>
7013 <p
><blockquote
><pre
>
7014 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
7015 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7017 </pre
></blockquote
></p
>
7019 <p
>At the moment the prebuilt virtual machine get some packages from
7020 http://ftp.debian-ports.org/debian, because some of the packages in
7021 unstable do not yet include the required patches that are lingering in
7022 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
7024 <p
><blockquote
><pre
>
7025 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
7026 i emacs - GNU Emacs editor (metapackage)
7027 i gdb - GNU Debugger
7028 i hurd-recommended - Miscellaneous translators
7029 i isc-dhcp-client - ISC DHCP client
7030 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7031 i libc-bin - Embedded GNU C Library: Binaries
7032 i libc-dev-bin - Embedded GNU C Library: Development binaries
7033 i libc0.3 - Embedded GNU C Library: Shared libraries
7034 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7035 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7036 i multiarch-support - Transitional package to ensure multiarch compatibilit
7037 i A x11-common - X Window System (X.Org) infrastructure
7038 i xorg - X.Org X Window System
7039 i A xserver-xorg - X.Org X server
7040 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7042 </pre
></blockquote
></p
>
7044 <p
>All in all, testing hurd has been an interesting experience. :)
7045 X.org did not work out of the box and I never took the time to follow
7046 the porters instructions to fix it. This time I was interested in the
7047 command line stuff.
<p
>
7052 <title>New chrpath release
0.16</title>
7053 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
7054 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
7055 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
7056 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
7057 find problems in C, C++ and Java code using static source code
7058 analysis. It can detect a lot of different problems, and is very
7059 useful to find memory and locking bugs in the error handling part of
7060 the source. The company behind it provide
7061 <a href=
"https://scan.coverity.com/
">check of free software projects as
7062 a community service
</a
>, and many hundred free software projects are
7063 already checked. A few days ago I decided to have a closer look at
7064 the Coverity system, and discovered that the
7065 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
7066 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
7067 projects I am involved with was already registered. But these are
7068 fairly big, and I would also like to have a small and easy project to
7069 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
7070 checking of the chrpath project
</a
>. It was
7071 added to the checker and discovered seven potential defects. Six of
7072 these were real, mostly resource
"leak
" when the program detected an
7073 error. Nothing serious, as the resources would be released a fraction
7074 of a second later when the program exited because of the error, but it
7075 is nice to do it right in case the source of the program some time in
7076 the future end up in a library. Having fixed all defects and added
7077 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
7078 mailing list for the chrpath developers
</a
>, I decided it was time to
7079 publish a new release. These are the release notes:
</p
>
7081 <p
>New in
0.16 released
2014-
01-
14:
</p
>
7085 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
7086 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
7087 <li
>Mention new project mailing list in the documentation.
</li
>
7092 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
7093 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
7094 project if something is wrong with the new release. The test suite
7095 did not discover any old errors, so if you find a new one, please also
7096 include a test suite check.
</p
>
7101 <title>New chrpath release
0.15</title>
7102 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
7103 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
7104 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
7105 <description><p
>After many years break from the package and a vain hope that
7106 development would be continued by someone else, I finally pulled my
7107 acts together this morning and wrapped up a new release of chrpath,
7108 the command line tool to modify the rpath and runpath of already
7109 compiled ELF programs. The update was triggered by the persistence of
7110 Isha Vishnoi at IBM, which needed a new config.guess file to get
7111 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
7112 is working on. I checked the
7113 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
7114 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
7115 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
7116 packages for interesting patches (failed to find the source from
7117 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7118 These are the release notes:
</p
>
7120 <p
>New in
0.15 released
2013-
11-
24:
</p
>
7124 <li
>Updated config.sub and config.guess from the GNU project to work
7125 with newer architectures. Thanks to isha vishnoi for the heads
7128 <li
>Updated README with current URLs.
</li
>
7130 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7131 Matthias Klose.
</li
>
7133 <li
>Added missing help for -k|--keepgoing option, using patch by
7134 Petr Machata found in Fedora.
</li
>
7136 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
7137 .dynamic is a NULL terminated string. Based on patch found in
7138 Fedora credited Axel Thimm and Christian Krause.
</li
>
7143 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
7144 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
7145 project if something is wrong with the new release. The test suite
7146 did not discover any old errors, so if you find a new one, please also
7147 include a testsuite check.
</p
>
7152 <title>Debian init.d boot script example for rsyslog
</title>
7153 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
7154 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
7155 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
7156 <description><p
>If one of the points of switching to a new init system in Debian is
7157 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
7158 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
7159 init.d scripts at all. Here is an example init.d script, ie a rewrite
7160 of /etc/init.d/rsyslog:
</p
>
7162 <p
><pre
>
7163 #!/lib/init/init-d-script
7166 # Required-Start: $remote_fs $time
7167 # Required-Stop: umountnfs $time
7168 # X-Stop-After: sendsigs
7169 # Default-Start:
2 3 4 5
7170 # Default-Stop:
0 1 6
7171 # Short-Description: enhanced syslogd
7172 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7173 # It is quite compatible to stock sysklogd and can be
7174 # used as a drop-in replacement.
7176 DESC=
"enhanced syslogd
"
7177 DAEMON=/usr/sbin/rsyslogd
7178 </pre
></p
>
7180 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
7181 script was
137 lines, and the above is just
15 lines, most of it meta
7182 info/comments.
</p
>
7184 <p
>How to do this, you ask? Well, one create a new script
7185 /lib/init/init-d-script looking something like this:
7187 <p
><pre
>
7190 # Define LSB log_* functions.
7191 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
7192 # and status_of_proc is working.
7193 . /lib/lsb/init-functions
7196 # Function that starts the daemon/service
7202 #
0 if daemon has been started
7203 #
1 if daemon was already running
7204 #
2 if daemon could not be started
7205 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
7207 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7210 # Add code here, if necessary, that waits for the process to be ready
7211 # to handle requests from services started subsequently which depend
7212 # on this one. As a last resort, sleep for some time.
7216 # Function that stops the daemon/service
7221 #
0 if daemon has been stopped
7222 #
1 if daemon was already stopped
7223 #
2 if daemon could not be stopped
7224 # other if a failure occurred
7225 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
7226 RETVAL=
"$?
"
7227 [
"$RETVAL
" =
2 ]
&& return
2
7228 # Wait for children to finish too if this is a daemon that forks
7229 # and if the daemon is only ever run from this initscript.
7230 # If the above conditions are not satisfied then add some other code
7231 # that waits for the process to drop all resources that could be
7232 # needed by services started subsequently. A last resort is to
7233 # sleep for some time.
7234 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
7235 [
"$?
" =
2 ]
&& return
2
7236 # Many daemons don
't delete their pidfiles when they exit.
7238 return
"$RETVAL
"
7242 # Function that sends a SIGHUP to the daemon/service
7246 # If the daemon can reload its configuration without
7247 # restarting (for example, when it is sent a SIGHUP),
7248 # then implement that here.
7250 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
7255 scriptbasename=
"$(basename $
1)
"
7256 echo
"SN: $scriptbasename
"
7257 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
7258 script=
"$
1"
7265 NAME=$(basename $DAEMON)
7266 PIDFILE=/var/run/$NAME.pid
7268 # Exit if the package is not installed
7269 #[ -x
"$DAEMON
" ] || exit
0
7271 # Read configuration variable file if it is present
7272 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
7274 # Load the VERBOSE setting and other rcS variables
7277 case
"$
1" in
7279 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
7281 case
"$?
" in
7282 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7283 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7287 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
7289 case
"$?
" in
7290 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7291 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7295 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
7297 #reload|force-reload)
7299 # If do_reload() is not implemented then leave this commented out
7300 # and leave
'force-reload
' as an alias for
'restart
'.
7302 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
7306 restart|force-reload)
7308 # If the
"reload
" option is implemented then remove the
7309 #
'force-reload
' alias
7311 log_daemon_msg
"Restarting $DESC
" "$NAME
"
7313 case
"$?
" in
7316 case
"$?
" in
7318 1) log_end_msg
1 ;; # Old process is still running
7319 *) log_end_msg
1 ;; # Failed to start
7329 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
7335 </pre
></p
>
7337 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
7338 lot. I did not really polish the approach, so it might not always
7339 work out of the box, but you get the idea. I did not try very hard to
7340 optimize it nor make it more robust either.
</p
>
7342 <p
>A better argument for switching init system in Debian than reducing
7343 the size of init scripts (which is a good thing to do anyway), is to
7344 get boot system that is able to handle the kernel events sensibly and
7345 robustly, and do not depend on the boot to run sequentially. The boot
7346 and the kernel have not behaved sequentially in years.
</p
>
7351 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
7352 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
7353 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
7354 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
7355 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
7356 remote display access is the preferred solution with oVirt and RedHat
7357 Enterprise Virtualization, and I was sad to discover the other day
7358 that the browser plugin needed to use these systems seamlessly was
7359 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
7360 for a package
</a
> was from
2012-
04-
10 with no progress since
7361 2013-
04-
01, so I decided to wrap up a package based on the great work
7362 from Cajus Pollmeier and put it in a collab-maint maintained git
7363 repository to get a package I could use. I would very much like
7364 others to help me maintain the package (or just take over, I do not
7365 mind), but as no-one had volunteered so far, I just uploaded it to
7366 NEW. I hope it will be available in Debian in a few days.
</p
>
7368 <p
>The source is now available from
7369 <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
>
7374 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
7375 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
7376 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
7377 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
7378 <description><p
>The
7379 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
7380 program is a a very nice system to create virtual machine images. It
7381 create a image file, add a partition table, mount it and run
7382 debootstrap in the mounted directory to create a Debian system on a
7383 stick. Yesterday, I decided to try to teach it how to make images for
7384 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
7385 of a plan to simplify the build system for
7386 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
7387 project
</a
>. The FreedomBox project already uses vmdebootstrap for
7388 the virtualbox images, but its current build system made multistrap
7389 based system for Dreamplug images, and it is lacking support for
7390 Raspberry Pi.
</p
>
7392 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
7393 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7394 code and adjusted it to be able to build armel images on my amd64
7395 Debian laptop. I ended up giving vmdebootstrap five new options,
7396 allowing me to replicate the image creation process I use to make
7397 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
7398 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
7399 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
7400 call debootstrap with --foreign and to copy the handler into the
7401 generated chroot before running the second stage. This allow
7402 vmdebootstrap to create armel images on an amd64 host. Next I added
7403 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
7404 fstype
</tt
> to teach it to create a separate /boot/ partition with the
7405 given file system type, allowing me to create an image with a vfat
7406 partition for the /boot/ stuff. I also added a
<tt
>--variant
7407 variant
</tt
> option to allow me to create smaller images without the
7408 Debian base system packages installed. Finally, I added an option
7409 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
7410 as a boot loader. It is not needed on the Raspberry Pi and probably
7411 most other non-x86 architectures. The changes were accepted by the
7412 upstream author of vmdebootstrap yesterday and today, and is now
7414 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
7415 upstream project page
</a
>.
</p
>
7417 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
7418 create a small script (the customize script) to add the non-free
7419 binary blob needed to boot the Raspberry Pi and the APT source
7422 <p
><pre
>
7424 set -e # Exit on first error
7425 rootdir=
"$
1"
7426 cd
"$rootdir
"
7427 cat
&lt;
&lt;EOF
> etc/apt/sources.list
7428 deb http://http.debian.net/debian/ jessie main contrib non-free
7430 # Install non-free binary blob needed to boot Raspberry Pi. This
7431 # install a kernel somewhere too.
7432 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7433 -O $rootdir/usr/bin/rpi-update
7434 chmod a+x $rootdir/usr/bin/rpi-update
7435 mkdir -p $rootdir/lib/modules
7436 touch $rootdir/boot/start.elf
7437 chroot $rootdir rpi-update
7438 </pre
></p
>
7440 <p
>Next, fetch the latest vmdebootstrap script and call it like this
7441 to build the image:
</p
>
7444 sudo ./vmdebootstrap \
7447 --distribution jessie \
7448 --mirror http://http.debian.net/debian \
7457 --root-password raspberry \
7458 --hostname raspberrypi \
7459 --foreign /usr/bin/qemu-arm-static \
7460 --customize `pwd`/customize \
7462 --package git-core \
7463 --package binutils \
7464 --package ca-certificates \
7467 </pre
></p
>
7469 <p
>The list of packages being installed are the ones needed by
7470 rpi-update to make the image bootable on the Raspberry Pi, with the
7471 exception of netbase, which is needed by debootstrap to find
7472 /etc/hosts with the minbase variant. I really wish there was a way to
7473 set up an Raspberry Pi using only packages in the Debian archive, but
7474 that is not possible as far as I know, because it boots from the GPU
7475 using a non-free binary blob.
</p
>
7477 <p
>The build host need debootstrap, kpartx and qemu-user-static and
7478 probably a few others installed. I have not checked the complete
7479 build dependency list.
</p
>
7481 <p
>The resulting image will not use the hardware floating point unit
7482 on the Raspberry PI, because the armel architecture in Debian is not
7483 optimized for that use. So the images created will be a bit slower
7484 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
7489 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
7490 <link>https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</link>
7491 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</guid>
7492 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
7493 <description><p
>The last few days I came across a few good causes that should get
7494 wider attention. I recommend signing and donating to each one of
7497 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
7498 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
7499 Women program which is a Google Summer of Code like initiative to get
7500 more women involved in free software. One debian sponsor has offered
7501 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
7502 earmarked
</a
> for this initiative. I donated a few minutes ago, and
7503 hope you will to. :)
</p
>
7505 <p
>And the Electronic Frontier Foundation just announced plans to
7506 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
7507 documentaries about the excessive spying
</a
> on every Internet user that
7508 take place these days, and their need to fund the work. I
've already
7509 donated. Are you next?
</p
>
7511 <p
>For my Norwegian audience, the organisation Studentenes og
7512 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7513 statement under the heading
7514 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
7515 Access
</a
> for those of us asking for more focus on open access in the
7516 Norwegian government. So far
499 signatures. I hope you will sign it
7522 <title>Videos about the Freedombox project - for inspiration and learning
</title>
7523 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
7524 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
7525 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
7526 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
7527 project
</a
> have been going on for a while, and have presented the
7528 vision, ideas and solution several places. Here is a little
7529 collection of videos of talks and presentation of the project.
</p
>
7533 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
7534 2,
5 minute marketing film
</a
> (Youtube)
</li
>
7536 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
7537 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
7539 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
7540 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7541 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
7542 (Youtube)
</li
>
7544 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
7545 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
7547 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
7548 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
7550 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
7551 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7552 York City in
2012</a
> (Youtube)
</li
>
7554 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
7555 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
7556 (Youtube)
</li
>
7558 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
7559 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
7561 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
7562 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
7564 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
7565 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7566 2013</a
> (Youtube)
</li
>
7570 <p
>A larger list is available from
7571 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
7572 Freedombox Wiki
</a
>.
</p
>
7574 <p
>On other news, I am happy to report that Freedombox based on Debian
7575 Jessie is coming along quite well, and soon both Owncloud and using
7576 Tor should be available for testers of the Freedombox solution. :) In
7577 a few weeks I hope everything needed to test it is included in Debian.
7578 The withsqlite package is already in Debian, and the plinth package is
7579 pending in NEW. The third and vital part of that puzzle is the
7580 metapackage/setup framework, which is still pending an upload. Join
7581 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
7582 (#freedombox on irc.debian.org)
</a
> and
7583 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7584 mailing list
</a
> if you want to help make this vision come true.
</p
>
7589 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
7590 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
7591 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
7592 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
7593 <description><p
>I was introduced to the
7594 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
7595 in
2010, when Eben Moglen presented his vision about serving the need
7596 of non-technical people to keep their personal information private and
7597 within the legal protection of their own homes. The idea is to give
7598 people back the power over their network and machines, and return
7599 Internet back to its intended peer-to-peer architecture. Instead of
7600 depending on a central service, the Freedombox will give everyone
7601 control over their own basic infrastructure.
</p
>
7603 <p
>I
've intended to join the effort since then, but other tasks have
7604 taken priority. But this summers nasty news about the misuse of trust
7605 and privilege exercised by the
"western
" intelligence gathering
7606 communities increased my eagerness to contribute to a point where I
7607 actually started working on the project a while back.
</p
>
7609 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
7610 Debian initiative
</a
> based on the vision from Eben Moglen, is to
7611 create a simple and cheap Debian based appliance that anyone can hook
7612 up in their home and get access to secure and private services and
7613 communication. The initial deployment platform have been the
7614 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
7615 which is a piece of hardware I do not own. So to be able to test what
7616 the current Freedombox setup look like, I had to come up with a way to install
7617 it on some hardware I do have access to. I have rewritten the
7618 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
7619 image build framework to use .deb packages instead of only copying
7620 setup into the boot images, and thanks to this rewrite I am able to
7621 set up any machine supported by Debian Wheezy as a Freedombox, using
7622 the previously mentioned deb (and a few support debs for packages
7623 missing in Debian).
</p
>
7625 <p
>The current Freedombox setup consist of a set of bootstrapping
7627 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
7628 and a administrative web interface
7629 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
7630 withsqlite), as well as a privacy enhancing proxy based on
7631 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
7632 (freedombox-privoxy). There is also a web/javascript based XMPP
7633 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
7634 trying (unsuccessfully so far) to talk to the XMPP server
7635 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
7636 web interface is pluggable, and the goal is to use it to enable OpenID
7637 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7638 this is really working yet, see
7639 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
7640 project TODO
</a
> for links to GIT repositories. Most of the code is
7641 on github at the moment. The HTTP proxy is operational out of the
7642 box, and the admin web interface can be used to add/remove plinth
7643 users. I
've not been able to do anything else with it so far, but
7644 know there are several branches spread around github and other places
7645 with lots of half baked features.
</p
>
7647 <p
>Anyway, if you want to have a look at the current state, the
7648 following recipes should work to give you a test machine to poke
7651 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
7655 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
7656 <li
>Boot from it, either as CD or USB stick.
</li
>
7657 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
7658 to the Debian installer:
<p
>
7659 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
7661 <li
>Answer the few language/region/password questions and pick disk to
7662 install on.
</li
>
7664 <li
>When the installation is finished and the machine have rebooted a
7665 few times, your Freedombox is ready for testing.
</li
>
7669 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
7673 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
7674 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
7675 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
7677 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
7678 </pre
></li
>
7679 <li
><p
>Run this as root:
</p
>
7681 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7684 apt-get install freedombox-setup
7685 /usr/lib/freedombox/setup
7686 </pre
></li
>
7687 <li
>Reboot into your freshly created Freedombox.
</li
>
7691 <p
>You can test it on other architectures too, but because the
7692 freedombox-privoxy package is binary, it will only work as intended on
7693 the architectures where I have had time to build the binary and put it
7694 in my APT repository. But do not let this stop you. It is only a
7695 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
7697 <p
>Note that by default Freedombox is a DHCP server on the
7698 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
7699 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
7700 disable
</tt
>" as root.
</p
>
7702 <p
>Please let me know if this works for you, or if you have any
7703 problems. We gather on the IRC channel
7704 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
7705 irc.debian.org and the
7706 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
7707 mailing list
</a
>.
</p
>
7709 <p
>Once you get your freedombox operational, you can visit
7710 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
7711 welcome screen (dead end - do not be surprised if you are unable to
7712 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
7713 to look at the rest of plinth. The default user is
'admin
' and the
7714 default password is
'secret
'.
</p
>
7719 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
7720 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
7721 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
7722 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
7723 <description><p
>Earlier, I reported about
7724 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
7725 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
7726 told by IBM that the original disk should be thrown away. And as
7727 there no longer was a problem if I bricked the firmware, I decided
7728 today to try to install Intel firmware to replace the Lenovo firmware
7729 currently on the disk.
</p
>
7731 <p
>I searched the Intel site for firmware, and found
7732 <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
>
7733 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7734 according to the site should contain the latest firmware for SSD
7735 disks. I inserted the broken disk in one of my spare laptops and
7736 booted the ISO from a USB stick. The disk was recognized, but the
7737 program claimed the newest firmware already were installed and refused
7738 to insert any Intel firmware. So no change, and the disk is still
7739 unable to handle write load. :( I guess the only way to get them
7740 working would be if Lenovo releases new firmware. No idea how likely
7741 that is. Anyway, just blogging about this test for completeness. I
7742 got a working Samsung disk, and see no point in spending more time on
7743 the broken disks.
</p
>
7748 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
7749 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
7750 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
7751 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
7752 <description><p
>Today I switched to
7753 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
7754 new laptop
</a
>. I
've previously written about the problems I had with
7755 my new Thinkpad X230, which was delivered with an
7756 <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
7757 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
7758 sustained writes. My hardware supplier have been very forthcoming in
7759 trying to find a solution, and after first trying with another
7760 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
7761 disk instead to fix it once and for all. The Samsung disk survived
7762 the installation of Debian with encrypted disks (filling the disk with
7763 random data during installation killed the first two), and I thus
7764 decided to trust it with my data. I have installed it as a Debian Edu
7765 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7766 server at home using Kerberos and LDAP, and will use it as my work
7767 station from now on.
</p
>
7769 <p
>As this is a solid state disk with no moving parts, I believe the
7770 Debian Wheezy default installation need to be tuned a bit to increase
7771 performance and increase life time of the disk. The Linux kernel and
7772 user space applications do not yet adjust automatically to such
7773 environment. To make it easier for my self, I created a draft Debian
7774 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
7775 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
7776 for the ssd-setup package
</a
> is available from collab-maint, and it
7777 is set up to adjust the setup of the machine by just installing the
7778 package. If there is any non-SSD disk in the machine, the package
7779 will refuse to install, as I did not try to write any logic to sort
7780 file systems in SSD and non-SSD file systems.
</p
>
7782 <p
>I consider the package a draft, as I am a bit unsure how to best
7783 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7784 where I set up the machine with one large encrypted partition (in
7785 addition to /boot), put LVM on top of this and set up partitions on
7786 top of this again. See the README file in the package source for the
7787 references I used to pick the settings. At the moment these
7788 parameters are tuned:
</p
>
7792 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
7793 (adding discard to /etc/crypttab)
</li
>
7795 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
7796 this case a cryptsetup partition) by changing issue_discards from
7797 0 to
1 in /etc/lvm/lvm.conf.
</li
>
7799 <li
>Set relatime as a file system option for ext3 and ext4 file
7802 <li
>Tell swap to use TRIM commands by adding
'discard
' to
7803 /etc/fstab.
</li
>
7805 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
7807 <li
>Run fstrim on every ext3 and ext4 file system every night (from
7808 cron.daily).
</li
>
7810 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
7811 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
7815 <p
>During installation, I cancelled the part where the installer fill
7816 the disk with random data, as this would kill the SSD performance for
7817 little gain. My goal with the encrypted file system is to ensure
7818 those stealing my laptop end up with a brick and not a working
7819 computer. I have no hope in keeping the really resourceful people
7820 from getting the data on the disk (see
7821 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
7822 Thus I concluded that adding the discard option to crypttab is the
7823 right thing to do.
</p
>
7825 <p
>I considered using the noop I/O scheduler, as several recommended
7826 it for SSD, but others recommended deadline and a benchmark I found
7827 indicated that deadline might be better for interactive use.
</p
>
7829 <p
>I also considered using the
'discard
' file system option for ext3
7830 and ext4, but read that it would give a performance hit ever time a
7831 file is removed, and thought it best to that that slowdown once a day
7832 instead of during my work.
</p
>
7834 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7835 this is already done by Debian Edu.
</p
>
7837 <p
>I have not yet started on the user space tuning. I expect
7838 iceweasel need some tuning, and perhaps other applications too, but
7839 have not yet had time to investigate those parts.
</p
>
7841 <p
>The package should work on Ubuntu too, but I have not yet tested it
7844 <p
>As for the answer to the question in the title of this blog post,
7845 as far as I know, the only solution I know about is to replace the
7846 disk. It might be possible to flash it with Intel firmware instead of
7847 the Lenovo firmware. But I have not tried and did not want to do so
7848 without approval from Lenovo as I wanted to keep the warranty on the
7849 disk until a solution was found and they wanted the broken disks
7855 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
7856 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
7857 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</guid>
7858 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
7859 <description><p
>A few days ago, I wrote about
7860 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
7861 problems I experienced with my new X230 and its SSD disk
</a
>, which
7862 was dying during installation because it is unable to cope with
7863 sustained write. My supplier is in contact with
7864 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
7865 replacement disk to try to fix the problem. They decided to send an
7866 identical model, so my hopes for a permanent fix was slim.
</p
>
7868 <p
>Anyway, today I got the replacement disk and tried to install
7869 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7870 same firmware version as the original. This time my hope raised
7871 slightly as the installation progressed, as the original disk used to
7872 die after
4-
7% of the disk was written to, while this time it kept
7873 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
7874 died again and I was back on square one. I still do not have a new
7875 laptop with a disk I can trust. I can not live with a disk that might
7876 lock up when I download a new
7877 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
7878 other large files. I look forward to hearing from my supplier with
7879 the next proposal from Lenovo.
</p
>
7881 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
7882 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7883 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7884 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
7885 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7886 P/N
45N8295, P0C38732.
</p
>
7888 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
7889 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
7890 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7891 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
7892 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7893 P/N
45N8295, P0C38732.
</p
>
7895 <p
>The only difference is in the first number (serial number?), ISN,
7896 SA, date and WNPP values. Mentioning all the details here in case
7897 someone is able to use the information to find a way to identify the
7898 failing disk among working ones (if any such working disk actually
7904 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
7905 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
7906 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
7907 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
7908 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
7909 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7910 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
7911 member assosiation NUUG
</a
> and
7912 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
7913 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
7914 Bitraf
</a
>.
</p
>
7916 <p
>It starts
10:
00 and continue until late evening. Everyone is
7917 welcome, and there is no fee to participate. There is on the other
7918 hand limited space, and only room for
30 people. Please put your name
7919 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
7920 wiki page
</a
> if you plan to join us.
</p
>
7925 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
7926 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
7927 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
7928 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
7929 <description><p
>Half a year ago, I reported that I had to find a
7930 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
7931 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
7932 time to spend on it, and it took a while to find a model I believe
7933 will do the job, but two days ago the replacement finally arrived. I
7935 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
7936 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7937 a roaming workstation, and it seemed to work flawlessly. But my
7938 second installation with encrypted disk was not as successful. More
7939 on that below.
</p
>
7941 <p
>I had a hard time trying to track down a good laptop, as my most
7942 important requirements (robust and with a good keyboard) are never
7943 listed in the feature list. But I did get good help from the search
7944 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7945 allowed me to limit the list of interesting laptops based on my other
7946 requirements. A bit surprising that SSD disk are not disks according
7947 to that search interface, so I had to drop specifying the number of
7948 disks from my search parameters. I also asked around among friends to
7949 get their impression on keyboards and robustness.
</p
>
7951 <p
>So the new laptop arrived, and it is quite a lot wider than the
7952 X41. I am not quite convinced about the keyboard, as it is
7953 significantly wider than my old keyboard, and I have to stretch my
7954 hand a lot more to reach the edges. But the key response is fairly
7955 good and the individual key shape is fairly easy to handle, so I hope
7956 I will get used to it. My old X40 was starting to fail, and I really
7957 needed a new laptop now. :)
</p
>
7959 <p
>Turning off the touch pad was simple. All it took was a quick
7960 visit to the BIOS during boot it disable it.
</p
>
7962 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
7963 lock up during load. And this happen when installing Debian Wheezy
7964 with encrypted disk, while the disk is being filled with random data.
7965 I also tested to install Ubuntu Raring, and it happen there too if I
7966 reenable the code to fill the disk with random data (it is disabled by
7967 default in Ubuntu). And the bug with is already known. It was
7968 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
7969 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
7970 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7971 kernel developers as
7972 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
7973 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
7974 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7975 Lenovo forums, both for
7976 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
7977 2012-
11-
10</a
> and for
7978 <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
7979 03-
20-
2013</a
>. The problem do not only affect installation. The
7980 reports state that the disk lock up during use if many writes are done
7981 on the disk, so it is much no use to work around the installation
7982 problem and end up with a computer that can lock up at any moment.
7984 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
7985 available
</a
> that will lock up the hard drive after running a few
7986 minutes by writing to a file.
</p
>
7988 <p
>I
've contacted my supplier and asked how to handle this, and after
7989 contacting PCHELP Norway (request
01D1FDP) which handle support
7990 requests for Lenovo, his first suggestion was to upgrade the disk
7991 firmware. Unfortunately there is no newer firmware available from
7992 Lenovo, as my disk already have the most recent one (version LF1i). I
7993 hope to hear more from him today and hope the problem can be
7999 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
8000 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
8001 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
8002 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
8003 <description><p
>Half a year ago, I reported that I had to find a replacement for my
8004 trusty old Thinkpad X41. Unfortunately I did not have much time to
8005 spend on it, but today the replacement finally arrived. I ended up
8006 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
8007 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
8008 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8009 this, it is installing what I hope will be a more final installation,
8010 with a encrypted hard drive to ensure any dope head stealing it end up
8011 with an expencive door stop.
</p
>
8013 <p
>I had a hard time trying to track down a good laptop, as my most
8014 important requirements (robust and with a good keyboard) are never
8015 listed in the feature list. But I did get good help from the search
8016 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
8017 allowed me to limit the list of interesting laptops based on my other
8018 requirements. A bit surprising that SSD disk are not disks, so I had
8019 to drop number of disks from my search parameters.
</p
>
8021 <p
>I am not quite convinced about the keyboard, as it is significantly
8022 wider than my old keyboard, and I have to stretch my hand a lot more
8023 to reach the edges. But the key response is fairly good and the
8024 individual key shape is fairly easy to handle, so I hope I will get
8025 used to it. My old X40 was starting to fail, and I really needed a
8026 new laptop now. :)
</p
>
8028 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
8033 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
8034 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
8035 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
8036 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
8037 <description><p
>It annoys me when the computer fail to do automatically what it is
8038 perfectly capable of, and I have to do it manually to get things
8039 working. One such task is to find out what firmware packages are
8040 needed to get the hardware on my computer working. Most often this
8041 affect the wifi card, but some times it even affect the RAID
8042 controller or the ethernet card. Today I pushed version
0.4 of the
8043 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
8044 including a new script isenkram-autoinstall-firmware handling the
8045 process of asking all the loaded kernel modules what firmware files
8046 they want, find debian packages providing these files and install the
8047 debian packages. Here is a test run on my laptop:
</p
>
8049 <p
><pre
>
8050 # isenkram-autoinstall-firmware
8051 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8052 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8053 info: locating packages with the requested firmware files
8054 info: Updating APT sources after adding non-free APT source
8055 info: trying to install firmware-ipw2x00
8058 Preconfiguring packages ...
8059 Selecting previously deselected package firmware-ipw2x00.
8060 (Reading database ...
259727 files and directories currently installed.)
8061 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8062 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
8064 </pre
></p
>
8066 <p
>When all the requested firmware is present, a simple message is
8067 printed instead:
</p
>
8069 <p
><pre
>
8070 # isenkram-autoinstall-firmware
8071 info: did not find any firmware files requested by loaded kernel modules. exiting
8073 </pre
></p
>
8075 <p
>It could use some polish, but it is already working well and saving
8076 me some time when setting up new machines. :)
</p
>
8078 <p
>So, how does it work? It look at the set of currently loaded
8079 kernel modules, and look up each one of them using modinfo, to find
8080 the firmware files listed in the module meta-information. Next, it
8081 download the Contents file from a nearby APT mirror, and search for
8082 the firmware files in this file to locate the package with the
8083 requested firmware file. If the package is in the non-free section, a
8084 non-free APT source is added and the package is installed using
8085 <tt
>apt-get install
</tt
>. The end result is a slightly better working
8088 <p
>I hope someone find time to implement a more polished version of
8089 this script as part of the hw-detect debian-installer module, to
8090 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
8091 #
655507</a
>. There really is no need to insert USB sticks with
8092 firmware during a PXE install when the packages already are available
8093 from the nearby Debian mirror.
</p
>
8098 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
8099 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
8100 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
8101 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
8102 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8103 the screen just turn black when Linux boot, either during installation
8104 or on first boot from the hard disk. I
've seen it once in a while the
8105 last few years, but only recently understood the cause. I
've seen it
8106 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8107 The reason seem to be in the wiring of some laptops. The system to
8108 control the screen background light is inverted, so when Linux try to
8109 turn the brightness fully on, it end up turning it off instead. I do
8110 not know which Linux drivers are affected, but this post is about the
8111 i915 driver used by the
8112 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8113 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
8115 <p
>The problem can be worked around two ways. Either by adding
8116 i915.invert_brightness=
1 as a kernel option, or by adding a file in
8117 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
8118 option when it load the i915 kernel module. On Debian and Ubuntu, it
8119 can be done by running these commands as root:
</p
>
8122 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
8123 update-initramfs -u -k all
8126 <p
>Since March
2012 there is
8127 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
8128 mechanism in the Linux kernel
</a
> to tell the i915 driver which
8129 hardware have this problem, and get the driver to invert the
8130 brightness setting automatically. To use it, one need to add a row in
8131 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
8132 intel_quirks array
</a
> in the driver source
8133 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
8134 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
8135 number (vendor number
8086 is assumed) and subdevice vendor and device
8138 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
8139 -vvnn
</tt
> for the video card in question:
</p
>
8141 <p
><pre
>
8142 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
8143 3rd Gen Core processor Graphics Controller [
8086:
0156] \
8144 (rev
09) (prog-if
00 [VGA controller])
8145 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
8146 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8147 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8148 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
8149 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
8151 Interrupt: pin A routed to IRQ
42
8152 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
8153 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
8154 Region
4: I/O ports at
4000 [size=
64]
8155 Expansion ROM at
<unassigned
> [disabled]
8156 Capabilities:
<access denied
>
8157 Kernel driver in use: i915
8158 </pre
></p
>
8160 <p
>The resulting intel_quirks entry would then look like this:
</p
>
8162 <p
><pre
>
8163 struct intel_quirk intel_quirks[] = {
8165 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8166 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
8169 </pre
></p
>
8171 <p
>According to the kernel module instructions (as seen using
8172 <tt
>modinfo i915
</tt
>), information about hardware needing the
8173 invert_brightness flag should be sent to the
8174 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
8175 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
8176 developers. But my email about the laptop sent
2013-
06-
03 have not
8178 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
8179 web archive for the mailing list
</a
>, so I suspect they do not accept
8180 emails from non-subscribers. Because of this, I sent my patch also to
8181 the Debian bug tracking system instead as
8182 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
8183 sure the patch is not lost.
</p
>
8185 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
8186 with this problem working properly with Linux. If you use Gnome, your
8187 worries should be over at this point. But if you use KDE, there is
8188 something in KDE ignoring the invert_brightness setting and turning on
8189 the screen during login. I
've reported it to Debian as
8190 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
8191 have no idea yet how to figure out exactly what subsystem is doing
8192 this. Perhaps you can help? Perhaps you know what the Gnome
8193 developers did to handle this, and this can give a clue to the KDE
8194 developers? Or you know where in KDE the screen brightness is changed
8195 during login? If so, please update the BTS report (or get in touch if
8196 you do not know how to update BTS).
</p
>
8198 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
8199 acpi_backlight=vendor, to disable ACPI backlight support completely,
8200 as the ACPI information on the machine is trash and it is better to
8201 leave it to the intel video driver to control the screen
8202 backlight.
</p
>
8207 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
8208 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
8209 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</guid>
8210 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
8211 <description><p
>Two days ago, I asked
8212 <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
8213 I could install Linux on a Packard Bell EasyNote LV computer
8214 preinstalled with Windows
8</a
>. I found a solution, but am horrified
8215 with the obstacles put in the way of Linux users on a laptop with UEFI
8216 and Windows
8.
</p
>
8218 <p
>I never found out if the cause of my problems were the use of UEFI
8219 secure booting or fast boot. I suspect fast boot was the problem,
8220 causing the firmware to boot directly from HD without considering any
8221 key presses and alternative devices, but do not know UEFI settings
8222 enough to tell.
</p
>
8224 <p
>There is no way to install Linux on the machine in question without
8225 opening the box and disconnecting the hard drive! This is as far as I
8226 can tell, the only way to get access to the firmware setup menu
8227 without accepting the Windows
8 license agreement. I am told (and
8228 found description on how to) that it is possible to configure the
8229 firmware setup once booted into Windows
8. But as I believe the terms
8230 of that agreement are completely unacceptable, accepting the license
8231 was never an alternative. I do not enter agreements I do not intend
8232 to follow.
</p
>
8234 <p
>I feared I had to return the laptops and ask for a refund, and
8235 waste many hours on this, but luckily there was a way to get it to
8236 work. But I would not recommend it to anyone planning to run Linux on
8237 it, and I have become sceptical to Windows
8 certified laptops. Is
8238 this the way Linux will be forced out of the market place, by making
8239 it close to impossible for
"normal
" users to install Linux without
8240 accepting the Microsoft Windows license terms? Or at least not
8241 without risking to loose the warranty?
</p
>
8243 <p
>I
've updated the
8244 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
8245 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
8246 do not have to struggle as much as I did to get Linux into the
8249 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8250 Michael Tokarev and others for feedback and ideas.
</p
>
8255 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
8256 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
8257 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</guid>
8258 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
8259 <description><p
>I
've run into quite a problem the last few days. I bought three
8260 new laptops for my parents and a few others. I bought Packard Bell
8261 Easynote LV to run Kubuntu on and use as their home computer. But I
8262 am completely unable to figure out how to install Linux on it. The
8263 computer is preinstalled with Windows
8, and I suspect it uses UEFI
8264 instead of a BIOS to boot.
</p
>
8266 <p
>The problem is that I am unable to get it to PXE boot, and unable
8267 to get it to boot the Linux installer from my USB stick. I have yet
8268 to try the DVD install, and still hope it will work. when I turn on
8269 the computer, there is no information on what buttons to press to get
8270 the normal boot menu. I expect to get some boot menu to select PXE or
8271 USB stick booting. When booting, it first ask for the language to
8272 use, then for some regional settings, and finally if I will accept the
8273 Windows
8 terms of use. As these terms are completely unacceptable to
8274 me, I have no other choice but to turn off the computer and try again
8275 to get it to boot the Linux installer.
</p
>
8277 <p
>I have gathered my findings so far on a Linlap page about the
8278 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8279 EasyNote LV
</a
> model. If you have any idea how to get Linux
8280 installed on this machine, please get in touch or update that wiki
8281 page. If I can
't find a way to install Linux, I will have to return
8282 the laptop to the seller and find another machine for my parents.
</p
>
8284 <p
>I wonder, is this the way Linux will be forced out of the market
8285 using UEFI and
"secure boot
" by making it impossible to install Linux
8286 on new Laptops?
</p
>
8291 <title>How to transform a Debian based system to a Debian Edu installation
</title>
8292 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
8293 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
8294 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
8295 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
8296 an operating system based on Debian intended for use in schools. It
8297 contain a turn-key solution for the computer network provided to
8298 pupils in the primary schools. It provide both the central server,
8299 network boot servers and desktop environments with heaps of
8300 educational software. The project was founded almost
12 years ago,
8301 2001-
07-
02. If you want to support the project, which is in need for
8302 cash to fund developer gatherings and other project related activity,
8303 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
8304 donate some money
</a
>.
8306 <p
>A topic that come up again and again on the Debian Edu mailing
8307 lists and elsewhere, is the question on how to transform a Debian or
8308 Ubuntu installation into a Debian Edu installation. It isn
't very
8309 hard, and last week I wrote a script to replicate the steps done by
8310 the Debian Edu installer.
</p
>
8312 <p
>The script,
8313 <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/
>
8314 in the debian-edu-config package, will go through these six steps and
8315 transform an existing Debian Wheezy or Ubuntu (untested) installation
8316 into a Debian Edu Workstation:
</p
>
8320 <li
>Add skolelinux related APT sources.
</li
>
8321 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
8322 <li
>Install debian-edu-install to load preseeding values and pull in
8323 our configuration.
</li
>
8324 <li
>Preseed debconf database with profile setup in
8325 /etc/debian-edu/config, and run tasksel to install packages
8326 according to the profile specified in the config above,
8327 overriding some of the Debian automation machinery.
</li
>
8328 <li
>Run debian-edu-cfengine-D installation to configure everything
8329 that could not be done using preseeding.
</li
>
8330 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
8334 <p
>There are some steps in the Debian Edu installation that can not be
8335 replicated like this. Disk partitioning and LVM setup, for example.
8336 So this script just assume there is enough disk space to install all
8337 the needed packages.
</p
>
8339 <p
>The script was created to help a Debian Edu student working on
8340 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
8341 Debian Edu client, and using it he can take the existing
8342 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
8343 transform it into a fully functioning Debian Edu Workstation (or
8344 Roaming Workstation, or whatever :).
</p
>
8346 <p
>The default setting in the script is to create a KDE Workstation.
8347 If a LXDE based Roaming workstation is wanted instead, modify the
8348 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
8350 <p
><pre
>
8351 PROFILE=
"Roaming-Workstation
"
8352 DESKTOP=
"lxde
"
8353 </pre
></p
>
8355 <p
>The script could even become useful to set up Debian Edu servers in
8356 the cloud, by starting with a virtual Debian installation at some
8357 virtual hosting service and setting up all the services on first
8363 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
8364 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
8365 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
8366 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
8367 <description><P
>In January,
8368 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
8369 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
8370 channel #debian-lego
</a
>, for those of us in the Debian and Linux
8371 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
8372 marvellous construction system from Denmark. We also created
8373 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
8374 a place to take notes and write down our plans and hopes. And several
8375 people showed up to help. I was very happy to see the effect of my
8376 call. Since the small start, we have a debtags tag
8377 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
8378 tag for LEGO related packages, and now count
10 packages related to
8379 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
8381 <p
><table
>
8382 <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
>
8383 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
8384 <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
>
8385 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
8386 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
8387 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
8388 <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
>
8389 <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
>
8390 <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
>
8391 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
8392 </table
></p
>
8394 <p
>Some of these are available in Wheezy, and all but one are
8395 currently available in Jessie/testing. leocad is so far only
8396 available in experimental.
</p
>
8398 <p
>If you care about LEGO in Debian, please join us on IRC and help
8399 adding the rest of the great free software tools available on Linux
8400 for LEGO designers.
</p
>
8405 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
8406 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
8407 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
8408 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
8409 <description><p
>When I woke up this morning, I was very happy to see that the
8410 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
8411 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
8412 Debian release, and I expect to move my machines at home over to it fairly
8415 <p
>The new debian release contain heaps of new stuff, and one program
8416 in particular make me very happy to see included. The
8417 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
8418 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
8419 included for the first time. Alongside similar programs like
8420 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
8421 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
8422 it allow for visual programming where syntax errors can not happen,
8423 and a friendly programming environment for learning to control the
8424 computer. Scratch will also be included in the next release of Debian
8427 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
8428 Edu/Skolelinux release too. The
8429 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
8430 alpha release
</a
> went out last week, and the next should soon
8436 <title>Isenkram
0.2 finally in the Debian archive
</title>
8437 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
8438 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
8439 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
8440 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
8441 package
</a
> finally made it into the archive, after lingering in NEW
8442 for many months. I uploaded it to the Debian experimental suite
8443 2013-
01-
27, and today it was accepted into the archive.
</p
>
8445 <p
>Isenkram is a system for suggesting to users what packages to
8446 install to work with a pluggable hardware device. The suggestion pop
8447 up when the device is plugged in. For example if a Lego Mindstorm NXT
8448 is inserted, it will suggest to install the program needed to program
8449 the NXT controller. Give it a go, and report bugs and suggestions to
8455 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
8456 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
8457 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
8458 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
8459 <description><p
>My
8460 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
8461 bitcoin related blog post
</a
> mentioned that the new
8462 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
8463 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8464 2013-
01-
19, and have been available in unstable since then. It was
8465 automatically copied to Ubuntu, and is available in their Raring
8466 version too.
</p
>
8468 <p
>But there is a strange problem with the build that block this new
8469 version from being available on the i386 and kfreebsd-i386
8470 architectures. For some strange reason, the autobuilders in Debian
8471 for these architectures fail to run the test suite on these
8472 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
8473 We are so far unable to reproduce it when building it manually, and
8474 no-one have been able to propose a fix. If you got an idea what is
8475 failing, please let us know via the BTS.
</p
>
8477 <p
>One feature that is annoying me with of the bitcoin client, because
8478 I often run low on disk space, is the fact that the client will exit
8479 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
8480 #
696715</a
>). So make sure you have enough disk space when you run
8483 <p
>As usual, if you use bitcoin and want to show your support of my
8484 activities, please send Bitcoin donations to my address
8485 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8490 <title>Welcome to the world, Isenkram!
</title>
8491 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
8492 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
8493 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
8494 <description><p
>Yesterday, I
8495 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
8496 for testers
</a
> for my prototype for making Debian better at handling
8497 pluggable hardware devices, which I
8498 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
8499 out to create
</a
> earlier this month. Several valuable testers showed
8500 up, and caused me to really want to to open up the development to more
8501 people. But before I did this, I want to come up with a sensible name
8502 for this project. Today I finally decided on a new name, and I have
8503 renamed the project from hw-support-handler to this new name. In the
8504 process, I moved the source to git and made it available as a
8505 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
8506 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
8507 To fetch and build the latest version of the source, use
</p
>
8510 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8511 cd isenkram
&& git-buildpackage -us -uc
8514 <p
>I have not yet adjusted all files to use the new name yet. If you
8515 want to hack on the source or improve the package, please go ahead.
8516 But please talk to me first on IRC or via email before you do major
8517 changes, to make sure we do not step on each others toes. :)
</p
>
8519 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
8520 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8521 stuff, in other words. I
've been told it is the Norwegian variant of
8522 the German word eisenkram, for those that are familiar with that
8525 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
8526 instructions, to avoid confusing people with an error from the signing
8529 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
8530 clone argument to avoid the need for authentication.
</p
>
8535 <title>First prototype ready making hardware easier to use in Debian
</title>
8536 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
8537 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
8538 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
8539 <description><p
>Early this month I set out to try to
8540 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
8541 the Debian support for pluggable hardware devices
</a
>. Now my
8542 prototype is working, and it is ready for a larger audience. To test
8544 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
8545 from the Debian Edu subversion repository
</a
>, build and install the
8546 package. You might have to log out and in again activate the
8547 autostart script.
</p
>
8549 <p
>The design is simple:
</p
>
8553 <li
>Add desktop entry in /usr/share/autostart/ causing a program
8554 hw-support-handlerd to start when the user log in.
</li
>
8556 <li
>This program listen for kernel events about new hardware (directly
8557 from the kernel like udev does), not using HAL dbus events as I
8558 initially did.
</li
>
8560 <li
>When new hardware is inserted, look up the hardware modalias in
8561 the APT database, a database
8562 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
8563 via HTTP
</a
> and a database available as part of the package.
</li
>
8565 <li
>If a package is mapped to the hardware in question, the package
8566 isn
't installed yet and this is the first time the hardware was
8567 plugged in, show a desktop notification suggesting to install the
8568 package or packages.
</li
>
8570 <li
>If the user click on the
'install package now
' button, ask
8571 aptdaemon via the PackageKit API to install the requrired package.
</li
>
8573 <li
>aptdaemon ask for root password or sudo password, and install the
8574 package while showing progress information in a window.
</li
>
8578 <p
>I still need to come up with a better name for the system. Here
8579 are some screen shots showing the prototype in action. First the
8580 notification, then the password request, and finally the request to
8581 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
8583 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
8584 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
8585 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
8586 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
8587 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
8589 <p
>The prototype still need to be improved with longer timeouts, but
8590 is already useful. The database of hardware to package mappings also
8591 need more work. It is currently compatible with the Ubuntu way of
8592 storing such information in the package control file, but could be
8593 changed to use other formats instead or in addition to the current
8594 method. I
've dropped the use of discover for this mapping, as the
8595 modalias approach is more flexible and easier to use on Linux as long
8596 as the Linux kernel expose its modalias strings directly.
</p
>
8598 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
8599 here is the command required to check out and build the source: Use
8600 '<tt
>svn checkout
8601 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8602 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
8603 devscripts package.
</p
>
8605 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
8606 renamed to Isenkram and the source moved from the Debian Edu
8607 subversion repository to a Debian collab-maint git repository. See
8608 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
8609 instructions
</a
> for details.
</p
>
8614 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
8615 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
8616 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
8617 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
8618 <description><p
>This Christmas my trusty old laptop died. It died quietly and
8619 suddenly in bed. With a quiet whimper, it went completely quiet and
8620 black. The power button was no longer able to turn it on. It was a
8621 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8622 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8623 Compaq I had before that. Now I need to find a replacement. To keep
8624 going during Christmas, I moved the one year old SSD disk to my old
8625 X40 where it fitted (only one I had left that could use it), but it is
8626 not a durable solution.
8628 <p
>My laptop needs are fairly modest. This is my wishlist from when I
8629 got a new one more than
10 years ago. It still holds true.:)
</p
>
8633 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
8634 than A4).
</li
>
8635 <li
>Robust, it will be in my backpack every day.
</li
>
8636 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
8637 <li
>Long battery life time. Preferable a week.
</li
>
8638 <li
>Internal WIFI network card.
</li
>
8639 <li
>Internal Twisted Pair network card.
</li
>
8640 <li
>Some USB slots (
2-
3 is plenty)
</li
>
8641 <li
>Good keyboard - similar to the Thinkpad.
</li
>
8642 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
8644 <li
>Hardware supported by Debian Stable, ie the default kernel and
8645 X.org packages.
</li
>
8646 <li
>Quiet, preferably fan free (or at least not using the fan most of
8651 <p
>You will notice that there are no RAM and CPU requirements in the
8652 list. The reason is simply that the specifications on laptops the
8653 last
10-
15 years have been sufficient for my needs, and I have to look
8654 at other features to choose my laptop. But are there still made as
8655 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8656 robust, and Thinkpads seem to be heading in the wrong direction since
8657 Lenovo took over. But I
've been told that X220 and X1 Carbon might
8658 still be useful.
</p
>
8660 <p
>Perhaps I should rethink my needs, and look for a pad with an
8661 external keyboard? I
'll have to check the
8662 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
8663 well-supported laptops, or perhaps just buy one preinstalled from one
8664 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
8665 Pre-loaded site
</a
>.
</p
>
8670 <title>How to find a browser plugin supporting a given MIME type
</title>
8671 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
8672 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
8673 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
8674 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
8675 install to get support for a given MIME type. Thanks to
8676 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
8677 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
8678 Unfortunately, not very many packages provide the needed meta
8679 information, Anyway, here is a small script to look up all browser
8680 plugin packages announcing ther MIME support using this specification:
</p
>
8686 def pkgs_handling_mimetype(mimetype):
8691 version = pkg.candidate
8693 version = pkg.installed
8696 record = version.record
8697 if not record.has_key(
'Npp-MimeType
'):
8699 mime_types = record[
'Npp-MimeType
'].split(
',
')
8700 for t in mime_types:
8701 t = t.rstrip().strip()
8703 thepkgs.append(pkg.name)
8705 mimetype =
"audio/ogg
"
8706 if
1 < len(sys.argv):
8707 mimetype = sys.argv[
1]
8708 print
"Browser plugin packages supporting %s:
" % mimetype
8709 for pkg in pkgs_handling_mimetype(mimetype):
8710 print
" %s
" %pkg
8713 <p
>It can be used like this to look up a given MIME type:
</p
>
8716 % ./apt-find-browserplug-for-mimetype
8717 Browser plugin packages supporting audio/ogg:
8719 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8720 Browser plugin packages supporting application/x-shockwave-flash:
8721 browser-plugin-gnash
8725 <p
>In Ubuntu this mechanism is combined with support in the browser
8726 itself to query for plugins and propose to install the needed
8727 packages. It would be great if Debian supported such feature too. Is
8728 anyone working on adding it?
</p
>
8730 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
8731 request for icweasel support for this feature is
8732 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
8733 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
8734 of manpower and wish for a different design is the reason thus feature
8735 is not yet in iceweasel from Debian.
</p
>
8740 <title>What is the most supported MIME type in Debian?
</title>
8741 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
8742 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
8743 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
8744 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
8745 proposal to add AppStream information to the Debian archive
</a
>, is a
8746 proposal to make it possible for a Desktop application to propose to
8747 the user some package to install to gain support for a given MIME
8748 type, font, library etc. that is currently missing. With such
8749 mechanism in place, it would be possible for the desktop to
8750 automatically propose and install leocad if some LDraw file is
8751 downloaded by the browser.
</p
>
8753 <p
>To get some idea about the current content of the archive, I decided
8754 to write a simple program to extract all .desktop files from the
8755 Debian archive and look up the claimed MIME support there. The result
8757 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
8758 site
</a
>. Using the collected information, it become possible to
8759 answer the question in the title. Here are the
20 most supported MIME
8760 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8761 The complete list is available from the link above.
</p
>
8763 <p
><strong
>Debian Stable:
</strong
></p
>
8767 ----- -----------------------
8783 18 application/x-ogg
8790 <p
><strong
>Debian Testing:
</strong
></p
>
8794 ----- -----------------------
8810 18 application/x-ogg
8817 <p
><strong
>Debian Unstable:
</strong
></p
>
8821 ----- -----------------------
8838 18 application/x-ogg
8844 <p
>I am told that PackageKit can provide an API to access the kind of
8845 information mentioned in DEP-
11. I have not yet had time to look at
8846 it, but hope the PackageKit people in Debian are on top of these
8849 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
8850 discovering a typo in my script.
</p
>
8855 <title>Using modalias info to find packages handling my hardware
</title>
8856 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
8857 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
8858 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
8859 <description><p
>Yesterday, I wrote about the
8860 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
8861 values provided by the Linux kernel
</a
> following my hope for
8862 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
8863 dongle support in Debian
</a
>. Using this knowledge, I have tested how
8864 modalias values attached to package names can be used to map packages
8865 to hardware. This allow the system to look up and suggest relevant
8866 packages when I plug in some new hardware into my machine, and replace
8867 discover and discover-data as the database used to map hardware to
8870 <p
>I create a modaliases file with entries like the following,
8871 containing package name, kernel module name (if relevant, otherwise
8872 the package name) and globs matching the relevant hardware
8875 <p
><blockquote
>
8876 Package: package-name
8877 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
8878 </blockquote
></p
>
8880 <p
>It is fairly trivial to write code to find the relevant packages
8881 for a given modalias value using this file.
</p
>
8883 <p
>An entry like this would suggest the video and picture application
8884 cheese for many USB web cameras (interface bus class
0E01):
</p
>
8886 <p
><blockquote
>
8888 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
8889 </blockquote
></p
>
8891 <p
>An entry like this would suggest the pcmciautils package when a
8892 CardBus bridge (bus class
0607) PCI device is present:
</p
>
8894 <p
><blockquote
>
8895 Package: pcmciautils
8896 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8897 </blockquote
></p
>
8899 <p
>An entry like this would suggest the package colorhug-client when
8900 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
8902 <p
><blockquote
>
8903 Package: colorhug-client
8904 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
8905 </blockquote
></p
>
8907 <p
>I believe the format is compatible with the format of the Packages
8908 file in the Debian archive. Ubuntu already uses their Packages file
8909 to store their mappings from packages to hardware.
</p
>
8911 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
8912 announce the hardware it support in a way my prototype understand.
8913 This allow those publishing packages in an APT source outside the
8914 Debian archive as well as those backporting packages to make sure the
8915 hardware mapping are included in the package meta information. I
've
8916 tested such header in the pymissile package, and its modalias mapping
8917 is working as it should with my prototype. It even made it to Ubuntu
8920 <p
>To test if it was possible to look up supported hardware using only
8921 the shell tools available in the Debian installer, I wrote a shell
8922 implementation of the lookup code. The idea is to create files for
8923 each modalias and let the shell do the matching. Please check out and
8925 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
8926 shell script. It run without any extra dependencies and fetch the
8927 hardware mappings from the Debian archive and the subversion
8928 repository where I currently work on my prototype.
</p
>
8930 <p
>When I use it on a machine with a yubikey inserted, it suggest to
8931 install yubikey-personalization:
</p
>
8933 <p
><blockquote
>
8934 % ./hw-support-lookup
8935 <br
>yubikey-personalization
8937 </blockquote
></p
>
8939 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8940 propose to install the pcmciautils package:
</p
>
8942 <p
><blockquote
>
8943 % ./hw-support-lookup
8944 <br
>pcmciautils
8946 </blockquote
></p
>
8948 <p
>If you know of any hardware-package mapping that should be added to
8949 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
8950 database
</a
>, please tell me about it.
</p
>
8952 <p
>It could be possible to generate several of the mappings between
8953 packages and hardware. One source would be to look at packages with
8954 kernel modules, ie packages with *.ko files in /lib/modules/, and
8955 extract their modalias information. Another would be to look at
8956 packages with udev rules, ie packages with files in
8957 /lib/udev/rules.d/, and extract their vendor/model information to
8958 generate a modalias matching rule. I have not tested any of these to
8959 see if it work.
</p
>
8961 <p
>If you want to help implementing a system to let us propose what
8962 packages to install when new hardware is plugged into a Debian
8963 machine, please send me an email or talk to me on
8964 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8969 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
8970 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
8971 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
8972 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
8973 <description><p
>While looking into how to look up Debian packages based on hardware
8974 information, to find the packages that support a given piece of
8975 hardware, I refreshed my memory regarding modalias values, and decided
8976 to document the details. Here are my findings so far, also available
8978 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8979 Debian Edu subversion repository
</a
>:
8981 <p
><strong
>Modalias decoded
</strong
></p
>
8983 <p
>This document try to explain what the different types of modalias
8984 values stands for. It is in part based on information from
8985 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
8986 &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;,
8987 &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
8988 &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;.
8990 <p
>The modalias entries for a given Linux machine can be found using
8991 this shell script:
</p
>
8994 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
8997 <p
>The supported modalias globs for a given kernel module can be found
8998 using modinfo:
</p
>
9001 % /sbin/modinfo psmouse | grep alias:
9002 alias: serio:ty05pr*id*ex*
9003 alias: serio:ty01pr*id*ex*
9007 <p
><strong
>PCI subtype
</strong
></p
>
9009 <p
>A typical PCI entry can look like this. This is an Intel Host
9010 Bridge memory controller:
</p
>
9012 <p
><blockquote
>
9013 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9014 </blockquote
></p
>
9016 <p
>This represent these values:
</p
>
9021 sv
00001028 (subvendor)
9022 sd
000001AD (subdevice)
9024 sc
00 (bus subclass)
9028 <p
>The vendor/device values are the same values outputted from
'lspci
9029 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
9030 0600. The
0600 class is a host bridge. Other useful bus values are
9031 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
9033 <p
>Not sure how to figure out the interface value, nor what it
9036 <p
><strong
>USB subtype
</strong
></p
>
9038 <p
>Some typical USB entries can look like this. This is an internal
9039 USB hub in a laptop:
</p
>
9041 <p
><blockquote
>
9042 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9043 </blockquote
></p
>
9045 <p
>Here is the values included in this alias:
</p
>
9048 v
1D6B (device vendor)
9049 p
0001 (device product)
9051 dc
09 (device class)
9052 dsc
00 (device subclass)
9053 dp
00 (device protocol)
9054 ic
09 (interface class)
9055 isc
00 (interface subclass)
9056 ip
00 (interface protocol)
9059 <p
>The
0900 device class/subclass means hub. Some times the relevant
9060 class is in the interface class section. For a simple USB web camera,
9061 these alias entries show up:
</p
>
9063 <p
><blockquote
>
9064 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9065 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9066 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9067 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9068 </blockquote
></p
>
9070 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
9071 camera),
0101 is audio control device and
0102 is audio streaming (aka
9072 microphone). Thus this is a camera with microphone included.
</p
>
9074 <p
><strong
>ACPI subtype
</strong
></p
>
9076 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
9077 receiver in a Thinkpad X40:
</p
>
9079 <p
><blockquote
>
9080 acpi:IBM0071:PNP0511:
9081 </blockquote
></p
>
9083 <p
>The values between the colons are IDs.
</p
>
9085 <p
><strong
>DMI subtype
</strong
></p
>
9087 <p
>The DMI table contain lots of information about the computer case
9088 and model. This is an entry for a IBM Thinkpad X40, fetched from
9089 /sys/devices/virtual/dmi/id/modalias:
</p
>
9091 <p
><blockquote
>
9092 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9093 </blockquote
></p
>
9095 <p
>The values present are
</p
>
9098 bvn IBM (BIOS vendor)
9099 bvr
1UETB
6WW(
1.66) (BIOS version)
9100 bd
06/
15/
2005 (BIOS date)
9101 svn IBM (system vendor)
9102 pn
2371H4G (product name)
9103 pvr ThinkPadX40 (product version)
9104 rvn IBM (board vendor)
9105 rn
2371H4G (board name)
9106 rvr NotAvailable (board version)
9107 cvn IBM (chassis vendor)
9108 ct
10 (chassis type)
9109 cvr NotAvailable (chassis version)
9112 <p
>The chassis type
10 is Notebook. Other interesting values can be
9113 found in the dmidecode source:
</p
>
9117 4 Low Profile Desktop
9130 17 Main Server Chassis
9131 18 Expansion Chassis
9133 20 Bus Expansion Chassis
9134 21 Peripheral Chassis
9136 23 Rack Mount Chassis
9145 <p
>The chassis type values are not always accurately set in the DMI
9146 table. For example my home server is a tower, but the DMI modalias
9147 claim it is a desktop.
</p
>
9149 <p
><strong
>SerIO subtype
</strong
></p
>
9151 <p
>This type is used for PS/
2 mouse plugs. One example is from my
9152 test machine:
</p
>
9154 <p
><blockquote
>
9155 serio:ty01pr00id00ex00
9156 </blockquote
></p
>
9158 <p
>The values present are
</p
>
9167 <p
>This type is supported by the psmouse driver. I am not sure what
9168 the valid values are.
</p
>
9170 <p
><strong
>Other subtypes
</strong
></p
>
9172 <p
>There are heaps of other modalias subtypes according to
9173 file2alias.c. There is the rest of the list from that source: amba,
9174 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9175 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9176 vmbus, x86cpu and zorro. I did not spend time documenting all of
9177 these, as they do not seem relevant for my intended use with mapping
9178 hardware to packages when new stuff is inserted during run time.
</p
>
9180 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
9182 <p
>To check which kernel modules provide support for a given modalias,
9183 one can use the following shell script:
</p
>
9186 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
9187 echo
"$id
" ; \
9188 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
9192 <p
>The output can look like this (only the first few entries as the
9193 list is very long on my test machine):
</p
>
9197 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
9199 FATAL: Module acpi:device: not found.
9201 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
9202 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
9203 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
9204 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9205 acpi:IBM0071:PNP0511:
9206 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
9207 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
9208 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
9212 <p
>If you want to help implementing a system to let us propose what
9213 packages to install when new hardware is plugged into a Debian
9214 machine, please send me an email or talk to me on
9215 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
9217 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
9218 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
9219 in /sys/ with space in them.
</p
>
9224 <title>Moved the pymissile Debian packaging to collab-maint
</title>
9225 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
9226 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
9227 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
9228 <description><p
>As part of my investigation on how to improve the support in Debian
9229 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9230 Launcher and updated the Debian package
9231 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
9232 sure udev will fix the device permissions when it is plugged in. I
9233 also added a
"Modaliases
" header to test it in the Debian archive and
9234 hopefully make the package be proposed by jockey in Ubuntu when a user
9235 plug in his rocket launcher. In the process I moved the source to a
9236 git repository under collab-maint, to make it easier for any DD to
9237 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
9238 is not very active, but the software still work for me even after five
9239 years of relative silence. The new git repository is not listed in
9240 the uploaded package yet, because I want to test the other changes a
9241 bit more before I upload the new version. If you want to check out
9242 the new version with a .desktop file included, visit the
9243 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
9244 view
</a
> or use
"<tt
>git clone
9245 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
9250 <title>Lets make hardware dongles easier to use in Debian
</title>
9251 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
9252 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
9253 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
9254 <description><p
>One thing that annoys me with Debian and Linux distributions in
9255 general, is that there is a great package management system with the
9256 ability to automatically install software packages by downloading them
9257 from the distribution mirrors, but no way to get it to automatically
9258 install the packages I need to use the hardware I plug into my
9259 machine. Even if the package to use it is easily available from the
9260 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9261 suggest to automatically install the python-nxt, nbc and t2n packages
9262 I need to talk to it. When I plug in a Yubikey, it could propose the
9263 yubikey-personalization package. The information required to do this
9264 is available, but no-one have pulled all the pieces together.
</p
>
9266 <p
>Some years ago, I proposed to
9267 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
9268 the discover subsystem to implement this
</a
>. The idea is fairly
9273 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
9274 starting when a user log in.
</li
>
9276 <li
>Set this program up to listen for kernel events emitted when new
9277 hardware is inserted into the computer.
</li
>
9279 <li
>When new hardware is inserted, look up the hardware ID in a
9280 database mapping to packages, and take note of any non-installed
9281 packages.
</li
>
9283 <li
>Show a message to the user proposing to install the discovered
9284 package, and make it easy to install it.
</li
>
9288 <p
>I am not sure what the best way to implement this is, but my
9289 initial idea was to use dbus events to discover new hardware, the
9290 discover database to find packages and
9291 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
9294 <p
>Yesterday, I found time to try to implement this idea, and the
9295 draft package is now checked into
9296 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
9297 Debian Edu subversion repository
</a
>. In the process, I updated the
9298 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
9299 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9300 the relevant packages in Debian, and uploaded a new version
9301 2.2013.01.09 to unstable. I also discovered that the current
9302 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
9303 package in Debian no longer discovered any USB devices, because
9304 /proc/bus/usb/devices is no longer present. I ported it to use
9305 libusb as a fall back option to get it working. The fixed package
9306 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
9307 because of the freeze).
</p
>
9309 <p
>With this prototype in place, I can insert my Yubikey, and get this
9310 desktop notification to show up (only once, the first time it is
9311 inserted):
</p
>
9313 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
9315 <p
>For this prototype to be really useful, some way to automatically
9316 install the proposed packages by pressing the
"Please install
9317 program(s)
" button should to be implemented.
</p
>
9319 <p
>If this idea seem useful to you, and you want to help make it
9320 happen, please help me update the discover-data database with mappings
9321 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
9322 list the package you would like to have installed when a given
9323 hardware device is inserted into your computer, and report bugs using
9324 reportbug if it isn
't. Or, if you know of a better way to provide
9325 such mapping, please let me know.
</p
>
9327 <p
>This prototype need more work, and there are several questions that
9328 should be considered before it is ready for production use. Is dbus
9329 the correct way to detect new hardware? At the moment I look for HAL
9330 dbus events on the system bus, because that is the events I could see
9331 on my Debian Squeeze KDE desktop. Are there better events to use?
9332 How should the user be notified? Is the desktop notification
9333 mechanism the best option, or should the background daemon raise a
9334 popup instead? How should packages be installed? When should they
9335 not be installed?
</p
>
9337 <p
>If you want to help getting such feature implemented in Debian,
9338 please send me an email. :)
</p
>
9343 <title>New IRC channel for LEGO designers using Debian
</title>
9344 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
9345 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
9346 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
9347 <description><p
>During Christmas, I have worked a bit on the Debian support for
9348 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
9349 NXT
</a
>. My son and I have played a bit with my NXT set, and I
9350 discovered I had to build all the tools myself because none were
9351 already in Debian Squeeze. If Debian support for LEGO is something
9352 you care about, please join me on the IRC channel
9353 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
9354 irc.debian.org). There is a lot that could be done to improve the
9355 Debian support for LEGO designers. For example both CAD software
9356 and Mindstorm compilers are missing. :)
</p
>
9358 <p
>Update
2012-
01-
03: A
9359 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
9360 including links to Lego related packages is now available.
</p
>
9365 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
9366 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
9367 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
9368 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
9369 <description><p
>Let me start by wishing you all marry Christmas and a happy new
9370 year! I hope next year will prove to be a good year.
</p
>
9372 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
9373 decentralised
"currency
" that allow people to transfer bitcoins
9374 between each other with minimal overhead, is a very interesting
9375 experiment. And as I wrote a few days ago, the bitcoin situation in
9376 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
9377 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
9378 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
9379 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
9380 for one of the ftpmasters to approve the new bitcoin-qt package
9383 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
9384 team in Debian, you can easily test the package in Debian Squeeze
9385 using the following steps to get a set of working packages:
</p
>
9387 <blockquote
><pre
>
9388 git clone git://git.debian.org/git/collab-maint/bitcoin
9390 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9391 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9392 </pre
></blockquote
>
9394 <p
>You might have to install some build dependencies as well. The
9395 list of commands should give you two packages, bitcoind and
9396 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9397 client will download the complete set of bitcoin
"blocks
", which need
9398 around
5.6 GiB of data on my machine at the moment. Make sure your
9399 ~/.bitcoin/ directory have lots of spare room if you want to download
9400 all the blocks. The client will warn if the disk is getting full, so
9401 there is not really a problem if you got too little room, but you will
9402 not be able to get all the features out of the client.
</p
>
9404 <p
>As usual, if you use bitcoin and want to show your support of my
9405 activities, please send Bitcoin donations to my address
9406 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9411 <title>A word on bitcoin support in Debian
</title>
9412 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
9413 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
9414 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
9415 <description><p
>It has been a while since I wrote about
9416 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
9417 peer-to-peer based crypto-currency, and the reason is simply that I
9418 have been busy elsewhere. But two days ago, I started looking at the
9419 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
9420 Debian
</a
> again to try to recover my old bitcoin wallet. The package
9421 is now maintained by a
9422 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
9423 people
</a
>, and the grunt work had already been done by this team. We
9424 owe a huge thank you to all these team members. :)
9425 But I was sad to discover that the bitcoin client is missing in
9426 Wheezy. It is only available in Sid (and an outdated client from
9427 backports). The client had several RC bugs registered in BTS blocking
9428 it from entering testing. To try to help the team and improve the
9429 situation, I spent some time providing patches and triaging the bug
9430 reports. I also had a look at the bitcoin package available from Matt
9432 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
9433 Ubuntu
</a
>, and moved the useful pieces from that version into the
9434 Debian package.
</p
>
9436 <p
>After checking with the main package maintainer Jonas Smedegaard on
9437 IRC, I pushed several patches into the collab-maint git repository to
9438 improve the package. It now contains fixes for the RC issues (not from
9439 me, but fixed by Scott Howard), build rules for a Qt GUI client
9440 package, konqueror support for the bitcoin: URI and bash completion
9441 setup. As I work on Debian Squeeze, I also created
9442 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
9443 patch to backport
</a
> the latest version. Jonas is going to look at
9444 it and try to integrate it into the git repository before uploading a
9445 new version to unstable.
9447 <p
>I would very much like bitcoin to succeed, to get rid of the
9448 centralized control currently exercised in the monetary system. I
9449 find it completely unacceptable that the USA government is collecting
9450 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9451 that the major credit card companies can block legal money
9452 transactions to Wikileaks. But for bitcoin to succeed, more people
9453 need to use bitcoins, and more people need to accept bitcoins when
9454 they sell products and services. Improving the bitcoin support in
9455 Debian is a small step in the right direction, but not enough.
9456 Unfortunately the user experience when browsing the web and wanting to
9457 pay with bitcoin is still not very good. The bitcoin: URI is a step
9458 in the right direction, but need to work in most or every browser in
9459 use. Also the bitcoin-qt client is too heavy to fire up to do a
9460 quick transaction. I believe there are other clients available, but
9461 have not tested them.
</p
>
9464 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
9465 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
9466 I received
20.15 BTC so far on the address I provided in my blog two
9467 years ago, as can be
9468 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
9469 on the blockexplorer service
</a
>. Thank you everyone for your
9470 donation. The blockexplorer service demonstrates quite well that
9471 bitcoin is not quite anonymous and untracked. :) I wonder if the
9472 number of users have gone up since then. If you use bitcoin and want
9473 to show your support of my activity, please send Bitcoin donations to
9474 the same address as last time,
9475 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9480 <title>Git repository for song book for Computer Scientists
</title>
9481 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
9482 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
9483 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
9484 <description><p
>As I
9485 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
9486 this summer
</a
>, I have created a Computer Science song book a few
9487 years ago, and today I finally found time to create a public
9488 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
9489 repository for the project
</a
>.
</p
>
9491 <p
>If you want to help out, please clone the source and submit patches
9492 to the HTML version. To generate the PDF and PostScript version,
9493 please use prince XML, or let me know about a useful free software
9494 processor capable of creating a good looking PDF from the HTML.
</p
>
9496 <p
>Want to sing? You can still find the song book in HTML, PDF and
9497 PostScript formats at
9498 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
9499 Science Songbook
</a
>.
</p
>
9504 <title>Gratulerer med
19-årsdagen, Debian!
</title>
9505 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
9506 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
9507 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
9508 <description><p
>I dag fyller
9509 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
9510 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
9511 si gratulerer med dagen, Debian!
</p
>
9516 <title>Song book for Computer Scientists
</title>
9517 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
9518 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
9519 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
9520 <description><p
>Many years ago, while studying Computer Science at the
9521 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
9522 collecting computer related songs for use at parties. The original
9523 version was written in LaTeX, but a few years ago I got help from
9524 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9525 while keeping the ability to create a nice book in PDF format. I have
9526 not had time to maintain the book for a while now, and guess I should
9527 put it up on some public version control repository where others can
9528 help me extend and update the book. If anyone is volunteering to help
9529 me with this, send me an email. Also let me know if there are songs
9530 missing in my book.
</p
>
9532 <p
>I have not mentioned the book on my blog so far, and it occured to
9533 me today that I really should let all my readers share the joys of
9534 singing out load about programming, computers and computer networks.
9535 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
9536 12</a
> is about to start (and I am not going). Want to sing? Check
9537 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
9538 Computer Science Songbook
</a
>.
9543 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
9544 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
9545 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
9546 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
9547 <description><p
>At work we have heaps of servers. I believe the total count is
9548 around
1000 at the moment. To be able to get help from the vendors
9549 when something go wrong, we want to keep the firmware on the servers
9550 up to date. If the firmware isn
't the latest and greatest, the
9551 vendors typically refuse to start debugging any problems until the
9552 firmware is upgraded. So before every reboot, we want to upgrade the
9553 firmware, and we would really like everyone handling servers at the
9554 university to do this themselves when they plan to reboot a machine.
9555 For that to happen we at the unix server admin group need to provide
9556 the tools to do so.
</p
>
9558 <p
>To make firmware upgrading easier, I am working on a script to
9559 fetch and install the latest firmware for the servers we got. Most of
9560 our hardware are from Dell and HP, so I have focused on these servers
9561 so far. This blog post is about the Dell part.
</P
>
9563 <p
>On the Dell FTP site I was lucky enough to find
9564 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
9565 with firmware information for all
11th generation servers, listing
9566 which firmware should be used on a given model and where on the FTP
9567 site I can find it. Using a simple perl XML parser I can then
9568 download the shell scripts Dell provides to do firmware upgrades from
9569 within Linux and reboot when all the firmware is primed and ready to
9570 be activated on the first reboot.
</p
>
9572 <p
>This is the Dell related fragment of the perl code I am working on.
9573 Are there anyone working on similar tools for firmware upgrading all
9574 servers at a site? Please get in touch and lets share resources.
</p
>
9576 <p
><pre
>
9580 use File::Temp qw(tempdir);
9582 # Install needed RHEL packages if missing
9584 'XML::Simple
' =
> 'perl-XML-Simple
',
9586 for my $module (keys %rhelmodules) {
9587 eval
"use $module;
";
9589 my $pkg = $rhelmodules{$module};
9590 system(
"yum install -y $pkg
");
9591 eval
"use $module;
";
9595 my $errorsto =
'pere@hungry.com
';
9601 sub run_firmware_script {
9602 my ($opts, $script) = @_;
9604 print STDERR
"fail: missing script name\n
";
9607 print STDERR
"Running $script\n\n
";
9609 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
9610 print STDERR
"success: firmware script ran succcessfully\n
";
9612 print STDERR
"fail: firmware script returned error\n
";
9616 sub run_firmware_scripts {
9617 my ($opts, @dirs) = @_;
9618 # Run firmware packages
9619 for my $dir (@dirs) {
9620 print STDERR
"info: Running scripts in $dir\n
";
9621 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
9622 while (my $s = readdir $dh) {
9623 next if $s =~ m/^\.\.?/;
9624 run_firmware_script($opts,
"$dir/$s
");
9632 print STDERR
"info: Downloading $url\n
";
9633 system(
"wget --quiet \
"$url\
"");
9638 my $product = `dmidecode -s system-product-name`;
9641 if ($product =~ m/PowerEdge/) {
9643 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9644 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
9646 my $tmpdir = tempdir(
9650 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
9651 system(
'gunzip Catalog.xml.gz
');
9652 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
9653 # -q is quiet, disabling interactivity and reducing console output
9654 my $fwopts =
"-q
";
9656 for my $url (@paths) {
9657 fetch_dell_fw($url);
9659 run_firmware_scripts($fwopts, $tmpdir);
9661 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9662 print STDERR
"error: Please report to $errorsto.\n
";
9666 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9667 print STDERR
"error: Please report to $errorsto.\n
";
9673 my $url =
"ftp://ftp.us.dell.com/$path
";
9677 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9678 # firmware packages to download from Dell. Only work for Linux
9679 # machines and
11th generation Dell servers.
9680 sub fetch_dell_fw_list {
9681 my $filename = shift;
9683 my $product = `dmidecode -s system-product-name`;
9685 my ($mybrand, $mymodel) = split(/\s+/, $product);
9687 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
9689 my $xml = XMLin($filename);
9691 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
9692 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
9693 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
9695 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
9696 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
9698 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
9700 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
9702 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
9705 for my $component (@{$xml-
>{SoftwareComponent}}) {
9706 my $componenttype = $component-
>{ComponentType}-
>{value};
9708 # Drop application packages, only firmware and BIOS
9709 next if
'APAC
' eq $componenttype;
9711 my $cpath = $component-
>{path};
9712 for my $path (@paths) {
9713 if ($cpath =~ m%/$path$%) {
9714 push(@paths, $cpath);
9722 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
9723 it could work on other platforms with some tweaking. Anyone know a
9724 index like Catalog.xml is available from HP for HP servers? At the
9725 moment I maintain a similar list manually and it is quickly getting
9731 <title>How is booting into runlevel
1 different from single user boots?
</title>
9732 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
9733 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
9734 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
9735 <description><p
>Wouter Verhelst have some
9736 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
9737 comments and opinions
</a
> on my blog post on
9738 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
9739 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
9740 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
9741 default KDE desktop in Debian
</a
>. I only have time to address one
9742 small piece of his comment now, and though it best to address the
9743 misunderstanding he bring forward:
</p
>
9745 <p
><blockquote
>
9746 Currently, a system admin has four options: [...] boot to a
9747 single-user system (by adding
'single
' to the kernel command line;
9748 this runs rcS and rc1 scripts)
9749 </blockquote
></p
>
9751 <p
>This make me believe Wouter believe booting into single user mode
9752 and booting into runlevel
1 is the same. I am not surprised he
9753 believe this, because it would make sense and is a quite sensible
9754 thing to believe. But because the boot in Debian is slightly broken,
9755 runlevel
1 do not work properly and it isn
't the same as single user
9756 mode. I
'll try to explain what is actually happing, but it is a bit
9757 hard to explain.
</p
>
9759 <p
>Single user mode is defined like this in /etc/inittab:
9760 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
9761 executed in single user mode is sulogin. Single user mode is a boot
9762 state
"between
" the runlevels, and when booting into single user mode,
9763 only the scripts in /etc/rcS.d/ are executed before the init process
9764 enters the single user state. When switching to runlevel
1, the state
9765 is in fact not ending in runlevel
1, but it passes through runlevel
1
9766 and end up in the single user mode (see /etc/rc1.d/S03single, which
9767 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
9768 1. It is confusing that the
'S
' (single user) init mode is not the
9769 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9772 <p
>This summary might make it clearer. When booting for the first
9773 time into single user mode, the following commands are executed:
9774 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
9775 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
9776 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
9777 trying to continue after visiting single user mode. Not all services
9778 are started again as they should, causing the machine to end up in an
9779 unpredicatble state. This is why Debian admins recommend rebooting
9780 after visiting single user mode.
</p
>
9782 <p
>A similar problem with runlevel
1 is caused by the amount of
9783 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
9784 to runlevel
1, the services started from /etc/rcS.d/ are not properly
9785 stopped when passing through the scripts in /etc/rc1.d/, and not
9786 started again when switching away from runlevel
1 to the runlevels
9787 2-
5. I believe the problem is best fixed by moving all the scripts
9788 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
9789 functioning single user mode during boot.
</p
>
9791 <p
>I have spent several years investigating the Debian boot system,
9792 and discovered this problem a few years ago. I suspect it originates
9793 from when sysvinit was introduced into Debian, a long time ago.
</p
>
9798 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
9799 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
9800 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
9801 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
9802 <description><p
>In the Debian boot system, several packages include scripts that
9803 are started from /etc/rcS.d/. In fact, there is a bite more of them
9804 than make sense, and this causes a few problems. What kind of
9805 problems, you might ask. There are at least two problems. The first
9806 is that it is not possible to recover a machine after switching to
9807 runlevel
1. One need to actually reboot to get the machine back to
9808 the expected state. The other is that single user boot will sometimes
9809 run into problems because some of the subsystems are activated before
9810 the root login is presented, causing problems when trying to recover a
9811 machine from a problem in that subsystem. A minor additional point is
9812 that moving more scripts out of rcS.d/ and into the other rc#.d/
9813 directories will increase the amount of scripts that can run in
9814 parallel during boot, and thus decrease the boot time.
</p
>
9816 <p
>So, which scripts should start from rcS.d/. In short, only the
9817 scripts that _have_ to execute before the root login prompt is
9818 presented during a single user boot should go there. Everything else
9819 should go into the numeric runlevels. This means things like
9820 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9821 the numeric runlevels. Today in Debian, there are around
115 init.d
9822 scripts that are started from rcS.d/, and most of them should be moved
9823 out. Do your package have one of them? Please help us make single
9824 user and runlevel
1 better by moving it.
</p
>
9826 <p
>Scripts setting up the screen, keyboard, system partitions
9827 etc. should still be started from rcS.d/, but there is for example no
9828 need to have the network enabled before the single user login prompt
9829 is presented.
</p
>
9831 <p
>As always, things are not so easy to fix as they sound. To keep
9832 Debian systems working while scripts migrate and during upgrades, the
9833 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9834 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9835 and the next ones can only be moved when their dependencies have been
9836 moved first. This migration must be done sequentially while we ensure
9837 that the package system upgrade packages in the right order to keep
9838 the system state correct. This will require some coordination when it
9839 comes to network related packages, but most of the packages with
9840 scripts that should migrate do not have anything in rcS.d/ depending
9841 on them. Some packages have already been updated, like the sudo
9842 package, while others are still left to do. I wish I had time to work
9843 on this myself, but real live constrains make it unlikely that I will
9844 find time to push this forward.
</p
>
9849 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
9850 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
9851 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
9852 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
9853 <description><p
>While at Debconf11, I have several times during discussions
9854 mentioned the issues I believe should be improved in Debian for its
9855 desktop to be useful for more people. The use case for this is my
9856 parents, which are currently running Kubuntu which solve the
9859 <p
>I suspect these four missing features are not very hard to
9860 implement. After all, they are present in Ubuntu, so if we wanted to
9861 do this in Debian we would have a source.
</p
>
9865 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
9866 are new packages available for upgrades, a icon in the KDE status bar
9867 indicate this, and clicking on it will activate the simple upgrade
9868 tool to handle it. I have no problem guiding both of my parents
9869 through the process over the phone. If a kernel reboot is required,
9870 this too is indicated by the status bars and the upgrade tool. Last
9871 time I checked, nothing with the same features was working in KDE in
9874 <li
><strong
>Simple handling of missing Firefox browser
9875 plugins.
</strong
> When the browser encounter a MIME type it do not
9876 currently have a handler for, it will ask the user if the system
9877 should search for a package that would add support for this MIME type,
9878 and if the user say yes, the APT sources will be searched for packages
9879 advertising the MIME type in their control file (visible in the
9880 Packages file in the APT archive). If one or more packages are found,
9881 it is a simple click of the mouse to add support for the missing mime
9882 type. If the package require the user to accept some non-free
9883 license, this is explained to the user. The entire process make it
9884 more clear to the user why something do not work in the browser, and
9885 make the chances higher for the user to blame the web page authors and
9886 not the browser for any missing features.
</li
>
9888 <li
><strong
>Simple handling of missing multimedia codec/format
9889 handlers.
</strong
> When the media players encounter a format or codec
9890 it is not supporting, a dialog pop up asking the user if the system
9891 should search for a package that would add support for it. This
9892 happen with things like MP3, Windows Media or H
.264. The selection
9893 and installation procedure is very similar to the Firefox browser
9894 plugin handling. This is as far as I know implemented using a
9895 gstreamer hook. The end result is that the user easily get access to
9896 the codecs that are present from the APT archives available, while
9897 explaining more on why a given format is unsupported by Ubuntu.
</li
>
9899 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
9900 displaying a text/plain file in my Debian browser, it will propose to
9901 start emacs to show it. If I remember correctly, when doing the same
9902 in Kunbutu it show the file as a text file in the browser. At least I
9903 know Opera will show text files within the browser. I much prefer the
9904 latter behaviour.
</li
>
9908 <p
>There are other nice features as well, like the simplified suite
9909 upgrader, but given that I am the one mostly doing the dist-upgrade,
9910 it do not matter much.
</p
>
9912 <p
>I really hope we could get these features in place for the next
9913 Debian release. It would require the coordinated effort of several
9914 maintainers, but would make the end user experience a lot better.
</p
>
9919 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
9920 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
9921 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
9922 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
9923 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
9924 site is build on Debian/Squeeze, and this platform was chosen because
9925 I am most familiar with Debian (being a Debian Developer for around
10
9926 years) because it is the latest stable Debian release which should get
9927 security support for a few years.
</p
>
9929 <p
>The web service is written in Perl, and depend on some perl modules
9930 that are missing in Debian at the moment. It would be great if these
9931 modules were added to the Debian archive, allowing anyone to set up
9932 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
9933 in their own country using only Debian packages. The list of modules
9934 missing in Debian/Squeeze isn
't very long, and I hope the perl group
9935 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
9936 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9937 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9938 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9939 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9940 easier in the future.
</p
>
9942 <p
>Thanks to the great tools in Debian, getting the missing modules
9943 installed on my server was a simple call to
'cpan2deb Module::Name
'
9944 and
'dpkg -i
' to install the resulting package. But this leave me
9945 with the responsibility of tracking security problems, which I really
9946 do not have time for.
</p
>
9951 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
9952 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
9953 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
9954 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
9955 <description><p
>Here is a small update for my English readers. Most of my blog
9956 posts have been in Norwegian the last few weeks, so here is a short
9957 update in English.
</p
>
9959 <p
>The kids still keep me too busy to get much free software work
9960 done, but I did manage to organise a project to get a Norwegian port
9961 of the British service
9962 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
9963 and it has been running for a month now. The entire project has been
9964 organised by me and two others. Around Christmas we gathered sponsors
9965 to fund the development work. In January I drafted a contract with
9966 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
9967 and in February the development took place. Most of it involved
9968 converting the source to use GPS coordinates instead of British
9969 easting/northing, and the resulting code should be a lot easier to get
9970 running in any country by now. The Norwegian
9971 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
9972 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
9973 source and the source for administrative borders in Norway, and
9974 support for this had to be added/fixed.
</p
>
9976 <p
>The Norwegian version went live March
3th, and we spent the weekend
9977 polishing the system before we announced it March
7th. The system is
9978 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
9979 problem reports in a few weeks. Soon we hope to announce the Android
9980 and iPhone versions making it even easier to report problems with the
9981 public infrastructure.
</p
>
9983 <p
>Perhaps something to consider for those of you in countries without
9984 such service?
</p
>
9989 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
9990 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
9991 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
9992 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
9993 <description><p
>The last few days I have looked at ways to track open security
9994 issues here at my work with the University of Oslo. My idea is that
9995 it should be possible to use the information about security issues
9996 available on the Internet, and check our locally
9997 maintained/distributed software against this information. It should
9998 allow us to verify that no known security issues are forgotten. The
9999 CVE database listing vulnerabilities seem like a great central point,
10000 and by using the package lists from Debian mapped to CVEs provided by
10001 the testing security team, I believed it should be possible to figure
10002 out which security holes were present in our free software
10003 collection.
</p
>
10005 <p
>After reading up on the topic, it became obvious that the first
10006 building block is to be able to name software packages in a unique and
10007 consistent way across data sources. I considered several ways to do
10008 this, for example coming up with my own naming scheme like using URLs
10009 to project home pages or URLs to the Freshmeat entries, or using some
10010 existing naming scheme. And it seem like I am not the first one to
10011 come across this problem, as MITRE already proposed and implemented a
10012 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
10013 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
10014 software, hardware and other platform components. The CPE ids are
10015 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
10016 Vulnerability Database
</a
>, allowing me to look up know security
10017 issues for any CPE name. With this in place, all I need to do is to
10018 locate the CPE id for the software packages we use at the university.
10019 This is fairly trivial (I google for
'cve cpe $package
' and check the
10020 NVD entry if a CVE for the package exist).
</p
>
10022 <p
>To give you an example. The GNU gzip source package have the CPE
10023 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
10024 check out, one could look up
10025 <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
10026 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
10027 The most recent one is
10028 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
10029 and at the bottom of the NVD page for this vulnerability the complete
10030 list of affected versions is provided.
</p
>
10032 <p
>The NVD database of CVEs is also available as a XML dump, allowing
10033 for offline processing of issues. Using this dump, I
've written a
10034 small script taking a list of CPEs as input and list all CVEs
10035 affecting the packages represented by these CPEs. One give it CPEs
10036 with version numbers as specified above and get a list of open
10037 security issues out.
</p
>
10039 <p
>Of course for this approach to be useful, the quality of the NVD
10040 information need to be high. For that to happen, I believe as many as
10041 possible need to use and contribute to the NVD database. I notice
10043 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
10044 map from CVE to CPE
</a
>, indicating that they are using the CPE
10045 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
10047 <p
>To get an idea about the quality for free software, I spent some
10048 time making it possible to compare the CVE database from Debian with
10049 the CVE database in NVD. The result look fairly good, but there are
10050 some inconsistencies in NVD (same software package having several
10051 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10052 Debian believe are affected by a CVE). Hope to find time to improve
10053 the quality of NVD, but that require being able to get in touch with
10054 someone maintaining it. So far my three emails with questions and
10055 corrections have not seen any reply, but I hope contact can be
10056 established soon.
</p
>
10058 <p
>An interesting application for CPEs is cross platform package
10059 mapping. It would be useful to know which packages in for example
10060 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10061 this would be trivial if all linux distributions provided CPE entries
10062 for their packages.
</p
>
10067 <title>Which module is loaded for a given PCI and USB device?
</title>
10068 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
10069 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
10070 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
10071 <description><p
>In the
10072 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
10073 package in Debian, there is a script to report useful information
10074 about the running hardware for use when people report missing
10075 information. One part of this script that I find very useful when
10076 debugging hardware problems, is the part mapping loaded kernel module
10077 to the PCI device it claims. It allow me to quickly see if the kernel
10078 module I expect is driving the hardware I am struggling with. To see
10079 the output, make sure discover-data is installed and run
10080 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
10081 one of my machines like this:
</p
>
10085 10de:
03eb i2c_nforce2
10088 10de:
03f0 snd_hda_intel
10093 109e:
0878 snd_bt87x
10097 <p
>The code in question look like this, slightly modified for
10098 readability and to drop the output to file descriptor
3:
</p
>
10101 if [ -d /sys/bus/pci/devices/ ] ; then
10102 echo loaded pci modules:
10104 cd /sys/bus/pci/devices/
10105 for address in * ; do
10106 if [ -d
"$address/driver/module
" ] ; then
10107 module=`cd $address/driver/module ; pwd -P | xargs basename`
10108 if grep -q
"^$module
" /proc/modules ; then
10109 address=$(echo $address |sed s/
0000://)
10110 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
10111 echo
"$id $module
"
10120 <p
>Similar code could be used to extract USB device module
10121 mappings:
</p
>
10124 if [ -d /sys/bus/usb/devices/ ] ; then
10125 echo loaded usb modules:
10127 cd /sys/bus/usb/devices/
10128 for address in * ; do
10129 if [ -d
"$address/driver/module
" ] ; then
10130 module=`cd $address/driver/module ; pwd -P | xargs basename`
10131 if grep -q
"^$module
" /proc/modules ; then
10132 address=$(echo $address |sed s/
0000://)
10133 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
10134 if [
"$id
" ] ; then
10135 echo
"$id $module
"
10145 <p
>This might perhaps be something to include in other tools as
10151 <title>How to test if a laptop is working with Linux
</title>
10152 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
10153 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
10154 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
10155 <description><p
>The last few days I have spent at work here at the
<a
10156 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
10157 batch of computers will work with Linux. Every year for the last few
10158 years the university have organised shared bid of a few thousand
10159 computers, and this year HP won the bid. Two different desktops and
10160 five different laptops are on the list this year. We in the UNIX
10161 group want to know which one of these computers work well with RHEL
10162 and Ubuntu, the two Linux distributions we currently handle at the
10163 university.
</p
>
10165 <p
>My test method is simple, and I share it here to get feedback and
10166 perhaps inspire others to test hardware as well. To test, I PXE
10167 install the OS version of choice, and log in as my normal user and run
10168 a few applications and plug in selected pieces of hardware. When
10169 something fail, I make a note about this in the test matrix and move
10170 on. If I have some spare time I try to report the bug to the OS
10171 vendor, but as I only have the machines for a short time, I rarely
10172 have the time to do this for all the problems I find.
</p
>
10174 <p
>Anyway, to get to the point of this post. Here is the simple tests
10175 I perform on a new model.
</p
>
10179 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
10180 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10181 RHEL5 and Debian Edu/Squeeze.
</li
>
10183 <li
>Is X.org working? If the graphical login screen show up after
10184 installation, X.org is working.
</li
>
10186 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
10187 package mesa-utils on Ubuntu) and writing down the frames per second
10188 reported by the program.
</li
>
10190 <li
>Is sound working? With Gnome and KDE, a sound is played when
10191 logging in, and if I can hear this the test is successful. If there
10192 are several audio exits on the machine, I try them all and check if
10193 the Gnome/KDE audio mixer can control where to send the sound. I
10194 normally test this by playing
10195 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
10196 video
</a
> in Firefox/Iceweasel.
</li
>
10198 <li
>Is the USB subsystem working? I test this by plugging in a USB
10199 memory stick and see if Gnome/KDE notices this.
</li
>
10201 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
10202 I have lying around, and see if Gnome/KDE notices this.
</li
>
10204 <li
>Is any built in camera working? Test using cheese, and see if a
10205 picture from the v4l device show up.
</li
>
10207 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10208 any bluetooth devices are discovered. In my office, I normally see a
10211 <li
>For laptops, is the SD or Compaq Flash reader working. I have
10212 memory modules lying around, and stick them in and see if Gnome/KDE
10213 notice this.
</li
>
10215 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
10216 special button work, and if the laptop continue to work after
10219 <li
>For laptops, is the extra buttons working, like audio level,
10220 adjusting background light, switching on/off external video output,
10221 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10222 laptop to laptop, so I just write down which are working and which are
10225 <li
>Some laptops have smart card readers, finger print readers,
10226 acceleration sensors etc. I rarely test these, as I do not know how
10227 to quickly test if they are working or not, so I only document their
10228 existence.
</li
>
10232 <p
>By now I suspect you are really curious what the test results are
10233 for the HP machines I am testing. I
'm not done yet, so I will report
10234 the test results later. For now I can report that HP
8100 Elite work
10235 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
10236 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
10237 can see, I have most machines left to test. One interesting
10238 observation is that Ubuntu Lucid has almost twice the frame rate than
10239 RHEL6 with glxgears. No idea why.
</p
>
10244 <title>Some thoughts on BitCoins
</title>
10245 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
10246 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
10247 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
10248 <description><p
>As I continue to explore
10249 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
10250 what properties the system have, and how it will be affected by laws
10251 and regulations here in Norway. Here are some random notes.
</p
>
10253 <p
>One interesting thing to note is that since the transactions are
10254 verified using a peer to peer network, all details about a transaction
10255 is known to everyone. This means that if a BitCoin address has been
10256 published like I did with mine in my initial post about BitCoin, it is
10257 possible for everyone to see how many BitCoins have been transfered to
10258 that address. There is even a web service to look at the details for
10259 all transactions. There I can see that my address
10260 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
10261 have received
16.06 Bitcoin, the
10262 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
10263 address of Simon Phipps have received
181.97 BitCoin and the address
10264 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
10265 of EFF have received
2447.38 BitCoins so far. Thank you to each and
10266 every one of you that donated bitcoins to support my activity. The
10267 fact that anyone can see how much money was transfered to a given
10268 address make it more obvious why the BitCoin community recommend to
10269 generate and hand out a new address for each transaction. I
'm told
10270 there is no way to track which addresses belong to a given person or
10271 organisation without the person or organisation revealing it
10272 themselves, as Simon, EFF and I have done.
</p
>
10274 <p
>In Norway, and in most other countries, there are laws and
10275 regulations limiting how much money one can transfer across the border
10276 without declaring it. There are money laundering, tax and accounting
10277 laws and regulations I would expect to apply to the use of BitCoin.
10278 If the Skolelinux foundation
10279 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
10280 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
10281 normal bank transfers like EFF is doing, how should this be accounted?
10282 Given that it is impossible to know if money can cross the border or
10283 not, should everything or nothing be declared? What exchange rate
10284 should be used when calculating taxes? Would receivers have to pay
10285 income tax if the foundation were to pay Skolelinux contributors in
10286 BitCoin? I have no idea, but it would be interesting to know.
</p
>
10288 <p
>For a currency to be useful and successful, it must be trusted and
10289 accepted by a lot of users. It must be possible to get easy access to
10290 the currency (as a wage or using currency exchanges), and it must be
10291 easy to spend it. At the moment BitCoin seem fairly easy to get
10292 access to, but there are very few places to spend it. I am not really
10293 a regular user of any of the vendor types currently accepting BitCoin,
10294 so I wonder when my kind of shop would start accepting BitCoins. I
10295 would like to buy electronics, travels and subway tickets, not herbs
10296 and books. :) The currency is young, and this will improve over time
10297 if it become popular, but I suspect regular banks will start to lobby
10298 to get BitCoin declared illegal if it become popular. I
'm sure they
10299 will claim it is helping fund terrorism and money laundering (which
10300 probably would be true, as is any currency in existence), but I
10301 believe the problems should be solved elsewhere and not by blaming
10302 currencies.
</p
>
10304 <p
>The process of creating new BitCoins is called mining, and it is
10305 CPU intensive process that depend on a bit of luck as well (as one is
10306 competing against all the other miners currently spending CPU cycles
10307 to see which one get the next lump of cash). The
"winner
" get
50
10308 BitCoin when this happen. Yesterday I came across the obvious way to
10309 join forces to increase ones changes of getting at least some coins,
10310 by coordinating the work on mining BitCoins across several machines
10311 and people, and sharing the result if one is lucky and get the
50
10312 BitCoins. Check out
10313 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
10314 if this sounds interesting. I have not had time to try to set up a
10315 machine to participate there yet, but have seen that running on ones
10316 own for a few days have not yield any BitCoins througth mining
10319 <p
>Update
2010-
12-
15: Found an
<a
10320 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
10321 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
10322 it was interesting to read. The arguments presented seem to be
10323 equally valid for gold, which was used as a currency for many years.
</p
>
10328 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
10329 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
10330 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
10331 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
10332 <description><p
>With this weeks lawless
10333 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
10334 attacks
</a
> on Wikileak and
10335 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
10336 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
10337 not be trusted to handle money transactions.
10339 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
10340 Phipps on bitcoin
</a
> reminded me about a project that a friend of
10341 mine mentioned earlier. I decided to follow Simon
's example, and get
10342 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
10343 some help from my friend to get it all running, and he even handed me
10344 some bitcoins to get started. I even donated a few bitcoins to Simon
10345 for helping me remember BitCoin.
</p
>
10347 <p
>So, what is bitcoins, you probably wonder? It is a digital
10348 crypto-currency, decentralised and handled using peer-to-peer
10349 networks. It allows anonymous transactions and prohibits central
10350 control over the transactions, making it impossible for governments
10351 and companies alike to block donations and other transactions. The
10352 source is free software, and while the key dependency wxWidgets
2.9
10353 for the graphical user interface is missing in Debian, the command
10354 line client builds just fine. Hopefully Jonas
10355 <a href=
"http://bugs.debian.org/
578157">will get the package into
10356 Debian
</a
> soon.
</p
>
10358 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
10359 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
10360 bitcoins
</a
> when selling services and goods, and there are even
10361 currency
"stock
" markets where the exchange rate is decided. There
10362 are not many users so far, but the concept seems promising. If you
10363 want to get started and lack a friend with any bitcoins to spare,
10365 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
10366 bitcoin at the time of writing). Use
10367 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
10368 on the current exchange rates.
</p
>
10370 <p
>As an experiment, I have decided to set up bitcoind on one of my
10371 machines. If you want to support my activity, please send Bitcoin
10372 donations to the address
10373 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
10378 <title>Why isn
't Debian Edu using VLC?
</title>
10379 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
10380 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
10381 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
10382 <description><p
>In the latest issue of Linux Journal, the readers choices were
10383 presented, and the winner among the multimedia player were VLC.
10384 Personally, I like VLC, and it is my player of choice when I first try
10385 to play a video file or stream. Only if VLC fail will I drag out
10386 gmplayer to see if it can do better. The reason is mostly the failure
10387 model and trust. When VLC fail, it normally pop up a error message
10388 reporting the problem. When mplayer fail, it normally segfault or
10389 just hangs. The latter failure mode drain my trust in the program.
<p
>
10391 <p
>But even if VLC is my player of choice, we have choosen to use
10392 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
10393 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
10394 plugin to play web videos seamlessly, and the VLC browser plugin is
10395 not very good. For example, it lack in-line control buttons, so there
10396 is no way for the user to pause the video. Also, when I
10397 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
10398 tested the browser plugins
</a
> available in Debian, the VLC plugin
10399 failed on several video pages where mplayer based plugins worked. If
10400 the browser plugin for VLC was as good as the gecko-mediaplayer
10401 package (which uses mplayer), we would switch.
</P
>
10403 <p
>While VLC is a good player, its user interface is slightly
10404 annoying. The most annoying feature is its inconsistent use of
10405 keyboard shortcuts. When the player is in full screen mode, its
10406 shortcuts are different from when it is playing the video in a window.
10407 For example, space only work as pause when in full screen mode. I
10408 wish it had consisten shortcuts and that space also would work when in
10409 window mode. Another nice shortcut in gmplayer is [enter] to restart
10410 the current video. It is very nice when playing short videos from the
10411 web and want to restart it when new people arrive to have a look at
10412 what is going on.
</p
>
10417 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
10418 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
10419 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</guid>
10420 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
10421 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
10422 upgrade testing of the
10423 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10424 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
10425 This seem like a very good idea, so I adjusted by test scripts and
10426 can now present the updated result from today:
</p
>
10428 <p
>This is for Gnome:
</p
>
10430 <p
>Installed using apt-get, missing with aptitude
</p
>
10432 <blockquote
><p
>
10437 browser-plugin-gnash
10444 freedesktop-sound-theme
10446 gconf-defaults-service
10459 gnome-codec-install
10461 gnome-desktop-environment
10465 gnome-session-canberra
10467 gnome-themes-extras
10470 gstreamer0.10-fluendo-mp3
10471 gstreamer0.10-tools
10473 gtk2-engines-pixbuf
10474 gtk2-engines-smooth
10476 libapache2-mod-dnssd
10479 libaprutil1-dbd-sqlite3
10482 libboost-date-time1.42
.0
10483 libboost-python1.42
.0
10484 libboost-thread1.42
.0
10486 libchamplain-gtk-
0.4-
0
10488 libclutter-gtk-
0.10-
0
10495 libfreerdp-plugins-standard
10508 libgnome-vfs2.0-cil
10510 libgnomepanel2.24-cil
10515 libgtksourceview2.0-common
10516 libmono-addins-gui0.2-cil
10517 libmono-addins0.2-cil
10518 libmono-cairo2.0-cil
10519 libmono-corlib2.0-cil
10520 libmono-i18n-west2.0-cil
10521 libmono-posix2.0-cil
10522 libmono-security2.0-cil
10523 libmono-sharpzip2.84-cil
10524 libmono-system2.0-cil
10527 libndesk-dbus-glib1.0-cil
10528 libndesk-dbus1.0-cil
10538 libtelepathy-farsight0
10547 nautilus-sendto-empathy
10551 python-aptdaemon-gtk
10553 python-beautifulsoup
10568 python-gtksourceview2
10579 python-pkg-resources
10586 python-twisted-conch
10587 python-twisted-core
10592 python-zope.interface
10594 remmina-plugin-data
10597 rhythmbox-plugin-cdrecorder
10604 system-config-printer-udev
10606 telepathy-mission-control-
5
10613 transmission-common
10617 </p
></blockquote
>
10619 <p
>Installed using apt-get, removed with aptitude
</p
>
10621 <blockquote
><p
>
10625 epiphany-extensions
10627 fast-user-switch-applet
10646 libgtksourceview2.0-
0
10648 libsdl1.2debian-alsa
10654 system-config-printer
10659 </p
></blockquote
>
10661 <p
>Installed using aptitude, missing with apt-get
</p
>
10663 <blockquote
><p
>
10664 gstreamer0.10-gnomevfs
10665 </p
></blockquote
>
10667 <p
>Installed using aptitude, removed with apt-get
</p
>
10669 <blockquote
><p
>
10671 </p
></blockquote
>
10673 <p
>This is for KDE:
</p
>
10675 <p
>Installed using apt-get, missing with aptitude
</p
>
10677 <blockquote
><p
>
10679 </p
></blockquote
>
10681 <p
>Installed using apt-get, removed with aptitude
</p
>
10683 <blockquote
><p
>
10685 network-manager-kde
10686 </p
></blockquote
>
10688 <p
>Installed using aptitude, missing with apt-get
</p
>
10690 <blockquote
><p
>
10704 kdeartwork-emoticons
10706 kdeartwork-theme-icon
10710 kdebase-workspace-bin
10711 kdebase-workspace-data
10723 konqueror-nsplugins
10725 kscreensaver-xsavers
10740 plasma-dataengines-workspace
10742 plasma-desktopthemes-artwork
10743 plasma-runners-addons
10744 plasma-scriptengine-googlegadgets
10745 plasma-scriptengine-python
10746 plasma-scriptengine-qedje
10747 plasma-scriptengine-ruby
10748 plasma-scriptengine-webkit
10749 plasma-scriptengines
10750 plasma-wallpapers-addons
10751 plasma-widget-folderview
10752 plasma-widget-networkmanagement
10755 update-notifier-kde
10756 xscreensaver-data-extra
10758 xscreensaver-gl-extra
10759 xscreensaver-screensaver-bsod
10760 </p
></blockquote
>
10762 <p
>Installed using aptitude, removed with apt-get
</p
>
10764 <blockquote
><p
>
10766 google-gadgets-common
10784 libggadget-qt-
1.0-
0b
10789 libkonqsidebarplugin4a
10793 libkunitconversion4
10798 libplasma-geolocation-interface4
10800 libplasmagenericshell4
10814 libsmokeknewstuff2-
3
10815 libsmokeknewstuff3-
3
10817 libsmokektexteditor3
10825 libsmokeqtnetwork4-
3
10826 libsmokeqtopengl4-
3
10827 libsmokeqtscript4-
3
10831 libsmokeqtuitools4-
3
10832 libsmokeqtwebkit4-
3
10843 plasma-dataengines-addons
10844 plasma-scriptengine-superkaramba
10845 plasma-widget-lancelot
10846 plasma-widgets-addons
10847 plasma-widgets-workspace
10851 update-notifier-common
10852 </p
></blockquote
>
10854 <p
>Running apt-get autoremove made the results using apt-get and
10855 aptitude a bit more similar, but there are still quite a lott of
10856 differences. I have no idea what packages should be installed after
10857 the upgrade, but hope those that do can have a look.
</p
>
10862 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
10863 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
10864 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
10865 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
10866 <description><p
>Most of the computers in use by the
10867 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
10868 are virtual machines. And they have been Xen machines running on a
10869 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
10870 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
10871 bit harder that it could have been, because we set up the Xen virtual
10872 machines to get the virtual partitions from LVM, which as far as I
10873 know is not supported by KVM. So to migrate, we had to convert
10874 several LVM logical volumes to partitions on a virtual disk file.
</p
>
10877 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
10878 nice recipe
</a
> to do this, and wrote the following script to do the
10879 migration. It uses qemu-img from the qemu package to make the disk
10880 image, parted to partition it, losetup and kpartx to present the disk
10881 image partions as devices, and dd to copy the data. I NFS mounted the
10882 new servers storage area on the old server to do the migration.
</p
>
10888 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10893 if [ -z
"$
1" ] ; then
10894 echo
"Usage: $
0 &lt;hostname
&gt;
"
10897 host=
"$
1"
10900 if [ ! -e /dev/vg_data/$host-disk ] ; then
10901 echo
"error: unable to find LVM volume for $host
"
10905 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10906 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10907 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10908 totalsize=$(( ( $disksize + $swapsize ) ))
10911 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
10912 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10914 parted $img mklabel msdos
10915 parted $img mkpart primary linux-swap
0 $disksize
10916 parted $img mkpart primary ext2 $disksize $totalsize
10917 parted $img set
1 boot on
10920 losetup /dev/loop0 $img
10921 kpartx -a /dev/loop0
10923 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
10924 fsck.ext3 -f /dev/mapper/loop0p1 || true
10925 mkswap /dev/mapper/loop0p2
10927 kpartx -d /dev/loop0
10928 losetup -d /dev/loop0
10931 <p
>The script is perhaps so simple that it is not copyrightable, but
10932 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
10934 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
10935 the new disk image attached, installed grub-pc and linux-image-
686 and
10936 set up grub to boot from the disk image. After this, the KVM machines
10937 seem to work just fine.
</p
>
10942 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
10943 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
10944 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
10945 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
10946 <description><p
>I
'm still running upgrade testing of the
10947 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10948 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
10949 status. Here is a short update based on a test I ran
20101118.
</p
>
10951 <p
>I still do not know what a correct migration should look like, so I
10952 report any differences between apt and aptitude and hope someone else
10953 can see if anything should be changed.
</p
>
10955 <p
>This is for Gnome:
</p
>
10957 <p
>Installed using apt-get, missing with aptitude
</p
>
10959 <blockquote
><p
>
10960 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10961 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
10962 dmz-cursor-theme empathy empathy-common finger
10963 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10964 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10965 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10966 gnome-cards-data gnome-codec-install gnome-core
10967 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10968 gnome-search-tool gnome-session-canberra gnome-spell
10969 gnome-system-log gnome-themes-extras gnome-themes-more
10970 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10971 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10972 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10973 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10974 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
10975 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
10976 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
10977 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
10978 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
10979 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10980 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
10981 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10982 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10983 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10984 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10985 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10986 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10987 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10988 libmono-security2.0-cil libmono-sharpzip2.84-cil
10989 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
10990 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
10991 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
10992 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
10993 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
10994 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
10995 libxalan2-java libxerces2-java media-player-info mesa-utils
10996 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
10997 nautilus-sendto-empathy openoffice.org-writer2latex
10998 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
10999 python-aptdaemon python-aptdaemon-gtk python-axiom
11000 python-beautifulsoup python-bugbuddy python-clientform
11001 python-coherence python-configobj python-crypto python-cupshelpers
11002 python-cupsutils python-eggtrayicon python-elementtree
11003 python-epsilon python-evolution python-feedparser python-gdata
11004 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11005 python-gtksourceview2 python-httplib2 python-louie python-mako
11006 python-markupsafe python-mechanize python-nevow python-notify
11007 python-opengl python-openssl python-pam python-pkg-resources
11008 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11009 python-tagpy python-twisted-bin python-twisted-conch
11010 python-twisted-core python-twisted-web python-utidylib python-webkit
11011 python-xdg python-zope.interface remmina remmina-plugin-data
11012 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11013 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11014 software-center svgalibg1 system-config-printer-udev
11015 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
11016 totem totem-coherence totem-mozilla totem-plugins
11017 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11019 </p
></blockquote
>
11021 Installed using apt-get, removed with aptitude
11023 <blockquote
><p
>
11024 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11025 epiphany-extensions epiphany-gecko evolution-exchange
11026 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11027 gedit-common gnome-app-install gnome-games gnome-games-data
11028 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11029 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11030 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11031 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
11032 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
11033 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
11034 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
11035 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11036 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11037 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11038 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
11039 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
11040 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11041 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11042 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11043 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11044 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
11045 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
11046 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
11047 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
11048 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
11049 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11050 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11051 sound-juicer swfdec-gnome system-config-printer totem-common
11052 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11053 </p
></blockquote
>
11055 <p
>Installed using aptitude, missing with apt-get
</p
>
11057 <blockquote
><p
>
11058 gstreamer0.10-gnomevfs
11059 </p
></blockquote
>
11061 <p
>Installed using aptitude, removed with apt-get
</p
>
11063 <blockquote
><p
>
11065 </p
></blockquote
>
11067 <p
>This is for KDE:
</p
>
11069 <p
>Installed using apt-get, missing with aptitude
</p
>
11071 <blockquote
><p
>
11072 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
11073 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11074 ghostscript-x git gnome-audio gnugo granatier gs-common
11075 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11076 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11077 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11078 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11079 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11080 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11081 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11082 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11083 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11084 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11085 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11086 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
11087 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11088 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11089 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11090 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11091 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11092 libkrossui4 libmailtools-perl libmime-tools-perl
11093 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11094 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11095 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11096 lirc luatex marble networkstatus noatun-plugins
11097 openoffice.org-writer2latex palapeli palapeli-data parley
11098 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11099 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11100 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11101 ttf-sazanami-gothic
11102 </p
></blockquote
>
11104 <p
>Installed using apt-get, removed with aptitude
</p
>
11106 <blockquote
><p
>
11107 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11108 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11109 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11110 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11111 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11112 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11113 kitchensync kiten kjumpingcube klatin klettres klickety klines
11114 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11115 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11116 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11117 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11118 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11119 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11120 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11121 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11122 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11123 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
11124 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
11125 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11126 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
11127 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
11128 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11129 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11130 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11131 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11132 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11133 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11134 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
11135 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
11136 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11137 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11138 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11139 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11140 </p
></blockquote
>
11142 <p
>Installed using aptitude, missing with apt-get
</p
>
11144 <blockquote
><p
>
11145 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11146 kdeartwork kdebase kdebase-apps kdebase-workspace
11147 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11148 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11149 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11150 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11151 xscreensaver-screensaver-bsod
11152 </p
></blockquote
>
11154 <p
>Installed using aptitude, removed with apt-get
</p
>
11156 <blockquote
><p
>
11157 kdebase-bin konq-plugins konqueror
11158 </p
></blockquote
>
11163 <title>Gnash buildbot slave and Debian kfreebsd
</title>
11164 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
11165 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
11166 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
11167 <description><p
>Answering
11168 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
11169 call from the Gnash project
</a
> for
11170 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
11171 current source, I have set up a virtual KVM machine on the Debian
11172 Edu/Skolelinux virtualization host to test the git source on
11173 Debian/Squeeze. I hope this can help the developers in getting new
11174 releases out more often.
</p
>
11176 <p
>As the developers want less main-stream build platforms tested to,
11177 I have considered setting up a
<a
11178 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
11179 machine as well. I have also considered using the kfreebsd
11180 architecture in Debian as a file server in NUUG to get access to the
5
11181 TB zfs volume we currently use to store DV video. Because of this, I
11182 finally got around to do a test installation of Debian/Squeeze with
11183 kfreebsd. Installation went fairly smooth, thought I noticed some
11184 visual glitches in the cdebconf dialogs (black cursor left on the
11185 screen at random locations). Have not gotten very far with the
11186 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11187 fatal problem. Have to spend some more time on it to see if it is
11188 useful as a file server for NUUG. Will try to find time to set up a
11189 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
11194 <title>Debian in
3D
</title>
11195 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
11196 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
11197 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
11198 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
11200 <p
>3D printing is just great. I just came across this Debian logo in
11202 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
11203 thingiverse blog
</a
>.
</p
>
11208 <title>Software updates
2010-
10-
24</title>
11209 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
11210 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
11211 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
11212 <description><p
>Some updates.
</p
>
11214 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
11215 raise money for the project is going well. The lower limit of
10
11216 signers was reached in
24 hours, and so far
13 people have signed it.
11217 More signers and more funding is most welcome, and I am really curious
11218 how far we can get before the time limit of December
24 is reached.
11221 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
11222 about what appear to be a great code coverage tool capable of
11223 generating code coverage stats without any changes to the source code.
11225 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
11226 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
11227 It is missing in Debian, but the git source built just fine in Squeeze
11228 after I installed libelf-dev, libdwarf-dev, pkg-config and
11229 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11230 solvable. I hope kcov make it into Debian soon.
</p
>
11232 <p
>Finally found time to wrap up the release notes for
<a
11233 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
11234 new alpha release of Debian Edu
</a
>, and just published the second
11235 alpha test release of the Squeeze based Debian Edu /
11236 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
11237 release. Give it a try if you need a complete linux solution for your
11238 school, including central infrastructure server, workstations, thin
11239 client servers and diskless workstations. A nice touch added
11240 yesterday is RDP support on the thin client servers, for windows
11241 clients to get a Linux desktop on request.
</p
>
11246 <title>Some notes on Flash in Debian and Debian Edu
</title>
11247 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
11248 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
11249 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
11250 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
11251 popularity-contest numbers
</a
>, the adobe-flashplugin package the
11252 second most popular used package that is missing in Debian. The sixth
11253 most popular is flashplayer-mozilla. This is a clear indication that
11254 working flash is important for Debian users. Around
10 percent of the
11255 users submitting data to popcon.debian.org have this package
11256 installed.
</p
>
11258 <p
>In the report written by Lars Risan in August
2008
11259 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
11260 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11261 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
11262 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
11263 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
11264 web sites require Flash to work, and lacking working Flash support in
11265 the web browser and the problems with installing it was perceived as a
11266 good reason to stay with Windows.
</p
>
11268 <p
>I once saw a funny and sad comment in a web forum, where Linux was
11269 said to be the retarded cousin that did not really understand
11270 everything you told him but could work fairly well. This was a
11271 comment regarding the problems Linux have with proprietary formats and
11272 non-standard web pages, and is sad because it exposes a fairly common
11273 understanding of whose fault it is if web pages that only work in for
11274 example Internet Explorer
6 fail to work on Firefox, and funny because
11275 it explain very well how annoying it is for users when Linux
11276 distributions do not work with the documents they receive or the web
11277 pages they want to visit.
</p
>
11279 <p
>This is part of the reason why I believe it is important for Debian
11280 and Debian Edu to have a well working Flash implementation in the
11281 distribution, to get at least popular sites as Youtube and Google
11282 Video to working out of the box. For Squeeze, Debian have the chance
11283 to include the latest version of Gnash that will make this happen, as
11284 the new release
0.8.8 was published a few weeks ago and is resting in
11285 unstable. The new version work with more sites that version
0.8.7.
11286 The Gnash maintainers have asked for a freeze exception, but the
11287 release team have not had time to reply to it yet. I hope they agree
11288 with me that Flash is important for the Debian desktop users, and thus
11289 accept the new package into Squeeze.
</p
>
11294 <title>Circular package dependencies harms apt recovery
</title>
11295 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
11296 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
11297 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
11298 <description><p
>I discovered this while doing
11299 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
11300 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
11301 in Debian still got circular dependencies, and it is often claimed
11302 that apt and aptitude should be able to handle this just fine, but
11303 some times these dependency loops causes apt to fail.
</p
>
11305 <p
>An example is from todays
11306 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
11307 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
11308 causes perl-modules to fail to upgrade. The cause is simple. If a
11309 package fail to unpack, then only part of packages with the circular
11310 dependency might end up being unpacked when unpacking aborts, and the
11311 ones already unpacked will fail to configure in the recovery phase
11312 because its dependencies are unavailable.
</p
>
11314 <p
>In this log, the problem manifest itself with this error:
</p
>
11316 <blockquote
><pre
>
11317 dpkg: dependency problems prevent configuration of perl-modules:
11318 perl-modules depends on perl (
>=
5.10.1-
1); however:
11319 Version of perl on system is
5.10.0-
19lenny
2.
11320 dpkg: error processing perl-modules (--configure):
11321 dependency problems - leaving unconfigured
11322 </pre
></blockquote
>
11324 <p
>The perl/perl-modules circular dependency is already
11325 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
11326 hopefully be solved as soon as possible, but it is not the only one,
11327 and each one of these loops in the dependency tree can cause similar
11328 failures. Of course, they only occur when there are bugs in other
11329 packages causing the unpacking to fail, but it is rather nasty when
11330 the failure of one package causes the problem to become worse because
11331 of dependency loops.
</p
>
11334 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
11335 tireless effort by Bill Allombert
</a
>, the number of circular
11337 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
11338 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
11340 <p
>Todays testing also exposed a bug in
11341 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
11342 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
11343 apt-get and aptitude, the latter possibly caused by some circular
11344 dependency. Reported both to BTS to try to get someone to look at
11350 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
11351 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
11352 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
11353 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
11354 <description><p
>This is a
11355 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
11357 <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
11359 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
11360 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
11362 <p
>As a step to try to see if it possible to merge the DNS and DHCP
11363 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11364 and dhcp3-server-ldap in Debian use the LDAP server. The two
11365 implementations are quite different in how they use LDAP.
</p
>
11367 To get this information, I started slapd with debugging enabled and
11368 dumped the debug output to a file to get the LDAP searches performed
11369 on a Debian Edu main-server. Here is a summary.
11371 <p
><strong
>powerdns
</strong
></p
>
11373 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
11374 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
11377 <p
>PowerDNS have two modes of operation using LDAP as its backend.
11378 One
"strict
" mode where the forward and reverse DNS lookups are done
11379 using the same LDAP objects, and a
"tree
" mode where the forward and
11380 reverse entries are in two different subtrees in LDAP with a structure
11381 based on the DNS names, as in tjener.intern and
11382 2.2.0.10.in-addr.arpa.
</p
>
11384 <p
>In tree mode, the server is set up to use a LDAP subtree as its
11385 base, and uses a
"base
" scoped search for the DNS name by adding
11386 "dc=tjener,dc=intern,
" to the base with a filter for
11387 "(associateddomain=tjener.intern)
" for the forward entry and
11388 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
11389 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
11390 forward entries, it is looking for attributes named dnsttl, arecord,
11391 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11392 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11393 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11394 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11395 spfrecord and modifytimestamp. For reverse entries it is looking for
11396 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11397 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11398 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11399 ldapsearch commands could look like this:
</p
>
11401 <blockquote
><pre
>
11402 ldapsearch -h ldap \
11403 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11404 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11405 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11406 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11407 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11408 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11410 ldapsearch -h ldap \
11411 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11412 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
11413 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11414 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11415 srvrecord naptrrecord modifytimestamp
11416 </pre
></blockquote
>
11418 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
11419 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11420 example LDAP objects used there. In addition to these objects, the
11421 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11422 also exist.
</p
>
11424 <blockquote
><pre
>
11425 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11427 objectclass: dnsdomain
11428 objectclass: domainrelatedobject
11431 associateddomain: tjener.intern
11433 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11435 objectclass: dnsdomain2
11436 objectclass: domainrelatedobject
11438 ptrrecord: tjener.intern
11439 associateddomain:
2.2.0.10.in-addr.arpa
11440 </pre
></blockquote
>
11442 <p
>In strict mode, the server behaves differently. When looking for
11443 forward DNS entries, it is doing a
"subtree
" scoped search with the
11444 same base as in the tree mode for a object with filter
11445 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
11446 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11447 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11448 naptrrecord and modifytimestamp. For reverse entires it also do a
11449 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
11450 and the requested attributes are associateddomain, dnsttl and
11451 modifytimestamp. In short, in strict mode the objects with ptrrecord
11452 go away, and the arecord attribute in the forward object is used
11455 <p
>The forward and reverse searches can be simulated using ldapsearch
11456 like this:
</p
>
11458 <blockquote
><pre
>
11459 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11460 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11461 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11462 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11463 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11464 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11466 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11467 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
11468 </pre
></blockquote
>
11470 <p
>In addition to the forward and reverse searches , there is also a
11471 search for SOA records, which behave similar to the forward and
11472 reverse lookups.
</p
>
11474 <p
>A thing to note with the PowerDNS behaviour is that it do not
11475 specify any objectclass names, and instead look for the attributes it
11476 need to generate a DNS reply. This make it able to work with any
11477 objectclass that provide the needed attributes.
</p
>
11479 <p
>The attributes are normally provided in the cosine (RFC
1274) and
11480 dnsdomain2 schemas. The latter is used for reverse entries like
11481 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
11483 <p
>In Debian Edu, we have created DNS objects using the object classes
11484 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11485 attributes) and domainrelatedobject (for associatedDomain). The use
11486 of structural object classes make it impossible to combine these
11487 classes with the object classes used by DHCP.
</p
>
11489 <p
>There are other schemas that could be used too, for example the
11490 dnszone structural object class used by Gosa and bind-sdb for the DNS
11491 attributes combined with the domainrelatedobject object class, but in
11492 this case some unused attributes would have to be included as well
11493 (zonename and relativedomainname).
</p
>
11495 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
11496 mode and not use any of the existing objectclasses (dnsdomain,
11497 dnsdomain2 and dnszone) when one want to combine the DNS information
11498 with DHCP information, and instead create a auxiliary object class
11499 defined something like this (using the attributes defined for
11500 dnsdomain and dnsdomain2 or dnszone):
</p
>
11502 <blockquote
><pre
>
11503 objectclass ( some-oid NAME
'dnsDomainAux
'
11506 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11507 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11508 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11509 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11510 A6Record $ DNAMERecord
11512 </pre
></blockquote
>
11514 <p
>This will allow any object to become a DNS entry when combined with
11515 the domainrelatedobject object class, and allow any entity to include
11516 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
11517 developers asking for their view on this schema and if they are
11518 interested in providing such schema with PowerDNS, and I hope my
11519 message will be accepted into their mailing list soon.
</p
>
11521 <p
><strong
>ISC dhcp
</strong
></p
>
11523 <p
>The DHCP server searches for specific objectclass and requests all
11524 the object attributes, and then uses the attributes it want. This
11525 make it harder to figure out exactly what attributes are used, but
11526 thanks to the working example in Debian Edu I can at least get an idea
11527 what is needed without having to read the source code.
</p
>
11529 <p
>In the DHCP server configuration, the LDAP base to use and the
11530 search filter to use to locate the correct dhcpServer entity is
11531 stored. These are the relevant entries from
11532 /etc/dhcp3/dhcpd.conf:
</p
>
11534 <blockquote
><pre
>
11535 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
11536 ldap-dhcp-server-cn
"dhcp
";
11537 </pre
></blockquote
>
11539 <p
>The DHCP server uses this information to nest all the DHCP
11540 configuration it need. The cn
"dhcp
" is located using the given LDAP
11541 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
11542 search result is this entry:
</p
>
11544 <blockquote
><pre
>
11545 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11548 objectClass: dhcpServer
11549 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11550 </pre
></blockquote
>
11552 <p
>The content of the dhcpServiceDN attribute is next used to locate the
11553 subtree with DHCP configuration. The DHCP configuration subtree base
11554 is located using a base scope search with base
"cn=DHCP
11555 Config,dc=skole,dc=skolelinux,dc=no
" and filter
11556 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
11557 The search result is this entry:
</p
>
11559 <blockquote
><pre
>
11560 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11563 objectClass: dhcpService
11564 objectClass: dhcpOptions
11565 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11566 dhcpStatements: ddns-update-style none
11567 dhcpStatements: authoritative
11568 dhcpOption: smtp-server code
69 = array of ip-address
11569 dhcpOption: www-server code
72 = array of ip-address
11570 dhcpOption: wpad-url code
252 = text
11571 </pre
></blockquote
>
11573 <p
>Next, the entire subtree is processed, one level at the time. When
11574 all the DHCP configuration is loaded, it is ready to receive requests.
11575 The subtree in Debian Edu contain objects with object classes
11576 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11577 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11578 and information about netmasks, dynamic range etc. Leaving out the
11579 details here because it is not relevant for the focus of my
11580 investigation, which is to see if it is possible to merge dns and dhcp
11581 related computer objects.
</p
>
11583 <p
>When a DHCP request come in, LDAP is searched for the MAC address
11584 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
11585 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
11586 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11587 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
11590 <blockquote
><pre
>
11591 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11594 objectClass: dhcpHost
11595 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11596 dhcpStatements: fixed-address hostname
11597 </pre
></blockquote
>
11599 <p
>There is less flexiblity in the way LDAP searches are done here.
11600 The object classes need to have fixed names, and the configuration
11601 need to be stored in a fairly specific LDAP structure. On the
11602 positive side, the invidiual dhcpHost entires can be anywhere without
11603 the DN pointed to by the dhcpServer entries. The latter should make
11604 it possible to group all host entries in a subtree next to the
11605 configuration entries, and this subtree can also be shared with the
11606 DNS server if the schema proposed above is combined with the dhcpHost
11607 structural object class.
11609 <p
><strong
>Conclusion
</strong
></p
>
11611 <p
>The PowerDNS implementation seem to be very flexible when it come
11612 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
11613 come to the the LDAP structure, the
"strict
" mode is very flexible,
11614 allowing DNS objects to be stored anywhere under the base cn specified
11615 in the configuration.
</p
>
11617 <p
>The DHCP implementation on the other hand is very inflexible, both
11618 regarding which LDAP schemas to use and which LDAP structure to use.
11619 I guess one could implement ones own schema, as long as the
11620 objectclasses and attributes have the names used, but this do not
11621 really help when the DHCP subtree need to have a fairly fixed
11622 structure.
</p
>
11624 <p
>Based on the observed behaviour, I suspect a LDAP structure like
11625 this might work for Debian Edu:
</p
>
11627 <blockquote
><pre
>
11629 cn=machine-info (dhcpService) - dhcpServiceDN points here
11630 cn=dhcp (dhcpServer)
11631 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11632 cn=
10.0.2.0 (dhcpSubnet)
11633 cn=group1 (dhcpGroup/dhcpOptions)
11634 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11635 cn=
192.168.0.0 (dhcpSubnet)
11636 cn=group1 (dhcpGroup/dhcpOptions)
11637 ou=machines - PowerDNS base points here
11638 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11639 </pre
></blockquote
>
11641 <P
>This is not tested yet. If the DHCP server require the dhcpHost
11642 entries to be in the dhcpGroup subtrees, the entries can be stored
11643 there instead of a common machines subtree, and the PowerDNS base
11644 would have to be moved one level up to the machine-info subtree.
</p
>
11646 <p
>The combined object under the machines subtree would look something
11647 like this:
</p
>
11649 <blockquote
><pre
>
11650 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11653 objectClass: dhcpHost
11654 objectclass: domainrelatedobject
11655 objectclass: dnsDomainAux
11656 associateddomain: hostname.intern
11657 arecord:
10.11.12.13
11658 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11659 dhcpStatements: fixed-address hostname.intern
11660 </pre
></blockquote
>
11662 </p
>One could even add the LTSP configuration associated with a given
11663 machine, as long as the required attributes are available in a
11664 auxiliary object class.
</p
>
11669 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
11670 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
11671 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
11672 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
11673 <description><p
>For a while now, I have wanted to find a way to change the DNS and
11674 DHCP services in Debian Edu to use the same LDAP objects for a given
11675 computer, to avoid the possibility of having a inconsistent state for
11676 a computer in LDAP (as in DHCP but no DNS entry or the other way
11677 around) and make it easier to add computers to LDAP.
</p
>
11679 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
11680 information finally found a solution that seem to work.
</p
>
11682 <p
>The old setup required three LDAP objects for a given computer.
11683 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11684 we switch powerdns to use its strict LDAP method (ldap-method=strict
11685 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11686 merged into one while making it impossible to transfer the reverse map
11687 to a slave DNS server.
</p
>
11689 <p
>If we also replace the object class used to get the DNS related
11690 attributes to one allowing these attributes to be combined with the
11691 dhcphost object class, we can merge the DNS and DHCP entries into one.
11692 I
've written such object class in the dnsdomainaux.schema file (need
11693 proper OIDs, but that is a minor issue), and tested the setup. It
11694 seem to work.
</p
>
11696 <p
>With this test setup in place, we can get away with one LDAP object
11697 for both DNS and DHCP, and even the LTSP configuration I suggested in
11698 an earlier email. The combined LDAP object will look something like
11701 <blockquote
><pre
>
11702 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11704 objectClass: dhcphost
11705 objectclass: domainrelatedobject
11706 objectclass: dnsdomainaux
11707 associateddomain: hostname.intern
11708 arecord:
10.11.12.13
11709 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
11710 dhcpstatements: fixed-address hostname
11712 </pre
></blockquote
>
11714 <p
>The DNS server uses the associateddomain and arecord entries, while
11715 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11716 before asking DNS to resolve the fixed-adddress. LTSP will use
11717 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
11719 <p
>I am not yet sure if I can get the DHCP server to look for its
11720 dhcphost in a different location, to allow us to put the objects
11721 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
11722 that. If I can
't figure out a way to do that, we can still get rid of
11723 the hosts subtree and move all its content into the DHCP Config tree
11724 (which probably should be renamed to be more related to the new
11725 content. I suspect cn=dnsdhcp,ou=services or something like that
11726 might be a good place to put it.
</p
>
11728 <p
>If you want to help out with implementing this for Debian Edu,
11729 please contact us on debian-edu@lists.debian.org.
</p
>
11734 <title>Idea for storing LTSP configuration in LDAP
</title>
11735 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
11736 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
11737 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
11738 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
11739 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11740 clients, and that this can be used to fetch configuration from LDAP if
11741 Debian Edu choose to store configuration there.
</p
>
11743 <p
>Armed with this information, I got inspired and wrote a test module
11744 to get configuration from LDAP. The idea is to look up the MAC
11745 address of the client in LDAP, and look for attributes on the form
11746 ltspconfigsetting=value, and use this to export SETTING=value to the
11747 LTSP clients.
</p
>
11749 <p
>The goal is to be able to store the LTSP configuration attributes
11750 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
11751 allowing us to store all information about a computer in one place.
</p
>
11753 <p
>This is a untested draft implementation, and I welcome feedback on
11754 this approach. A real LDAP schema for the ltspClientAux objectclass
11755 need to be written. Comments, suggestions, etc?
</p
>
11757 <blockquote
><pre
>
11758 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11760 # Fetch LTSP client settings from LDAP based on MAC address
11762 # Uses ethernet address as stored in the dhcpHost objectclass using
11763 # the dhcpHWAddress attribute or ethernet address stored in the
11764 # ieee802Device objectclass with the macAddress attribute.
11766 # This module is written to be schema agnostic, and only depend on the
11767 # existence of attribute names.
11769 # The LTSP configuration variables are saved directly using a
11770 # ltspConfig prefix and uppercasing the rest of the attribute name.
11771 # To set the SERVER variable, set the ltspConfigServer attribute.
11773 # Some LDAP schema should be created with all the relevant
11774 # configuration settings. Something like this should work:
11776 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
11779 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11781 LDAPSERVER=$(debian-edu-ldapserver)
11782 if [
"$LDAPSERVER
" ] ; then
11783 LDAPBASE=$(debian-edu-ldapserver -b)
11784 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
11785 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
11786 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
11787 grep
'^ltspConfig
' | while read attr value ; do
11788 # Remove prefix and convert to upper case
11789 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
11790 # bass value on to clients
11791 eval
"$attr=$value; export $attr
"
11795 </pre
></blockquote
>
11797 <p
>I
'm not sure this shell construction will work, because I suspect
11798 the while block might end up in a subshell causing the variables set
11799 there to not show up in ltsp-config, but if that is the case I am sure
11800 the code can be restructured to make sure the variables are passed on.
11801 I expect that can be solved with some testing. :)
</p
>
11803 <p
>If you want to help out with implementing this for Debian Edu,
11804 please contact us on debian-edu@lists.debian.org.
</p
>
11806 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
11807 configuration in LDAP that was created around year
2000 by
11808 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
11809 Xperience, Inc.,
2000</a
>. I found its
11810 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
11811 personal home page over at redhat.com.
</p
>
11816 <title>jXplorer, a very nice LDAP GUI
</title>
11817 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
11818 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
11819 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
11820 <description><p
>Since
11821 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
11822 last post
</a
> about available LDAP tools in Debian, I was told about a
11823 LDAP GUI that is even better than luma. The java application
11824 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
11825 moving LDAP objects and subtrees using drag-and-drop, and can
11826 authenticate using Kerberos. I have only tested the Kerberos
11827 authentication, but do not have a LDAP setup allowing me to rewrite
11828 LDAP with my test user yet. It is
11829 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
11830 Debian
</a
> testing and unstable at the moment. The only problem I
11831 have with it is how it handle errors. If something go wrong, its
11832 non-intuitive behaviour require me to go through some query work list
11833 and remove the failing query. Nothing big, but very annoying.
</p
>
11838 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
11839 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
11840 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
11841 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
11842 <description><p
>Here is a short update on my
<a
11843 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
11844 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
11845 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
11846 not reporting the status for KDE, because the upgrade crashes when
11847 aptitude try because of missing conflicts
11848 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
11849 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
11851 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
11852 complete list of the installed packages. Based on this I see these
11853 differences when I did a test run today. As usual, I do not really
11854 know what the correct set of packages would be, but thought it best to
11855 publish the difference.
</p
>
11857 <p
>Installed using apt-get, missing with aptitude
</p
>
11859 <blockquote
><p
>
11860 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
11861 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
11862 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11863 libgtksourceview-common libpt-
1.10.10-plugins-alsa
11864 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11865 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11866 python-
4suite-xml python-eggtrayicon python-gtkhtml2
11867 python-gtkmozembed svgalibg1 xserver-xephyr zip
11868 </p
></blockquote
>
11870 <p
>Installed using apt-get, removed with aptitude
</p
>
11872 <blockquote
><p
>
11873 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11874 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11875 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
11876 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
11877 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
11878 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
11879 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11880 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11881 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11882 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
11883 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
11884 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
11885 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11886 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
11887 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11888 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
11889 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
11890 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11891 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11892 mysql-common swfdec-gnome totem-gstreamer wodim
11893 </p
></blockquote
>
11895 <p
>Installed using aptitude, missing with apt-get
</p
>
11897 <blockquote
><p
>
11898 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11899 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11900 xserver-xorg-input-all xserver-xorg-input-evdev
11901 xserver-xorg-input-kbd xserver-xorg-input-mouse
11902 xserver-xorg-input-synaptics xserver-xorg-video-all
11903 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11904 xserver-xorg-video-chips xserver-xorg-video-cirrus
11905 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11906 xserver-xorg-video-glint xserver-xorg-video-i128
11907 xserver-xorg-video-i740 xserver-xorg-video-mach64
11908 xserver-xorg-video-mga xserver-xorg-video-neomagic
11909 xserver-xorg-video-nouveau xserver-xorg-video-nv
11910 xserver-xorg-video-r128 xserver-xorg-video-radeon
11911 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11912 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11913 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11914 xserver-xorg-video-sis xserver-xorg-video-sisusb
11915 xserver-xorg-video-tdfx xserver-xorg-video-tga
11916 xserver-xorg-video-trident xserver-xorg-video-tseng
11917 xserver-xorg-video-vesa xserver-xorg-video-vmware
11918 xserver-xorg-video-voodoo
11919 </p
></blockquote
>
11921 <p
>Installed using aptitude, removed with apt-get
</p
>
11923 <blockquote
><p
>
11924 deskbar-applet xserver-xorg xserver-xorg-core
11925 xserver-xorg-input-wacom xserver-xorg-video-intel
11926 xserver-xorg-video-openchrome
11927 </p
></blockquote
>
11929 <p
>I was told on IRC that the xorg-xserver package was
11930 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
11931 in git
</a
> today to try to get apt-get to not remove xorg completely.
11932 No idea when it hits Squeeze, but when it does I hope it will reduce
11933 the difference somewhat.
11938 <title>LUMA, a very nice LDAP GUI
</title>
11939 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
11940 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
11941 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
11942 <description><p
>The last few days I have been looking into the status of the LDAP
11943 directory in Debian Edu, and in the process I started to miss a GUI
11944 tool to browse the LDAP tree. The only one I was able to find in
11945 Debian/Squeeze and Lenny is
11946 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
11947 be a great tool to get a overview of the current LDAP directory
11948 populated by default in Skolelinux. Thanks to it, I have been able to
11949 find empty and obsolete subtrees, misplaced objects and duplicate
11950 objects. It will be installed by default in Debian/Squeeze. If you
11951 are working with LDAP, give it a go. :)
</p
>
11953 <p
>I did notice one problem with it I have not had time to report to
11954 the BTS yet. There is no .desktop file in the package, so the tool do
11955 not show up in the Gnome and KDE menus, but only deep down in in the
11956 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11957 released.
</p
>
11959 <p
>I have not yet been able to get it to modify the tree yet. I would
11960 like to move objects and remove subtrees directly in the GUI, but have
11961 not found a way to do that with LUMA yet. So in the mean time, I use
11962 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
11964 <p
>If you have tips on other GUI tools for LDAP that might be useful
11965 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
11967 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
11968 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
11969 useful GUI alternative. It seem like a good tool, but is unmaintained
11970 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11971 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
11976 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
11977 <link>https://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>
11978 <guid isPermaLink=
"true">https://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>
11979 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
11980 <description><p
>A while back, I
11981 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
11982 about the fact
</a
> that it is not possible with the provided schemas
11983 for storing DNS and DHCP information in LDAP to combine the two sets
11984 of information into one LDAP object representing a computer.
</p
>
11986 <p
>In the mean time, I discovered that a simple fix would be to make
11987 the dhcpHost object class auxiliary, to allow it to be combined with
11988 the dNSDomain object class, and thus forming one object for one
11989 computer when storing both DHCP and DNS information in LDAP.
</p
>
11991 <p
>If I understand this correctly, it is not safe to do this change
11992 without also changing the assigned number for the object class, and I
11993 do not know enough about LDAP schema design to do that properly for
11994 Debian Edu.
</p
>
11996 <p
>Anyway, for future reference, this is how I believe we could change
11998 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
11999 schema
</a
> to solve at least part of the problem with the LDAP schemas
12000 available today from IETF.
</p
>
12003 --- dhcp.schema (revision
65192)
12004 +++ dhcp.schema (working copy)
12005 @@ -
376,
7 +
376,
7 @@
12006 objectclass (
2.16.840.1.113719.1.203.6.6
12007 NAME
'dhcpHost
'
12008 DESC
'This represents information about a particular client
'
12010 + SUP top AUXILIARY
12012 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12013 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
12016 <p
>I very much welcome clues on how to do this properly for Debian
12017 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12018 package, and should thus be free to rewrite it as we see fit.
</p
>
12020 <p
>If you want to help out with implementing this for Debian Edu,
12021 please contact us on debian-edu@lists.debian.org.
</p
>
12026 <title>Calling tasksel like the installer, while still getting useful output
</title>
12027 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
12028 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
12029 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
12030 <description><p
>A few times I have had the need to simulate the way tasksel
12031 installs packages during the normal debian-installer run. Until now,
12032 I have ended up letting tasksel do the work, with the annoying problem
12033 of not getting any feedback at all when something fails (like a
12034 conffile question from dpkg or a download that fails), using code like
12037 <blockquote
><pre
>
12038 export DEBIAN_FRONTEND=noninteractive
12039 tasksel --new-install
12040 </pre
></blockquote
>
12042 This would invoke tasksel, let its automatic task selection pick the
12043 tasks to install, and continue to install the requested tasks without
12044 any output what so ever.
12046 Recently I revisited this problem while working on the automatic
12047 package upgrade testing, because tasksel would some times hang without
12048 any useful feedback, and I want to see what is going on when it
12049 happen. Then it occured to me, I can parse the output from tasksel
12050 when asked to run in test mode, and use that aptitude command line
12051 printed by tasksel then to simulate the tasksel run. I ended up using
12054 <blockquote
><pre
>
12055 export DEBIAN_FRONTEND=noninteractive
12056 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
12058 </pre
></blockquote
>
12060 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
12061 --without-recommends -o APT::Install-Recommends=no -y install
12062 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12063 ~pimportant
</tt
>", which will install the gnome desktop task, the
12064 laptop task and all packages with priority standard , required and
12065 important, just like tasksel would have done it during
12066 installation.
</p
>
12068 <p
>A better approach is probably to extend tasksel to be able to
12069 install packages without using debconf-apt-progress, for use cases
12070 like this.
</p
>
12075 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
12076 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
12077 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
12078 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
12079 <description><p
>My
12080 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
12081 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
12082 finally made the upgrade logs available from
12083 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
12084 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12085 apt and aptitude, and found their differences interesting. This time
12086 I will only focus on their removal plans.
</p
>
12088 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
12089 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
12090 surprising part is that it want to remove xorg and all
12091 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12092 sure why. When asking aptitude to do the same, it want to remove
129
12093 packages, but most of them are library packages I suspect are no
12094 longer needed. Both of them want to remove bluetooth packages, which
12095 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
12097 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
12098 which seem like a bad idea and xorg the same way as with Gnome. Asking
12099 aptitude for the same, it wants to remove
192 packages, none which are
12100 too surprising.
</p
>
12102 <p
>I guess the removal of xorg during upgrades should be investigated
12103 and avoided, and perhaps others as well. Here are the complete list
12104 of planned removals. The complete logs is available from the URL
12105 above. Note if you want to repeat these tests, that the upgrade test
12106 for kde+apt-get hung in the tasksel setup because of dpkg asking
12107 conffile questions. No idea why. I worked around it by using
12108 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
12109 continue.
</p
>
12111 <p
><b
>apt-get gnome
72</b
>
12112 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
12113 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12114 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
12115 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12116 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12117 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12118 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12119 xserver-xorg-input-kbd xserver-xorg-input-mouse
12120 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12121 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12122 xserver-xorg-video-ati xserver-xorg-video-chips
12123 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12124 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12125 xserver-xorg-video-glint xserver-xorg-video-i128
12126 xserver-xorg-video-i740 xserver-xorg-video-imstt
12127 xserver-xorg-video-intel xserver-xorg-video-mach64
12128 xserver-xorg-video-mga xserver-xorg-video-neomagic
12129 xserver-xorg-video-nsc xserver-xorg-video-nv
12130 xserver-xorg-video-openchrome xserver-xorg-video-r128
12131 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12132 xserver-xorg-video-rendition xserver-xorg-video-s3
12133 xserver-xorg-video-s3virge xserver-xorg-video-savage
12134 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12135 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12136 xserver-xorg-video-tga xserver-xorg-video-trident
12137 xserver-xorg-video-tseng xserver-xorg-video-v4l
12138 xserver-xorg-video-vesa xserver-xorg-video-vga
12139 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
12140 xulrunner-
1.9-gnome-support
</p
>
12142 <p
><b
>aptitude gnome
129</b
>
12144 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
12145 djvulibre-desktop finger gnome-app-install gnome-mount
12146 gnome-network-admin gnome-spell gnome-vfs-obexftp
12147 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12148 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12149 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12150 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
12151 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
12152 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
12153 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
12154 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
12155 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
12156 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
12157 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
12158 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
12159 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12160 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
12161 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
12162 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
12163 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
12164 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
12165 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12166 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12167 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12168 openoffice.org-writer2latex openssl-blacklist p7zip
12169 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
12170 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12171 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12172 swfdec-mozilla totem-gstreamer update-manager wodim
12173 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12174 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12177 <p
><b
>apt-get kde
82</b
>
12179 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12180 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12181 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12182 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12183 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12184 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12185 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12186 xserver-xorg-input-kbd xserver-xorg-input-mouse
12187 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12188 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12189 xserver-xorg-video-ati xserver-xorg-video-chips
12190 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12191 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12192 xserver-xorg-video-glint xserver-xorg-video-i128
12193 xserver-xorg-video-i740 xserver-xorg-video-imstt
12194 xserver-xorg-video-intel xserver-xorg-video-mach64
12195 xserver-xorg-video-mga xserver-xorg-video-neomagic
12196 xserver-xorg-video-nsc xserver-xorg-video-nv
12197 xserver-xorg-video-openchrome xserver-xorg-video-r128
12198 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12199 xserver-xorg-video-rendition xserver-xorg-video-s3
12200 xserver-xorg-video-s3virge xserver-xorg-video-savage
12201 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12202 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12203 xserver-xorg-video-tga xserver-xorg-video-trident
12204 xserver-xorg-video-tseng xserver-xorg-video-v4l
12205 xserver-xorg-video-vesa xserver-xorg-video-vga
12206 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
12208 <p
><b
>aptitude kde
192</b
>
12209 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
12210 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12211 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12212 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12213 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12214 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12215 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12216 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12217 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12218 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12219 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12220 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12221 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12222 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12223 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12224 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12225 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12226 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12227 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
12228 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12229 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12230 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
12231 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12232 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12233 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12234 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12235 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12236 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
12237 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
12238 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12239 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12240 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12241 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12242 texlive-common texlive-doc-base texlive-fonts-recommended
12243 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12244 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12245 xulrunner-
1.9</p
>
12251 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
12252 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
12253 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
12254 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
12255 <description><p
>The last few days I have done some upgrade testing in Debian, to
12256 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12257 have been discovered and reported in the process
12258 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
12259 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
12260 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
12261 kdebase-workspace-data), and to get a more regular testing going on, I
12262 am working on a script to automate the test.
</p
>
12264 <p
>The idea is to create a Lenny chroot and use tasksel to install a
12265 Gnome or KDE desktop installation inside the chroot before upgrading
12266 it. To ensure no services are started in the chroot, a policy-rc.d
12267 script is inserted. To make sure tasksel believe it is to install a
12268 desktop on a laptop, the tasksel tests are replaced in the chroot
12269 (only acceptable because this is a throw-away chroot).
</p
>
12271 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12272 currently always fail because udev refuses to upgrade with the kernel
12273 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12274 is created. The bug report
12275 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
12276 this problem do not trigger in a chroot, but I touch the file anyway
12277 to make sure the upgrade go well. Testing on virtual and real
12278 hardware have failed me because of udev so far, and creating this file
12279 do the trick in such settings anyway. This is a
12280 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
12281 issue
</a
> and the current udev behaviour is intended by the udev
12282 maintainer because he lack the resources to rewrite udev to keep
12283 working with old kernels or something like that. I really wish the
12284 udev upstream would keep udev backwards compatible, to avoid such
12285 upgrade problem, but given that they fail to do so, I guess
12286 documenting the way out of this mess is the best option we got for
12287 Debian Squeeze.
</p
>
12289 <p
>Anyway, back to the task at hand, testing upgrades. This test
12290 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
12293 <blockquote
><pre
>
12297 if [
"$
1" ] ; then
12306 exec
&lt; /dev/null
12308 mirror=http://ftp.skolelinux.org/debian
12309 tmpdir=chroot-$from-upgrade-$to-$desktop
12311 debootstrap $from $tmpdir $mirror
12312 chroot $tmpdir aptitude update
12313 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
12317 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12319 umount $tmpdir/proc
12321 mount -t proc proc $tmpdir/proc
12322 # Make sure proc is unmounted also on failure
12323 trap exit_cleanup EXIT INT
12325 chroot $tmpdir aptitude -y install debconf-utils
12327 # Make sure tasksel autoselection trigger. It need the test scripts
12328 # to return the correct answers.
12329 echo tasksel tasksel/desktop multiselect $desktop | \
12330 chroot $tmpdir debconf-set-selections
12332 # Include the desktop and laptop task
12333 for test in desktop laptop ; do
12334 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
12338 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12341 DEBIAN_FRONTEND=noninteractive
12342 DEBIAN_PRIORITY=critical
12343 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12344 chroot $tmpdir tasksel --new-install
12346 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
12347 chroot $tmpdir aptitude update
12348 touch $tmpdir/etc/udev/kernel-upgrade
12349 chroot $tmpdir aptitude -y dist-upgrade
12351 </pre
></blockquote
>
12353 <p
>I suspect it would be useful to test upgrades with both apt-get and
12354 with aptitude, but I have not had time to look at how they behave
12355 differently so far. I hope to get a cron job running to do the test
12356 regularly and post the result on the web. The Gnome upgrade currently
12357 work, while the KDE upgrade fail because of the bug in
12358 kdebase-workspace-data
</p
>
12360 <p
>I am not quite sure what kind of extract from the huge upgrade logs
12361 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
12362 post, so I will refrain from trying. I can report that for Gnome,
12363 aptitude report
760 packages upgraded,
448 newly installed,
129 to
12364 remove and
1 not upgraded and
1024MB need to be downloaded while for
12365 KDE the same numbers are
702 packages upgraded,
507 newly installed,
12366 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
12368 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
12369 is able to migrate to dependency based boot sequencing and parallel
12370 booting without a hitch. Was unsure if there were still bugs with
12371 packages failing to clean up their obsolete init.d script during
12372 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12373 packages.
</p
>
12378 <title>Upstart or sysvinit - as init.d scripts see it
</title>
12379 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
12380 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
12381 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
12382 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
12383 scripts to migrate (some of) their operations to upstart job while
12384 keeping the init.d for hurd and kfreebsd. The packages with such
12385 needs will need a way to get their init.d scripts to behave
12386 differently when used with sysvinit and with upstart. Because of
12387 this, I had a look at the environment variables set when a init.d
12388 script is running under upstart, and when it is not.
</p
>
12390 <p
>With upstart, I notice these environment variables are set when a
12391 script is started from rcS.d/ (ignoring some irrelevant ones like
12392 COLUMNS):
</p
>
12394 <blockquote
><pre
>
12400 UPSTART_EVENTS=startup
12402 UPSTART_JOB=rc-sysinit
12403 </pre
></blockquote
>
12405 <p
>With sysvinit, these environment variables are set for the same
12408 <blockquote
><pre
>
12409 INIT_VERSION=sysvinit-
2.88
12414 </pre
></blockquote
>
12416 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
12417 sysvinit are not set by upstart. Not sure if it is intentional or not
12418 to not be compatible with sysvinit in this regard.
</p
>
12420 <p
>For scripts needing to behave differently when upstart is used,
12421 looking for the UPSTART_JOB environment variable seem to be a good
12427 <title>A manual for standards wars...
</title>
12428 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
12429 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
12430 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
12431 <description><p
>Via the
12432 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
12433 of Rob Weir
</a
> I came across the very interesting essay named
12434 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
12435 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
12436 following the standards wars of today.
</p
>
12441 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
12442 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
12443 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
12444 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
12445 <description><p
>When using sitesummary at a site to track machines, it is possible
12446 to get a list of the machine types in use thanks to the DMI
12447 information extracted from each machine. The script to do so is
12448 included in the sitesummary package, and here is example output from
12449 the Skolelinux build servers:
</p
>
12451 <blockquote
><pre
>
12452 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12454 Dell Computer Corporation
1
12457 eserver xSeries
345 -[
8670M1X]-
1
12461 </pre
></blockquote
>
12463 <p
>The quality of the report depend on the quality of the DMI tables
12464 provided in each machine. Here there are Intel machines without model
12465 information listed with Intel as vendor and no model, and virtual Xen
12466 machines listed as [no-dmi-info]. One can add -l as a command line
12467 option to list the individual machines.
</p
>
12469 <p
>A larger list is
12470 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
12471 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
12472 provide the basic sitesummary report publicly. In their report there
12473 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
12474 their machines, and as sitesummary is available in both distributions,
12475 it is trivial to get all of them to report to the same central
12476 collector.
</p
>
12481 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
12482 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12483 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</guid>
12484 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
12485 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
12486 start at boot when an NVidia video card is used is handled. The
12487 problem seem to be that the nvidia X.org driver uses a long time to
12488 initialize, and this duration is longer than kdm is configured to
12491 <p
>I came across two bugs related to this issue,
12492 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
12493 against initscripts and passed on to nvidia-glx when it became obvious
12494 that the nvidia drivers were involved, and
12495 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
12496 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
12498 <p
>To me, it seem that no-one is interested in actually solving the
12499 problem nvidia video card owners experience and make sure the Debian
12500 distribution work out of the box for these users. The nvidia driver
12501 maintainers expect kdm to be set up to wait longer, while kdm expect
12502 the nvidia driver maintainers to fix the driver to start faster, and
12503 while they wait for each other I guess the users end up switching to a
12504 distribution that work for them. I have no idea what the solution is,
12505 but I am pretty sure that waiting for each other is not it.
</p
>
12507 <p
>I wonder why we end up handling bugs this way.
</p
>
12512 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
12513 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
12514 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
12515 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
12516 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
12517 The feature seem to hold up pretty well, but three fairly serious
12518 issues are known and should be solved:
12520 <p
><ul
>
12522 <li
>The wicd package seen to
12523 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
12524 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
12525 parallel booting is enabled. No idea why, but the wicd maintainer
12526 seem to be on the case.
</li
>
12528 <li
>The nvidia X driver seem to
12529 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
12530 triggered more easily when parallel booting is in effect. The
12531 maintainer is on the case.
</li
>
12533 <li
>The sysv-rc package fail to properly enable dependency based boot
12534 sequencing (the shutdown is broken) when old file-rc users
12535 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
12536 sysv-rc. One way to solve it would be for file-rc to create
12537 /etc/init.d/.legacy-bootordering, and another is to try to make
12538 sysv-rc more robust. Will investigate some more and probably upload a
12539 workaround in sysv-rc to help those trying to move from file-rc to
12540 sysv-rc get a working shutdown.
</li
>
12542 </ul
></p
>
12544 <p
>All in all not many surprising issues, and all of them seem
12545 solvable before Squeeze is released. In addition to these there are
12546 some packages with bugs in their dependencies and run level settings,
12547 which I expect will be fixed in a reasonable time span.
</p
>
12549 <p
>If you report any problems with dependencies in init.d scripts to
12550 the BTS, please usertag the report to get it to show up at
12551 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12552 list of usertagged bugs related to this
</a
>.
</p
>
12554 <p
>Update: Correct bug number to file-rc issue.
</p
>
12559 <title>More flexible firmware handling in debian-installer
</title>
12560 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
12561 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
12562 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
12563 <description><p
>After a long break from debian-installer development, I finally
12564 found time today to return to the project. Having to spend less time
12565 working dependency based boot in debian, as it is almost complete now,
12566 definitely helped freeing some time.
</p
>
12568 <p
>A while back, I ran into a problem while working on Debian Edu. We
12569 include some firmware packages on the Debian Edu CDs, those needed to
12570 get disk and network controllers working. Without having these
12571 firmware packages available during installation, it is impossible to
12572 install Debian Edu on the given machine, and because our target group
12573 are non-technical people, asking them to provide firmware packages on
12574 an external medium is a support pain. Initially, I expected it to be
12575 enough to include the firmware packages on the CD to get
12576 debian-installer to find and use them. This proved to be wrong.
12577 Next, I hoped it was enough to symlink the relevant firmware packages
12578 to some useful location on the CD (tried /cdrom/ and
12579 /cdrom/firmware/). This also proved to not work, and at this point I
12580 found time to look at the debian-installer code to figure out what was
12581 going to work.
</p
>
12583 <p
>The firmware loading code is in the hw-detect package, and a closer
12584 look revealed that it would only look for firmware packages outside
12585 the installation media, so the CD was never checked for firmware
12586 packages. It would only check USB sticks, floppies and other
12587 "external
" media devices. Today I changed it to also look in the
12588 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12589 solve the problem I ran into with Debian edu. I also changed it to
12590 look in /firmware/, to make sure the installer also find firmware
12591 provided in the initrd when booting the installer via PXE, to allow us
12592 to provide the same feature in the PXE setup included in Debian
12595 <p
>To make sure firmware deb packages with a license questions are not
12596 activated without asking if the license is accepted, I extended
12597 hw-detect to look for preinst scripts in the firmware packages, and
12598 run these before activating the firmware during installation. The
12599 license question is asked using debconf in the preinst, so this should
12600 solve the issue for the firmware packages I have looked at so far.
</p
>
12602 <p
>If you want to discuss the details of these features, please
12603 contact us on debian-boot@lists.debian.org.
</p
>
12608 <title>Parallellized boot is now the default in Debian/unstable
</title>
12609 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
12610 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
12611 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
12612 <description><p
>Since this evening, parallel booting is the default in
12613 Debian/unstable for machines using dependency based boot sequencing.
12614 Apparently the testing of concurrent booting has been wider than
12615 expected, if I am to believe the
12616 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12617 on debian-devel@
</a
>, and I concluded a few days ago to move forward
12618 with the feature this weekend, to give us some time to detect any
12619 remaining problems before Squeeze is frozen. If serious problems are
12620 detected, it is simple to change the default back to sequential boot.
12621 The upload of the new sysvinit package also activate a new upstream
12624 More information about
12625 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12626 based boot sequencing
</a
> is available from the Debian wiki. It is
12627 currently possible to disable parallel booting when one run into
12628 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
12630 <blockquote
><pre
>
12632 </pre
></blockquote
>
12634 <p
>If you report any problems with dependencies in init.d scripts to
12635 the BTS, please usertag the report to get it to show up at
12636 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12637 list of usertagged bugs related to this
</a
>.
</p
>
12642 <title>Sitesummary tip: Listing MAC address of all clients
</title>
12643 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
12644 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
12645 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
12646 <description><p
>In the recent Debian Edu versions, the
12647 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
12648 system
</a
> is used to keep track of the machines in the school
12649 network. Each machine will automatically report its status to the
12650 central server after boot and once per night. The network setup is
12651 also reported, and using this information it is possible to get the
12652 MAC address of all network interfaces in the machines. This is useful
12653 to update the DHCP configuration.
</p
>
12655 <p
>To give some idea how to use sitesummary, here is a one-liner to
12656 ist all MAC addresses of all machines reporting to sitesummary. Run
12657 this on the collector host:
</p
>
12659 <blockquote
><pre
>
12660 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
12661 </pre
></blockquote
>
12663 <p
>This will list all MAC addresses assosiated with all machine, one
12664 line per machine and with space between the MAC addresses.
</p
>
12666 <p
>To allow system administrators easier job at adding static DHCP
12667 addresses for hosts, it would be possible to extend this to fetch
12668 machine information from sitesummary and update the DHCP and DNS
12669 tables in LDAP using this information. Such tool is unfortunately not
12670 written yet.
</p
>
12675 <title>systemd, an interesting alternative to upstart
</title>
12676 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
12677 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
12678 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
12679 <description><p
>The last few days a new boot system called
12680 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
12682 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
12684 to the free software world. I have not yet had time to play around
12685 with it, but it seem to be a very interesting alternative to
12686 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
12687 a good alternative for Debian when we are able to switch to an event
12688 based boot system. Tollef is
12689 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
12690 systemd into Debian, and I look forward to seeing how well it work. I
12691 like the fact that systemd handles init.d scripts with dependency
12692 information natively, allowing them to run in parallel where upstart
12693 at the moment do not.
</p
>
12695 <p
>Unfortunately do systemd have the same problem as upstart regarding
12696 platform support. It only work on recent Linux kernels, and also need
12697 some new kernel features enabled to function properly. This means
12698 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12699 system. Not sure how that will be handled if systemd proves to be the
12700 way forward.
</p
>
12702 <p
>In the mean time, based on the
12703 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12704 on debian-devel@
</a
> regarding parallel booting in Debian, I have
12705 decided to enable full parallel booting as the default in Debian as
12706 soon as possible (probably this weekend or early next week), to see if
12707 there are any remaining serious bugs in the init.d dependencies. A
12708 new version of the sysvinit package implementing this change is
12709 already in experimental. If all go well, Squeeze will be released
12710 with parallel booting enabled by default.
</p
>
12715 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
12716 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
12717 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
12718 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
12719 <description><p
>These days, the init.d script dependencies in Squeeze are quite
12720 complete, so complete that it is actually possible to run all the
12721 init.d scripts in parallell based on these dependencies. If you want
12722 to test your Squeeze system, make sure
12723 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12724 based boot sequencing
</a
> is enabled, and add this line to
12725 /etc/default/rcS:
</p
>
12727 <blockquote
><pre
>
12728 CONCURRENCY=makefile
12729 </pre
></blockquote
>
12731 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
12732 scripts in parallel using the dependency information stored in
12733 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12734 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12735 to try to start the kdm and gdm scripts as early as possible, and will
12736 start the facilities required by kdm or gdm as early as possible to
12737 make this happen.
</p
>
12739 <p
>Give it a try, and see if you like the result. If some services
12740 fail to start properly, it is most likely because they have incomplete
12741 init.d script dependencies in their startup script (or some of their
12742 dependent scripts have incomplete dependencies). Report bugs and get
12743 the package maintainers to fix it. :)
</p
>
12745 <p
>Running scripts in parallel could be the default in Debian when we
12746 manage to get the init.d script dependencies complete and correct. I
12747 expect we will get there in Squeeze+
1, if we get manage to test and
12748 fix the remaining issues.
</p
>
12750 <p
>If you report any problems with dependencies in init.d scripts to
12751 the BTS, please usertag the report to get it to show up at
12752 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12753 list of usertagged bugs related to this
</a
>.
</p
>
12758 <title>Debian has switched to dependency based boot sequencing
</title>
12759 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
12760 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
12761 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
12762 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
12763 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
12764 have been migrated to using dependency based boot sequencing. This
12765 conclude work me and others have been doing for the last three days.
12766 It feels great to see this finally part of the default Debian
12767 installation. Now we just need to weed out the last few problems that
12768 are bound to show up, to get everything ready for Squeeze.
</p
>
12770 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
12771 fixing the more fundamental problem of handing the event based
12772 non-predictable kernel in the early boot.
</p
>
12777 <title>Taking over sysvinit development
</title>
12778 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
12779 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
12780 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
12781 <description><p
>After several years of frustration with the lack of activity from
12782 the existing sysvinit upstream developer, I decided a few weeks ago to
12783 take over the package and become the new upstream. The number of
12784 patches to track for the Debian package was becoming a burden, and the
12785 lack of synchronization between the distribution made it hard to keep
12786 the package up to date.
</p
>
12788 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12789 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
12790 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
12791 and Fedora), based on the patches currently in use in these
12792 distributions. We Debian maintainers plan to move to this tarball as
12793 the new upstream as soon as we find time to do the merge. Since the
12794 new tarball was created, we agreed with Werner at SuSe to make a new
12795 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
12796 development there. The project is registered and currently waiting
12797 for approval by the Savannah administrators, and as soon as it is
12798 approved, we will import the old versions from svn and continue
12799 working on the future release.
</p
>
12801 <p
>It is a bit ironic that this is done now, when some of the involved
12802 distributions are moving to upstart as a syvinit replacement.
</p
>
12807 <title>Debian boots quicker and quicker
</title>
12808 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
12809 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
12810 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
12811 <description><p
>I spent Monday and tuesday this week in London with a lot of the
12812 people involved in the boot system on Debian and Ubuntu, to see if we
12813 could find more ways to speed up the boot system. This was an Ubuntu
12815 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
12816 gathering
</a
>. It was quite productive. We also discussed the future
12817 of boot systems, and ways to handle the increasing number of boot
12818 issues introduced by the Linux kernel becoming more and more
12819 asynchronous and event base. The Ubuntu approach using udev and
12820 upstart might be a good way forward. Time will show.
</p
>
12822 <p
>Anyway, there are a few ways at the moment to speed up the boot
12823 process in Debian. All of these should be applied to get a quick
12828 <li
>Use dash as /bin/sh.
</li
>
12830 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
12831 clock is in UTC.
</li
>
12833 <li
>Install and activate the insserv package to enable
12834 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12835 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
12839 These points are based on the Google summer of code work done by
12840 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
12841 Villegas
</a
>.
12843 <p
>Support for makefile-style concurrency during boot was uploaded to
12844 unstable yesterday. When we tested it, we were able to cut
6 seconds
12845 from the boot sequence. It depend on very correct dependency
12846 declaration in all init.d scripts, so I expect us to find edge cases
12847 where the dependences in some scripts are slightly wrong when we start
12848 using this.
</p
>
12850 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12851 introduced by Raphael Geissert today, one that could affect the
12852 startup speed as well. Instead of starting some scripts concurrently
12853 from rcS.d/ and another set of scripts from rc2.d/, it would be
12854 possible to run a of them in the same process. A quick way to test
12855 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
12856 insserv
'. Will need to test if that work. :)
</p
>
12861 <title>BSAs påstander om piratkopiering møter motstand
</title>
12862 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
12863 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
12864 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
12865 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
12866 programvareselskapene som Microsoft og Apple, publisert en rapport der
12867 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12868 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12870 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
12871 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
12872 dagene. Et spesielt interessant kommentar fra Sverige,
12873 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
12874 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
12877 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
12878 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12879 företag.
"Man bör nog kanske inte se de här siffrorna som helt
12880 exakta
", säger BSAs Sverigechef John Hugosson.
12881 </blockquote
>
12883 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
12884 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
12885 piracy figures need a shot of reality
</a
> og
<a
12886 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
12887 Copyright Treaty Work?
</a
></p
>
12889 <p
>Fant lenkene via
<a
12890 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
12891 på Slashdot
</a
>.
</p
>
12896 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
12897 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
12898 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
12899 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
12900 <description><p
>Kom over
12901 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
12902 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12903 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12904 jobber til daglig. En rask opptelling forteller meg at vi har
490
12905 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
12906 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
12907 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
12912 <title>Kryptert harddisk - naturligvis
</title>
12913 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
12914 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
12915 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
12916 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
12917 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
12918 når en tar tap av arbeidstid, fortrolige dokumenter,
12919 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12920 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12921 til at jeg har kryptert harddisken på både kontormaskinen og min
12922 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12923 komme på avveie, den første informasjon relatert til jobben min ved
12924 Universitetet i Oslo, og den andre relatert til blant annet
12925 foreningsarbeide. Kryptering av diskene gjør at det er lite
12926 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12927 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12928 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12929 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12930 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12931 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12932 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12933 det er gjort slik jeg gjør det er minimale, og gevinstene er
12934 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12935 maskinen reinstalleres og alt er tapt.
</p
>
12937 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12938 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12939 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12940 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12941 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12942 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12943 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12944 betydelige.
</p
>
12949 <title>Two projects that have improved the quality of free software a lot
</title>
12950 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
12951 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
12952 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
12953 <description><p
>There are two software projects that have had huge influence on the
12954 quality of free software, and I wanted to mention both in case someone
12955 do not yet know them.
</p
>
12957 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
12958 tool to detect and expose errors in the memory handling of programs.
12959 It is easy to use, all one need to do is to run
'valgrind program
',
12960 and it will report any problems on stdout. It is even better if the
12961 program include debug information. With debug information, it is able
12962 to report the source file name and line number where the problem
12963 occurs. It can report things like
'reading past memory block in file
12964 X line N, the memory block was allocated in file Y, line M
', and
12965 'using uninitialised value in control logic
'. This tool has made it
12966 trivial to investigate reproducible crash bugs in programs, and have
12967 reduced the number of this kind of bugs in free software a lot.
12969 <p
>The second one is
12970 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
12971 a source code checker. It is able to process the source of a program
12972 and find problems in the logic without running the program. It
12973 started out as the Stanford Checker and became well known when it was
12974 used to find bugs in the Linux kernel. It is now a commercial tool
12975 and the company behind it is running
12976 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
12977 free software community, where a lot of free software projects get
12978 their source checked for free. Several thousand defects have been
12979 found and fixed so far. It can find errors like
'lock L taken in file
12980 X line N is never released if exiting in line M
', or
'the code in file
12981 Y lines O to P can never be executed
'. The projects included in the
12982 community service project have managed to get rid of a lot of
12983 reliability problems thanks to Coverity.
</p
>
12985 <p
>I believe tools like this, that are able to automatically find
12986 errors in the source, are vital to improve the quality of software and
12987 make sure we can get rid of the crashing and failing software we are
12988 surrounded by today.
</p
>
12993 <title>No patch is not better than a useless patch
</title>
12994 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
12995 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
12996 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
12997 <description><p
>Julien Blache
12998 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
12999 patch is better than a useless patch
</a
>. I completely disagree, as a
13000 patch allow one to discuss a concrete and proposed solution, and also
13001 prove that the issue at hand is important enough for someone to spent
13002 time on fixing it. No patch do not provide any of these positive
13003 properties.
</p
>
13008 <title>Standardize on protocols and formats, not vendors and applications
</title>
13009 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
13010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
13011 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
13012 <description><p
>Where I work at the University of Oslo, one decision stand out as a
13013 very good one to form a long lived computer infrastructure. It is the
13014 simple one, lost by many in todays computer industry: Standardize on
13015 open network protocols and open exchange/storage formats, not applications.
13016 Applications come and go, while protocols and files tend to stay, and
13017 thus one want to make it easy to change application and vendor, while
13018 avoiding conversion costs and locking users to a specific platform or
13019 application.
</p
>
13021 <p
>This approach make it possible to replace the client applications
13022 independently of the server applications. One can even allow users to
13023 use several different applications as long as they handle the selected
13024 protocol and format. In the normal case, only one client application
13025 is recommended and users only get help if they choose to use this
13026 application, but those that want to deviate from the easy path are not
13027 blocked from doing so.
</p
>
13029 <p
>It also allow us to replace the server side without forcing the
13030 users to replace their applications, and thus allow us to select the
13031 best server implementation at any moment, when scale and resouce
13032 requirements change.
</p
>
13034 <p
>I strongly recommend standardizing - on open network protocols and
13035 open formats, but I would never recommend standardizing on a single
13036 application that do not use open network protocol or open formats.
</p
>
13041 <title>Returning from Skolelinux developer gathering
</title>
13042 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
13043 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
13044 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
13045 <description><p
>I
'm sitting on the train going home from this weekends Debian
13046 Edu/Skolelinux development gathering. I got a bit done tuning the
13047 desktop, and looked into the dynamic service location protocol
13048 implementation avahi. It look like it could be useful for us. Almost
13049 30 people participated, and I believe it was a great environment to
13050 get to know the Skolelinux system. Walter Bender, involved in the
13051 development of the Sugar educational platform, presented his stuff and
13052 also helped me improve my OLPC installation. He also showed me that
13053 his Turtle Art application can be used in standalone mode, and we
13054 agreed that I would help getting it packaged for Debian. As a
13055 standalone application it would be great for Debian Edu. We also
13056 tried to get the video conferencing working with two OLPCs, but that
13057 proved to be too hard for us. The application seem to need more work
13058 before it is ready for me. I look forward to getting home and relax
13064 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
13065 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
13066 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
13067 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
13068 <description><p
>The state of standardized LDAP schemas on Linux is far from
13069 optimal. There is RFC
2307 documenting one way to store NIS maps in
13070 LDAP, and a modified version of this normally called RFC
2307bis, with
13071 some modifications to be compatible with Active Directory. The RFC
13072 specification handle the content of a lot of system databases, but do
13073 not handle DNS zones and DHCP configuration.
</p
>
13075 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
13076 we would like to store information about users, SMB clients/hosts,
13077 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13078 and LTSP configuration in LDAP. These objects have a lot in common,
13079 but with the current LDAP schemas it is not possible to have one
13080 object per entity. For example, one need to have at least three LDAP
13081 objects for a given computer, one with the SMB related stuff, one with
13082 DNS information and another with DHCP information. The schemas
13083 provided for DNS and DHCP are impossible to combine into one LDAP
13084 object. In addition, it is impossible to implement quick queries for
13085 netgroup membership, because of the way NIS triples are implemented.
13086 It just do not scale. I believe it is time for a few RFC
13087 specifications to cleam up this mess.
</p
>
13089 <p
>I would like to have one LDAP object representing each computer in
13090 the network, and this object can then keep the SMB (ie host key), DHCP
13091 (mac address/name) and DNS (name/IP address) settings in one place.
13092 It need to be efficently stored to make sure it scale well.
</p
>
13094 <p
>I would also like to have a quick way to map from a user or
13095 computer and to the net group this user or computer is a member.
</p
>
13097 <p
>Active Directory have done a better job than unix heads like myself
13098 in this regard, and the unix side need to catch up. Time to start a
13099 new IETF work group?
</p
>
13104 <title>Endelig er Debian Lenny gitt ut
</title>
13105 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
13106 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
13107 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
13108 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
13109 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
13110 Et langt steg videre for Debian-prosjektet, og en rekke nye
13111 programpakker blir nå tilgjengelig for de av oss som bruker den
13112 stabile utgaven av Debian. Neste steg er nå å få
13113 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
13114 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
13115 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13116 slippes løs på skolene. Takk til alle debian-utviklerne som har
13117 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13118 bootsekvens tilgjengelig i stabil utgave, vha pakken
13119 <tt
>insserv
</tt
>.
</p
>
13124 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
13125 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
13126 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
13127 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
13128 <description><p
>This weekend we had a small developer gathering for Debian Edu in
13129 Oslo. Most of Saturday was used for the general assemly for the
13130 member organization, but the rest of the weekend I used to tune the
13131 LTSP installation. LTSP now work out of the box on the
10-network.
13132 Acer Aspire One proved to be a very nice thin client, with both
13133 screen, mouse and keybard in a small box. Was working on getting the
13134 diskless workstation setup configured out of the box, but did not
13135 finish it before the weekend was up.
</p
>
13137 <p
>Did not find time to look at the
4 VGA cards in one box we got from
13138 the Brazilian group, so that will have to wait for the next
13139 development gathering. Would love to have the Debian Edu installer
13140 automatically detect and configure a multiseat setup when it find one
13141 of these cards.
</p
>
13146 <title>The sorry state of multimedia browser plugins in Debian
</title>
13147 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
13148 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
13149 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
13150 <description><p
>Recently I have spent some time evaluating the multimedia browser
13151 plugins available in Debian Lenny, to see which one we should use by
13152 default in Debian Edu. We need an embedded video playing plugin with
13153 control buttons to pause or stop the video, and capable of streaming
13154 all the multimedia content available on the web. The test results and
13155 notes are available on
13156 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
13157 Debian wiki
</a
>. I was surprised how few of the plugins are able to
13158 fill this need. My personal video player favorite, VLC, has a really
13159 bad plugin which fail on a lot of the test pages. A lot of the MIME
13160 types I would expect to work with any free software player (like
13161 video/ogg), just do not work. And simple formats like the
13162 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
13163 totem and vlc plugins. I hope the situation will improve soon. No
13164 wonder sites use the proprietary Adobe flash to play video.
</p
>
13166 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
13167 be the only one fitting our needs. :/
</p
>