]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
New post.
[homepage.git] / blog / index.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
3 <channel>
4 <title>Petter Reinholdtsen</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
8
9 <item>
10 <title>I spent last weekend recording MakerCon Nordic</title>
11 <link>http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html</guid>
13 <pubDate>Thu, 23 Oct 2014 23:00:00 +0200</pubDate>
14 <description>&lt;p&gt;I spent last weekend at &lt;a href=&quot;http://www.makercon.no/&quot;&gt;Makercon
15 Nordic&lt;/a&gt;, a great conference and workshop for makers in Norway and
16 the surrounding countries. I had volunteered on behalf of the
17 Norwegian Unix Users Group (NUUG) to video record the talks, and we
18 had a great and exhausting time recording the entire day, two days in
19 a row. There were only two of us, Hans-Petter and me, and we used the
20 regular video equipment for NUUG, with a
21 &lt;a href=&quot;http://dvswitch.alioth.debian.org/wiki/&quot;&gt;dvswitch&lt;/a&gt;, a
22 camera and a VGA to DV convert box, and mixed video and slides
23 live.&lt;/p&gt;
24
25 &lt;p&gt;Hans-Petter did the post-processing, consisting of uploading the
26 around 180 GiB of raw video to Youtube, and the result is
27 &lt;a href=&quot;https://www.youtube.com/user/MakerConNordic/&quot;&gt;now becoming
28 public&lt;/a&gt; on the MakerConNordic account. The videos have the license
29 NUUG always use on our recordings, which is
30 &lt;a href=&quot;http://creativecommons.org/licenses/by-sa/3.0/no/&quot;&gt;Creative
31 Commons Navngivelse-Del på samme vilkår 3.0 Norge&lt;/a&gt;. Many great
32 talks available. Check it out! :)&lt;/p&gt;
33 </description>
34 </item>
35
36 <item>
37 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
38 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
39 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
40 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
41 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
42 alioth.debian.org, you know the web interface is fairly slow to
43 operate. First you visit one web page, enter the moderation password
44 and get a new page shown with a list of all the messages to moderate
45 and various options for each email address. This take a while for
46 every list you moderate, and you need to do it regularly to do a good
47 job as a list moderator. But there is a quick alternative,
48 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
49 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
50 to moderate in a fraction of a second. Here is a test run on two
51 lists I recently took over:&lt;/p&gt;
52
53 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
54 % time listadmin xiph
55 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
56 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
57
58 real 0m1.709s
59 user 0m0.232s
60 sys 0m0.012s
61 %
62 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
63
64 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
65 there are no message in the moderation queue. Every morning I
66 currently moderate 68 mailman lists, and it normally take around two
67 minutes. When I took over the two pkg-xiph lists above a few days
68 ago, there were 400 emails waiting in the moderator queue. It took me
69 less than 15 minutes to process them all using the listadmin
70 program.&lt;/p&gt;
71
72 &lt;p&gt;If you install
73 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
74 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
75 with content like this, the moderation task is a breeze:&lt;/p&gt;
76
77 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
78 username username@example.org
79 spamlevel 23
80 default discard
81 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
82
83 password secret
84 adminurl https://{domain}/mailman/admindb/{list}
85 mailman-list@lists.example.com
86
87 password hidden
88 other-list@otherserver.example.org
89 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
90
91 &lt;p&gt;There are other options to set as well. Check the manual page to
92 learn the details.&lt;/p&gt;
93
94 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
95 the SSL certificate is self signed or not properly signed by a
96 generally accepted signing authority, you can set a environment
97 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
98
99 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
100 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
101 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
102
103 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
104 can provide an argument to the listadmin script like I do in the
105 initial screen dump (the xiph argument). Using an argument, only
106 lists matching the argument string will be processed. This make it
107 quick to accept messages if you notice the moderation request in your
108 email.&lt;/p&gt;
109
110 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
111 mailing lists, as I simply do not have time to spend on that if the
112 process was any slower. The listadmin program have saved me hours of
113 time I could spend elsewhere over the years. It truly is nice free
114 software.&lt;/p&gt;
115
116 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
117 activities, please send Bitcoin donations to my address
118 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
119
120 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
121 configuration example. Also, I&#39;ve been told that the
122 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
123 sure why.&lt;/p&gt;
124 </description>
125 </item>
126
127 <item>
128 <title>Debian Jessie, PXE and automatic firmware installation</title>
129 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
131 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
132 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
133 problem that the WiFi card require some firmware to work properly.
134 And it has been a pain to fix this using preseeding in Debian.
135 Normally something more is needed. But thanks to
136 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
137 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
138 to do this using simple preseeding.&lt;/p&gt;
139
140 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
141 firmware for the hardware found in the machine (actually, requested by
142 the kernel modules for the hardware). (It can also install user space
143 programs supporting the hardware detected, but that is not the focus
144 of this story.)&lt;/p&gt;
145
146 &lt;p&gt;To get this working in the default installation, two preeseding
147 values are needed. First, the isenkram-cli package must be installed
148 into the target chroot (aka the hard drive) before tasksel is executed
149 in the pkgsel step of the debian-installer system. This is done by
150 preseeding the base-installer/includes debconf value to include the
151 isenkram-cli package. The package name is next passed to debootstrap
152 for installation. With the isenkram-cli package in place, tasksel
153 will automatically use the isenkram tasks to detect hardware specific
154 packages for the machine being installed and install them, because
155 isenkram-cli contain tasksel tasks.&lt;/p&gt;
156
157 &lt;p&gt;Second, one need to enable the non-free APT repository, because
158 most firmware unfortunately is non-free. This is done by preseeding
159 the apt-mirror-setup step. This is unfortunate, but for a lot of
160 hardware it is the only option in Debian.&lt;/p&gt;
161
162 &lt;p&gt;The end result is two lines needed in your preseeding file to get
163 firmware installed automatically by the installer:&lt;/p&gt;
164
165 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
166 base-installer base-installer/includes string isenkram-cli
167 apt-mirror-setup apt-setup/non-free boolean true
168 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
169
170 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
171 both firmware and user space packages when using this method. It also
172 do not work well, so use version 0.15 or later. Installing both
173 firmware and user space packages might give you a bit more than you
174 want, so I decided to split the tasksel task in two, one for firmware
175 and one for user space programs. The firmware task is enabled by
176 default, while the one for user space programs is not. This split is
177 implemented in the package currently in unstable.&lt;/p&gt;
178
179 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
180 this recipe work for you. :)&lt;/p&gt;
181
182 &lt;p&gt;So, I bet you are wondering, how can this work. First and
183 foremost, it work because tasksel is modular, and driven by whatever
184 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
185 isenkram-cli package place two files for tasksel to find. First there
186 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
187
188 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
189 Task: isenkram-packages
190 Section: hardware
191 Description: Hardware specific packages (autodetected by isenkram)
192 Based on the detected hardware various hardware specific packages are
193 proposed.
194 Test-new-install: show show
195 Relevance: 8
196 Packages: for-current-hardware
197
198 Task: isenkram-firmware
199 Section: hardware
200 Description: Hardware specific firmware packages (autodetected by isenkram)
201 Based on the detected hardware various hardware specific firmware
202 packages are proposed.
203 Test-new-install: mark show
204 Relevance: 8
205 Packages: for-current-hardware-firmware
206 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
207
208 &lt;p&gt;The key parts are Test-new-install which indicate how the task
209 should be handled and the Packages line referencing to a script in
210 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
211 list of packages to install. The for-current-hardware-firmware script
212 look like this to list relevant firmware for the machine:
213
214 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
215 #!/bin/sh
216 #
217 PATH=/usr/sbin:$PATH
218 export PATH
219 isenkram-autoinstall-firmware -l
220 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
221
222 &lt;p&gt;With those two pieces in place, the firmware is installed by
223 tasksel during the normal d-i run. :)&lt;/p&gt;
224
225 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
226 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
227 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
228 install.&lt;/p&gt;
229
230 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
231 pilots in testing this feature, as isenkram is used there now to
232 install firmware, replacing the earlier scripts.&lt;/p&gt;
233 </description>
234 </item>
235
236 <item>
237 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
238 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
239 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
240 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
241 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
242 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
243 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
244 on a screen normally showing the bread types and prizes:&lt;/p&gt;
245
246 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
247
248 &lt;p&gt;If it had booted as it was supposed to, I would never had known
249 about this hidden Linux installation. It is interesting what
250 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
251 </description>
252 </item>
253
254 <item>
255 <title>New lsdvd release version 0.17 is ready</title>
256 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
258 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
259 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
260 got a new set of developers a few weeks ago, after the original
261 developer decided to step down and pass the project to fresh blood.
262 This project is now maintained by Petter Reinholdtsen and Steve
263 Dibb.&lt;/p&gt;
264
265 &lt;p&gt;I just wrapped up
266 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
267 new lsdvd release&lt;/a&gt;, available in git or from
268 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
269 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
270 0.17.&lt;/p&gt;
271
272 &lt;ul&gt;
273
274 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
275 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
276 non-existant, to work around additional copy protection&lt;/li&gt;
277 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
278 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
279 &lt;li&gt;Fix include orders&lt;/li&gt;
280 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
281 &lt;li&gt;Fix the chapter count&lt;/li&gt;
282 &lt;li&gt;Make sure the array size and the array limit used when initialising
283 the palette size is the same.&lt;/li&gt;
284 &lt;li&gt;Fix array printing.&lt;/li&gt;
285 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
286 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
287 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
288 with more GCC compiler warnings.&lt;/li&gt;
289
290 &lt;/ul&gt;
291
292 &lt;p&gt;This change bring together patches for lsdvd in use in various
293 Linux and Unix distributions, as well as patches submitted to the
294 project the last nine years. Please check it out. :)&lt;/p&gt;
295 </description>
296 </item>
297
298 <item>
299 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
300 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
301 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
302 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
303 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
304 project&lt;/a&gt; provide a Linux solution for schools, including a
305 powerful desktop with education software, a central server providing
306 web pages, user database, user home directories, central login and PXE
307 boot of both clients without disk and the installation to install Debian
308 Edu on machines with disk (and a few other services perhaps to small
309 to mention here). We in the Debian Edu team are currently working on
310 the Jessie based version, trying to get everything in shape before the
311 freeze, to avoid having to maintain our own package repository in the
312 future. The
313 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
314 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
315 work left. Some fatal problems block testing, breaking the installer,
316 but it is possible to work around these to get anyway. Here is a
317 recipe on how to get the installation limping along.&lt;/p&gt;
318
319 &lt;p&gt;First, download the test ISO via
320 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
321 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
322 or rsync (use
323 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
324 The ISO build was broken on Tuesday, so we do not get a new ISO every
325 12 hours or so, but thankfully the ISO we already got we are able to
326 install with some tweaking.&lt;/p&gt;
327
328 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
329 (use Alt-Ctrl-F2), run&lt;/p&gt;
330
331 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
332 nano /usr/bin/edu-eatmydata-install
333 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
334
335 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
336 optimization. Return to the installation, select the profile you want
337 and continue. Without this change, exim4-config will fail to install
338 due to a known bug in eatmydata.&lt;/p&gt;
339
340 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
341 this do not work, figure out what your correct value would be. All my
342 test machines need /dev/sda, so I have no advice if it do not fit
343 your need.&lt;/p&gt;
344
345 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
346 root after the initial boot from hard drive, and install the
347 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
348 or mate. If you want several desktop options, install more than one
349 metapackage. Once this is done, reboot and you should have a working
350 graphical login screen. This workaround should no longer be needed
351 once the education-tasks package version 1.801 enter testing in two
352 days.&lt;/p&gt;
353
354 &lt;p&gt;I believe the ISO build will start working on two days when the new
355 tasksel package enter testing and Steve McIntyre get a chance to
356 update the debian-cd git repository. The eatmydata, grub and desktop
357 issues are already fixed in unstable and testing, and should show up
358 on the ISO as soon as the ISO build start working again. Well the
359 eatmydata optimization is really just disabled. The proper fix
360 require an upload by the eatmydata maintainer applying the patch
361 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
362 The rest have proper fixes in unstable.&lt;/p&gt;
363
364 &lt;p&gt;I hope this get you going with the installation testing, as we are
365 quickly running out of time trying to get our Jessie based
366 installation ready before the distribution freeze in a month.&lt;/p&gt;
367 </description>
368 </item>
369
370 <item>
371 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
372 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
373 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
374 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
375 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
376 to handle my fairly large DVD collection. It is a nice command line
377 tool to get details about a DVD, like title, tracks, track length,
378 etc, in XML, Perl or human readable format. But lsdvd have not seen
379 any new development since 2006 and had a few irritating bugs affecting
380 its use with some DVDs. Upstream seemed to be dead, and in January I
381 sent a small probe asking for a version control repository for the
382 project, without any reply. But I use it regularly and would like to
383 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
384 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
385 the project admin, and after getting a reply from him explaining that
386 he was no longer interested in the project, I asked if I could take
387 over. And yesterday, I became project admin.&lt;/p&gt;
388
389 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
390 maintainer interested in joining forces to maintain the upstream
391 project, and I hope we can get a new release out fairly quickly,
392 collecting the patches spread around on the internet into on place.
393 I&#39;ve added the relevant Debian patches to the freshly created git
394 repository, and expect the Gentoo patches to make it too. If you got
395 a DVD collection and care about command line tools, check out
396 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
397 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
398 list&lt;/a&gt;. :)&lt;/p&gt;
399 </description>
400 </item>
401
402 <item>
403 <title>Hva henger under skibrua over E16 på Sollihøgda?</title>
404 <link>http://people.skolelinux.org/pere/blog/Hva_henger_under_skibrua_over_E16_p__Sollih_gda_.html</link>
405 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hva_henger_under_skibrua_over_E16_p__Sollih_gda_.html</guid>
406 <pubDate>Sun, 21 Sep 2014 09:50:00 +0200</pubDate>
407 <description>&lt;p&gt;Rundt omkring i Oslo og Østlandsområdet henger det bokser over
408 veiene som jeg har lurt på hva gjør. De har ut fra plassering og
409 vinkling sett ut som bokser som sniffer ut et eller annet fra
410 forbipasserende trafikk, men det har vært uklart for meg hva det er de
411 leser av. Her om dagen tok jeg bilde av en slik boks som henger under
412 &lt;a href=&quot;http://www.openstreetmap.no/?zoom=19&amp;mlat=59.96396&amp;mlon=10.34443&amp;layers=B00000&quot;&gt;ei
413 skibru på Sollihøgda&lt;/a&gt;:&lt;/p&gt;
414
415 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;60%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-09-13-kapsch-sollihogda-crop.jpeg&quot;&gt;&lt;/p&gt;
416
417 &lt;p&gt;Boksen er tydelig merket «Kapsch &gt;&gt;&gt;», logoen til
418 &lt;a href=&quot;http://www.kapsch.net/&quot;&gt;det sveitsiske selskapet Kapsch&lt;/a&gt; som
419 blant annet lager sensorsystemer for veitrafikk. Men de lager mye
420 forskjellig, og jeg kjente ikke igjen boksen på utseendet etter en
421 kjapp titt på produktlista til selskapet.&lt;/p&gt;
422
423 &lt;p&gt;I og med at boksen henger over veien E16, en riksvei vedlikeholdt
424 av Statens Vegvesen, så antok jeg at det burde være mulig å bruke
425 REST-API-et som gir tilgang til vegvesenets database over veier,
426 skilter og annet veirelatert til å finne ut hva i alle dager dette
427 kunne være. De har både
428 &lt;a href=&quot;https://www.vegvesen.no/nvdb/api/dokumentasjon/datakatalog&quot;&gt;en
429 datakatalog&lt;/a&gt; og
430 &lt;a href=&quot;https://www.vegvesen.no/nvdb/api/dokumentasjon/sok&quot;&gt;et
431 søk&lt;/a&gt;, der en kan søke etter ulike typer oppføringer innen for et
432 gitt geografisk område. Jeg laget et enkelt shell-script for å hente
433 ut antall av en gitt type innenfor området skibrua dekker, og listet
434 opp navnet på typene som ble funnet. Orket ikke slå opp hvordan
435 URL-koding av aktuelle strenger kunne gjøres mer generisk, og brukte
436 en stygg sed-linje i stedet.&lt;/p&gt;
437
438 &lt;blockquote&gt;&lt;pre&gt;
439 #!/bin/sh
440 urlmap() {
441 sed \
442 -e &#39;s/ / /g&#39; -e &#39;s/{/%7B/g&#39; \
443 -e &#39;s/}/%7D/g&#39; -e &#39;s/\[/%5B/g&#39; \
444 -e &#39;s/\]/%5D/g&#39; -e &#39;s/ /%20/g&#39; \
445 -e &#39;s/,/%2C/g&#39; -e &#39;s/\&quot;/%22/g&#39; \
446 -e &#39;s/:/%3A/g&#39;
447 }
448
449 lookup() {
450 url=&quot;$1&quot;
451 curl -s -H &#39;Accept: application/vnd.vegvesen.nvdb-v1+xml&#39; \
452 &quot;https://www.vegvesen.no/nvdb/api$url&quot; | xmllint --format -
453 }
454
455 for id in $(seq 1 874) ; do
456 search=&quot;{
457 lokasjon: {
458 bbox: \&quot;10.34425,59.96386,10.34458,59.96409\&quot;,
459 srid: \&quot;WGS84\&quot;
460 },
461 objektTyper: [{
462 id: $id, antall: 10
463 }]
464 }&quot;
465
466 query=/sok?kriterie=$(echo $search | urlmap)
467 if lookup &quot;$query&quot; |
468 grep -q &#39;&amp;lt;totaltAntallReturnert&gt;0&amp;lt;&#39;
469 then
470 :
471 else
472 echo $id
473 lookup &quot;/datakatalog/objekttyper/$id&quot; |grep &#39;^ &amp;lt;navn&gt;&#39;
474 fi
475 done
476
477 exit 0
478 &lt;/pre&gt;&lt;/blockquote&gt;
479
480 Aktuelt ID-område 1-874 var riktig i datakatalogen da jeg laget
481 scriptet. Det vil endre seg over tid. Skriptet listet så opp
482 aktuelle typer i og rundt skibrua:
483
484 &lt;blockquote&gt;&lt;pre&gt;
485 5
486 &amp;lt;navn&gt;Rekkverk&amp;lt;/navn&gt;
487 14
488 &amp;lt;navn&gt;Rekkverksende&amp;lt;/navn&gt;
489 47
490 &amp;lt;navn&gt;Trafikklomme&amp;lt;/navn&gt;
491 49
492 &amp;lt;navn&gt;Trafikkøy&amp;lt;/navn&gt;
493 60
494 &amp;lt;navn&gt;Bru&amp;lt;/navn&gt;
495 79
496 &amp;lt;navn&gt;Stikkrenne/Kulvert&amp;lt;/navn&gt;
497 80
498 &amp;lt;navn&gt;Grøft, åpen&amp;lt;/navn&gt;
499 86
500 &amp;lt;navn&gt;Belysningsstrekning&amp;lt;/navn&gt;
501 95
502 &amp;lt;navn&gt;Skiltpunkt&amp;lt;/navn&gt;
503 96
504 &amp;lt;navn&gt;Skiltplate&amp;lt;/navn&gt;
505 98
506 &amp;lt;navn&gt;Referansestolpe&amp;lt;/navn&gt;
507 99
508 &amp;lt;navn&gt;Vegoppmerking, langsgående&amp;lt;/navn&gt;
509 105
510 &amp;lt;navn&gt;Fartsgrense&amp;lt;/navn&gt;
511 106
512 &amp;lt;navn&gt;Vinterdriftsstrategi&amp;lt;/navn&gt;
513 172
514 &amp;lt;navn&gt;Trafikkdeler&amp;lt;/navn&gt;
515 241
516 &amp;lt;navn&gt;Vegdekke&amp;lt;/navn&gt;
517 293
518 &amp;lt;navn&gt;Breddemåling&amp;lt;/navn&gt;
519 301
520 &amp;lt;navn&gt;Kantklippareal&amp;lt;/navn&gt;
521 318
522 &amp;lt;navn&gt;Snø-/isrydding&amp;lt;/navn&gt;
523 445
524 &amp;lt;navn&gt;Skred&amp;lt;/navn&gt;
525 446
526 &amp;lt;navn&gt;Dokumentasjon&amp;lt;/navn&gt;
527 452
528 &amp;lt;navn&gt;Undergang&amp;lt;/navn&gt;
529 528
530 &amp;lt;navn&gt;Tverrprofil&amp;lt;/navn&gt;
531 532
532 &amp;lt;navn&gt;Vegreferanse&amp;lt;/navn&gt;
533 534
534 &amp;lt;navn&gt;Region&amp;lt;/navn&gt;
535 535
536 &amp;lt;navn&gt;Fylke&amp;lt;/navn&gt;
537 536
538 &amp;lt;navn&gt;Kommune&amp;lt;/navn&gt;
539 538
540 &amp;lt;navn&gt;Gate&amp;lt;/navn&gt;
541 539
542 &amp;lt;navn&gt;Transportlenke&amp;lt;/navn&gt;
543 540
544 &amp;lt;navn&gt;Trafikkmengde&amp;lt;/navn&gt;
545 570
546 &amp;lt;navn&gt;Trafikkulykke&amp;lt;/navn&gt;
547 571
548 &amp;lt;navn&gt;Ulykkesinvolvert enhet&amp;lt;/navn&gt;
549 572
550 &amp;lt;navn&gt;Ulykkesinvolvert person&amp;lt;/navn&gt;
551 579
552 &amp;lt;navn&gt;Politidistrikt&amp;lt;/navn&gt;
553 583
554 &amp;lt;navn&gt;Vegbredde&amp;lt;/navn&gt;
555 591
556 &amp;lt;navn&gt;Høydebegrensning&amp;lt;/navn&gt;
557 592
558 &amp;lt;navn&gt;Nedbøyningsmåling&amp;lt;/navn&gt;
559 597
560 &amp;lt;navn&gt;Støy-luft, Strekningsdata&amp;lt;/navn&gt;
561 601
562 &amp;lt;navn&gt;Oppgravingsdata&amp;lt;/navn&gt;
563 602
564 &amp;lt;navn&gt;Oppgravingslag&amp;lt;/navn&gt;
565 603
566 &amp;lt;navn&gt;PMS-parsell&amp;lt;/navn&gt;
567 604
568 &amp;lt;navn&gt;Vegnormalstrekning&amp;lt;/navn&gt;
569 605
570 &amp;lt;navn&gt;Værrelatert strekning&amp;lt;/navn&gt;
571 616
572 &amp;lt;navn&gt;Feltstrekning&amp;lt;/navn&gt;
573 617
574 &amp;lt;navn&gt;Adressepunkt&amp;lt;/navn&gt;
575 626
576 &amp;lt;navn&gt;Friksjonsmåleserie&amp;lt;/navn&gt;
577 629
578 &amp;lt;navn&gt;Vegdekke, flatelapping&amp;lt;/navn&gt;
579 639
580 &amp;lt;navn&gt;Kurvatur, horisontalelement&amp;lt;/navn&gt;
581 640
582 &amp;lt;navn&gt;Kurvatur, vertikalelement&amp;lt;/navn&gt;
583 642
584 &amp;lt;navn&gt;Kurvatur, vertikalpunkt&amp;lt;/navn&gt;
585 643
586 &amp;lt;navn&gt;Statistikk, trafikkmengde&amp;lt;/navn&gt;
587 647
588 &amp;lt;navn&gt;Statistikk, vegbredde&amp;lt;/navn&gt;
589 774
590 &amp;lt;navn&gt;Nedbøyningsmåleserie&amp;lt;/navn&gt;
591 775
592 &amp;lt;navn&gt;ATK, influensstrekning&amp;lt;/navn&gt;
593 794
594 &amp;lt;navn&gt;Systemobjekt&amp;lt;/navn&gt;
595 810
596 &amp;lt;navn&gt;Vinterdriftsklasse&amp;lt;/navn&gt;
597 821
598 &amp;lt;navn&gt;Funksjonell vegklasse&amp;lt;/navn&gt;
599 825
600 &amp;lt;navn&gt;Kurvatur, stigning&amp;lt;/navn&gt;
601 838
602 &amp;lt;navn&gt;Vegbredde, beregnet&amp;lt;/navn&gt;
603 862
604 &amp;lt;navn&gt;Reisetidsregistreringspunkt&amp;lt;/navn&gt;
605 871
606 &amp;lt;navn&gt;Bruksklasse&amp;lt;/navn&gt;
607 &lt;/pre&gt;&lt;/blockquote&gt;
608
609 &lt;p&gt;Av disse ser ID 775 og 862 mest relevant ut. ID 775 antar jeg
610 refererer til fotoboksen som står like ved brua, mens
611 «Reisetidsregistreringspunkt» kanskje kan være boksen som henger der.
612 Hvordan finner jeg så ut hva dette kan være for noe. En titt på
613 &lt;a href=&quot;http://labs.vegdata.no/nvdb-datakatalog/862-Reisetidsregistreringspunkt/&quot;&gt;datakatalogsiden
614 for ID 862/Reisetidsregistreringspunkt&lt;/a&gt; viser at det er finnes 53
615 slike målere i Norge, og hvor de er plassert, men gir ellers få
616 detaljer. Det er plassert 40 på østlandet og 13 i Trondheimsregionen.
617 Men siden nevner «AutoPASS», og hvis en slår opp oppføringen på
618 Sollihøgda nevner den «Ciber AS» som ID for eksternt system. (Kan det
619 være snakk om
620 &lt;a href=&quot;http://www.proff.no/selskap/ciber-norge-as/oslo/internettdesign-og-programmering/Z0I3KMF4/&quot;&gt;Ciber
621 Norge AS&lt;/a&gt;, et selskap eid av Ciber Europe Bv?) Et nettsøk på
622 «Ciber AS autopass» fører meg til en artikkel fra NRK Trøndelag i
623 2013 med tittel
624 «&lt;a href=&quot;http://www.nrk.no/trondelag/sjekk-dette-hvis-du-vil-unnga-ko-1.11327947&quot;&gt;Sjekk
625 dette hvis du vil unngå kø&lt;/a&gt;». Artikkelen henviser til vegvesenets
626 nettside
627 &lt;a href=&quot;http://www.reisetider.no/reisetid/forside.html&quot;&gt;reisetider.no&lt;/a&gt;
628 som har en
629 &lt;a href=&quot;http://www.reisetider.no/reisetid/omrade.html?omrade=5&quot;&gt;kartside
630 for Østlandet&lt;/a&gt; som viser at det måles mellom Sandvika og Sollihøgda.
631 Det kan dermed se ut til at jeg har funnet ut hva boksene gjør.&lt;/p&gt;
632
633 &lt;p&gt;Hvis det stemmer, så er dette bokser som leser av AutoPASS-ID-en
634 til alle passerende biler med AutoPASS-brikke, og dermed gjør det mulig
635 for de som kontrollerer boksene å holde rede på hvor en gitt bil er
636 når den passerte et slikt målepunkt. NRK-artikkelen forteller at
637 denne informasjonen i dag kun brukes til å koble to
638 AutoPASS-brikkepasseringer passeringer sammen for å beregne
639 reisetiden, og at bruken er godkjent av Datatilsynet. Det er desverre
640 ikke mulig for en sjåfør som passerer under en slik boks å kontrollere
641 at AutoPASS-ID-en kun brukes til dette i dag og i fremtiden.&lt;/p&gt;
642
643 &lt;p&gt;I tillegg til denne type AutoPASS-sniffere vet jeg at det også
644 finnes mange automatiske stasjoner som tar betalt pr. passering (aka
645 bomstasjoner), og der lagres informasjon om tid, sted og bilnummer i
646 10 år. Finnes det andre slike sniffere plassert ut på veiene?&lt;/p&gt;
647
648 &lt;p&gt;Personlig har jeg valgt å ikke bruke AutoPASS-brikke, for å gjøre
649 det vanskeligere og mer kostbart for de som vil invadere privatsfæren
650 og holde rede på hvor bilen min beveger seg til enhver tid. Jeg håper
651 flere vil gjøre det samme, selv om det gir litt høyere private
652 utgifter (dyrere bompassering). Vern om privatsfæren koster i disse
653 dager.&lt;/p&gt;
654
655 &lt;p&gt;Takk til Jan Kristian Jensen i Statens Vegvesen for tips om
656 dokumentasjon på vegvesenets REST-API.&lt;/p&gt;
657 </description>
658 </item>
659
660 <item>
661 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
662 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
663 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
664 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
665 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
666 a lot quicker. When we install more than 2000 packages in
667 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
668 tasksel in the installer, unpacking the binary packages take forever.
669 A part of the slow I/O issue was discussed in
670 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
671 much file system sync-ing done by dpkg, which is the package
672 responsible for unpacking the binary packages. Other parts (like code
673 executed by postinst scripts) might also sync to disk during
674 installation. All this sync-ing to disk do not really make sense to
675 me. If the machine crash half-way through, I start over, I do not try
676 to salvage the half installed system. So the failure sync-ing is
677 supposed to protect against, hardware or system crash, is not really
678 relevant while the installer is running.&lt;/p&gt;
679
680 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
681 system sync()-ing in a fairly non-intrusive way, without the need to
682 change the code in several packages. The idea is not new, but I have
683 not heard anyone propose the approach using dpkg-divert before. It
684 depend on the small and clever package
685 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
686 uses LD_PRELOAD to replace the system functions for syncing data to
687 disk with functions doing nothing, thus allowing programs to live
688 dangerous while speeding up disk I/O significantly. Instead of
689 modifying the implementation of dpkg, apt and tasksel (which are the
690 packages responsible for selecting, fetching and installing packages),
691 it occurred to me that we could just divert the programs away, replace
692 them with a simple shell wrapper calling
693 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
694 Two days ago I decided to test the idea, and wrapped up a simple
695 implementation for the Debian Edu udeb.&lt;/p&gt;
696
697 &lt;p&gt;The effect was stunning. In my first test it reduced the running
698 time of the pkgsel step (installing tasks) from 64 to less than 44
699 minutes (20 minutes shaved off the installation) on an old Dell
700 Latitude D505 machine. I am not quite sure what the optimised time
701 would have been, as I messed up the testing a bit, causing the debconf
702 priority to get low enough for two questions to pop up during
703 installation. As soon as I saw the questions I moved the installation
704 along, but do not know how long the question were holding up the
705 installation. I did some more measurements using Debian Edu Jessie,
706 and got these results. The time measured is the time stamp in
707 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
708 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
709 yourself. In Debian Edu, the tasksel dialog do not show up, and the
710 timing thus do not depend on how quickly the user handle the tasksel
711 dialog.&lt;/p&gt;
712
713 &lt;p&gt;&lt;table&gt;
714
715 &lt;tr&gt;
716 &lt;th&gt;Machine/setup&lt;/th&gt;
717 &lt;th&gt;Original tasksel&lt;/th&gt;
718 &lt;th&gt;Optimised tasksel&lt;/th&gt;
719 &lt;th&gt;Reduction&lt;/th&gt;
720 &lt;/tr&gt;
721
722 &lt;tr&gt;
723 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
724 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
725 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
726 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
727 &lt;/tr&gt;
728
729 &lt;tr&gt;
730 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
731 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
732 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
733 &lt;td&gt;23 min 40%&lt;/td&gt;
734 &lt;/tr&gt;
735
736 &lt;tr&gt;
737 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
738 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
739 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
740 &lt;td&gt;11 min 50%&lt;/td&gt;
741 &lt;/tr&gt;
742
743 &lt;tr&gt;
744 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
745 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
746 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
747 &lt;td&gt;2 min 33%&lt;/td&gt;
748 &lt;/tr&gt;
749
750 &lt;tr&gt;
751 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
752 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
753 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
754 &lt;td&gt;4 min 21%&lt;/td&gt;
755 &lt;/tr&gt;
756
757 &lt;/table&gt;&lt;/p&gt;
758
759 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
760 time is spent downloading packages. The connection to the Internet
761 was 100Mbit/s during testing, so downloading should not be a
762 significant factor in the measurement. Download typically took a few
763 seconds to a few minutes, depending on the amount of packages being
764 installed.&lt;/p&gt;
765
766 &lt;p&gt;The speedup is implemented by using two hooks in
767 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
768 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
769 finish-install.d hook to remove the divert at the end of the
770 installation. I picked the pre-pkgsel.d hook instead of the
771 post-base-installer.d hook because I test using an ISO without the
772 eatmydata package included, and the post-base-installer.d hook in
773 Debian Edu can only operate on packages included in the ISO. The
774 negative effect of this is that I am unable to activate this
775 optimization for the kernel installation step in d-i. If the code is
776 moved to the post-base-installer.d hook, the speedup would be larger
777 for the entire installation.&lt;/p&gt;
778
779 &lt;p&gt;I&#39;ve implemented this in the
780 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
781 git repository, and plan to provide the optimization as part of the
782 Debian Edu installation. If you want to test this yourself, you can
783 create two files in the installer (or in an udeb). One shell script
784 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
785
786 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
787 #!/bin/sh
788 set -e
789 . /usr/share/debconf/confmodule
790 info() {
791 logger -t my-pkgsel &quot;info: $*&quot;
792 }
793 error() {
794 logger -t my-pkgsel &quot;error: $*&quot;
795 }
796 override_install() {
797 apt-install eatmydata || true
798 if [ -x /target/usr/bin/eatmydata ] ; then
799 for bin in dpkg apt-get aptitude tasksel ; do
800 file=/usr/bin/$bin
801 # Test that the file exist and have not been diverted already.
802 if [ -f /target$file ] ; then
803 info &quot;diverting $file using eatmydata&quot;
804 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
805 &gt; /target$file.edu
806 chmod 755 /target$file.edu
807 in-target dpkg-divert --package debian-edu-config \
808 --rename --quiet --add $file
809 ln -sf ./$bin.edu /target$file
810 else
811 error &quot;unable to divert $file, as it is missing.&quot;
812 fi
813 done
814 else
815 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
816 fi
817 }
818
819 override_install
820 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
821
822 &lt;p&gt;To clean up, another shell script should go into
823 /usr/lib/finish-install.d/ with code like this:
824
825 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
826 #! /bin/sh -e
827 . /usr/share/debconf/confmodule
828 error() {
829 logger -t my-finish-install &quot;error: $@&quot;
830 }
831 remove_install_override() {
832 for bin in dpkg apt-get aptitude tasksel ; do
833 file=/usr/bin/$bin
834 if [ -x /target$file.edu ] ; then
835 rm /target$file
836 in-target dpkg-divert --package debian-edu-config \
837 --rename --quiet --remove $file
838 rm /target$file.edu
839 else
840 error &quot;Missing divert for $file.&quot;
841 fi
842 done
843 sync # Flush file buffers before continuing
844 }
845
846 remove_install_override
847 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
848
849 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
850 edu-eatmydata-install and call it from the pre-pkgsel.d and
851 finish-install.d scripts.&lt;/p&gt;
852
853 &lt;p&gt;By now you might ask if this change should get into the normal
854 Debian installer too? I suspect it should, but am not sure the
855 current debian-installer coordinators find it useful enough. It also
856 depend on the side effects of the change. I&#39;m not aware of any, but I
857 guess we will see if the change is safe after some more testing.
858 Perhaps there is some package in Debian depending on sync() and
859 fsync() having effect? Perhaps it should go into its own udeb, to
860 allow those of us wanting to enable it to do so without affecting
861 everyone.&lt;/p&gt;
862
863 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
864 will break installation of all programs using gnutls because of
865 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
866 eatmydata package in Debian will solve it.&lt;/p&gt;
867
868 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
869 the optimization work again. And I have discovered that the
870 dpkg-divert trick is not really needed and implemented a slightly
871 simpler approach as part of the debian-edu-install package. See
872 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
873 </description>
874 </item>
875
876 <item>
877 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
878 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
880 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
881 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
882 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
883 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
884 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
885 learn that there is a large set of publicly available key servers to
886 use when looking for peoples public key. So far I have used
887 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
888 were misbehaving, but those days are ended. The servers I have used
889 up until yesterday have been slow and some times unavailable. I hope
890 those problems are gone now.&lt;/p&gt;
891
892 &lt;p&gt;Behind the round robin DNS entry of the
893 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
894 there is a pool of more than 100 keyservers which are checked every
895 day to ensure they are well connected and up to date. It must be
896 better than what I have used so far. :)&lt;/p&gt;
897
898 &lt;p&gt;Yesterdays speaker told me that the service is the default
899 keyserver provided by the default configuration in GnuPG, but this do
900 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
901
902 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
903 line:&lt;/p&gt;
904
905 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
906 keyserver pool.sks-keyservers.net
907 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
908
909 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
910 entries in DNS. Just for fun, I did just that at work, so now every
911 user of GnuPG at the University of Oslo should find a OpenGPG
912 keyserver automatically should their need it:&lt;/p&gt;
913
914 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
915 % host -t srv _pgpkey-http._tcp.uio.no
916 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
917 %
918 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
919
920 &lt;p&gt;Now if only
921 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
922 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
923 very happy. It can look up a given key or search for a user ID, but I
924 normally do not want that, but to find a trust path from my key to
925 another key. Given a user ID or key ID, I would like to find (and
926 download) the keys representing a signature path from my key to the
927 key in question, to be able to get a trust path between the two keys.
928 This is as far as I can tell not possible today. Perhaps something
929 for a future version of the protocol?&lt;/p&gt;
930 </description>
931 </item>
932
933 </channel>
934 </rss>