1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from October
2014</title>
5 <description>Entries from October
2014</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
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><p
>I spent last weekend at
<a href=
"http://www.makercon.no/
">Makercon
15 Nordic
</a
>, 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 <a href=
"http://dvswitch.alioth.debian.org/wiki/
">dvswitch
</a
>, a
22 camera and a VGA to DV convert box, and mixed video and slides
25 <p
>Hans-Petter did the post-processing, consisting of uploading the
26 around
180 GiB of raw video to Youtube, and the result is
27 <a href=
"https://www.youtube.com/user/MakerConNordic/
">now becoming
28 public
</a
> on the MakerConNordic account. The videos have the license
29 NUUG always use on our recordings, which is
30 <a href=
"http://creativecommons.org/licenses/by-sa/
3.0/no/
">Creative
31 Commons Navngivelse-Del på samme vilkår
3.0 Norge
</a
>. Many great
32 talks available. Check it out! :)
</p
>
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><p
>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 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
49 listadmin program
</a
>. 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:
</p
>
53 <p
><blockquote
><pre
>
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
62 </pre
></blockquote
></p
>
64 <p
>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
72 <p
>If you install
73 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
74 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
75 with content like this, the moderation task is a breeze:
</p
>
77 <p
><blockquote
><pre
>
78 username username@example.org
81 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
84 adminurl https://{domain}/mailman/admindb/{list}
85 mailman-list@lists.example.com
88 other-list@otherserver.example.org
89 </pre
></blockquote
></p
>
91 <p
>There are other options to set as well. Check the manual page to
92 learn the details.
</p
>
94 <p
>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:
</p
>
99 <p
><blockquote
><pre
>
100 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
101 </pre
></blockquote
></p
>
103 <p
>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
110 <p
>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
116 <p
>As usual, if you use Bitcoin and want to show your support of my
117 activities, please send Bitcoin donations to my address
118 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
120 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
121 configuration example. Also, I
've been told that the
122 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
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><p
>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 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
137 package
</a
> and its recent tasksel extension, it has now become easy
138 to do this using simple preseeding.
</p
>
140 <p
>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.)
</p
>
146 <p
>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.
</p
>
157 <p
>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.
</p
>
162 <p
>The end result is two lines needed in your preseeding file to get
163 firmware installed automatically by the installer:
</p
>
165 <p
><blockquote
><pre
>
166 base-installer base-installer/includes string isenkram-cli
167 apt-mirror-setup apt-setup/non-free boolean true
168 </pre
></blockquote
></p
>
170 <p
>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.
</p
>
179 <p
>If you decide to give this a go, please let me know (via email) how
180 this recipe work for you. :)
</p
>
182 <p
>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):
</p
>
188 <p
><blockquote
><pre
>
189 Task: isenkram-packages
191 Description: Hardware specific packages (autodetected by isenkram)
192 Based on the detected hardware various hardware specific packages are
194 Test-new-install: show show
196 Packages: for-current-hardware
198 Task: isenkram-firmware
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
205 Packages: for-current-hardware-firmware
206 </pre
></blockquote
></p
>
208 <p
>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:
214 <p
><blockquote
><pre
>
219 isenkram-autoinstall-firmware -l
220 </pre
></blockquote
></p
>
222 <p
>With those two pieces in place, the firmware is installed by
223 tasksel during the normal d-i run. :)
</p
>
225 <p
>If you want to test what tasksel will install when isenkram-cli is
226 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
227 --new-install
</tt
> to get the list of packages that tasksel would
230 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
231 pilots in testing this feature, as isenkram is used there now to
232 install firmware, replacing the earlier scripts.
</p
>
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><p
>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:
</p
>
246 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
248 <p
>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 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
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><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
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
265 <p
>I just wrapped up
266 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
267 new lsdvd release
</a
>, available in git or from
268 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
269 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
274 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
275 <li
>Check for garbage in the program chains, which indicate that a track is
276 non-existant, to work around additional copy protection
</li
>
277 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
278 <li
>Fix pallete display of first entry
</li
>
279 <li
>Fix include orders
</li
>
280 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
281 <li
>Fix the chapter count
</li
>
282 <li
>Make sure the array size and the array limit used when initialising
283 the palette size is the same.
</li
>
284 <li
>Fix array printing.
</li
>
285 <li
>Correct subsecond calculations.
</li
>
286 <li
>Add sector information to the output format.
</li
>
287 <li
>Clean up code to be closer to ANSI C and compile without warnings
288 with more GCC compiler warnings.
</li
>
292 <p
>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. :)
</p
>