]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
5c890562f78564e608e5783d601a5492f442228a
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
11 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
13 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
14 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
15 related packages relevant for the computer installed automatically.
16 So I implemented one, using
17 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
18 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
19 run tasksel as user root. You should be presented with a new option,
20 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
21 select it, tasksel will install the packages isenkram claim is fit for
22 the current hardware, hot pluggable or not.&lt;p&gt;
23
24 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
25 description, and the other is the script used to extract the list of
26 packages to install. The first part is in
27 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
28 this:&lt;/p&gt;
29
30 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
31 Task: isenkram
32 Section: hardware
33 Description: Hardware specific packages (autodetected by isenkram)
34 Based on the detected hardware various hardware specific packages are
35 proposed.
36 Test-new-install: mark show
37 Relevance: 8
38 Packages: for-current-hardware
39 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
40
41 &lt;p&gt;The second part is in
42 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
43 this:&lt;/p&gt;
44
45 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
46 #!/bin/sh
47 #
48 (
49 isenkram-lookup
50 isenkram-autoinstall-firmware -l
51 ) | sort -u
52 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
53
54 &lt;p&gt;All in all, a very short and simple implementation making it
55 trivial to install the hardware dependent package we all may want to
56 have installed on our machines. I&#39;ve not been able to find a way to
57 get tasksel to tell you exactly which packages it plan to install
58 before doing the installation. So if you are curious or careful,
59 check the output from the isenkram-* command line tools first.&lt;/p&gt;
60
61 &lt;p&gt;The information about which packages are handling which hardware is
62 fetched either from the isenkram package itself in
63 /usr/share/isenkram/, from git.debian.org or from the APT package
64 database (using the Modaliases header). The APT package database
65 parsing have caused a nasty resource leak in the isenkram daemon (bugs
66 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
67 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
68 the python-apt code (bug
69 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
70 workaround I was able to get rid of the file descriptor leak and
71 reduce the memory leak from ~30 MiB per hardware detection down to
72 around 2 MiB per hardware detection. It should make the desktop
73 daemon a lot more useful. The fix is in version 0.7 uploaded to
74 unstable today.&lt;/p&gt;
75
76 &lt;p&gt;I believe the current way of mapping hardware to packages in
77 Isenkram is is a good draft, but in the future I expect isenkram to
78 use the AppStream data source for this. A proposal for getting proper
79 AppStream support into Debian is floating around as
80 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
81 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
82 project&lt;/a&gt; will take place this summer to improve the situation. I
83 look forward to seeing the result, and welcome patches for isenkram to
84 start using the information when it is ready.&lt;/p&gt;
85
86 &lt;p&gt;If you want your package to map to some specific hardware, either
87 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
88 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
89 package&lt;/a&gt; or submit a bug report with the details to the isenkram
90 package. See also
91 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
92 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
93 the information will be migrated to AppStream eventually, but for the
94 moment I got no better place to store it.&lt;/p&gt;
95 </description>
96 </item>
97
98 <item>
99 <title>FreedomBox milestone - all packages now in Debian Sid</title>
100 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
102 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
103 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
104 project&lt;/a&gt; is working on providing the software and hardware to make
105 it easy for non-technical people to host their data and communication
106 at home, and being able to communicate with their friends and family
107 encrypted and away from prying eyes. It is still going strong, and
108 today a major mile stone was reached.&lt;/p&gt;
109
110 &lt;p&gt;Today, the last of the packages currently used by the project to
111 created the system images were accepted into Debian Unstable. It was
112 the freedombox-setup package, which is used to configure the images
113 during build and on the first boot. Now all one need to get going is
114 the build code from the freedom-maker git repository and packages from
115 Debian. And once the freedombox-setup package enter testing, we can
116 build everything directly from Debian. :)&lt;/p&gt;
117
118 &lt;p&gt;Some key packages used by Freedombox are
119 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
120 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
121 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
122 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
123 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
124 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
125 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
126 are plans to integrate more packages into the setup. User
127 documentation is maintained on the Debian wiki. Please
128 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
129 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
130
131 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
132 setup, run this on a Debian machine using a user with sudo rights to
133 become root:&lt;/p&gt;
134
135 &lt;p&gt;&lt;pre&gt;
136 sudo apt-get install git vmdebootstrap mercurial python-docutils \
137 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
138 u-boot-tools
139 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
140 freedom-maker
141 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
142 &lt;/pre&gt;&lt;/p&gt;
143
144 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
145 devices. See the README in the freedom-maker git repo for more
146 details on the build. If you do not want all three images, trim the
147 make line. Note that the virtualbox-image target is not really
148 virtualbox specific. It create a x86 image usable in kvm, qemu,
149 vmware and any other x86 virtual machine environment. You might need
150 the version of vmdebootstrap in Jessie to get the build working, as it
151 include fixes for a race condition with kpartx.&lt;/p&gt;
152
153 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
154 method, boot a Debian Wheezy ISO and use this boot argument to load
155 the preseed values:&lt;/p&gt;
156
157 &lt;p&gt;&lt;pre&gt;
158 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
159 &lt;/pre&gt;&lt;/p&gt;
160
161 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
162 it still work.&lt;/p&gt;
163
164 &lt;p&gt;If you wonder how to help, one task you could look at is using
165 systemd as the boot system. It will become the default for Linux in
166 Jessie, so we need to make sure it is usable on the Freedombox. I did
167 a simple test a few weeks ago, and noticed dnsmasq failed to start
168 during boot when using systemd. I suspect there are other problems
169 too. :) To detect problems, there is a test suite included, which can
170 be run from the plinth web interface.&lt;/p&gt;
171
172 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
173 us get the new release published. :) Please join us on
174 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
175 irc.debian.org)&lt;/a&gt; and
176 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
177 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
178 </description>
179 </item>
180
181 <item>
182 <title>S3QL, a locally mounted cloud file system - nice free software</title>
183 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
185 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
186 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
187 solution for use at home. My requirements are simple, it must be
188 cheap and locally encrypted (in other words, I keep the encryption
189 keys, the storage provider do not have access to my private files).
190 One idea me and my friends had many years ago, before the cloud
191 storage providers showed up, was to use Google mail as storage,
192 writing a Linux block device storing blocks as emails in the mail
193 service provided by Google, and thus get heaps of free space. On top
194 of this one can add encryption, RAID and volume management to have
195 lots of (fairly slow, I admit that) cheap and encrypted storage. But
196 I never found time to implement such system. But the last few weeks I
197 have looked at a system called
198 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
199 mounted network backed file system with the features I need.&lt;/p&gt;
200
201 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
202 handling several different storage providers, any with Amazon S3,
203 Google Drive or OpenStack API. There are heaps of such storage
204 providers. S3QL can also use a local directory as storage, which
205 combined with sshfs allow for file storage on any ssh server. S3QL
206 include support for encryption, compression, de-duplication, snapshots
207 and immutable file systems, allowing me to mount the remote storage as
208 a local mount point, look at and use the files as if they were local,
209 while the content is stored in the cloud as well. This allow me to
210 have a backup that should survive fire. The file system can not be
211 shared between several machines at the same time, as only one can
212 mount it at the time, but any machine with the encryption key and
213 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
214
215 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
216 package is included already. So to get started, run &lt;tt&gt;apt-get
217 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
218 Greenqloud, after reading their nice recipe on
219 &lt;a href=&quot;https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy&quot;&gt;how
220 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
221 in Iceland more than those in USA when it come to keeping my personal
222 data safe and private, and thus would rather spend money on a company
223 in Iceland. Another nice recipe is available from the article
224 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
225 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
226 Admin magazine. When the provider is picked, figure out how to get
227 the API key needed to connect to the storage API. With Greencloud,
228 the key did not show up until I had added payment details to my
229 account.&lt;/p&gt;
230
231 &lt;p&gt;Armed with the API access details, it is time to create the file
232 system. First, create a new bucket in the cloud. This bucket is the
233 file system storage area. I picked a bucket name reflecting the
234 machine that was going to store data there, but any name will do.
235 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
236 the API login and password, and a locally created password. Store it
237 all in ~root/.s3ql/authinfo2 like this:
238
239 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
240 [s3c]
241 storage-url: s3c://s.greenqloud.com:443/bucket-name
242 backend-login: API-login
243 backend-password: API-password
244 fs-passphrase: local-password
245 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
246
247 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
248 but any sensible way to create a fairly random password should do it.
249 Armed with these details, it is now time to run mkfs, entering the API
250 details and password to create it:&lt;/p&gt;
251
252 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
253 # mkdir -m 700 /var/lib/s3ql-cache
254 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
255 --ssl s3c://s.greenqloud.com:443/bucket-name
256 Enter backend login:
257 Enter backend password:
258 Before using S3QL, make sure to read the user&#39;s guide, especially
259 the &#39;Important Rules to Avoid Loosing Data&#39; section.
260 Enter encryption password:
261 Confirm encryption password:
262 Generating random encryption key...
263 Creating metadata tables...
264 Dumping metadata...
265 ..objects..
266 ..blocks..
267 ..inodes..
268 ..inode_blocks..
269 ..symlink_targets..
270 ..names..
271 ..contents..
272 ..ext_attributes..
273 Compressing and uploading metadata...
274 Wrote 0.00 MB of compressed metadata.
275 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
276
277 &lt;p&gt;The next step is mounting the file system to make the storage available.
278
279 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
280 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
281 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
282 Using 4 upload threads.
283 Downloading and decompressing metadata...
284 Reading metadata...
285 ..objects..
286 ..blocks..
287 ..inodes..
288 ..inode_blocks..
289 ..symlink_targets..
290 ..names..
291 ..contents..
292 ..ext_attributes..
293 Mounting filesystem...
294 # df -h /s3ql
295 Filesystem Size Used Avail Use% Mounted on
296 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
297 #
298 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
299
300 &lt;p&gt;The file system is now ready for use. I use rsync to store my
301 backups in it, and as the metadata used by rsync is downloaded at
302 mount time, no network traffic (and storage cost) is triggered by
303 running rsync. To unmount, one should not use the normal umount
304 command, as this will not flush the cache to the cloud storage, but
305 instead running the umount.s3ql command like this:
306
307 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
308 # umount.s3ql /s3ql
309 #
310 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
311
312 &lt;p&gt;There is a fsck command available to check the file system and
313 correct any problems detected. This can be used if the local server
314 crashes while the file system is mounted, to reset the &quot;already
315 mounted&quot; flag. This is what it look like when processing a working
316 file system:&lt;/p&gt;
317
318 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
319 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
320 Using cached metadata.
321 File system seems clean, checking anyway.
322 Checking DB integrity...
323 Creating temporary extra indices...
324 Checking lost+found...
325 Checking cached objects...
326 Checking names (refcounts)...
327 Checking contents (names)...
328 Checking contents (inodes)...
329 Checking contents (parent inodes)...
330 Checking objects (reference counts)...
331 Checking objects (backend)...
332 ..processed 5000 objects so far..
333 ..processed 10000 objects so far..
334 ..processed 15000 objects so far..
335 Checking objects (sizes)...
336 Checking blocks (referenced objects)...
337 Checking blocks (refcounts)...
338 Checking inode-block mapping (blocks)...
339 Checking inode-block mapping (inodes)...
340 Checking inodes (refcounts)...
341 Checking inodes (sizes)...
342 Checking extended attributes (names)...
343 Checking extended attributes (inodes)...
344 Checking symlinks (inodes)...
345 Checking directory reachability...
346 Checking unix conventions...
347 Checking referential integrity...
348 Dropping temporary indices...
349 Backing up old metadata...
350 Dumping metadata...
351 ..objects..
352 ..blocks..
353 ..inodes..
354 ..inode_blocks..
355 ..symlink_targets..
356 ..names..
357 ..contents..
358 ..ext_attributes..
359 Compressing and uploading metadata...
360 Wrote 0.89 MB of compressed metadata.
361 #
362 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
363
364 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
365 quick, about the same speed as local file access. Uploading large
366 amount of data is to me limited by the bandwidth out of and into my
367 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
368 which is very close to my upload speed, and downloading the same
369 Debian installation ISO gave me 610 kiB/s, close to my download speed.
370 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
371 network, not the file system code. I do not know what a good cache
372 size would be, but suspect that the cache should e larger than your
373 working set.&lt;/p&gt;
374
375 &lt;p&gt;I mentioned that only one machine can mount the file system at the
376 time. If another machine try, it is told that the file system is
377 busy:&lt;/p&gt;
378
379 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
380 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
381 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
382 Using 8 upload threads.
383 Backend reports that fs is still mounted elsewhere, aborting.
384 #
385 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
386
387 &lt;p&gt;The file content is uploaded when the cache is full, while the
388 metadata is uploaded once every 24 hour by default. To ensure the
389 file system content is flushed to the cloud, one can either umount the
390 file system, or ask S3QL to flush the cache and metadata using
391 s3qlctrl:
392
393 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
394 # s3qlctrl upload-meta /s3ql
395 # s3qlctrl flushcache /s3ql
396 #
397 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
398
399 &lt;p&gt;If you are curious about how much space your data uses in the
400 cloud, and how much compression and deduplication cut down on the
401 storage usage, you can use s3qlstat on the mounted file system to get
402 a report:&lt;/p&gt;
403
404 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
405 # s3qlstat /s3ql
406 Directory entries: 9141
407 Inodes: 9143
408 Data blocks: 8851
409 Total data size: 22049.38 MB
410 After de-duplication: 21955.46 MB (99.57% of total)
411 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
412 Database size: 2.39 MB (uncompressed)
413 (some values do not take into account not-yet-uploaded dirty blocks in cache)
414 #
415 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
416
417 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
418 storage. I did not try to locate them all, but am aware of at least
419 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
420 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
421 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
422 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
423 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
424 accept payment in Bitcoin. Pick one that suit your need. Some of
425 them provide several GiB of free storage, but the prize models are
426 quite different and you will have to figure out what suits you
427 best.&lt;/p&gt;
428
429 &lt;p&gt;While researching this blog post, I had a look at research papers
430 and posters discussing the S3QL file system. There are several, which
431 told me that the file system is getting a critical check by the
432 science community and increased my confidence in using it. One nice
433 poster is titled
434 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
435 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
436 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
437 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
438 and Pamela Smith. Please have a look.&lt;/p&gt;
439
440 &lt;p&gt;Given my problems with different file systems earlier, I decided to
441 check out the mounted S3QL file system to see if it would be usable as
442 a home directory (in other word, that it provided POSIX semantics when
443 it come to locking and umask handling etc). Running
444 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html&quot;&gt;my
445 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
446 no error was found. So the file system can be used for home
447 directories, if one chooses to do so.&lt;/p&gt;
448
449 &lt;p&gt;If you do not want a locally file system, and want something that
450 work without the Linux fuse file system, I would like to mention the
451 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
452 provide locally encrypted backup using a command line client. It have
453 a nicer access control system, where one can split out read and write
454 access, allowing some systems to write to the backup and others to
455 only read from it.&lt;/p&gt;
456
457 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
458 activities, please send Bitcoin donations to my address
459 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
460 </description>
461 </item>
462
463 <item>
464 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
465 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
467 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
468 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
469 project&lt;/a&gt; is working on providing the software and hardware for
470 making it easy for non-technical people to host their data and
471 communication at home, and being able to communicate with their
472 friends and family encrypted and away from prying eyes. It has been
473 going on for a while, and is slowly progressing towards a new test
474 release (0.2).&lt;/p&gt;
475
476 &lt;p&gt;And what day could be better than the Pi day to announce that the
477 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
478 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
479 system), and can also be installed using a Debian installer preseed
480 file. The Debian based Freedombox is now based on Debian Jessie,
481 where most of the needed packages used are already present. Only one,
482 the freedombox-setup package, is missing. To try to build your own
483 boot image to test the current status, fetch the freedom-maker scripts
484 and build using
485 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
486 with a user with sudo access to become root:
487
488 &lt;pre&gt;
489 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
490 freedom-maker
491 sudo apt-get install git vmdebootstrap mercurial python-docutils \
492 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
493 u-boot-tools
494 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
495 &lt;/pre&gt;
496
497 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
498 devices. See the README for more details on the build. If you do not
499 want all three images, trim the make line. But note that thanks to &lt;a
500 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
501 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
502 kpartx call.&lt;/p&gt;
503
504 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
505 method, boot a Debian Wheezy ISO and use this boot argument to load
506 the preseed values:&lt;/p&gt;
507
508 &lt;pre&gt;
509 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
510 &lt;/pre&gt;
511
512 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
513 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
514 currently hang while setting up APT sources. Killing the
515 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
516 installation will get the installation going. This affect all
517 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
518
519 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
520 us get the new release published. :) Please join us on
521 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
522 irc.debian.org)&lt;/a&gt; and
523 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
524 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
525 </description>
526 </item>
527
528 <item>
529 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
530 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
532 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
533 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
534 innetgr tools, because I needed them in
535 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
536 ng-utils, and it has served me well. I placed the project under the
537 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
538 repository. But many years ago, the CVS repository was dropped (lost,
539 not migrated to new hardware, not sure), and the project have lacked a
540 proper home since then.&lt;/p&gt;
541
542 &lt;p&gt;Last summer, I had a look at the package and made a new release
543 fixing a irritating crash bug, but was unable to store the changes in
544 a proper source control system. I applied for a project on
545 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
546 to follow up on it. Until today. :)&lt;/p&gt;
547
548 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
549 now have a new home, and a git repository with the highlight of the
550 history of the project. I published all release tarballs and imported
551 them into the git repository. As the project is really stable and not
552 expected to gain new features any time soon, I decided to make a new
553 release and call it 1.0. Visit the new project home on
554 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
555 if you want to check it out. The new version is also uploaded into
556 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
557 </description>
558 </item>
559
560 <item>
561 <title>Testing sysvinit from experimental in Debian Hurd</title>
562 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
563 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
564 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
565 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
566 their changes into sysvinit, to allow them to use the normal sysvinit
567 boot system instead of their old one. This follow up on the
568 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
569 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
570 get Debian on Hurd working more like Debian on Linux. To get started,
571 I downloaded a prebuilt hard disk image from
572 &lt;a href=&quot;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&quot;&gt;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&lt;/a&gt;,
573 and started it using virt-manager.&lt;/p&gt;
574
575 &lt;p&gt;The first think I had to do after logging in (root without any
576 password) was to get the network operational. I followed
577 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
578 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
579 commands as root to get the machine to accept a IP address from the
580 kvm internal DHCP server:&lt;/p&gt;
581
582 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
583 settrans -fgap /dev/netdde /hurd/netdde
584 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
585 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
586 dhclient /dev/eth0
587 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
588
589 &lt;p&gt;After this, the machine had internet connectivity, and I could
590 upgrade it and install the sysvinit packages from experimental and
591 enable it as the default boot system in Hurd.&lt;/p&gt;
592
593 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
594 running on the machine it for ssh login to work a password need to be
595 set. Also, note that a bug somewhere in openssh on Hurd block
596 compression from working. Remember to turn that off on the client
597 side.&lt;/p&gt;
598
599 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
600 stuff:&lt;/p&gt;
601
602 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
603 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
604 deb http://http.debian.net/debian/ experimental main
605 EOF
606 apt-get update
607 apt-get dist-upgrade
608 apt-get install -t experimental initscripts sysv-rc sysvinit \
609 sysvinit-core sysvinit-utils
610 update-alternatives --config runsystem
611 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
612
613 &lt;p&gt;To reboot after switching boot system, you have to use
614 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
615 yet a sysvinit process able to receive the signals from the normal
616 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
617 upgrading every package and rebooting, the network come up with DHCP
618 after boot as it should, and the settrans/pkill hack mentioned at the
619 start is no longer needed. But for some strange reason, there are no
620 longer any login prompt in the virtual console, so I logged in using
621 ssh instead.
622
623 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
624 fail some times. No idea what the cause is, but hope the Hurd porters
625 figure it out. At least Justus said on IRC (#debian-hurd on
626 irc.debian.org) that they are aware of the problem. A way to reduce
627 the impact is to upgrade to the Hurd packages built by Justus by
628 adding this repository to the machine:&lt;/p&gt;
629
630 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
631 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
632 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
633 EOF
634 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
635
636 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
637 http://ftp.debian-ports.org/debian, because some of the packages in
638 unstable do not yet include the required patches that are lingering in
639 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
640
641 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
642 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
643 i emacs - GNU Emacs editor (metapackage)
644 i gdb - GNU Debugger
645 i hurd-recommended - Miscellaneous translators
646 i isc-dhcp-client - ISC DHCP client
647 i isc-dhcp-common - common files used by all the isc-dhcp* packages
648 i libc-bin - Embedded GNU C Library: Binaries
649 i libc-dev-bin - Embedded GNU C Library: Development binaries
650 i libc0.3 - Embedded GNU C Library: Shared libraries
651 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
652 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
653 i multiarch-support - Transitional package to ensure multiarch compatibilit
654 i A x11-common - X Window System (X.Org) infrastructure
655 i xorg - X.Org X Window System
656 i A xserver-xorg - X.Org X server
657 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
658 #
659 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
660
661 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
662 X.org did not work out of the box and I never took the time to follow
663 the porters instructions to fix it. This time I was interested in the
664 command line stuff.&lt;p&gt;
665 </description>
666 </item>
667
668 <item>
669 <title>New chrpath release 0.16</title>
670 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
671 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
672 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
673 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
674 find problems in C, C++ and Java code using static source code
675 analysis. It can detect a lot of different problems, and is very
676 useful to find memory and locking bugs in the error handling part of
677 the source. The company behind it provide
678 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
679 a community service&lt;/a&gt;, and many hundred free software projects are
680 already checked. A few days ago I decided to have a closer look at
681 the Coverity system, and discovered that the
682 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
683 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
684 projects I am involved with was already registered. But these are
685 fairly big, and I would also like to have a small and easy project to
686 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
687 checking of the chrpath project&lt;/a&gt;. It was
688 added to the checker and discovered seven potential defects. Six of
689 these were real, mostly resource &quot;leak&quot; when the program detected an
690 error. Nothing serious, as the resources would be released a fraction
691 of a second later when the program exited because of the error, but it
692 is nice to do it right in case the source of the program some time in
693 the future end up in a library. Having fixed all defects and added
694 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
695 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
696 publish a new release. These are the release notes:&lt;/p&gt;
697
698 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
699
700 &lt;ul&gt;
701
702 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
703 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
704 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
705
706 &lt;/ul&gt;
707
708 &lt;p&gt;You can
709 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
710 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
711 project if something is wrong with the new release. The test suite
712 did not discover any old errors, so if you find a new one, please also
713 include a test suite check.&lt;/p&gt;
714 </description>
715 </item>
716
717 <item>
718 <title>New chrpath release 0.15</title>
719 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
720 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
721 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
722 <description>&lt;p&gt;After many years break from the package and a vain hope that
723 development would be continued by someone else, I finally pulled my
724 acts together this morning and wrapped up a new release of chrpath,
725 the command line tool to modify the rpath and runpath of already
726 compiled ELF programs. The update was triggered by the persistence of
727 Isha Vishnoi at IBM, which needed a new config.guess file to get
728 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
729 is working on. I checked the
730 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
731 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
732 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
733 packages for interesting patches (failed to find the source from
734 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
735 These are the release notes:&lt;/p&gt;
736
737 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
738
739 &lt;ul&gt;
740
741 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
742 with newer architectures. Thanks to isha vishnoi for the heads
743 up.&lt;/li&gt;
744
745 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
746
747 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
748 Matthias Klose.&lt;/li&gt;
749
750 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
751 Petr Machata found in Fedora.&lt;/li&gt;
752
753 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
754 .dynamic is a NULL terminated string. Based on patch found in
755 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
756
757 &lt;/ul&gt;
758
759 &lt;p&gt;You can
760 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
761 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
762 project if something is wrong with the new release. The test suite
763 did not discover any old errors, so if you find a new one, please also
764 include a testsuite check.&lt;/p&gt;
765 </description>
766 </item>
767
768 <item>
769 <title>Debian init.d boot script example for rsyslog</title>
770 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
772 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
773 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
774 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
775 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
776 init.d scripts at all. Here is an example init.d script, ie a rewrite
777 of /etc/init.d/rsyslog:&lt;/p&gt;
778
779 &lt;p&gt;&lt;pre&gt;
780 #!/lib/init/init-d-script
781 ### BEGIN INIT INFO
782 # Provides: rsyslog
783 # Required-Start: $remote_fs $time
784 # Required-Stop: umountnfs $time
785 # X-Stop-After: sendsigs
786 # Default-Start: 2 3 4 5
787 # Default-Stop: 0 1 6
788 # Short-Description: enhanced syslogd
789 # Description: Rsyslog is an enhanced multi-threaded syslogd.
790 # It is quite compatible to stock sysklogd and can be
791 # used as a drop-in replacement.
792 ### END INIT INFO
793 DESC=&quot;enhanced syslogd&quot;
794 DAEMON=/usr/sbin/rsyslogd
795 &lt;/pre&gt;&lt;/p&gt;
796
797 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
798 script was 137 lines, and the above is just 15 lines, most of it meta
799 info/comments.&lt;/p&gt;
800
801 &lt;p&gt;How to do this, you ask? Well, one create a new script
802 /lib/init/init-d-script looking something like this:
803
804 &lt;p&gt;&lt;pre&gt;
805 #!/bin/sh
806
807 # Define LSB log_* functions.
808 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
809 # and status_of_proc is working.
810 . /lib/lsb/init-functions
811
812 #
813 # Function that starts the daemon/service
814
815 #
816 do_start()
817 {
818 # Return
819 # 0 if daemon has been started
820 # 1 if daemon was already running
821 # 2 if daemon could not be started
822 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
823 || return 1
824 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
825 $DAEMON_ARGS \
826 || return 2
827 # Add code here, if necessary, that waits for the process to be ready
828 # to handle requests from services started subsequently which depend
829 # on this one. As a last resort, sleep for some time.
830 }
831
832 #
833 # Function that stops the daemon/service
834 #
835 do_stop()
836 {
837 # Return
838 # 0 if daemon has been stopped
839 # 1 if daemon was already stopped
840 # 2 if daemon could not be stopped
841 # other if a failure occurred
842 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
843 RETVAL=&quot;$?&quot;
844 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
845 # Wait for children to finish too if this is a daemon that forks
846 # and if the daemon is only ever run from this initscript.
847 # If the above conditions are not satisfied then add some other code
848 # that waits for the process to drop all resources that could be
849 # needed by services started subsequently. A last resort is to
850 # sleep for some time.
851 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
852 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
853 # Many daemons don&#39;t delete their pidfiles when they exit.
854 rm -f $PIDFILE
855 return &quot;$RETVAL&quot;
856 }
857
858 #
859 # Function that sends a SIGHUP to the daemon/service
860 #
861 do_reload() {
862 #
863 # If the daemon can reload its configuration without
864 # restarting (for example, when it is sent a SIGHUP),
865 # then implement that here.
866 #
867 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
868 return 0
869 }
870
871 SCRIPTNAME=$1
872 scriptbasename=&quot;$(basename $1)&quot;
873 echo &quot;SN: $scriptbasename&quot;
874 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
875 script=&quot;$1&quot;
876 shift
877 . $script
878 else
879 exit 0
880 fi
881
882 NAME=$(basename $DAEMON)
883 PIDFILE=/var/run/$NAME.pid
884
885 # Exit if the package is not installed
886 #[ -x &quot;$DAEMON&quot; ] || exit 0
887
888 # Read configuration variable file if it is present
889 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
890
891 # Load the VERBOSE setting and other rcS variables
892 . /lib/init/vars.sh
893
894 case &quot;$1&quot; in
895 start)
896 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
897 do_start
898 case &quot;$?&quot; in
899 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
900 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
901 esac
902 ;;
903 stop)
904 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
905 do_stop
906 case &quot;$?&quot; in
907 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
908 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
909 esac
910 ;;
911 status)
912 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
913 ;;
914 #reload|force-reload)
915 #
916 # If do_reload() is not implemented then leave this commented out
917 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
918 #
919 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
920 #do_reload
921 #log_end_msg $?
922 #;;
923 restart|force-reload)
924 #
925 # If the &quot;reload&quot; option is implemented then remove the
926 # &#39;force-reload&#39; alias
927 #
928 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
929 do_stop
930 case &quot;$?&quot; in
931 0|1)
932 do_start
933 case &quot;$?&quot; in
934 0) log_end_msg 0 ;;
935 1) log_end_msg 1 ;; # Old process is still running
936 *) log_end_msg 1 ;; # Failed to start
937 esac
938 ;;
939 *)
940 # Failed to stop
941 log_end_msg 1
942 ;;
943 esac
944 ;;
945 *)
946 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
947 exit 3
948 ;;
949 esac
950
951 :
952 &lt;/pre&gt;&lt;/p&gt;
953
954 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
955 lot. I did not really polish the approach, so it might not always
956 work out of the box, but you get the idea. I did not try very hard to
957 optimize it nor make it more robust either.&lt;/p&gt;
958
959 &lt;p&gt;A better argument for switching init system in Debian than reducing
960 the size of init scripts (which is a good thing to do anyway), is to
961 get boot system that is able to handle the kernel events sensibly and
962 robustly, and do not depend on the boot to run sequentially. The boot
963 and the kernel have not behaved sequentially in years.&lt;/p&gt;
964 </description>
965 </item>
966
967 <item>
968 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
969 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
970 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
971 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
972 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
973 remote display access is the preferred solution with oVirt and RedHat
974 Enterprise Virtualization, and I was sad to discover the other day
975 that the browser plugin needed to use these systems seamlessly was
976 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
977 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
978 2013-04-01, so I decided to wrap up a package based on the great work
979 from Cajus Pollmeier and put it in a collab-maint maintained git
980 repository to get a package I could use. I would very much like
981 others to help me maintain the package (or just take over, I do not
982 mind), but as no-one had volunteered so far, I just uploaded it to
983 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
984
985 &lt;p&gt;The source is now available from
986 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&quot;&gt;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&lt;/a&gt;.&lt;/p&gt;
987 </description>
988 </item>
989
990 <item>
991 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
992 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
994 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
995 <description>&lt;p&gt;The
996 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
997 program is a a very nice system to create virtual machine images. It
998 create a image file, add a partition table, mount it and run
999 debootstrap in the mounted directory to create a Debian system on a
1000 stick. Yesterday, I decided to try to teach it how to make images for
1001 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1002 of a plan to simplify the build system for
1003 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1004 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1005 the virtualbox images, but its current build system made multistrap
1006 based system for Dreamplug images, and it is lacking support for
1007 Raspberry Pi.&lt;/p&gt;
1008
1009 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1010 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1011 code and adjusted it to be able to build armel images on my amd64
1012 Debian laptop. I ended up giving vmdebootstrap five new options,
1013 allowing me to replicate the image creation process I use to make
1014 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1015 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1016 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1017 call debootstrap with --foreign and to copy the handler into the
1018 generated chroot before running the second stage. This allow
1019 vmdebootstrap to create armel images on an amd64 host. Next I added
1020 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1021 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1022 given file system type, allowing me to create an image with a vfat
1023 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1024 variant&lt;/tt&gt; option to allow me to create smaller images without the
1025 Debian base system packages installed. Finally, I added an option
1026 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1027 as a boot loader. It is not needed on the Raspberry Pi and probably
1028 most other non-x86 architectures. The changes were accepted by the
1029 upstream author of vmdebootstrap yesterday and today, and is now
1030 available from
1031 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1032 upstream project page&lt;/a&gt;.&lt;/p&gt;
1033
1034 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1035 create a small script (the customize script) to add the non-free
1036 binary blob needed to boot the Raspberry Pi and the APT source
1037 list:&lt;/p&gt;
1038
1039 &lt;p&gt;&lt;pre&gt;
1040 #!/bin/sh
1041 set -e # Exit on first error
1042 rootdir=&quot;$1&quot;
1043 cd &quot;$rootdir&quot;
1044 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1045 deb http://http.debian.net/debian/ jessie main contrib non-free
1046 EOF
1047 # Install non-free binary blob needed to boot Raspberry Pi. This
1048 # install a kernel somewhere too.
1049 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1050 -O $rootdir/usr/bin/rpi-update
1051 chmod a+x $rootdir/usr/bin/rpi-update
1052 mkdir -p $rootdir/lib/modules
1053 touch $rootdir/boot/start.elf
1054 chroot $rootdir rpi-update
1055 &lt;/pre&gt;&lt;/p&gt;
1056
1057 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1058 to build the image:&lt;/p&gt;
1059
1060 &lt;pre&gt;
1061 sudo ./vmdebootstrap \
1062 --variant minbase \
1063 --arch armel \
1064 --distribution jessie \
1065 --mirror http://http.debian.net/debian \
1066 --image test.img \
1067 --size 600M \
1068 --bootsize 64M \
1069 --boottype vfat \
1070 --log-level debug \
1071 --verbose \
1072 --no-kernel \
1073 --no-extlinux \
1074 --root-password raspberry \
1075 --hostname raspberrypi \
1076 --foreign /usr/bin/qemu-arm-static \
1077 --customize `pwd`/customize \
1078 --package netbase \
1079 --package git-core \
1080 --package binutils \
1081 --package ca-certificates \
1082 --package wget \
1083 --package kmod
1084 &lt;/pre&gt;&lt;/p&gt;
1085
1086 &lt;p&gt;The list of packages being installed are the ones needed by
1087 rpi-update to make the image bootable on the Raspberry Pi, with the
1088 exception of netbase, which is needed by debootstrap to find
1089 /etc/hosts with the minbase variant. I really wish there was a way to
1090 set up an Raspberry Pi using only packages in the Debian archive, but
1091 that is not possible as far as I know, because it boots from the GPU
1092 using a non-free binary blob.&lt;/p&gt;
1093
1094 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1095 probably a few others installed. I have not checked the complete
1096 build dependency list.&lt;/p&gt;
1097
1098 &lt;p&gt;The resulting image will not use the hardware floating point unit
1099 on the Raspberry PI, because the armel architecture in Debian is not
1100 optimized for that use. So the images created will be a bit slower
1101 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1102 </description>
1103 </item>
1104
1105 <item>
1106 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1107 <link>http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</link>
1108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</guid>
1109 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1110 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1111 wider attention. I recommend signing and donating to each one of
1112 these. :)&lt;/p&gt;
1113
1114 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1115 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1116 Women program which is a Google Summer of Code like initiative to get
1117 more women involved in free software. One debian sponsor has offered
1118 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1119 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1120 hope you will to. :)&lt;/p&gt;
1121
1122 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1123 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1124 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1125 take place these days, and their need to fund the work. I&#39;ve already
1126 donated. Are you next?&lt;/p&gt;
1127
1128 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1129 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1130 statement under the heading
1131 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1132 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1133 Norwegian government. So far 499 signatures. I hope you will sign it
1134 too.&lt;/p&gt;
1135 </description>
1136 </item>
1137
1138 <item>
1139 <title>Videos about the Freedombox project - for inspiration and learning</title>
1140 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1142 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1143 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1144 project&lt;/a&gt; have been going on for a while, and have presented the
1145 vision, ideas and solution several places. Here is a little
1146 collection of videos of talks and presentation of the project.&lt;/p&gt;
1147
1148 &lt;ul&gt;
1149
1150 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1151 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1152
1153 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1154 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1155
1156 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1157 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1158 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1159 (Youtube)&lt;/li&gt;
1160
1161 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1162 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1163
1164 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1165 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1166
1167 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1168 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1169 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1170
1171 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1172 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1173 (Youtube)&lt;/li&gt;
1174
1175 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1176 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1177
1178 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1179 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1180
1181 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1182 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1183 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1184
1185 &lt;/ul&gt;
1186
1187 &lt;p&gt;A larger list is available from
1188 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1189 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1190
1191 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1192 Jessie is coming along quite well, and soon both Owncloud and using
1193 Tor should be available for testers of the Freedombox solution. :) In
1194 a few weeks I hope everything needed to test it is included in Debian.
1195 The withsqlite package is already in Debian, and the plinth package is
1196 pending in NEW. The third and vital part of that puzzle is the
1197 metapackage/setup framework, which is still pending an upload. Join
1198 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1199 (#freedombox on irc.debian.org)&lt;/a&gt; and
1200 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1201 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1202 </description>
1203 </item>
1204
1205 <item>
1206 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1207 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1208 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1209 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1210 <description>&lt;p&gt;I was introduced to the
1211 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1212 in 2010, when Eben Moglen presented his vision about serving the need
1213 of non-technical people to keep their personal information private and
1214 within the legal protection of their own homes. The idea is to give
1215 people back the power over their network and machines, and return
1216 Internet back to its intended peer-to-peer architecture. Instead of
1217 depending on a central service, the Freedombox will give everyone
1218 control over their own basic infrastructure.&lt;/p&gt;
1219
1220 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1221 taken priority. But this summers nasty news about the misuse of trust
1222 and privilege exercised by the &quot;western&quot; intelligence gathering
1223 communities increased my eagerness to contribute to a point where I
1224 actually started working on the project a while back.&lt;/p&gt;
1225
1226 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1227 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1228 create a simple and cheap Debian based appliance that anyone can hook
1229 up in their home and get access to secure and private services and
1230 communication. The initial deployment platform have been the
1231 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1232 which is a piece of hardware I do not own. So to be able to test what
1233 the current Freedombox setup look like, I had to come up with a way to install
1234 it on some hardware I do have access to. I have rewritten the
1235 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1236 image build framework to use .deb packages instead of only copying
1237 setup into the boot images, and thanks to this rewrite I am able to
1238 set up any machine supported by Debian Wheezy as a Freedombox, using
1239 the previously mentioned deb (and a few support debs for packages
1240 missing in Debian).&lt;/p&gt;
1241
1242 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1243 scripts
1244 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1245 and a administrative web interface
1246 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1247 withsqlite), as well as a privacy enhancing proxy based on
1248 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1249 (freedombox-privoxy). There is also a web/javascript based XMPP
1250 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1251 trying (unsuccessfully so far) to talk to the XMPP server
1252 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1253 web interface is pluggable, and the goal is to use it to enable OpenID
1254 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1255 this is really working yet, see
1256 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1257 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1258 on github at the moment. The HTTP proxy is operational out of the
1259 box, and the admin web interface can be used to add/remove plinth
1260 users. I&#39;ve not been able to do anything else with it so far, but
1261 know there are several branches spread around github and other places
1262 with lots of half baked features.&lt;/p&gt;
1263
1264 &lt;p&gt;Anyway, if you want to have a look at the current state, the
1265 following recipes should work to give you a test machine to poke
1266 at.&lt;/p&gt;
1267
1268 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
1269
1270 &lt;ol&gt;
1271
1272 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
1273 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
1274 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
1275 to the Debian installer:&lt;p&gt;
1276 &lt;pre&gt;url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&lt;/a&gt;&lt;/pre&gt;&lt;/li&gt;
1277
1278 &lt;li&gt;Answer the few language/region/password questions and pick disk to
1279 install on.&lt;/li&gt;
1280
1281 &lt;li&gt;When the installation is finished and the machine have rebooted a
1282 few times, your Freedombox is ready for testing.&lt;/li&gt;
1283
1284 &lt;/ol&gt;
1285
1286 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
1287
1288 &lt;ol&gt;
1289
1290 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
1291 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
1292 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
1293 &lt;pre&gt;
1294 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
1295 &lt;/pre&gt;&lt;/li&gt;
1296 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
1297 &lt;pre&gt;
1298 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1299 apt-key add -
1300 apt-get update
1301 apt-get install freedombox-setup
1302 /usr/lib/freedombox/setup
1303 &lt;/pre&gt;&lt;/li&gt;
1304 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
1305
1306 &lt;/ol&gt;
1307
1308 &lt;p&gt;You can test it on other architectures too, but because the
1309 freedombox-privoxy package is binary, it will only work as intended on
1310 the architectures where I have had time to build the binary and put it
1311 in my APT repository. But do not let this stop you. It is only a
1312 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
1313
1314 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
1315 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
1316 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
1317 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
1318
1319 &lt;p&gt;Please let me know if this works for you, or if you have any
1320 problems. We gather on the IRC channel
1321 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
1322 irc.debian.org and the
1323 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
1324 mailing list&lt;/a&gt;.&lt;/p&gt;
1325
1326 &lt;p&gt;Once you get your freedombox operational, you can visit
1327 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
1328 welcome screen (dead end - do not be surprised if you are unable to
1329 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
1330 to look at the rest of plinth. The default user is &#39;admin&#39; and the
1331 default password is &#39;secret&#39;.&lt;/p&gt;
1332 </description>
1333 </item>
1334
1335 <item>
1336 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
1337 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
1338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
1339 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
1340 <description>&lt;p&gt;Earlier, I reported about
1341 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html&quot;&gt;my
1342 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
1343 told by IBM that the original disk should be thrown away. And as
1344 there no longer was a problem if I bricked the firmware, I decided
1345 today to try to install Intel firmware to replace the Lenovo firmware
1346 currently on the disk.&lt;/p&gt;
1347
1348 &lt;p&gt;I searched the Intel site for firmware, and found
1349 &lt;a href=&quot;https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&amp;ProdId=3472&amp;DwnldID=18363&amp;ProductFamily=Solid-State+Drives+and+Caching&amp;ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&amp;ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&amp;lang=eng&quot;&gt;issdfut_2.0.4.iso&lt;/a&gt;
1350 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1351 according to the site should contain the latest firmware for SSD
1352 disks. I inserted the broken disk in one of my spare laptops and
1353 booted the ISO from a USB stick. The disk was recognized, but the
1354 program claimed the newest firmware already were installed and refused
1355 to insert any Intel firmware. So no change, and the disk is still
1356 unable to handle write load. :( I guess the only way to get them
1357 working would be if Lenovo releases new firmware. No idea how likely
1358 that is. Anyway, just blogging about this test for completeness. I
1359 got a working Samsung disk, and see no point in spending more time on
1360 the broken disks.&lt;/p&gt;
1361 </description>
1362 </item>
1363
1364 <item>
1365 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
1366 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
1367 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
1368 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
1369 <description>&lt;p&gt;Today I switched to
1370 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
1371 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
1372 my new Thinkpad X230, which was delivered with an
1373 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html&quot;&gt;180
1374 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
1375 sustained writes. My hardware supplier have been very forthcoming in
1376 trying to find a solution, and after first trying with another
1377 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
1378 disk instead to fix it once and for all. The Samsung disk survived
1379 the installation of Debian with encrypted disks (filling the disk with
1380 random data during installation killed the first two), and I thus
1381 decided to trust it with my data. I have installed it as a Debian Edu
1382 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1383 server at home using Kerberos and LDAP, and will use it as my work
1384 station from now on.&lt;/p&gt;
1385
1386 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
1387 Debian Wheezy default installation need to be tuned a bit to increase
1388 performance and increase life time of the disk. The Linux kernel and
1389 user space applications do not yet adjust automatically to such
1390 environment. To make it easier for my self, I created a draft Debian
1391 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
1392 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
1393 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
1394 is set up to adjust the setup of the machine by just installing the
1395 package. If there is any non-SSD disk in the machine, the package
1396 will refuse to install, as I did not try to write any logic to sort
1397 file systems in SSD and non-SSD file systems.&lt;/p&gt;
1398
1399 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
1400 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1401 where I set up the machine with one large encrypted partition (in
1402 addition to /boot), put LVM on top of this and set up partitions on
1403 top of this again. See the README file in the package source for the
1404 references I used to pick the settings. At the moment these
1405 parameters are tuned:&lt;/p&gt;
1406
1407 &lt;ul&gt;
1408
1409 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
1410 (adding discard to /etc/crypttab)&lt;/li&gt;
1411
1412 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
1413 this case a cryptsetup partition) by changing issue_discards from
1414 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
1415
1416 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
1417 systems.&lt;/li&gt;
1418
1419 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
1420 /etc/fstab.&lt;/li&gt;
1421
1422 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
1423
1424 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
1425 cron.daily).&lt;/li&gt;
1426
1427 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
1428 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
1429
1430 &lt;/ul&gt;
1431
1432 &lt;p&gt;During installation, I cancelled the part where the installer fill
1433 the disk with random data, as this would kill the SSD performance for
1434 little gain. My goal with the encrypted file system is to ensure
1435 those stealing my laptop end up with a brick and not a working
1436 computer. I have no hope in keeping the really resourceful people
1437 from getting the data on the disk (see
1438 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
1439 Thus I concluded that adding the discard option to crypttab is the
1440 right thing to do.&lt;/p&gt;
1441
1442 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
1443 it for SSD, but others recommended deadline and a benchmark I found
1444 indicated that deadline might be better for interactive use.&lt;/p&gt;
1445
1446 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
1447 and ext4, but read that it would give a performance hit ever time a
1448 file is removed, and thought it best to that that slowdown once a day
1449 instead of during my work.&lt;/p&gt;
1450
1451 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1452 this is already done by Debian Edu.&lt;/p&gt;
1453
1454 &lt;p&gt;I have not yet started on the user space tuning. I expect
1455 iceweasel need some tuning, and perhaps other applications too, but
1456 have not yet had time to investigate those parts.&lt;/p&gt;
1457
1458 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
1459 there.&lt;/p&gt;
1460
1461 &lt;p&gt;As for the answer to the question in the title of this blog post,
1462 as far as I know, the only solution I know about is to replace the
1463 disk. It might be possible to flash it with Intel firmware instead of
1464 the Lenovo firmware. But I have not tried and did not want to do so
1465 without approval from Lenovo as I wanted to keep the warranty on the
1466 disk until a solution was found and they wanted the broken disks
1467 back.&lt;/p&gt;
1468 </description>
1469 </item>
1470
1471 <item>
1472 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
1473 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
1474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</guid>
1475 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
1476 <description>&lt;p&gt;A few days ago, I wrote about
1477 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
1478 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
1479 was dying during installation because it is unable to cope with
1480 sustained write. My supplier is in contact with
1481 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
1482 replacement disk to try to fix the problem. They decided to send an
1483 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
1484
1485 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
1486 Debian Edu Wheezy with encrypted disk on it. The new disk have the
1487 same firmware version as the original. This time my hope raised
1488 slightly as the installation progressed, as the original disk used to
1489 die after 4-7% of the disk was written to, while this time it kept
1490 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
1491 died again and I was back on square one. I still do not have a new
1492 laptop with a disk I can trust. I can not live with a disk that might
1493 lock up when I download a new
1494 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
1495 other large files. I look forward to hearing from my supplier with
1496 the next proposal from Lenovo.&lt;/p&gt;
1497
1498 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
1499 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
1500 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1501 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
1502 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1503 P/N 45N8295, P0C38732.&lt;/p&gt;
1504
1505 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
1506 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
1507 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1508 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
1509 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1510 P/N 45N8295, P0C38732.&lt;/p&gt;
1511
1512 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
1513 SA, date and WNPP values. Mentioning all the details here in case
1514 someone is able to use the information to find a way to identify the
1515 failing disk among working ones (if any such working disk actually
1516 exist).&lt;/p&gt;
1517 </description>
1518 </item>
1519
1520 <item>
1521 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
1522 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
1523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
1524 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
1525 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
1526 Debian Edu developer gathering and Debian and Ubuntu bug squashing
1527 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
1528 member assosiation NUUG&lt;/a&gt; and
1529 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
1530 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
1531 Bitraf&lt;/a&gt;.&lt;/p&gt;
1532
1533 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
1534 welcome, and there is no fee to participate. There is on the other
1535 hand limited space, and only room for 30 people. Please put your name
1536 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
1537 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
1538 </description>
1539 </item>
1540
1541 <item>
1542 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
1543 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
1544 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
1545 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
1546 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
1547 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
1548 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
1549 time to spend on it, and it took a while to find a model I believe
1550 will do the job, but two days ago the replacement finally arrived. I
1551 ended up picking a
1552 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
1553 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
1554 a roaming workstation, and it seemed to work flawlessly. But my
1555 second installation with encrypted disk was not as successful. More
1556 on that below.&lt;/p&gt;
1557
1558 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
1559 important requirements (robust and with a good keyboard) are never
1560 listed in the feature list. But I did get good help from the search
1561 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
1562 allowed me to limit the list of interesting laptops based on my other
1563 requirements. A bit surprising that SSD disk are not disks according
1564 to that search interface, so I had to drop specifying the number of
1565 disks from my search parameters. I also asked around among friends to
1566 get their impression on keyboards and robustness.&lt;/p&gt;
1567
1568 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
1569 X41. I am not quite convinced about the keyboard, as it is
1570 significantly wider than my old keyboard, and I have to stretch my
1571 hand a lot more to reach the edges. But the key response is fairly
1572 good and the individual key shape is fairly easy to handle, so I hope
1573 I will get used to it. My old X40 was starting to fail, and I really
1574 needed a new laptop now. :)&lt;/p&gt;
1575
1576 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
1577 visit to the BIOS during boot it disable it.&lt;/p&gt;
1578
1579 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
1580 lock up during load. And this happen when installing Debian Wheezy
1581 with encrypted disk, while the disk is being filled with random data.
1582 I also tested to install Ubuntu Raring, and it happen there too if I
1583 reenable the code to fill the disk with random data (it is disabled by
1584 default in Ubuntu). And the bug with is already known. It was
1585 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
1586 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
1587 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
1588 kernel developers as
1589 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
1590 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
1591 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
1592 Lenovo forums, both for
1593 &lt;a href=&quot;http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-520-180GB-issue/m-p/1070549&quot;&gt;T430
1594 2012-11-10&lt;/a&gt; and for
1595 &lt;a href=&quot;http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-180GB-Intel-520-SSD-under-heavy-write-load/m-p/1068147&quot;&gt;X230
1596 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
1597 reports state that the disk lock up during use if many writes are done
1598 on the disk, so it is much no use to work around the installation
1599 problem and end up with a computer that can lock up at any moment.
1600 There is even a
1601 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
1602 available&lt;/a&gt; that will lock up the hard drive after running a few
1603 minutes by writing to a file.&lt;/p&gt;
1604
1605 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
1606 contacting PCHELP Norway (request 01D1FDP) which handle support
1607 requests for Lenovo, his first suggestion was to upgrade the disk
1608 firmware. Unfortunately there is no newer firmware available from
1609 Lenovo, as my disk already have the most recent one (version LF1i). I
1610 hope to hear more from him today and hope the problem can be
1611 fixed. :)&lt;/p&gt;
1612 </description>
1613 </item>
1614
1615 <item>
1616 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
1617 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
1618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
1619 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
1620 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
1621 trusty old Thinkpad X41. Unfortunately I did not have much time to
1622 spend on it, but today the replacement finally arrived. I ended up
1623 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
1624 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
1625 Wheezy as a roaming workstation, and it worked flawlessly. As I write
1626 this, it is installing what I hope will be a more final installation,
1627 with a encrypted hard drive to ensure any dope head stealing it end up
1628 with an expencive door stop.&lt;/p&gt;
1629
1630 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
1631 important requirements (robust and with a good keyboard) are never
1632 listed in the feature list. But I did get good help from the search
1633 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
1634 allowed me to limit the list of interesting laptops based on my other
1635 requirements. A bit surprising that SSD disk are not disks, so I had
1636 to drop number of disks from my search parameters.&lt;/p&gt;
1637
1638 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
1639 wider than my old keyboard, and I have to stretch my hand a lot more
1640 to reach the edges. But the key response is fairly good and the
1641 individual key shape is fairly easy to handle, so I hope I will get
1642 used to it. My old X40 was starting to fail, and I really needed a
1643 new laptop now. :)&lt;/p&gt;
1644
1645 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
1646 </description>
1647 </item>
1648
1649 <item>
1650 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
1651 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
1652 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
1653 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
1654 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
1655 perfectly capable of, and I have to do it manually to get things
1656 working. One such task is to find out what firmware packages are
1657 needed to get the hardware on my computer working. Most often this
1658 affect the wifi card, but some times it even affect the RAID
1659 controller or the ethernet card. Today I pushed version 0.4 of the
1660 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
1661 including a new script isenkram-autoinstall-firmware handling the
1662 process of asking all the loaded kernel modules what firmware files
1663 they want, find debian packages providing these files and install the
1664 debian packages. Here is a test run on my laptop:&lt;/p&gt;
1665
1666 &lt;p&gt;&lt;pre&gt;
1667 # isenkram-autoinstall-firmware
1668 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
1669 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
1670 info: locating packages with the requested firmware files
1671 info: Updating APT sources after adding non-free APT source
1672 info: trying to install firmware-ipw2x00
1673 firmware-ipw2x00
1674 firmware-ipw2x00
1675 Preconfiguring packages ...
1676 Selecting previously deselected package firmware-ipw2x00.
1677 (Reading database ... 259727 files and directories currently installed.)
1678 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
1679 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
1680 #
1681 &lt;/pre&gt;&lt;/p&gt;
1682
1683 &lt;p&gt;When all the requested firmware is present, a simple message is
1684 printed instead:&lt;/p&gt;
1685
1686 &lt;p&gt;&lt;pre&gt;
1687 # isenkram-autoinstall-firmware
1688 info: did not find any firmware files requested by loaded kernel modules. exiting
1689 #
1690 &lt;/pre&gt;&lt;/p&gt;
1691
1692 &lt;p&gt;It could use some polish, but it is already working well and saving
1693 me some time when setting up new machines. :)&lt;/p&gt;
1694
1695 &lt;p&gt;So, how does it work? It look at the set of currently loaded
1696 kernel modules, and look up each one of them using modinfo, to find
1697 the firmware files listed in the module meta-information. Next, it
1698 download the Contents file from a nearby APT mirror, and search for
1699 the firmware files in this file to locate the package with the
1700 requested firmware file. If the package is in the non-free section, a
1701 non-free APT source is added and the package is installed using
1702 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
1703 machine.&lt;/p&gt;
1704
1705 &lt;p&gt;I hope someone find time to implement a more polished version of
1706 this script as part of the hw-detect debian-installer module, to
1707 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
1708 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
1709 firmware during a PXE install when the packages already are available
1710 from the nearby Debian mirror.&lt;/p&gt;
1711 </description>
1712 </item>
1713
1714 <item>
1715 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
1716 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
1717 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
1718 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
1719 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
1720 the screen just turn black when Linux boot, either during installation
1721 or on first boot from the hard disk. I&#39;ve seen it once in a while the
1722 last few years, but only recently understood the cause. I&#39;ve seen it
1723 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
1724 The reason seem to be in the wiring of some laptops. The system to
1725 control the screen background light is inverted, so when Linux try to
1726 turn the brightness fully on, it end up turning it off instead. I do
1727 not know which Linux drivers are affected, but this post is about the
1728 i915 driver used by the
1729 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
1730 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
1731
1732 &lt;p&gt;The problem can be worked around two ways. Either by adding
1733 i915.invert_brightness=1 as a kernel option, or by adding a file in
1734 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
1735 option when it load the i915 kernel module. On Debian and Ubuntu, it
1736 can be done by running these commands as root:&lt;/p&gt;
1737
1738 &lt;pre&gt;
1739 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
1740 update-initramfs -u -k all
1741 &lt;/pre&gt;
1742
1743 &lt;p&gt;Since March 2012 there is
1744 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
1745 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
1746 hardware have this problem, and get the driver to invert the
1747 brightness setting automatically. To use it, one need to add a row in
1748 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c&quot;&gt;the
1749 intel_quirks array&lt;/a&gt; in the driver source
1750 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
1751 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
1752 number (vendor number 8086 is assumed) and subdevice vendor and device
1753 number.&lt;/p&gt;
1754
1755 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
1756 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
1757
1758 &lt;p&gt;&lt;pre&gt;
1759 00:02.0 VGA compatible controller [0300]: Intel Corporation \
1760 3rd Gen Core processor Graphics Controller [8086:0156] \
1761 (rev 09) (prog-if 00 [VGA controller])
1762 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
1763 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
1764 ParErr- Stepping- SE RR- FastB2B- DisINTx+
1765 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
1766 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
1767 Latency: 0
1768 Interrupt: pin A routed to IRQ 42
1769 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
1770 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
1771 Region 4: I/O ports at 4000 [size=64]
1772 Expansion ROM at &lt;unassigned&gt; [disabled]
1773 Capabilities: &lt;access denied&gt;
1774 Kernel driver in use: i915
1775 &lt;/pre&gt;&lt;/p&gt;
1776
1777 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
1778
1779 &lt;p&gt;&lt;pre&gt;
1780 struct intel_quirk intel_quirks[] = {
1781 ...
1782 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
1783 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
1784 ...
1785 }
1786 &lt;/pre&gt;&lt;/p&gt;
1787
1788 &lt;p&gt;According to the kernel module instructions (as seen using
1789 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
1790 invert_brightness flag should be sent to the
1791 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
1792 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
1793 developers. But my email about the laptop sent 2013-06-03 have not
1794 yet shown up in
1795 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
1796 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
1797 emails from non-subscribers. Because of this, I sent my patch also to
1798 the Debian bug tracking system instead as
1799 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
1800 sure the patch is not lost.&lt;/p&gt;
1801
1802 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
1803 with this problem working properly with Linux. If you use Gnome, your
1804 worries should be over at this point. But if you use KDE, there is
1805 something in KDE ignoring the invert_brightness setting and turning on
1806 the screen during login. I&#39;ve reported it to Debian as
1807 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
1808 have no idea yet how to figure out exactly what subsystem is doing
1809 this. Perhaps you can help? Perhaps you know what the Gnome
1810 developers did to handle this, and this can give a clue to the KDE
1811 developers? Or you know where in KDE the screen brightness is changed
1812 during login? If so, please update the BTS report (or get in touch if
1813 you do not know how to update BTS).&lt;/p&gt;
1814
1815 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
1816 acpi_backlight=vendor, to disable ACPI backlight support completely,
1817 as the ACPI information on the machine is trash and it is better to
1818 leave it to the intel video driver to control the screen
1819 backlight.&lt;/p&gt;
1820 </description>
1821 </item>
1822
1823 <item>
1824 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
1825 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
1826 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</guid>
1827 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
1828 <description>&lt;p&gt;Two days ago, I asked
1829 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html&quot;&gt;how
1830 I could install Linux on a Packard Bell EasyNote LV computer
1831 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
1832 with the obstacles put in the way of Linux users on a laptop with UEFI
1833 and Windows 8.&lt;/p&gt;
1834
1835 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
1836 secure booting or fast boot. I suspect fast boot was the problem,
1837 causing the firmware to boot directly from HD without considering any
1838 key presses and alternative devices, but do not know UEFI settings
1839 enough to tell.&lt;/p&gt;
1840
1841 &lt;p&gt;There is no way to install Linux on the machine in question without
1842 opening the box and disconnecting the hard drive! This is as far as I
1843 can tell, the only way to get access to the firmware setup menu
1844 without accepting the Windows 8 license agreement. I am told (and
1845 found description on how to) that it is possible to configure the
1846 firmware setup once booted into Windows 8. But as I believe the terms
1847 of that agreement are completely unacceptable, accepting the license
1848 was never an alternative. I do not enter agreements I do not intend
1849 to follow.&lt;/p&gt;
1850
1851 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
1852 waste many hours on this, but luckily there was a way to get it to
1853 work. But I would not recommend it to anyone planning to run Linux on
1854 it, and I have become sceptical to Windows 8 certified laptops. Is
1855 this the way Linux will be forced out of the market place, by making
1856 it close to impossible for &quot;normal&quot; users to install Linux without
1857 accepting the Microsoft Windows license terms? Or at least not
1858 without risking to loose the warranty?&lt;/p&gt;
1859
1860 &lt;p&gt;I&#39;ve updated the
1861 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
1862 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
1863 do not have to struggle as much as I did to get Linux into the
1864 machine.&lt;/p&gt;
1865
1866 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
1867 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
1868 </description>
1869 </item>
1870
1871 <item>
1872 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
1873 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
1874 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</guid>
1875 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
1876 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
1877 new laptops for my parents and a few others. I bought Packard Bell
1878 Easynote LV to run Kubuntu on and use as their home computer. But I
1879 am completely unable to figure out how to install Linux on it. The
1880 computer is preinstalled with Windows 8, and I suspect it uses UEFI
1881 instead of a BIOS to boot.&lt;/p&gt;
1882
1883 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
1884 to get it to boot the Linux installer from my USB stick. I have yet
1885 to try the DVD install, and still hope it will work. when I turn on
1886 the computer, there is no information on what buttons to press to get
1887 the normal boot menu. I expect to get some boot menu to select PXE or
1888 USB stick booting. When booting, it first ask for the language to
1889 use, then for some regional settings, and finally if I will accept the
1890 Windows 8 terms of use. As these terms are completely unacceptable to
1891 me, I have no other choice but to turn off the computer and try again
1892 to get it to boot the Linux installer.&lt;/p&gt;
1893
1894 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
1895 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
1896 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
1897 installed on this machine, please get in touch or update that wiki
1898 page. If I can&#39;t find a way to install Linux, I will have to return
1899 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
1900
1901 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
1902 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
1903 on new Laptops?&lt;/p&gt;
1904 </description>
1905 </item>
1906
1907 <item>
1908 <title>How to transform a Debian based system to a Debian Edu installation</title>
1909 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
1910 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
1911 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
1912 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
1913 an operating system based on Debian intended for use in schools. It
1914 contain a turn-key solution for the computer network provided to
1915 pupils in the primary schools. It provide both the central server,
1916 network boot servers and desktop environments with heaps of
1917 educational software. The project was founded almost 12 years ago,
1918 2001-07-02. If you want to support the project, which is in need for
1919 cash to fund developer gatherings and other project related activity,
1920 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
1921 donate some money&lt;/a&gt;.
1922
1923 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
1924 lists and elsewhere, is the question on how to transform a Debian or
1925 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
1926 hard, and last week I wrote a script to replicate the steps done by
1927 the Debian Edu installer.&lt;/p&gt;
1928
1929 &lt;p&gt;The script,
1930 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup&quot;&gt;debian-edu-bless&lt;a/&gt;
1931 in the debian-edu-config package, will go through these six steps and
1932 transform an existing Debian Wheezy or Ubuntu (untested) installation
1933 into a Debian Edu Workstation:&lt;/p&gt;
1934
1935 &lt;ol&gt;
1936
1937 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
1938 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
1939 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
1940 our configuration.&lt;/li&gt;
1941 &lt;li&gt;Preseed debconf database with profile setup in
1942 /etc/debian-edu/config, and run tasksel to install packages
1943 according to the profile specified in the config above,
1944 overriding some of the Debian automation machinery.&lt;/li&gt;
1945 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
1946 that could not be done using preseeding.&lt;/li&gt;
1947 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
1948
1949 &lt;/ol&gt;
1950
1951 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
1952 replicated like this. Disk partitioning and LVM setup, for example.
1953 So this script just assume there is enough disk space to install all
1954 the needed packages.&lt;/p&gt;
1955
1956 &lt;p&gt;The script was created to help a Debian Edu student working on
1957 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
1958 Debian Edu client, and using it he can take the existing
1959 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
1960 transform it into a fully functioning Debian Edu Workstation (or
1961 Roaming Workstation, or whatever :).&lt;/p&gt;
1962
1963 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
1964 If a LXDE based Roaming workstation is wanted instead, modify the
1965 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
1966
1967 &lt;p&gt;&lt;pre&gt;
1968 PROFILE=&quot;Roaming-Workstation&quot;
1969 DESKTOP=&quot;lxde&quot;
1970 &lt;/pre&gt;&lt;/p&gt;
1971
1972 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
1973 the cloud, by starting with a virtual Debian installation at some
1974 virtual hosting service and setting up all the services on first
1975 boot.&lt;/p&gt;
1976 </description>
1977 </item>
1978
1979 <item>
1980 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
1981 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
1982 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
1983 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
1984 <description>&lt;P&gt;In January,
1985 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
1986 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
1987 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
1988 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
1989 marvellous construction system from Denmark. We also created
1990 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
1991 a place to take notes and write down our plans and hopes. And several
1992 people showed up to help. I was very happy to see the effect of my
1993 call. Since the small start, we have a debtags tag
1994 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
1995 tag for LEGO related packages, and now count 10 packages related to
1996 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
1997
1998 &lt;p&gt;&lt;table&gt;
1999 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/brickos&quot;&gt;brickos&lt;/a&gt;&lt;/td&gt;&lt;td&gt;alternative OS for LEGO Mindstorms RCX. Supports development in C/C++&lt;/td&gt;&lt;/tr&gt;
2000 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/leocad&quot;&gt;leocad&lt;/a&gt;&lt;/td&gt;&lt;td&gt;virtual brick CAD software&lt;/td&gt;&lt;/tr&gt;
2001 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/libnxt&quot;&gt;libnxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;utility library for talking to the LEGO Mindstorms NX&lt;/td&gt;&lt;/tr&gt;
2002 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/lnpd&quot;&gt;lnpd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;daemon for LNP communication with BrickOS&lt;/td&gt;&lt;/tr&gt;
2003 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nbc&quot;&gt;nbc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;compiler for LEGO Mindstorms NXT bricks&lt;/td&gt;&lt;/tr&gt;
2004 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nqc&quot;&gt;nqc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Not Quite C compiler for LEGO Mindstorms RCX&lt;/td&gt;&lt;/tr&gt;
2005 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt&quot;&gt;python-nxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;python driver/interface/wrapper for the Lego Mindstorms NXT robot&lt;/td&gt;&lt;/tr&gt;
2006 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt-filer&quot;&gt;python-nxt-filer&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple GUI to manage files on a LEGO Mindstorms NXT&lt;/td&gt;&lt;/tr&gt;
2007 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/scratch&quot;&gt;scratch&lt;/a&gt;&lt;/td&gt;&lt;td&gt;easy to use programming environment for ages 8 and up&lt;/td&gt;&lt;/tr&gt;
2008 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/t2n&quot;&gt;t2n&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple command-line tool for Lego NXT&lt;/td&gt;&lt;/tr&gt;
2009 &lt;/table&gt;&lt;/p&gt;
2010
2011 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2012 currently available in Jessie/testing. leocad is so far only
2013 available in experimental.&lt;/p&gt;
2014
2015 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2016 adding the rest of the great free software tools available on Linux
2017 for LEGO designers.&lt;/p&gt;
2018 </description>
2019 </item>
2020
2021 <item>
2022 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2023 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2024 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2025 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2026 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2027 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2028 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2029 Debian release, and I expect to move my machines at home over to it fairly
2030 soon.&lt;/p&gt;
2031
2032 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2033 in particular make me very happy to see included. The
2034 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2035 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2036 included for the first time. Alongside similar programs like
2037 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2038 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2039 it allow for visual programming where syntax errors can not happen,
2040 and a friendly programming environment for learning to control the
2041 computer. Scratch will also be included in the next release of Debian
2042 Edu.&lt;/a&gt;
2043
2044 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2045 Edu/Skolelinux release too. The
2046 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2047 alpha release&lt;/a&gt; went out last week, and the next should soon
2048 follow.&lt;p&gt;
2049 </description>
2050 </item>
2051
2052 <item>
2053 <title>Isenkram 0.2 finally in the Debian archive</title>
2054 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2055 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2056 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2057 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2058 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2059 for many months. I uploaded it to the Debian experimental suite
2060 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2061
2062 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2063 install to work with a pluggable hardware device. The suggestion pop
2064 up when the device is plugged in. For example if a Lego Mindstorm NXT
2065 is inserted, it will suggest to install the program needed to program
2066 the NXT controller. Give it a go, and report bugs and suggestions to
2067 BTS. :)&lt;/p&gt;
2068 </description>
2069 </item>
2070
2071 <item>
2072 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2073 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2074 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2075 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2076 <description>&lt;p&gt;My
2077 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
2078 bitcoin related blog post&lt;/a&gt; mentioned that the new
2079 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2080 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2081 2013-01-19, and have been available in unstable since then. It was
2082 automatically copied to Ubuntu, and is available in their Raring
2083 version too.&lt;/p&gt;
2084
2085 &lt;p&gt;But there is a strange problem with the build that block this new
2086 version from being available on the i386 and kfreebsd-i386
2087 architectures. For some strange reason, the autobuilders in Debian
2088 for these architectures fail to run the test suite on these
2089 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2090 We are so far unable to reproduce it when building it manually, and
2091 no-one have been able to propose a fix. If you got an idea what is
2092 failing, please let us know via the BTS.&lt;/p&gt;
2093
2094 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2095 I often run low on disk space, is the fact that the client will exit
2096 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2097 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2098 it. :)&lt;/p&gt;
2099
2100 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2101 activities, please send Bitcoin donations to my address
2102 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2103 </description>
2104 </item>
2105
2106 <item>
2107 <title>Welcome to the world, Isenkram!</title>
2108 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2110 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2111 <description>&lt;p&gt;Yesterday, I
2112 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2113 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2114 pluggable hardware devices, which I
2115 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2116 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2117 up, and caused me to really want to to open up the development to more
2118 people. But before I did this, I want to come up with a sensible name
2119 for this project. Today I finally decided on a new name, and I have
2120 renamed the project from hw-support-handler to this new name. In the
2121 process, I moved the source to git and made it available as a
2122 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2123 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2124 To fetch and build the latest version of the source, use&lt;/p&gt;
2125
2126 &lt;pre&gt;
2127 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2128 cd isenkram &amp;&amp; git-buildpackage -us -uc
2129 &lt;/pre&gt;
2130
2131 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2132 want to hack on the source or improve the package, please go ahead.
2133 But please talk to me first on IRC or via email before you do major
2134 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2135
2136 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2137 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2138 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2139 the German word eisenkram, for those that are familiar with that
2140 word.&lt;/p&gt;
2141
2142 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2143 instructions, to avoid confusing people with an error from the signing
2144 process.&lt;/p&gt;
2145
2146 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2147 clone argument to avoid the need for authentication.&lt;/p&gt;
2148 </description>
2149 </item>
2150
2151 <item>
2152 <title>First prototype ready making hardware easier to use in Debian</title>
2153 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2155 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2156 <description>&lt;p&gt;Early this month I set out to try to
2157 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2158 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2159 prototype is working, and it is ready for a larger audience. To test
2160 it, fetch the
2161 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2162 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2163 package. You might have to log out and in again activate the
2164 autostart script.&lt;/p&gt;
2165
2166 &lt;p&gt;The design is simple:&lt;/p&gt;
2167
2168 &lt;ul&gt;
2169
2170 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2171 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2172
2173 &lt;li&gt;This program listen for kernel events about new hardware (directly
2174 from the kernel like udev does), not using HAL dbus events as I
2175 initially did.&lt;/li&gt;
2176
2177 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2178 the APT database, a database
2179 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2180 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2181
2182 &lt;li&gt;If a package is mapped to the hardware in question, the package
2183 isn&#39;t installed yet and this is the first time the hardware was
2184 plugged in, show a desktop notification suggesting to install the
2185 package or packages.&lt;/li&gt;
2186
2187 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2188 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2189
2190 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2191 package while showing progress information in a window.&lt;/li&gt;
2192
2193 &lt;/ul&gt;
2194
2195 &lt;p&gt;I still need to come up with a better name for the system. Here
2196 are some screen shots showing the prototype in action. First the
2197 notification, then the password request, and finally the request to
2198 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2199
2200 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2201 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2202 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2203 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2204 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
2205
2206 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2207 is already useful. The database of hardware to package mappings also
2208 need more work. It is currently compatible with the Ubuntu way of
2209 storing such information in the package control file, but could be
2210 changed to use other formats instead or in addition to the current
2211 method. I&#39;ve dropped the use of discover for this mapping, as the
2212 modalias approach is more flexible and easier to use on Linux as long
2213 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2214
2215 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2216 here is the command required to check out and build the source: Use
2217 &#39;&lt;tt&gt;svn checkout
2218 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2219 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2220 devscripts package.&lt;/p&gt;
2221
2222 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2223 renamed to Isenkram and the source moved from the Debian Edu
2224 subversion repository to a Debian collab-maint git repository. See
2225 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2226 instructions&lt;/a&gt; for details.&lt;/p&gt;
2227 </description>
2228 </item>
2229
2230 <item>
2231 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2232 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2234 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2235 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2236 suddenly in bed. With a quiet whimper, it went completely quiet and
2237 black. The power button was no longer able to turn it on. It was a
2238 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2239 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2240 Compaq I had before that. Now I need to find a replacement. To keep
2241 going during Christmas, I moved the one year old SSD disk to my old
2242 X40 where it fitted (only one I had left that could use it), but it is
2243 not a durable solution.
2244
2245 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2246 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2247
2248 &lt;ul&gt;
2249
2250 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2251 than A4).&lt;/li&gt;
2252 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2253 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2254 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2255 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2256 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2257 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2258 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2259 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
2260 size).&lt;/li&gt;
2261 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
2262 X.org packages.&lt;/li&gt;
2263 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
2264 the time).
2265
2266 &lt;/ul&gt;
2267
2268 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
2269 list. The reason is simply that the specifications on laptops the
2270 last 10-15 years have been sufficient for my needs, and I have to look
2271 at other features to choose my laptop. But are there still made as
2272 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2273 robust, and Thinkpads seem to be heading in the wrong direction since
2274 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
2275 still be useful.&lt;/p&gt;
2276
2277 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
2278 external keyboard? I&#39;ll have to check the
2279 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
2280 well-supported laptops, or perhaps just buy one preinstalled from one
2281 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
2282 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
2283 </description>
2284 </item>
2285
2286 <item>
2287 <title>How to find a browser plugin supporting a given MIME type</title>
2288 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
2289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
2290 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
2291 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
2292 install to get support for a given MIME type. Thanks to
2293 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
2294 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
2295 Unfortunately, not very many packages provide the needed meta
2296 information, Anyway, here is a small script to look up all browser
2297 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
2298
2299 &lt;pre&gt;
2300 #!/usr/bin/python
2301 import sys
2302 import apt
2303 def pkgs_handling_mimetype(mimetype):
2304 cache = apt.Cache()
2305 cache.open(None)
2306 thepkgs = []
2307 for pkg in cache:
2308 version = pkg.candidate
2309 if version is None:
2310 version = pkg.installed
2311 if version is None:
2312 continue
2313 record = version.record
2314 if not record.has_key(&#39;Npp-MimeType&#39;):
2315 continue
2316 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
2317 for t in mime_types:
2318 t = t.rstrip().strip()
2319 if t == mimetype:
2320 thepkgs.append(pkg.name)
2321 return thepkgs
2322 mimetype = &quot;audio/ogg&quot;
2323 if 1 &lt; len(sys.argv):
2324 mimetype = sys.argv[1]
2325 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
2326 for pkg in pkgs_handling_mimetype(mimetype):
2327 print &quot; %s&quot; %pkg
2328 &lt;/pre&gt;
2329
2330 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
2331
2332 &lt;pre&gt;
2333 % ./apt-find-browserplug-for-mimetype
2334 Browser plugin packages supporting audio/ogg:
2335 gecko-mediaplayer
2336 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2337 Browser plugin packages supporting application/x-shockwave-flash:
2338 browser-plugin-gnash
2339 %
2340 &lt;/pre&gt;
2341
2342 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
2343 itself to query for plugins and propose to install the needed
2344 packages. It would be great if Debian supported such feature too. Is
2345 anyone working on adding it?&lt;/p&gt;
2346
2347 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
2348 request for icweasel support for this feature is
2349 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
2350 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
2351 of manpower and wish for a different design is the reason thus feature
2352 is not yet in iceweasel from Debian.&lt;/p&gt;
2353 </description>
2354 </item>
2355
2356 <item>
2357 <title>What is the most supported MIME type in Debian?</title>
2358 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
2359 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
2360 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
2361 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
2362 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
2363 proposal to make it possible for a Desktop application to propose to
2364 the user some package to install to gain support for a given MIME
2365 type, font, library etc. that is currently missing. With such
2366 mechanism in place, it would be possible for the desktop to
2367 automatically propose and install leocad if some LDraw file is
2368 downloaded by the browser.&lt;/p&gt;
2369
2370 &lt;p&gt;To get some idea about the current content of the archive, I decided
2371 to write a simple program to extract all .desktop files from the
2372 Debian archive and look up the claimed MIME support there. The result
2373 can be found on the
2374 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
2375 site&lt;/a&gt;. Using the collected information, it become possible to
2376 answer the question in the title. Here are the 20 most supported MIME
2377 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2378 The complete list is available from the link above.&lt;/p&gt;
2379
2380 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
2381
2382 &lt;pre&gt;
2383 count MIME type
2384 ----- -----------------------
2385 32 text/plain
2386 30 audio/mpeg
2387 29 image/png
2388 28 image/jpeg
2389 27 application/ogg
2390 26 audio/x-mp3
2391 25 image/tiff
2392 25 image/gif
2393 22 image/bmp
2394 22 audio/x-wav
2395 20 audio/x-flac
2396 19 audio/x-mpegurl
2397 18 video/x-ms-asf
2398 18 audio/x-musepack
2399 18 audio/x-mpeg
2400 18 application/x-ogg
2401 17 video/mpeg
2402 17 audio/x-scpls
2403 17 audio/ogg
2404 16 video/x-ms-wmv
2405 &lt;/pre&gt;
2406
2407 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
2408
2409 &lt;pre&gt;
2410 count MIME type
2411 ----- -----------------------
2412 33 text/plain
2413 32 image/png
2414 32 image/jpeg
2415 29 audio/mpeg
2416 27 image/gif
2417 26 image/tiff
2418 26 application/ogg
2419 25 audio/x-mp3
2420 22 image/bmp
2421 21 audio/x-wav
2422 19 audio/x-mpegurl
2423 19 audio/x-mpeg
2424 18 video/mpeg
2425 18 audio/x-scpls
2426 18 audio/x-flac
2427 18 application/x-ogg
2428 17 video/x-ms-asf
2429 17 text/html
2430 17 audio/x-musepack
2431 16 image/x-xbitmap
2432 &lt;/pre&gt;
2433
2434 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2435
2436 &lt;pre&gt;
2437 count MIME type
2438 ----- -----------------------
2439 31 text/plain
2440 31 image/png
2441 31 image/jpeg
2442 29 audio/mpeg
2443 28 application/ogg
2444 27 image/gif
2445 26 image/tiff
2446 26 audio/x-mp3
2447 23 audio/x-wav
2448 22 image/bmp
2449 21 audio/x-flac
2450 20 audio/x-mpegurl
2451 19 audio/x-mpeg
2452 18 video/x-ms-asf
2453 18 video/mpeg
2454 18 audio/x-scpls
2455 18 application/x-ogg
2456 17 audio/x-musepack
2457 16 video/x-ms-wmv
2458 16 video/x-msvideo
2459 &lt;/pre&gt;
2460
2461 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
2462 information mentioned in DEP-11. I have not yet had time to look at
2463 it, but hope the PackageKit people in Debian are on top of these
2464 issues.&lt;/p&gt;
2465
2466 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
2467 discovering a typo in my script.&lt;/p&gt;
2468 </description>
2469 </item>
2470
2471 <item>
2472 <title>Using modalias info to find packages handling my hardware</title>
2473 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
2474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
2475 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
2476 <description>&lt;p&gt;Yesterday, I wrote about the
2477 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
2478 values provided by the Linux kernel&lt;/a&gt; following my hope for
2479 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
2480 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
2481 modalias values attached to package names can be used to map packages
2482 to hardware. This allow the system to look up and suggest relevant
2483 packages when I plug in some new hardware into my machine, and replace
2484 discover and discover-data as the database used to map hardware to
2485 packages.&lt;/p&gt;
2486
2487 &lt;p&gt;I create a modaliases file with entries like the following,
2488 containing package name, kernel module name (if relevant, otherwise
2489 the package name) and globs matching the relevant hardware
2490 modalias.&lt;/p&gt;
2491
2492 &lt;p&gt;&lt;blockquote&gt;
2493 Package: package-name
2494 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
2495 &lt;/blockquote&gt;&lt;/p&gt;
2496
2497 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
2498 for a given modalias value using this file.&lt;/p&gt;
2499
2500 &lt;p&gt;An entry like this would suggest the video and picture application
2501 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
2502
2503 &lt;p&gt;&lt;blockquote&gt;
2504 Package: cheese
2505 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
2506 &lt;/blockquote&gt;&lt;/p&gt;
2507
2508 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
2509 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
2510
2511 &lt;p&gt;&lt;blockquote&gt;
2512 Package: pcmciautils
2513 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
2514 &lt;/blockquote&gt;&lt;/p&gt;
2515
2516 &lt;p&gt;An entry like this would suggest the package colorhug-client when
2517 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
2518
2519 &lt;p&gt;&lt;blockquote&gt;
2520 Package: colorhug-client
2521 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
2522 &lt;/blockquote&gt;&lt;/p&gt;
2523
2524 &lt;p&gt;I believe the format is compatible with the format of the Packages
2525 file in the Debian archive. Ubuntu already uses their Packages file
2526 to store their mappings from packages to hardware.&lt;/p&gt;
2527
2528 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
2529 announce the hardware it support in a way my prototype understand.
2530 This allow those publishing packages in an APT source outside the
2531 Debian archive as well as those backporting packages to make sure the
2532 hardware mapping are included in the package meta information. I&#39;ve
2533 tested such header in the pymissile package, and its modalias mapping
2534 is working as it should with my prototype. It even made it to Ubuntu
2535 Raring.&lt;/p&gt;
2536
2537 &lt;p&gt;To test if it was possible to look up supported hardware using only
2538 the shell tools available in the Debian installer, I wrote a shell
2539 implementation of the lookup code. The idea is to create files for
2540 each modalias and let the shell do the matching. Please check out and
2541 try the
2542 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
2543 shell script. It run without any extra dependencies and fetch the
2544 hardware mappings from the Debian archive and the subversion
2545 repository where I currently work on my prototype.&lt;/p&gt;
2546
2547 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
2548 install yubikey-personalization:&lt;/p&gt;
2549
2550 &lt;p&gt;&lt;blockquote&gt;
2551 % ./hw-support-lookup
2552 &lt;br&gt;yubikey-personalization
2553 &lt;br&gt;%
2554 &lt;/blockquote&gt;&lt;/p&gt;
2555
2556 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
2557 propose to install the pcmciautils package:&lt;/p&gt;
2558
2559 &lt;p&gt;&lt;blockquote&gt;
2560 % ./hw-support-lookup
2561 &lt;br&gt;pcmciautils
2562 &lt;br&gt;%
2563 &lt;/blockquote&gt;&lt;/p&gt;
2564
2565 &lt;p&gt;If you know of any hardware-package mapping that should be added to
2566 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
2567 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
2568
2569 &lt;p&gt;It could be possible to generate several of the mappings between
2570 packages and hardware. One source would be to look at packages with
2571 kernel modules, ie packages with *.ko files in /lib/modules/, and
2572 extract their modalias information. Another would be to look at
2573 packages with udev rules, ie packages with files in
2574 /lib/udev/rules.d/, and extract their vendor/model information to
2575 generate a modalias matching rule. I have not tested any of these to
2576 see if it work.&lt;/p&gt;
2577
2578 &lt;p&gt;If you want to help implementing a system to let us propose what
2579 packages to install when new hardware is plugged into a Debian
2580 machine, please send me an email or talk to me on
2581 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
2582 </description>
2583 </item>
2584
2585 <item>
2586 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
2587 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
2588 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
2589 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
2590 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
2591 information, to find the packages that support a given piece of
2592 hardware, I refreshed my memory regarding modalias values, and decided
2593 to document the details. Here are my findings so far, also available
2594 in
2595 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
2596 Debian Edu subversion repository&lt;/a&gt;:
2597
2598 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
2599
2600 &lt;p&gt;This document try to explain what the different types of modalias
2601 values stands for. It is in part based on information from
2602 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
2603 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
2604 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
2605 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
2606
2607 &lt;p&gt;The modalias entries for a given Linux machine can be found using
2608 this shell script:&lt;/p&gt;
2609
2610 &lt;pre&gt;
2611 find /sys -name modalias -print0 | xargs -0 cat | sort -u
2612 &lt;/pre&gt;
2613
2614 &lt;p&gt;The supported modalias globs for a given kernel module can be found
2615 using modinfo:&lt;/p&gt;
2616
2617 &lt;pre&gt;
2618 % /sbin/modinfo psmouse | grep alias:
2619 alias: serio:ty05pr*id*ex*
2620 alias: serio:ty01pr*id*ex*
2621 %
2622 &lt;/pre&gt;
2623
2624 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
2625
2626 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
2627 Bridge memory controller:&lt;/p&gt;
2628
2629 &lt;p&gt;&lt;blockquote&gt;
2630 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
2631 &lt;/blockquote&gt;&lt;/p&gt;
2632
2633 &lt;p&gt;This represent these values:&lt;/p&gt;
2634
2635 &lt;pre&gt;
2636 v 00008086 (vendor)
2637 d 00002770 (device)
2638 sv 00001028 (subvendor)
2639 sd 000001AD (subdevice)
2640 bc 06 (bus class)
2641 sc 00 (bus subclass)
2642 i 00 (interface)
2643 &lt;/pre&gt;
2644
2645 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
2646 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
2647 0600. The 0600 class is a host bridge. Other useful bus values are
2648 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
2649
2650 &lt;p&gt;Not sure how to figure out the interface value, nor what it
2651 means.&lt;/p&gt;
2652
2653 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
2654
2655 &lt;p&gt;Some typical USB entries can look like this. This is an internal
2656 USB hub in a laptop:&lt;/p&gt;
2657
2658 &lt;p&gt;&lt;blockquote&gt;
2659 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
2660 &lt;/blockquote&gt;&lt;/p&gt;
2661
2662 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
2663
2664 &lt;pre&gt;
2665 v 1D6B (device vendor)
2666 p 0001 (device product)
2667 d 0206 (bcddevice)
2668 dc 09 (device class)
2669 dsc 00 (device subclass)
2670 dp 00 (device protocol)
2671 ic 09 (interface class)
2672 isc 00 (interface subclass)
2673 ip 00 (interface protocol)
2674 &lt;/pre&gt;
2675
2676 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
2677 class is in the interface class section. For a simple USB web camera,
2678 these alias entries show up:&lt;/p&gt;
2679
2680 &lt;p&gt;&lt;blockquote&gt;
2681 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
2682 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
2683 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
2684 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
2685 &lt;/blockquote&gt;&lt;/p&gt;
2686
2687 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
2688 camera), 0101 is audio control device and 0102 is audio streaming (aka
2689 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
2690
2691 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
2692
2693 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
2694 receiver in a Thinkpad X40:&lt;/p&gt;
2695
2696 &lt;p&gt;&lt;blockquote&gt;
2697 acpi:IBM0071:PNP0511:
2698 &lt;/blockquote&gt;&lt;/p&gt;
2699
2700 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
2701
2702 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
2703
2704 &lt;p&gt;The DMI table contain lots of information about the computer case
2705 and model. This is an entry for a IBM Thinkpad X40, fetched from
2706 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
2707
2708 &lt;p&gt;&lt;blockquote&gt;
2709 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
2710 &lt;/blockquote&gt;&lt;/p&gt;
2711
2712 &lt;p&gt;The values present are&lt;/p&gt;
2713
2714 &lt;pre&gt;
2715 bvn IBM (BIOS vendor)
2716 bvr 1UETB6WW(1.66) (BIOS version)
2717 bd 06/15/2005 (BIOS date)
2718 svn IBM (system vendor)
2719 pn 2371H4G (product name)
2720 pvr ThinkPadX40 (product version)
2721 rvn IBM (board vendor)
2722 rn 2371H4G (board name)
2723 rvr NotAvailable (board version)
2724 cvn IBM (chassis vendor)
2725 ct 10 (chassis type)
2726 cvr NotAvailable (chassis version)
2727 &lt;/pre&gt;
2728
2729 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
2730 found in the dmidecode source:&lt;/p&gt;
2731
2732 &lt;pre&gt;
2733 3 Desktop
2734 4 Low Profile Desktop
2735 5 Pizza Box
2736 6 Mini Tower
2737 7 Tower
2738 8 Portable
2739 9 Laptop
2740 10 Notebook
2741 11 Hand Held
2742 12 Docking Station
2743 13 All In One
2744 14 Sub Notebook
2745 15 Space-saving
2746 16 Lunch Box
2747 17 Main Server Chassis
2748 18 Expansion Chassis
2749 19 Sub Chassis
2750 20 Bus Expansion Chassis
2751 21 Peripheral Chassis
2752 22 RAID Chassis
2753 23 Rack Mount Chassis
2754 24 Sealed-case PC
2755 25 Multi-system
2756 26 CompactPCI
2757 27 AdvancedTCA
2758 28 Blade
2759 29 Blade Enclosing
2760 &lt;/pre&gt;
2761
2762 &lt;p&gt;The chassis type values are not always accurately set in the DMI
2763 table. For example my home server is a tower, but the DMI modalias
2764 claim it is a desktop.&lt;/p&gt;
2765
2766 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
2767
2768 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
2769 test machine:&lt;/p&gt;
2770
2771 &lt;p&gt;&lt;blockquote&gt;
2772 serio:ty01pr00id00ex00
2773 &lt;/blockquote&gt;&lt;/p&gt;
2774
2775 &lt;p&gt;The values present are&lt;/p&gt;
2776
2777 &lt;pre&gt;
2778 ty 01 (type)
2779 pr 00 (prototype)
2780 id 00 (id)
2781 ex 00 (extra)
2782 &lt;/pre&gt;
2783
2784 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
2785 the valid values are.&lt;/p&gt;
2786
2787 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
2788
2789 &lt;p&gt;There are heaps of other modalias subtypes according to
2790 file2alias.c. There is the rest of the list from that source: amba,
2791 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
2792 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
2793 vmbus, x86cpu and zorro. I did not spend time documenting all of
2794 these, as they do not seem relevant for my intended use with mapping
2795 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
2796
2797 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
2798
2799 &lt;p&gt;To check which kernel modules provide support for a given modalias,
2800 one can use the following shell script:&lt;/p&gt;
2801
2802 &lt;pre&gt;
2803 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
2804 echo &quot;$id&quot; ; \
2805 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
2806 done
2807 &lt;/pre&gt;
2808
2809 &lt;p&gt;The output can look like this (only the first few entries as the
2810 list is very long on my test machine):&lt;/p&gt;
2811
2812 &lt;pre&gt;
2813 acpi:ACPI0003:
2814 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
2815 acpi:device:
2816 FATAL: Module acpi:device: not found.
2817 acpi:IBM0068:
2818 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
2819 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
2820 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
2821 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
2822 acpi:IBM0071:PNP0511:
2823 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
2824 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
2825 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
2826 [...]
2827 &lt;/pre&gt;
2828
2829 &lt;p&gt;If you want to help implementing a system to let us propose what
2830 packages to install when new hardware is plugged into a Debian
2831 machine, please send me an email or talk to me on
2832 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
2833
2834 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
2835 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
2836 in /sys/ with space in them.&lt;/p&gt;
2837 </description>
2838 </item>
2839
2840 <item>
2841 <title>Moved the pymissile Debian packaging to collab-maint</title>
2842 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
2843 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
2844 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
2845 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
2846 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
2847 Launcher and updated the Debian package
2848 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
2849 sure udev will fix the device permissions when it is plugged in. I
2850 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
2851 hopefully make the package be proposed by jockey in Ubuntu when a user
2852 plug in his rocket launcher. In the process I moved the source to a
2853 git repository under collab-maint, to make it easier for any DD to
2854 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
2855 is not very active, but the software still work for me even after five
2856 years of relative silence. The new git repository is not listed in
2857 the uploaded package yet, because I want to test the other changes a
2858 bit more before I upload the new version. If you want to check out
2859 the new version with a .desktop file included, visit the
2860 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
2861 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
2862 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
2863 </description>
2864 </item>
2865
2866 <item>
2867 <title>Lets make hardware dongles easier to use in Debian</title>
2868 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
2869 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
2870 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
2871 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
2872 general, is that there is a great package management system with the
2873 ability to automatically install software packages by downloading them
2874 from the distribution mirrors, but no way to get it to automatically
2875 install the packages I need to use the hardware I plug into my
2876 machine. Even if the package to use it is easily available from the
2877 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
2878 suggest to automatically install the python-nxt, nbc and t2n packages
2879 I need to talk to it. When I plug in a Yubikey, it could propose the
2880 yubikey-personalization package. The information required to do this
2881 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
2882
2883 &lt;p&gt;Some years ago, I proposed to
2884 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
2885 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
2886 simple:
2887
2888 &lt;ul&gt;
2889
2890 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
2891 starting when a user log in.&lt;/li&gt;
2892
2893 &lt;li&gt;Set this program up to listen for kernel events emitted when new
2894 hardware is inserted into the computer.&lt;/li&gt;
2895
2896 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
2897 database mapping to packages, and take note of any non-installed
2898 packages.&lt;/li&gt;
2899
2900 &lt;li&gt;Show a message to the user proposing to install the discovered
2901 package, and make it easy to install it.&lt;/li&gt;
2902
2903 &lt;/ul&gt;
2904
2905 &lt;p&gt;I am not sure what the best way to implement this is, but my
2906 initial idea was to use dbus events to discover new hardware, the
2907 discover database to find packages and
2908 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
2909 packages.&lt;/p&gt;
2910
2911 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
2912 draft package is now checked into
2913 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
2914 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
2915 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
2916 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
2917 the relevant packages in Debian, and uploaded a new version
2918 2.2013.01.09 to unstable. I also discovered that the current
2919 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
2920 package in Debian no longer discovered any USB devices, because
2921 /proc/bus/usb/devices is no longer present. I ported it to use
2922 libusb as a fall back option to get it working. The fixed package
2923 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
2924 because of the freeze).&lt;/p&gt;
2925
2926 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
2927 desktop notification to show up (only once, the first time it is
2928 inserted):&lt;/p&gt;
2929
2930 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-09-hw-autoinstall.png&quot;&gt;&lt;/p&gt;
2931
2932 &lt;p&gt;For this prototype to be really useful, some way to automatically
2933 install the proposed packages by pressing the &quot;Please install
2934 program(s)&quot; button should to be implemented.&lt;/p&gt;
2935
2936 &lt;p&gt;If this idea seem useful to you, and you want to help make it
2937 happen, please help me update the discover-data database with mappings
2938 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
2939 list the package you would like to have installed when a given
2940 hardware device is inserted into your computer, and report bugs using
2941 reportbug if it isn&#39;t. Or, if you know of a better way to provide
2942 such mapping, please let me know.&lt;/p&gt;
2943
2944 &lt;p&gt;This prototype need more work, and there are several questions that
2945 should be considered before it is ready for production use. Is dbus
2946 the correct way to detect new hardware? At the moment I look for HAL
2947 dbus events on the system bus, because that is the events I could see
2948 on my Debian Squeeze KDE desktop. Are there better events to use?
2949 How should the user be notified? Is the desktop notification
2950 mechanism the best option, or should the background daemon raise a
2951 popup instead? How should packages be installed? When should they
2952 not be installed?&lt;/p&gt;
2953
2954 &lt;p&gt;If you want to help getting such feature implemented in Debian,
2955 please send me an email. :)&lt;/p&gt;
2956 </description>
2957 </item>
2958
2959 <item>
2960 <title>New IRC channel for LEGO designers using Debian</title>
2961 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
2962 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
2963 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
2964 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
2965 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
2966 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
2967 discovered I had to build all the tools myself because none were
2968 already in Debian Squeeze. If Debian support for LEGO is something
2969 you care about, please join me on the IRC channel
2970 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
2971 irc.debian.org). There is a lot that could be done to improve the
2972 Debian support for LEGO designers. For example both CAD software
2973 and Mindstorm compilers are missing. :)&lt;/p&gt;
2974
2975 &lt;p&gt;Update 2012-01-03: A
2976 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
2977 including links to Lego related packages is now available.&lt;/p&gt;
2978 </description>
2979 </item>
2980
2981 <item>
2982 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
2983 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
2984 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
2985 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
2986 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
2987 year! I hope next year will prove to be a good year.&lt;/p&gt;
2988
2989 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
2990 decentralised &quot;currency&quot; that allow people to transfer bitcoins
2991 between each other with minimal overhead, is a very interesting
2992 experiment. And as I wrote a few days ago, the bitcoin situation in
2993 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
2994 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
2995 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
2996 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
2997 for one of the ftpmasters to approve the new bitcoin-qt package
2998 name.&lt;/p&gt;
2999
3000 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3001 team in Debian, you can easily test the package in Debian Squeeze
3002 using the following steps to get a set of working packages:&lt;/p&gt;
3003
3004 &lt;blockquote&gt;&lt;pre&gt;
3005 git clone git://git.debian.org/git/collab-maint/bitcoin
3006 cd bitcoin
3007 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3008 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3009 &lt;/pre&gt;&lt;/blockquote&gt;
3010
3011 &lt;p&gt;You might have to install some build dependencies as well. The
3012 list of commands should give you two packages, bitcoind and
3013 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3014 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3015 around 5.6 GiB of data on my machine at the moment. Make sure your
3016 ~/.bitcoin/ directory have lots of spare room if you want to download
3017 all the blocks. The client will warn if the disk is getting full, so
3018 there is not really a problem if you got too little room, but you will
3019 not be able to get all the features out of the client.&lt;/p&gt;
3020
3021 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3022 activities, please send Bitcoin donations to my address
3023 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3024 </description>
3025 </item>
3026
3027 <item>
3028 <title>A word on bitcoin support in Debian</title>
3029 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3031 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3032 <description>&lt;p&gt;It has been a while since I wrote about
3033 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3034 peer-to-peer based crypto-currency, and the reason is simply that I
3035 have been busy elsewhere. But two days ago, I started looking at the
3036 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3037 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3038 is now maintained by a
3039 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3040 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3041 owe a huge thank you to all these team members. :)
3042 But I was sad to discover that the bitcoin client is missing in
3043 Wheezy. It is only available in Sid (and an outdated client from
3044 backports). The client had several RC bugs registered in BTS blocking
3045 it from entering testing. To try to help the team and improve the
3046 situation, I spent some time providing patches and triaging the bug
3047 reports. I also had a look at the bitcoin package available from Matt
3048 Corallo in a
3049 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3050 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3051 Debian package.&lt;/p&gt;
3052
3053 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3054 IRC, I pushed several patches into the collab-maint git repository to
3055 improve the package. It now contains fixes for the RC issues (not from
3056 me, but fixed by Scott Howard), build rules for a Qt GUI client
3057 package, konqueror support for the bitcoin: URI and bash completion
3058 setup. As I work on Debian Squeeze, I also created
3059 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3060 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3061 it and try to integrate it into the git repository before uploading a
3062 new version to unstable.
3063
3064 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3065 centralized control currently exercised in the monetary system. I
3066 find it completely unacceptable that the USA government is collecting
3067 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3068 that the major credit card companies can block legal money
3069 transactions to Wikileaks. But for bitcoin to succeed, more people
3070 need to use bitcoins, and more people need to accept bitcoins when
3071 they sell products and services. Improving the bitcoin support in
3072 Debian is a small step in the right direction, but not enough.
3073 Unfortunately the user experience when browsing the web and wanting to
3074 pay with bitcoin is still not very good. The bitcoin: URI is a step
3075 in the right direction, but need to work in most or every browser in
3076 use. Also the bitcoin-qt client is too heavy to fire up to do a
3077 quick transaction. I believe there are other clients available, but
3078 have not tested them.&lt;/p&gt;
3079
3080 &lt;p&gt;My
3081 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3082 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3083 I received 20.15 BTC so far on the address I provided in my blog two
3084 years ago, as can be
3085 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3086 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3087 donation. The blockexplorer service demonstrates quite well that
3088 bitcoin is not quite anonymous and untracked. :) I wonder if the
3089 number of users have gone up since then. If you use bitcoin and want
3090 to show your support of my activity, please send Bitcoin donations to
3091 the same address as last time,
3092 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3093 </description>
3094 </item>
3095
3096 <item>
3097 <title>Git repository for song book for Computer Scientists</title>
3098 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3100 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3101 <description>&lt;p&gt;As I
3102 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3103 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3104 years ago, and today I finally found time to create a public
3105 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3106 repository for the project&lt;/a&gt;.&lt;/p&gt;
3107
3108 &lt;p&gt;If you want to help out, please clone the source and submit patches
3109 to the HTML version. To generate the PDF and PostScript version,
3110 please use prince XML, or let me know about a useful free software
3111 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3112
3113 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3114 PostScript formats at
3115 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3116 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3117 </description>
3118 </item>
3119
3120 <item>
3121 <title>Gratulerer med 19-årsdagen, Debian!</title>
3122 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3124 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3125 <description>&lt;p&gt;I dag fyller
3126 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3127 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3128 si gratulerer med dagen, Debian!&lt;/p&gt;
3129 </description>
3130 </item>
3131
3132 <item>
3133 <title>Song book for Computer Scientists</title>
3134 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3135 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3136 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3137 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3138 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3139 collecting computer related songs for use at parties. The original
3140 version was written in LaTeX, but a few years ago I got help from
3141 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3142 while keeping the ability to create a nice book in PDF format. I have
3143 not had time to maintain the book for a while now, and guess I should
3144 put it up on some public version control repository where others can
3145 help me extend and update the book. If anyone is volunteering to help
3146 me with this, send me an email. Also let me know if there are songs
3147 missing in my book.&lt;/p&gt;
3148
3149 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3150 me today that I really should let all my readers share the joys of
3151 singing out load about programming, computers and computer networks.
3152 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3153 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3154 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3155 Computer Science Songbook&lt;/a&gt;.
3156 </description>
3157 </item>
3158
3159 <item>
3160 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3161 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3162 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3163 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3164 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3165 around 1000 at the moment. To be able to get help from the vendors
3166 when something go wrong, we want to keep the firmware on the servers
3167 up to date. If the firmware isn&#39;t the latest and greatest, the
3168 vendors typically refuse to start debugging any problems until the
3169 firmware is upgraded. So before every reboot, we want to upgrade the
3170 firmware, and we would really like everyone handling servers at the
3171 university to do this themselves when they plan to reboot a machine.
3172 For that to happen we at the unix server admin group need to provide
3173 the tools to do so.&lt;/p&gt;
3174
3175 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3176 fetch and install the latest firmware for the servers we got. Most of
3177 our hardware are from Dell and HP, so I have focused on these servers
3178 so far. This blog post is about the Dell part.&lt;/P&gt;
3179
3180 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3181 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3182 with firmware information for all 11th generation servers, listing
3183 which firmware should be used on a given model and where on the FTP
3184 site I can find it. Using a simple perl XML parser I can then
3185 download the shell scripts Dell provides to do firmware upgrades from
3186 within Linux and reboot when all the firmware is primed and ready to
3187 be activated on the first reboot.&lt;/p&gt;
3188
3189 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3190 Are there anyone working on similar tools for firmware upgrading all
3191 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3192
3193 &lt;p&gt;&lt;pre&gt;
3194 #!/usr/bin/perl
3195 use strict;
3196 use warnings;
3197 use File::Temp qw(tempdir);
3198 BEGIN {
3199 # Install needed RHEL packages if missing
3200 my %rhelmodules = (
3201 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3202 );
3203 for my $module (keys %rhelmodules) {
3204 eval &quot;use $module;&quot;;
3205 if ($@) {
3206 my $pkg = $rhelmodules{$module};
3207 system(&quot;yum install -y $pkg&quot;);
3208 eval &quot;use $module;&quot;;
3209 }
3210 }
3211 }
3212 my $errorsto = &#39;pere@hungry.com&#39;;
3213
3214 upgrade_dell();
3215
3216 exit 0;
3217
3218 sub run_firmware_script {
3219 my ($opts, $script) = @_;
3220 unless ($script) {
3221 print STDERR &quot;fail: missing script name\n&quot;;
3222 exit 1
3223 }
3224 print STDERR &quot;Running $script\n\n&quot;;
3225
3226 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3227 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3228 } else {
3229 print STDERR &quot;fail: firmware script returned error\n&quot;;
3230 }
3231 }
3232
3233 sub run_firmware_scripts {
3234 my ($opts, @dirs) = @_;
3235 # Run firmware packages
3236 for my $dir (@dirs) {
3237 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3238 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3239 while (my $s = readdir $dh) {
3240 next if $s =~ m/^\.\.?/;
3241 run_firmware_script($opts, &quot;$dir/$s&quot;);
3242 }
3243 closedir $dh;
3244 }
3245 }
3246
3247 sub download {
3248 my $url = shift;
3249 print STDERR &quot;info: Downloading $url\n&quot;;
3250 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3251 }
3252
3253 sub upgrade_dell {
3254 my @dirs;
3255 my $product = `dmidecode -s system-product-name`;
3256 chomp $product;
3257
3258 if ($product =~ m/PowerEdge/) {
3259
3260 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3261 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
3262
3263 my $tmpdir = tempdir(
3264 CLEANUP =&gt; 1
3265 );
3266 chdir($tmpdir);
3267 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
3268 system(&#39;gunzip Catalog.xml.gz&#39;);
3269 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
3270 # -q is quiet, disabling interactivity and reducing console output
3271 my $fwopts = &quot;-q&quot;;
3272 if (@paths) {
3273 for my $url (@paths) {
3274 fetch_dell_fw($url);
3275 }
3276 run_firmware_scripts($fwopts, $tmpdir);
3277 } else {
3278 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3279 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3280 }
3281 chdir(&#39;/&#39;);
3282 } else {
3283 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3284 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3285 }
3286 }
3287
3288 sub fetch_dell_fw {
3289 my $path = shift;
3290 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
3291 download($url);
3292 }
3293
3294 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3295 # firmware packages to download from Dell. Only work for Linux
3296 # machines and 11th generation Dell servers.
3297 sub fetch_dell_fw_list {
3298 my $filename = shift;
3299
3300 my $product = `dmidecode -s system-product-name`;
3301 chomp $product;
3302 my ($mybrand, $mymodel) = split(/\s+/, $product);
3303
3304 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
3305
3306 my $xml = XMLin($filename);
3307 my @paths;
3308 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
3309 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
3310 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
3311 my $oscode;
3312 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
3313 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
3314 } else {
3315 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
3316 }
3317 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
3318 {
3319 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
3320 }
3321 }
3322 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
3323 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
3324
3325 # Drop application packages, only firmware and BIOS
3326 next if &#39;APAC&#39; eq $componenttype;
3327
3328 my $cpath = $component-&gt;{path};
3329 for my $path (@paths) {
3330 if ($cpath =~ m%/$path$%) {
3331 push(@paths, $cpath);
3332 }
3333 }
3334 }
3335 return @paths;
3336 }
3337 &lt;/pre&gt;
3338
3339 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
3340 it could work on other platforms with some tweaking. Anyone know a
3341 index like Catalog.xml is available from HP for HP servers? At the
3342 moment I maintain a similar list manually and it is quickly getting
3343 outdated.&lt;/p&gt;
3344 </description>
3345 </item>
3346
3347 <item>
3348 <title>How is booting into runlevel 1 different from single user boots?</title>
3349 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
3350 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
3351 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
3352 <description>&lt;p&gt;Wouter Verhelst have some
3353 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
3354 comments and opinions&lt;/a&gt; on my blog post on
3355 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html&quot;&gt;the
3356 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
3357 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html&quot;&gt;the
3358 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
3359 small piece of his comment now, and though it best to address the
3360 misunderstanding he bring forward:&lt;/p&gt;
3361
3362 &lt;p&gt;&lt;blockquote&gt;
3363 Currently, a system admin has four options: [...] boot to a
3364 single-user system (by adding &#39;single&#39; to the kernel command line;
3365 this runs rcS and rc1 scripts)
3366 &lt;/blockquote&gt;&lt;/p&gt;
3367
3368 &lt;p&gt;This make me believe Wouter believe booting into single user mode
3369 and booting into runlevel 1 is the same. I am not surprised he
3370 believe this, because it would make sense and is a quite sensible
3371 thing to believe. But because the boot in Debian is slightly broken,
3372 runlevel 1 do not work properly and it isn&#39;t the same as single user
3373 mode. I&#39;ll try to explain what is actually happing, but it is a bit
3374 hard to explain.&lt;/p&gt;
3375
3376 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
3377 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
3378 executed in single user mode is sulogin. Single user mode is a boot
3379 state &quot;between&quot; the runlevels, and when booting into single user mode,
3380 only the scripts in /etc/rcS.d/ are executed before the init process
3381 enters the single user state. When switching to runlevel 1, the state
3382 is in fact not ending in runlevel 1, but it passes through runlevel 1
3383 and end up in the single user mode (see /etc/rc1.d/S03single, which
3384 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
3385 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
3386 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3387 mode).&lt;/p&gt;
3388
3389 &lt;p&gt;This summary might make it clearer. When booting for the first
3390 time into single user mode, the following commands are executed:
3391 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
3392 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
3393 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
3394 trying to continue after visiting single user mode. Not all services
3395 are started again as they should, causing the machine to end up in an
3396 unpredicatble state. This is why Debian admins recommend rebooting
3397 after visiting single user mode.&lt;/p&gt;
3398
3399 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
3400 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
3401 to runlevel 1, the services started from /etc/rcS.d/ are not properly
3402 stopped when passing through the scripts in /etc/rc1.d/, and not
3403 started again when switching away from runlevel 1 to the runlevels
3404 2-5. I believe the problem is best fixed by moving all the scripts
3405 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
3406 functioning single user mode during boot.&lt;/p&gt;
3407
3408 &lt;p&gt;I have spent several years investigating the Debian boot system,
3409 and discovered this problem a few years ago. I suspect it originates
3410 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
3411 </description>
3412 </item>
3413
3414 <item>
3415 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
3416 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
3417 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
3418 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
3419 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
3420 are started from /etc/rcS.d/. In fact, there is a bite more of them
3421 than make sense, and this causes a few problems. What kind of
3422 problems, you might ask. There are at least two problems. The first
3423 is that it is not possible to recover a machine after switching to
3424 runlevel 1. One need to actually reboot to get the machine back to
3425 the expected state. The other is that single user boot will sometimes
3426 run into problems because some of the subsystems are activated before
3427 the root login is presented, causing problems when trying to recover a
3428 machine from a problem in that subsystem. A minor additional point is
3429 that moving more scripts out of rcS.d/ and into the other rc#.d/
3430 directories will increase the amount of scripts that can run in
3431 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
3432
3433 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
3434 scripts that _have_ to execute before the root login prompt is
3435 presented during a single user boot should go there. Everything else
3436 should go into the numeric runlevels. This means things like
3437 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3438 the numeric runlevels. Today in Debian, there are around 115 init.d
3439 scripts that are started from rcS.d/, and most of them should be moved
3440 out. Do your package have one of them? Please help us make single
3441 user and runlevel 1 better by moving it.&lt;/p&gt;
3442
3443 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
3444 etc. should still be started from rcS.d/, but there is for example no
3445 need to have the network enabled before the single user login prompt
3446 is presented.&lt;/p&gt;
3447
3448 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
3449 Debian systems working while scripts migrate and during upgrades, the
3450 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3451 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3452 and the next ones can only be moved when their dependencies have been
3453 moved first. This migration must be done sequentially while we ensure
3454 that the package system upgrade packages in the right order to keep
3455 the system state correct. This will require some coordination when it
3456 comes to network related packages, but most of the packages with
3457 scripts that should migrate do not have anything in rcS.d/ depending
3458 on them. Some packages have already been updated, like the sudo
3459 package, while others are still left to do. I wish I had time to work
3460 on this myself, but real live constrains make it unlikely that I will
3461 find time to push this forward.&lt;/p&gt;
3462 </description>
3463 </item>
3464
3465 <item>
3466 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
3467 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
3468 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
3469 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
3470 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
3471 mentioned the issues I believe should be improved in Debian for its
3472 desktop to be useful for more people. The use case for this is my
3473 parents, which are currently running Kubuntu which solve the
3474 issues.&lt;/p&gt;
3475
3476 &lt;p&gt;I suspect these four missing features are not very hard to
3477 implement. After all, they are present in Ubuntu, so if we wanted to
3478 do this in Debian we would have a source.&lt;/p&gt;
3479
3480 &lt;ol&gt;
3481
3482 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
3483 are new packages available for upgrades, a icon in the KDE status bar
3484 indicate this, and clicking on it will activate the simple upgrade
3485 tool to handle it. I have no problem guiding both of my parents
3486 through the process over the phone. If a kernel reboot is required,
3487 this too is indicated by the status bars and the upgrade tool. Last
3488 time I checked, nothing with the same features was working in KDE in
3489 Debian.&lt;/li&gt;
3490
3491 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
3492 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
3493 currently have a handler for, it will ask the user if the system
3494 should search for a package that would add support for this MIME type,
3495 and if the user say yes, the APT sources will be searched for packages
3496 advertising the MIME type in their control file (visible in the
3497 Packages file in the APT archive). If one or more packages are found,
3498 it is a simple click of the mouse to add support for the missing mime
3499 type. If the package require the user to accept some non-free
3500 license, this is explained to the user. The entire process make it
3501 more clear to the user why something do not work in the browser, and
3502 make the chances higher for the user to blame the web page authors and
3503 not the browser for any missing features.&lt;/li&gt;
3504
3505 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
3506 handlers.&lt;/strong&gt; When the media players encounter a format or codec
3507 it is not supporting, a dialog pop up asking the user if the system
3508 should search for a package that would add support for it. This
3509 happen with things like MP3, Windows Media or H.264. The selection
3510 and installation procedure is very similar to the Firefox browser
3511 plugin handling. This is as far as I know implemented using a
3512 gstreamer hook. The end result is that the user easily get access to
3513 the codecs that are present from the APT archives available, while
3514 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
3515
3516 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
3517 displaying a text/plain file in my Debian browser, it will propose to
3518 start emacs to show it. If I remember correctly, when doing the same
3519 in Kunbutu it show the file as a text file in the browser. At least I
3520 know Opera will show text files within the browser. I much prefer the
3521 latter behaviour.&lt;/li&gt;
3522
3523 &lt;/ol&gt;
3524
3525 &lt;p&gt;There are other nice features as well, like the simplified suite
3526 upgrader, but given that I am the one mostly doing the dist-upgrade,
3527 it do not matter much.&lt;/p&gt;
3528
3529 &lt;p&gt;I really hope we could get these features in place for the next
3530 Debian release. It would require the coordinated effort of several
3531 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
3532 </description>
3533 </item>
3534
3535 <item>
3536 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
3537 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
3538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
3539 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
3540 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
3541 site is build on Debian/Squeeze, and this platform was chosen because
3542 I am most familiar with Debian (being a Debian Developer for around 10
3543 years) because it is the latest stable Debian release which should get
3544 security support for a few years.&lt;/p&gt;
3545
3546 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
3547 that are missing in Debian at the moment. It would be great if these
3548 modules were added to the Debian archive, allowing anyone to set up
3549 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
3550 in their own country using only Debian packages. The list of modules
3551 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
3552 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
3553 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
3554 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
3555 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
3556 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
3557 easier in the future.&lt;/p&gt;
3558
3559 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
3560 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
3561 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
3562 with the responsibility of tracking security problems, which I really
3563 do not have time for.&lt;/p&gt;
3564 </description>
3565 </item>
3566
3567 <item>
3568 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
3569 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
3570 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
3571 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
3572 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
3573 posts have been in Norwegian the last few weeks, so here is a short
3574 update in English.&lt;/p&gt;
3575
3576 &lt;p&gt;The kids still keep me too busy to get much free software work
3577 done, but I did manage to organise a project to get a Norwegian port
3578 of the British service
3579 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
3580 and it has been running for a month now. The entire project has been
3581 organised by me and two others. Around Christmas we gathered sponsors
3582 to fund the development work. In January I drafted a contract with
3583 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
3584 and in February the development took place. Most of it involved
3585 converting the source to use GPS coordinates instead of British
3586 easting/northing, and the resulting code should be a lot easier to get
3587 running in any country by now. The Norwegian
3588 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
3589 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
3590 source and the source for administrative borders in Norway, and
3591 support for this had to be added/fixed.&lt;/p&gt;
3592
3593 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
3594 polishing the system before we announced it March 7th. The system is
3595 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
3596 problem reports in a few weeks. Soon we hope to announce the Android
3597 and iPhone versions making it even easier to report problems with the
3598 public infrastructure.&lt;/p&gt;
3599
3600 &lt;p&gt;Perhaps something to consider for those of you in countries without
3601 such service?&lt;/p&gt;
3602 </description>
3603 </item>
3604
3605 <item>
3606 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
3607 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
3608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
3609 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
3610 <description>&lt;p&gt;The last few days I have looked at ways to track open security
3611 issues here at my work with the University of Oslo. My idea is that
3612 it should be possible to use the information about security issues
3613 available on the Internet, and check our locally
3614 maintained/distributed software against this information. It should
3615 allow us to verify that no known security issues are forgotten. The
3616 CVE database listing vulnerabilities seem like a great central point,
3617 and by using the package lists from Debian mapped to CVEs provided by
3618 the testing security team, I believed it should be possible to figure
3619 out which security holes were present in our free software
3620 collection.&lt;/p&gt;
3621
3622 &lt;p&gt;After reading up on the topic, it became obvious that the first
3623 building block is to be able to name software packages in a unique and
3624 consistent way across data sources. I considered several ways to do
3625 this, for example coming up with my own naming scheme like using URLs
3626 to project home pages or URLs to the Freshmeat entries, or using some
3627 existing naming scheme. And it seem like I am not the first one to
3628 come across this problem, as MITRE already proposed and implemented a
3629 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
3630 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
3631 software, hardware and other platform components. The CPE ids are
3632 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
3633 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
3634 issues for any CPE name. With this in place, all I need to do is to
3635 locate the CPE id for the software packages we use at the university.
3636 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
3637 NVD entry if a CVE for the package exist).&lt;/p&gt;
3638
3639 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
3640 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
3641 check out, one could look up
3642 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%3A%2Fa%3Agnu%3Agzip:1.3.3&quot;&gt;cpe:/a:gnu:gzip:1.3.3
3643 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
3644 The most recent one is
3645 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
3646 and at the bottom of the NVD page for this vulnerability the complete
3647 list of affected versions is provided.&lt;/p&gt;
3648
3649 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
3650 for offline processing of issues. Using this dump, I&#39;ve written a
3651 small script taking a list of CPEs as input and list all CVEs
3652 affecting the packages represented by these CPEs. One give it CPEs
3653 with version numbers as specified above and get a list of open
3654 security issues out.&lt;/p&gt;
3655
3656 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
3657 information need to be high. For that to happen, I believe as many as
3658 possible need to use and contribute to the NVD database. I notice
3659 RHEL is providing
3660 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
3661 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
3662 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
3663
3664 &lt;p&gt;To get an idea about the quality for free software, I spent some
3665 time making it possible to compare the CVE database from Debian with
3666 the CVE database in NVD. The result look fairly good, but there are
3667 some inconsistencies in NVD (same software package having several
3668 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
3669 Debian believe are affected by a CVE). Hope to find time to improve
3670 the quality of NVD, but that require being able to get in touch with
3671 someone maintaining it. So far my three emails with questions and
3672 corrections have not seen any reply, but I hope contact can be
3673 established soon.&lt;/p&gt;
3674
3675 &lt;p&gt;An interesting application for CPEs is cross platform package
3676 mapping. It would be useful to know which packages in for example
3677 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
3678 this would be trivial if all linux distributions provided CPE entries
3679 for their packages.&lt;/p&gt;
3680 </description>
3681 </item>
3682
3683 <item>
3684 <title>Which module is loaded for a given PCI and USB device?</title>
3685 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
3686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
3687 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
3688 <description>&lt;p&gt;In the
3689 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
3690 package in Debian, there is a script to report useful information
3691 about the running hardware for use when people report missing
3692 information. One part of this script that I find very useful when
3693 debugging hardware problems, is the part mapping loaded kernel module
3694 to the PCI device it claims. It allow me to quickly see if the kernel
3695 module I expect is driving the hardware I am struggling with. To see
3696 the output, make sure discover-data is installed and run
3697 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
3698 one of my machines like this:&lt;/p&gt;
3699
3700 &lt;pre&gt;
3701 loaded modules:
3702 10de:03eb i2c_nforce2
3703 10de:03f1 ohci_hcd
3704 10de:03f2 ehci_hcd
3705 10de:03f0 snd_hda_intel
3706 10de:03ec pata_amd
3707 10de:03f6 sata_nv
3708 1022:1103 k8temp
3709 109e:036e bttv
3710 109e:0878 snd_bt87x
3711 11ab:4364 sky2
3712 &lt;/pre&gt;
3713
3714 &lt;p&gt;The code in question look like this, slightly modified for
3715 readability and to drop the output to file descriptor 3:&lt;/p&gt;
3716
3717 &lt;pre&gt;
3718 if [ -d /sys/bus/pci/devices/ ] ; then
3719 echo loaded pci modules:
3720 (
3721 cd /sys/bus/pci/devices/
3722 for address in * ; do
3723 if [ -d &quot;$address/driver/module&quot; ] ; then
3724 module=`cd $address/driver/module ; pwd -P | xargs basename`
3725 if grep -q &quot;^$module &quot; /proc/modules ; then
3726 address=$(echo $address |sed s/0000://)
3727 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
3728 echo &quot;$id $module&quot;
3729 fi
3730 fi
3731 done
3732 )
3733 echo
3734 fi
3735 &lt;/pre&gt;
3736
3737 &lt;p&gt;Similar code could be used to extract USB device module
3738 mappings:&lt;/p&gt;
3739
3740 &lt;pre&gt;
3741 if [ -d /sys/bus/usb/devices/ ] ; then
3742 echo loaded usb modules:
3743 (
3744 cd /sys/bus/usb/devices/
3745 for address in * ; do
3746 if [ -d &quot;$address/driver/module&quot; ] ; then
3747 module=`cd $address/driver/module ; pwd -P | xargs basename`
3748 if grep -q &quot;^$module &quot; /proc/modules ; then
3749 address=$(echo $address |sed s/0000://)
3750 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
3751 if [ &quot;$id&quot; ] ; then
3752 echo &quot;$id $module&quot;
3753 fi
3754 fi
3755 fi
3756 done
3757 )
3758 echo
3759 fi
3760 &lt;/pre&gt;
3761
3762 &lt;p&gt;This might perhaps be something to include in other tools as
3763 well.&lt;/p&gt;
3764 </description>
3765 </item>
3766
3767 <item>
3768 <title>How to test if a laptop is working with Linux</title>
3769 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
3770 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
3771 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
3772 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
3773 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
3774 batch of computers will work with Linux. Every year for the last few
3775 years the university have organised shared bid of a few thousand
3776 computers, and this year HP won the bid. Two different desktops and
3777 five different laptops are on the list this year. We in the UNIX
3778 group want to know which one of these computers work well with RHEL
3779 and Ubuntu, the two Linux distributions we currently handle at the
3780 university.&lt;/p&gt;
3781
3782 &lt;p&gt;My test method is simple, and I share it here to get feedback and
3783 perhaps inspire others to test hardware as well. To test, I PXE
3784 install the OS version of choice, and log in as my normal user and run
3785 a few applications and plug in selected pieces of hardware. When
3786 something fail, I make a note about this in the test matrix and move
3787 on. If I have some spare time I try to report the bug to the OS
3788 vendor, but as I only have the machines for a short time, I rarely
3789 have the time to do this for all the problems I find.&lt;/p&gt;
3790
3791 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
3792 I perform on a new model.&lt;/p&gt;
3793
3794 &lt;ul&gt;
3795
3796 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
3797 and Ubuntu Maverik at the moment. If I feel like it, I also test with
3798 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
3799
3800 &lt;li&gt;Is X.org working? If the graphical login screen show up after
3801 installation, X.org is working.&lt;/li&gt;
3802
3803 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
3804 package mesa-utils on Ubuntu) and writing down the frames per second
3805 reported by the program.&lt;/li&gt;
3806
3807 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
3808 logging in, and if I can hear this the test is successful. If there
3809 are several audio exits on the machine, I try them all and check if
3810 the Gnome/KDE audio mixer can control where to send the sound. I
3811 normally test this by playing
3812 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
3813 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
3814
3815 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
3816 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
3817
3818 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
3819 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
3820
3821 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
3822 picture from the v4l device show up.&lt;/li&gt;
3823
3824 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
3825 any bluetooth devices are discovered. In my office, I normally see a
3826 few.&lt;/li&gt;
3827
3828 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
3829 memory modules lying around, and stick them in and see if Gnome/KDE
3830 notice this.&lt;/li&gt;
3831
3832 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
3833 special button work, and if the laptop continue to work after
3834 resume.&lt;/li&gt;
3835
3836 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
3837 adjusting background light, switching on/off external video output,
3838 switching on/off wifi, bluetooth, etc? The set of buttons differ from
3839 laptop to laptop, so I just write down which are working and which are
3840 not.&lt;/li&gt;
3841
3842 &lt;li&gt;Some laptops have smart card readers, finger print readers,
3843 acceleration sensors etc. I rarely test these, as I do not know how
3844 to quickly test if they are working or not, so I only document their
3845 existence.&lt;/li&gt;
3846
3847 &lt;/ul&gt;
3848
3849 &lt;p&gt;By now I suspect you are really curious what the test results are
3850 for the HP machines I am testing. I&#39;m not done yet, so I will report
3851 the test results later. For now I can report that HP 8100 Elite work
3852 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
3853 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
3854 can see, I have most machines left to test. One interesting
3855 observation is that Ubuntu Lucid has almost twice the frame rate than
3856 RHEL6 with glxgears. No idea why.&lt;/p&gt;
3857 </description>
3858 </item>
3859
3860 <item>
3861 <title>Some thoughts on BitCoins</title>
3862 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
3863 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
3864 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
3865 <description>&lt;p&gt;As I continue to explore
3866 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
3867 what properties the system have, and how it will be affected by laws
3868 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
3869
3870 &lt;p&gt;One interesting thing to note is that since the transactions are
3871 verified using a peer to peer network, all details about a transaction
3872 is known to everyone. This means that if a BitCoin address has been
3873 published like I did with mine in my initial post about BitCoin, it is
3874 possible for everyone to see how many BitCoins have been transfered to
3875 that address. There is even a web service to look at the details for
3876 all transactions. There I can see that my address
3877 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
3878 have received 16.06 Bitcoin, the
3879 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
3880 address of Simon Phipps have received 181.97 BitCoin and the address
3881 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
3882 of EFF have received 2447.38 BitCoins so far. Thank you to each and
3883 every one of you that donated bitcoins to support my activity. The
3884 fact that anyone can see how much money was transfered to a given
3885 address make it more obvious why the BitCoin community recommend to
3886 generate and hand out a new address for each transaction. I&#39;m told
3887 there is no way to track which addresses belong to a given person or
3888 organisation without the person or organisation revealing it
3889 themselves, as Simon, EFF and I have done.&lt;/p&gt;
3890
3891 &lt;p&gt;In Norway, and in most other countries, there are laws and
3892 regulations limiting how much money one can transfer across the border
3893 without declaring it. There are money laundering, tax and accounting
3894 laws and regulations I would expect to apply to the use of BitCoin.
3895 If the Skolelinux foundation
3896 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
3897 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
3898 normal bank transfers like EFF is doing, how should this be accounted?
3899 Given that it is impossible to know if money can cross the border or
3900 not, should everything or nothing be declared? What exchange rate
3901 should be used when calculating taxes? Would receivers have to pay
3902 income tax if the foundation were to pay Skolelinux contributors in
3903 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
3904
3905 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
3906 accepted by a lot of users. It must be possible to get easy access to
3907 the currency (as a wage or using currency exchanges), and it must be
3908 easy to spend it. At the moment BitCoin seem fairly easy to get
3909 access to, but there are very few places to spend it. I am not really
3910 a regular user of any of the vendor types currently accepting BitCoin,
3911 so I wonder when my kind of shop would start accepting BitCoins. I
3912 would like to buy electronics, travels and subway tickets, not herbs
3913 and books. :) The currency is young, and this will improve over time
3914 if it become popular, but I suspect regular banks will start to lobby
3915 to get BitCoin declared illegal if it become popular. I&#39;m sure they
3916 will claim it is helping fund terrorism and money laundering (which
3917 probably would be true, as is any currency in existence), but I
3918 believe the problems should be solved elsewhere and not by blaming
3919 currencies.&lt;/p&gt;
3920
3921 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
3922 CPU intensive process that depend on a bit of luck as well (as one is
3923 competing against all the other miners currently spending CPU cycles
3924 to see which one get the next lump of cash). The &quot;winner&quot; get 50
3925 BitCoin when this happen. Yesterday I came across the obvious way to
3926 join forces to increase ones changes of getting at least some coins,
3927 by coordinating the work on mining BitCoins across several machines
3928 and people, and sharing the result if one is lucky and get the 50
3929 BitCoins. Check out
3930 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
3931 if this sounds interesting. I have not had time to try to set up a
3932 machine to participate there yet, but have seen that running on ones
3933 own for a few days have not yield any BitCoins througth mining
3934 yet.&lt;/p&gt;
3935
3936 &lt;p&gt;Update 2010-12-15: Found an &lt;a
3937 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
3938 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
3939 it was interesting to read. The arguments presented seem to be
3940 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
3941 </description>
3942 </item>
3943
3944 <item>
3945 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
3946 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
3947 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
3948 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
3949 <description>&lt;p&gt;With this weeks lawless
3950 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
3951 attacks&lt;/a&gt; on Wikileak and
3952 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
3953 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
3954 not be trusted to handle money transactions.
3955 A blog post from
3956 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
3957 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
3958 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
3959 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
3960 some help from my friend to get it all running, and he even handed me
3961 some bitcoins to get started. I even donated a few bitcoins to Simon
3962 for helping me remember BitCoin.&lt;/p&gt;
3963
3964 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
3965 crypto-currency, decentralised and handled using peer-to-peer
3966 networks. It allows anonymous transactions and prohibits central
3967 control over the transactions, making it impossible for governments
3968 and companies alike to block donations and other transactions. The
3969 source is free software, and while the key dependency wxWidgets 2.9
3970 for the graphical user interface is missing in Debian, the command
3971 line client builds just fine. Hopefully Jonas
3972 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
3973 Debian&lt;/a&gt; soon.&lt;/p&gt;
3974
3975 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
3976 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
3977 bitcoins&lt;/a&gt; when selling services and goods, and there are even
3978 currency &quot;stock&quot; markets where the exchange rate is decided. There
3979 are not many users so far, but the concept seems promising. If you
3980 want to get started and lack a friend with any bitcoins to spare,
3981 you can even get
3982 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
3983 bitcoin at the time of writing). Use
3984 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
3985 on the current exchange rates.&lt;/p&gt;
3986
3987 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
3988 machines. If you want to support my activity, please send Bitcoin
3989 donations to the address
3990 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
3991 </description>
3992 </item>
3993
3994 <item>
3995 <title>Why isn&#39;t Debian Edu using VLC?</title>
3996 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
3997 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
3998 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
3999 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4000 presented, and the winner among the multimedia player were VLC.
4001 Personally, I like VLC, and it is my player of choice when I first try
4002 to play a video file or stream. Only if VLC fail will I drag out
4003 gmplayer to see if it can do better. The reason is mostly the failure
4004 model and trust. When VLC fail, it normally pop up a error message
4005 reporting the problem. When mplayer fail, it normally segfault or
4006 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4007
4008 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4009 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4010 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4011 plugin to play web videos seamlessly, and the VLC browser plugin is
4012 not very good. For example, it lack in-line control buttons, so there
4013 is no way for the user to pause the video. Also, when I
4014 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4015 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4016 failed on several video pages where mplayer based plugins worked. If
4017 the browser plugin for VLC was as good as the gecko-mediaplayer
4018 package (which uses mplayer), we would switch.&lt;/P&gt;
4019
4020 &lt;p&gt;While VLC is a good player, its user interface is slightly
4021 annoying. The most annoying feature is its inconsistent use of
4022 keyboard shortcuts. When the player is in full screen mode, its
4023 shortcuts are different from when it is playing the video in a window.
4024 For example, space only work as pause when in full screen mode. I
4025 wish it had consisten shortcuts and that space also would work when in
4026 window mode. Another nice shortcut in gmplayer is [enter] to restart
4027 the current video. It is very nice when playing short videos from the
4028 web and want to restart it when new people arrive to have a look at
4029 what is going on.&lt;/p&gt;
4030 </description>
4031 </item>
4032
4033 <item>
4034 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4035 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4036 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</guid>
4037 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4038 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4039 upgrade testing of the
4040 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4041 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4042 This seem like a very good idea, so I adjusted by test scripts and
4043 can now present the updated result from today:&lt;/p&gt;
4044
4045 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4046
4047 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4048
4049 &lt;blockquote&gt;&lt;p&gt;
4050 apache2.2-bin
4051 aptdaemon
4052 baobab
4053 binfmt-support
4054 browser-plugin-gnash
4055 cheese-common
4056 cli-common
4057 cups-pk-helper
4058 dmz-cursor-theme
4059 empathy
4060 empathy-common
4061 freedesktop-sound-theme
4062 freeglut3
4063 gconf-defaults-service
4064 gdm-themes
4065 gedit-plugins
4066 geoclue
4067 geoclue-hostip
4068 geoclue-localnet
4069 geoclue-manual
4070 geoclue-yahoo
4071 gnash
4072 gnash-common
4073 gnome
4074 gnome-backgrounds
4075 gnome-cards-data
4076 gnome-codec-install
4077 gnome-core
4078 gnome-desktop-environment
4079 gnome-disk-utility
4080 gnome-screenshot
4081 gnome-search-tool
4082 gnome-session-canberra
4083 gnome-system-log
4084 gnome-themes-extras
4085 gnome-themes-more
4086 gnome-user-share
4087 gstreamer0.10-fluendo-mp3
4088 gstreamer0.10-tools
4089 gtk2-engines
4090 gtk2-engines-pixbuf
4091 gtk2-engines-smooth
4092 hamster-applet
4093 libapache2-mod-dnssd
4094 libapr1
4095 libaprutil1
4096 libaprutil1-dbd-sqlite3
4097 libaprutil1-ldap
4098 libart2.0-cil
4099 libboost-date-time1.42.0
4100 libboost-python1.42.0
4101 libboost-thread1.42.0
4102 libchamplain-0.4-0
4103 libchamplain-gtk-0.4-0
4104 libcheese-gtk18
4105 libclutter-gtk-0.10-0
4106 libcryptui0
4107 libdiscid0
4108 libelf1
4109 libepc-1.0-2
4110 libepc-common
4111 libepc-ui-1.0-2
4112 libfreerdp-plugins-standard
4113 libfreerdp0
4114 libgconf2.0-cil
4115 libgdata-common
4116 libgdata7
4117 libgdu-gtk0
4118 libgee2
4119 libgeoclue0
4120 libgexiv2-0
4121 libgif4
4122 libglade2.0-cil
4123 libglib2.0-cil
4124 libgmime2.4-cil
4125 libgnome-vfs2.0-cil
4126 libgnome2.24-cil
4127 libgnomepanel2.24-cil
4128 libgpod-common
4129 libgpod4
4130 libgtk2.0-cil
4131 libgtkglext1
4132 libgtksourceview2.0-common
4133 libmono-addins-gui0.2-cil
4134 libmono-addins0.2-cil
4135 libmono-cairo2.0-cil
4136 libmono-corlib2.0-cil
4137 libmono-i18n-west2.0-cil
4138 libmono-posix2.0-cil
4139 libmono-security2.0-cil
4140 libmono-sharpzip2.84-cil
4141 libmono-system2.0-cil
4142 libmtp8
4143 libmusicbrainz3-6
4144 libndesk-dbus-glib1.0-cil
4145 libndesk-dbus1.0-cil
4146 libopal3.6.8
4147 libpolkit-gtk-1-0
4148 libpt2.6.7
4149 libpython2.6
4150 librpm1
4151 librpmio1
4152 libsdl1.2debian
4153 libsrtp0
4154 libssh-4
4155 libtelepathy-farsight0
4156 libtelepathy-glib0
4157 libtidy-0.99-0
4158 media-player-info
4159 mesa-utils
4160 mono-2.0-gac
4161 mono-gac
4162 mono-runtime
4163 nautilus-sendto
4164 nautilus-sendto-empathy
4165 p7zip-full
4166 pkg-config
4167 python-aptdaemon
4168 python-aptdaemon-gtk
4169 python-axiom
4170 python-beautifulsoup
4171 python-bugbuddy
4172 python-clientform
4173 python-coherence
4174 python-configobj
4175 python-crypto
4176 python-cupshelpers
4177 python-elementtree
4178 python-epsilon
4179 python-evolution
4180 python-feedparser
4181 python-gdata
4182 python-gdbm
4183 python-gst0.10
4184 python-gtkglext1
4185 python-gtksourceview2
4186 python-httplib2
4187 python-louie
4188 python-mako
4189 python-markupsafe
4190 python-mechanize
4191 python-nevow
4192 python-notify
4193 python-opengl
4194 python-openssl
4195 python-pam
4196 python-pkg-resources
4197 python-pyasn1
4198 python-pysqlite2
4199 python-rdflib
4200 python-serial
4201 python-tagpy
4202 python-twisted-bin
4203 python-twisted-conch
4204 python-twisted-core
4205 python-twisted-web
4206 python-utidylib
4207 python-webkit
4208 python-xdg
4209 python-zope.interface
4210 remmina
4211 remmina-plugin-data
4212 remmina-plugin-rdp
4213 remmina-plugin-vnc
4214 rhythmbox-plugin-cdrecorder
4215 rhythmbox-plugins
4216 rpm-common
4217 rpm2cpio
4218 seahorse-plugins
4219 shotwell
4220 software-center
4221 system-config-printer-udev
4222 telepathy-gabble
4223 telepathy-mission-control-5
4224 telepathy-salut
4225 tomboy
4226 totem
4227 totem-coherence
4228 totem-mozilla
4229 totem-plugins
4230 transmission-common
4231 xdg-user-dirs
4232 xdg-user-dirs-gtk
4233 xserver-xephyr
4234 &lt;/p&gt;&lt;/blockquote&gt;
4235
4236 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4237
4238 &lt;blockquote&gt;&lt;p&gt;
4239 cheese
4240 ekiga
4241 eog
4242 epiphany-extensions
4243 evolution-exchange
4244 fast-user-switch-applet
4245 file-roller
4246 gcalctool
4247 gconf-editor
4248 gdm
4249 gedit
4250 gedit-common
4251 gnome-games
4252 gnome-games-data
4253 gnome-nettool
4254 gnome-system-tools
4255 gnome-themes
4256 gnuchess
4257 gucharmap
4258 guile-1.8-libs
4259 libavahi-ui0
4260 libdmx1
4261 libgalago3
4262 libgtk-vnc-1.0-0
4263 libgtksourceview2.0-0
4264 liblircclient0
4265 libsdl1.2debian-alsa
4266 libspeexdsp1
4267 libsvga1
4268 rhythmbox
4269 seahorse
4270 sound-juicer
4271 system-config-printer
4272 totem-common
4273 transmission-gtk
4274 vinagre
4275 vino
4276 &lt;/p&gt;&lt;/blockquote&gt;
4277
4278 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4279
4280 &lt;blockquote&gt;&lt;p&gt;
4281 gstreamer0.10-gnomevfs
4282 &lt;/p&gt;&lt;/blockquote&gt;
4283
4284 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4285
4286 &lt;blockquote&gt;&lt;p&gt;
4287 [nothing]
4288 &lt;/p&gt;&lt;/blockquote&gt;
4289
4290 &lt;p&gt;This is for KDE:&lt;/p&gt;
4291
4292 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4293
4294 &lt;blockquote&gt;&lt;p&gt;
4295 ksmserver
4296 &lt;/p&gt;&lt;/blockquote&gt;
4297
4298 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4299
4300 &lt;blockquote&gt;&lt;p&gt;
4301 kwin
4302 network-manager-kde
4303 &lt;/p&gt;&lt;/blockquote&gt;
4304
4305 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4306
4307 &lt;blockquote&gt;&lt;p&gt;
4308 arts
4309 dolphin
4310 freespacenotifier
4311 google-gadgets-gst
4312 google-gadgets-xul
4313 kappfinder
4314 kcalc
4315 kcharselect
4316 kde-core
4317 kde-plasma-desktop
4318 kde-standard
4319 kde-window-manager
4320 kdeartwork
4321 kdeartwork-emoticons
4322 kdeartwork-style
4323 kdeartwork-theme-icon
4324 kdebase
4325 kdebase-apps
4326 kdebase-workspace
4327 kdebase-workspace-bin
4328 kdebase-workspace-data
4329 kdeeject
4330 kdelibs
4331 kdeplasma-addons
4332 kdeutils
4333 kdewallpapers
4334 kdf
4335 kfloppy
4336 kgpg
4337 khelpcenter4
4338 kinfocenter
4339 konq-plugins-l10n
4340 konqueror-nsplugins
4341 kscreensaver
4342 kscreensaver-xsavers
4343 ktimer
4344 kwrite
4345 libgle3
4346 libkde4-ruby1.8
4347 libkonq5
4348 libkonq5-templates
4349 libnetpbm10
4350 libplasma-ruby
4351 libplasma-ruby1.8
4352 libqt4-ruby1.8
4353 marble-data
4354 marble-plugins
4355 netpbm
4356 nuvola-icon-theme
4357 plasma-dataengines-workspace
4358 plasma-desktop
4359 plasma-desktopthemes-artwork
4360 plasma-runners-addons
4361 plasma-scriptengine-googlegadgets
4362 plasma-scriptengine-python
4363 plasma-scriptengine-qedje
4364 plasma-scriptengine-ruby
4365 plasma-scriptengine-webkit
4366 plasma-scriptengines
4367 plasma-wallpapers-addons
4368 plasma-widget-folderview
4369 plasma-widget-networkmanagement
4370 ruby
4371 sweeper
4372 update-notifier-kde
4373 xscreensaver-data-extra
4374 xscreensaver-gl
4375 xscreensaver-gl-extra
4376 xscreensaver-screensaver-bsod
4377 &lt;/p&gt;&lt;/blockquote&gt;
4378
4379 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4380
4381 &lt;blockquote&gt;&lt;p&gt;
4382 ark
4383 google-gadgets-common
4384 google-gadgets-qt
4385 htdig
4386 kate
4387 kdebase-bin
4388 kdebase-data
4389 kdepasswd
4390 kfind
4391 klipper
4392 konq-plugins
4393 konqueror
4394 ksysguard
4395 ksysguardd
4396 libarchive1
4397 libcln6
4398 libeet1
4399 libeina-svn-06
4400 libggadget-1.0-0b
4401 libggadget-qt-1.0-0b
4402 libgps19
4403 libkdecorations4
4404 libkephal4
4405 libkonq4
4406 libkonqsidebarplugin4a
4407 libkscreensaver5
4408 libksgrd4
4409 libksignalplotter4
4410 libkunitconversion4
4411 libkwineffects1a
4412 libmarblewidget4
4413 libntrack-qt4-1
4414 libntrack0
4415 libplasma-geolocation-interface4
4416 libplasmaclock4a
4417 libplasmagenericshell4
4418 libprocesscore4a
4419 libprocessui4a
4420 libqalculate5
4421 libqedje0a
4422 libqtruby4shared2
4423 libqzion0a
4424 libruby1.8
4425 libscim8c2a
4426 libsmokekdecore4-3
4427 libsmokekdeui4-3
4428 libsmokekfile3
4429 libsmokekhtml3
4430 libsmokekio3
4431 libsmokeknewstuff2-3
4432 libsmokeknewstuff3-3
4433 libsmokekparts3
4434 libsmokektexteditor3
4435 libsmokekutils3
4436 libsmokenepomuk3
4437 libsmokephonon3
4438 libsmokeplasma3
4439 libsmokeqtcore4-3
4440 libsmokeqtdbus4-3
4441 libsmokeqtgui4-3
4442 libsmokeqtnetwork4-3
4443 libsmokeqtopengl4-3
4444 libsmokeqtscript4-3
4445 libsmokeqtsql4-3
4446 libsmokeqtsvg4-3
4447 libsmokeqttest4-3
4448 libsmokeqtuitools4-3
4449 libsmokeqtwebkit4-3
4450 libsmokeqtxml4-3
4451 libsmokesolid3
4452 libsmokesoprano3
4453 libtaskmanager4a
4454 libtidy-0.99-0
4455 libweather-ion4a
4456 libxklavier16
4457 libxxf86misc1
4458 okteta
4459 oxygencursors
4460 plasma-dataengines-addons
4461 plasma-scriptengine-superkaramba
4462 plasma-widget-lancelot
4463 plasma-widgets-addons
4464 plasma-widgets-workspace
4465 polkit-kde-1
4466 ruby1.8
4467 systemsettings
4468 update-notifier-common
4469 &lt;/p&gt;&lt;/blockquote&gt;
4470
4471 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
4472 aptitude a bit more similar, but there are still quite a lott of
4473 differences. I have no idea what packages should be installed after
4474 the upgrade, but hope those that do can have a look.&lt;/p&gt;
4475 </description>
4476 </item>
4477
4478 <item>
4479 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
4480 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
4481 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
4482 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
4483 <description>&lt;p&gt;Most of the computers in use by the
4484 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
4485 are virtual machines. And they have been Xen machines running on a
4486 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
4487 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
4488 bit harder that it could have been, because we set up the Xen virtual
4489 machines to get the virtual partitions from LVM, which as far as I
4490 know is not supported by KVM. So to migrate, we had to convert
4491 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
4492
4493 &lt;p&gt;I found
4494 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
4495 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
4496 migration. It uses qemu-img from the qemu package to make the disk
4497 image, parted to partition it, losetup and kpartx to present the disk
4498 image partions as devices, and dd to copy the data. I NFS mounted the
4499 new servers storage area on the old server to do the migration.&lt;/p&gt;
4500
4501 &lt;pre&gt;
4502 #!/bin/sh
4503
4504 # Based on
4505 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
4506
4507 set -e
4508 set -x
4509
4510 if [ -z &quot;$1&quot; ] ; then
4511 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
4512 exit 1
4513 else
4514 host=&quot;$1&quot;
4515 fi
4516
4517 if [ ! -e /dev/vg_data/$host-disk ] ; then
4518 echo &quot;error: unable to find LVM volume for $host&quot;
4519 exit 1
4520 fi
4521
4522 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
4523 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
4524 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
4525 totalsize=$(( ( $disksize + $swapsize ) ))
4526
4527 img=$host.img
4528 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
4529 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
4530
4531 parted $img mklabel msdos
4532 parted $img mkpart primary linux-swap 0 $disksize
4533 parted $img mkpart primary ext2 $disksize $totalsize
4534 parted $img set 1 boot on
4535
4536 modprobe dm-mod
4537 losetup /dev/loop0 $img
4538 kpartx -a /dev/loop0
4539
4540 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
4541 fsck.ext3 -f /dev/mapper/loop0p1 || true
4542 mkswap /dev/mapper/loop0p2
4543
4544 kpartx -d /dev/loop0
4545 losetup -d /dev/loop0
4546 &lt;/pre&gt;
4547
4548 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
4549 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
4550
4551 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
4552 the new disk image attached, installed grub-pc and linux-image-686 and
4553 set up grub to boot from the disk image. After this, the KVM machines
4554 seem to work just fine.&lt;/p&gt;
4555 </description>
4556 </item>
4557
4558 <item>
4559 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
4560 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
4561 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
4562 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
4563 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
4564 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4565 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
4566 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
4567
4568 &lt;p&gt;I still do not know what a correct migration should look like, so I
4569 report any differences between apt and aptitude and hope someone else
4570 can see if anything should be changed.&lt;/p&gt;
4571
4572 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4573
4574 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4575
4576 &lt;blockquote&gt;&lt;p&gt;
4577 apache2.2-bin aptdaemon at-spi baobab binfmt-support
4578 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
4579 dmz-cursor-theme empathy empathy-common finger
4580 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
4581 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
4582 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
4583 gnome-cards-data gnome-codec-install gnome-core
4584 gnome-desktop-environment gnome-disk-utility gnome-screenshot
4585 gnome-search-tool gnome-session-canberra gnome-spell
4586 gnome-system-log gnome-themes-extras gnome-themes-more
4587 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
4588 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
4589 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
4590 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
4591 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
4592 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
4593 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
4594 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
4595 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
4596 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
4597 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
4598 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
4599 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
4600 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
4601 libgtk2.0-cil libgtkglext1 libgtksourceview-common
4602 libgtksourceview2.0-common libmono-addins-gui0.2-cil
4603 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
4604 libmono-i18n-west2.0-cil libmono-posix2.0-cil
4605 libmono-security2.0-cil libmono-sharpzip2.84-cil
4606 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
4607 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
4608 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
4609 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
4610 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
4611 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
4612 libxalan2-java libxerces2-java media-player-info mesa-utils
4613 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
4614 nautilus-sendto-empathy openoffice.org-writer2latex
4615 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
4616 python-aptdaemon python-aptdaemon-gtk python-axiom
4617 python-beautifulsoup python-bugbuddy python-clientform
4618 python-coherence python-configobj python-crypto python-cupshelpers
4619 python-cupsutils python-eggtrayicon python-elementtree
4620 python-epsilon python-evolution python-feedparser python-gdata
4621 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
4622 python-gtksourceview2 python-httplib2 python-louie python-mako
4623 python-markupsafe python-mechanize python-nevow python-notify
4624 python-opengl python-openssl python-pam python-pkg-resources
4625 python-pyasn1 python-pysqlite2 python-rdflib python-serial
4626 python-tagpy python-twisted-bin python-twisted-conch
4627 python-twisted-core python-twisted-web python-utidylib python-webkit
4628 python-xdg python-zope.interface remmina remmina-plugin-data
4629 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
4630 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
4631 software-center svgalibg1 system-config-printer-udev
4632 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
4633 totem totem-coherence totem-mozilla totem-plugins
4634 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
4635 zip
4636 &lt;/p&gt;&lt;/blockquote&gt;
4637
4638 Installed using apt-get, removed with aptitude
4639
4640 &lt;blockquote&gt;&lt;p&gt;
4641 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
4642 epiphany-extensions epiphany-gecko evolution-exchange
4643 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
4644 gedit-common gnome-app-install gnome-games gnome-games-data
4645 gnome-nettool gnome-system-tools gnome-themes gnome-utils
4646 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
4647 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
4648 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
4649 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
4650 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
4651 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
4652 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
4653 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
4654 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
4655 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
4656 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
4657 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
4658 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
4659 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
4660 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
4661 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
4662 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
4663 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
4664 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
4665 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
4666 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
4667 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
4668 sound-juicer swfdec-gnome system-config-printer totem-common
4669 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
4670 &lt;/p&gt;&lt;/blockquote&gt;
4671
4672 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4673
4674 &lt;blockquote&gt;&lt;p&gt;
4675 gstreamer0.10-gnomevfs
4676 &lt;/p&gt;&lt;/blockquote&gt;
4677
4678 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4679
4680 &lt;blockquote&gt;&lt;p&gt;
4681 [nothing]
4682 &lt;/p&gt;&lt;/blockquote&gt;
4683
4684 &lt;p&gt;This is for KDE:&lt;/p&gt;
4685
4686 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4687
4688 &lt;blockquote&gt;&lt;p&gt;
4689 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
4690 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
4691 ghostscript-x git gnome-audio gnugo granatier gs-common
4692 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
4693 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
4694 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
4695 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
4696 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
4697 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
4698 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
4699 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
4700 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
4701 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
4702 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
4703 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
4704 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
4705 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
4706 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
4707 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
4708 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
4709 libkrossui4 libmailtools-perl libmime-tools-perl
4710 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
4711 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
4712 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
4713 lirc luatex marble networkstatus noatun-plugins
4714 openoffice.org-writer2latex palapeli palapeli-data parley
4715 parley-data poster psutils pulseaudio pulseaudio-esound-compat
4716 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
4717 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
4718 ttf-sazanami-gothic
4719 &lt;/p&gt;&lt;/blockquote&gt;
4720
4721 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4722
4723 &lt;blockquote&gt;&lt;p&gt;
4724 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
4725 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
4726 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
4727 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
4728 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
4729 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
4730 kitchensync kiten kjumpingcube klatin klettres klickety klines
4731 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
4732 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
4733 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
4734 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
4735 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
4736 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
4737 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
4738 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
4739 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
4740 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
4741 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
4742 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
4743 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
4744 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
4745 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
4746 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
4747 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
4748 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
4749 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
4750 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
4751 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
4752 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
4753 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
4754 mpeglib network-manager-kde noatun pmount tex-common texlive-base
4755 texlive-common texlive-doc-base texlive-fonts-recommended tidy
4756 ttf-dustin ttf-kochi-gothic ttf-sjfonts
4757 &lt;/p&gt;&lt;/blockquote&gt;
4758
4759 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4760
4761 &lt;blockquote&gt;&lt;p&gt;
4762 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
4763 kdeartwork kdebase kdebase-apps kdebase-workspace
4764 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
4765 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
4766 netpbm plasma-widget-folderview plasma-widget-networkmanagement
4767 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
4768 xscreensaver-screensaver-bsod
4769 &lt;/p&gt;&lt;/blockquote&gt;
4770
4771 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4772
4773 &lt;blockquote&gt;&lt;p&gt;
4774 kdebase-bin konq-plugins konqueror
4775 &lt;/p&gt;&lt;/blockquote&gt;
4776 </description>
4777 </item>
4778
4779 <item>
4780 <title>Gnash buildbot slave and Debian kfreebsd</title>
4781 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
4782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
4783 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
4784 <description>&lt;p&gt;Answering
4785 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
4786 call from the Gnash project&lt;/a&gt; for
4787 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
4788 current source, I have set up a virtual KVM machine on the Debian
4789 Edu/Skolelinux virtualization host to test the git source on
4790 Debian/Squeeze. I hope this can help the developers in getting new
4791 releases out more often.&lt;/p&gt;
4792
4793 &lt;p&gt;As the developers want less main-stream build platforms tested to,
4794 I have considered setting up a &lt;a
4795 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
4796 machine as well. I have also considered using the kfreebsd
4797 architecture in Debian as a file server in NUUG to get access to the 5
4798 TB zfs volume we currently use to store DV video. Because of this, I
4799 finally got around to do a test installation of Debian/Squeeze with
4800 kfreebsd. Installation went fairly smooth, thought I noticed some
4801 visual glitches in the cdebconf dialogs (black cursor left on the
4802 screen at random locations). Have not gotten very far with the
4803 testing. Noticed cfdisk did not work, but fdisk did so it was not a
4804 fatal problem. Have to spend some more time on it to see if it is
4805 useful as a file server for NUUG. Will try to find time to set up a
4806 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
4807 </description>
4808 </item>
4809
4810 <item>
4811 <title>Debian in 3D</title>
4812 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
4813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
4814 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
4815 <description>&lt;p&gt;&lt;img src=&quot;http://thingiverse-production.s3.amazonaws.com/renders/23/e0/c4/f9/2b/debswagtdose_preview_medium.jpg&quot;&gt;&lt;/p&gt;
4816
4817 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
4818 3D linked in from
4819 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
4820 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
4821 </description>
4822 </item>
4823
4824 <item>
4825 <title>Software updates 2010-10-24</title>
4826 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
4827 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
4828 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
4829 <description>&lt;p&gt;Some updates.&lt;/p&gt;
4830
4831 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
4832 raise money for the project is going well. The lower limit of 10
4833 signers was reached in 24 hours, and so far 13 people have signed it.
4834 More signers and more funding is most welcome, and I am really curious
4835 how far we can get before the time limit of December 24 is reached.
4836 :)&lt;/p&gt;
4837
4838 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
4839 about what appear to be a great code coverage tool capable of
4840 generating code coverage stats without any changes to the source code.
4841 It is called
4842 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
4843 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
4844 It is missing in Debian, but the git source built just fine in Squeeze
4845 after I installed libelf-dev, libdwarf-dev, pkg-config and
4846 libglib2.0-dev. Failed to build in Lenny, but suspect that is
4847 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
4848
4849 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
4850 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
4851 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
4852 alpha test release of the Squeeze based Debian Edu /
4853 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
4854 release. Give it a try if you need a complete linux solution for your
4855 school, including central infrastructure server, workstations, thin
4856 client servers and diskless workstations. A nice touch added
4857 yesterday is RDP support on the thin client servers, for windows
4858 clients to get a Linux desktop on request.&lt;/p&gt;
4859 </description>
4860 </item>
4861
4862 <item>
4863 <title>Some notes on Flash in Debian and Debian Edu</title>
4864 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
4865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
4866 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
4867 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
4868 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
4869 second most popular used package that is missing in Debian. The sixth
4870 most popular is flashplayer-mozilla. This is a clear indication that
4871 working flash is important for Debian users. Around 10 percent of the
4872 users submitting data to popcon.debian.org have this package
4873 installed.&lt;/p&gt;
4874
4875 &lt;p&gt;In the report written by Lars Risan in August 2008
4876&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
4877 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
4878 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
4879 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4880 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
4881 web sites require Flash to work, and lacking working Flash support in
4882 the web browser and the problems with installing it was perceived as a
4883 good reason to stay with Windows.&lt;/p&gt;
4884
4885 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
4886 said to be the retarded cousin that did not really understand
4887 everything you told him but could work fairly well. This was a
4888 comment regarding the problems Linux have with proprietary formats and
4889 non-standard web pages, and is sad because it exposes a fairly common
4890 understanding of whose fault it is if web pages that only work in for
4891 example Internet Explorer 6 fail to work on Firefox, and funny because
4892 it explain very well how annoying it is for users when Linux
4893 distributions do not work with the documents they receive or the web
4894 pages they want to visit.&lt;/p&gt;
4895
4896 &lt;p&gt;This is part of the reason why I believe it is important for Debian
4897 and Debian Edu to have a well working Flash implementation in the
4898 distribution, to get at least popular sites as Youtube and Google
4899 Video to working out of the box. For Squeeze, Debian have the chance
4900 to include the latest version of Gnash that will make this happen, as
4901 the new release 0.8.8 was published a few weeks ago and is resting in
4902 unstable. The new version work with more sites that version 0.8.7.
4903 The Gnash maintainers have asked for a freeze exception, but the
4904 release team have not had time to reply to it yet. I hope they agree
4905 with me that Flash is important for the Debian desktop users, and thus
4906 accept the new package into Squeeze.&lt;/p&gt;
4907 </description>
4908 </item>
4909
4910 <item>
4911 <title>Circular package dependencies harms apt recovery</title>
4912 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
4913 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
4914 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
4915 <description>&lt;p&gt;I discovered this while doing
4916 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
4917 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
4918 in Debian still got circular dependencies, and it is often claimed
4919 that apt and aptitude should be able to handle this just fine, but
4920 some times these dependency loops causes apt to fail.&lt;/p&gt;
4921
4922 &lt;p&gt;An example is from todays
4923 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
4924 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
4925 causes perl-modules to fail to upgrade. The cause is simple. If a
4926 package fail to unpack, then only part of packages with the circular
4927 dependency might end up being unpacked when unpacking aborts, and the
4928 ones already unpacked will fail to configure in the recovery phase
4929 because its dependencies are unavailable.&lt;/p&gt;
4930
4931 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
4932
4933 &lt;blockquote&gt;&lt;pre&gt;
4934 dpkg: dependency problems prevent configuration of perl-modules:
4935 perl-modules depends on perl (&gt;= 5.10.1-1); however:
4936 Version of perl on system is 5.10.0-19lenny2.
4937 dpkg: error processing perl-modules (--configure):
4938 dependency problems - leaving unconfigured
4939 &lt;/pre&gt;&lt;/blockquote&gt;
4940
4941 &lt;p&gt;The perl/perl-modules circular dependency is already
4942 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
4943 hopefully be solved as soon as possible, but it is not the only one,
4944 and each one of these loops in the dependency tree can cause similar
4945 failures. Of course, they only occur when there are bugs in other
4946 packages causing the unpacking to fail, but it is rather nasty when
4947 the failure of one package causes the problem to become worse because
4948 of dependency loops.&lt;/p&gt;
4949
4950 &lt;p&gt;Thanks to
4951 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
4952 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
4953 dependencies
4954 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
4955 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
4956
4957 &lt;p&gt;Todays testing also exposed a bug in
4958 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
4959 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
4960 apt-get and aptitude, the latter possibly caused by some circular
4961 dependency. Reported both to BTS to try to get someone to look at
4962 it.&lt;/p&gt;
4963 </description>
4964 </item>
4965
4966 <item>
4967 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
4968 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
4969 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
4970 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
4971 <description>&lt;p&gt;This is a
4972 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;followup&lt;/a&gt;
4973 on my
4974 &lt;a href=&quot;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&quot;&gt;previous
4975 work&lt;/a&gt; on
4976 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
4977 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
4978
4979 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
4980 LDAP objects, I have had a look at how the packages pdns-backend-ldap
4981 and dhcp3-server-ldap in Debian use the LDAP server. The two
4982 implementations are quite different in how they use LDAP.&lt;/p&gt;
4983
4984 To get this information, I started slapd with debugging enabled and
4985 dumped the debug output to a file to get the LDAP searches performed
4986 on a Debian Edu main-server. Here is a summary.
4987
4988 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
4989
4990 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
4991 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
4992 the web.
4993
4994 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
4995 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
4996 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
4997 reverse entries are in two different subtrees in LDAP with a structure
4998 based on the DNS names, as in tjener.intern and
4999 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5000
5001 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5002 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5003 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5004 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5005 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5006 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5007 forward entries, it is looking for attributes named dnsttl, arecord,
5008 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5009 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5010 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5011 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5012 spfrecord and modifytimestamp. For reverse entries it is looking for
5013 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5014 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5015 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5016 ldapsearch commands could look like this:&lt;/p&gt;
5017
5018 &lt;blockquote&gt;&lt;pre&gt;
5019 ldapsearch -h ldap \
5020 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5021 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5022 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5023 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5024 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5025 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5026
5027 ldapsearch -h ldap \
5028 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5029 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5030 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5031 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5032 srvrecord naptrrecord modifytimestamp
5033 &lt;/pre&gt;&lt;/blockquote&gt;
5034
5035 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5036 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5037 example LDAP objects used there. In addition to these objects, the
5038 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5039 also exist.&lt;/p&gt;
5040
5041 &lt;blockquote&gt;&lt;pre&gt;
5042 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5043 objectclass: top
5044 objectclass: dnsdomain
5045 objectclass: domainrelatedobject
5046 dc: tjener
5047 arecord: 10.0.2.2
5048 associateddomain: tjener.intern
5049
5050 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5051 objectclass: top
5052 objectclass: dnsdomain2
5053 objectclass: domainrelatedobject
5054 dc: 2
5055 ptrrecord: tjener.intern
5056 associateddomain: 2.2.0.10.in-addr.arpa
5057 &lt;/pre&gt;&lt;/blockquote&gt;
5058
5059 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5060 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5061 same base as in the tree mode for a object with filter
5062 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5063 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5064 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5065 naptrrecord and modifytimestamp. For reverse entires it also do a
5066 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5067 and the requested attributes are associateddomain, dnsttl and
5068 modifytimestamp. In short, in strict mode the objects with ptrrecord
5069 go away, and the arecord attribute in the forward object is used
5070 instead.&lt;/p&gt;
5071
5072 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5073 like this:&lt;/p&gt;
5074
5075 &lt;blockquote&gt;&lt;pre&gt;
5076 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5077 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5078 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5079 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5080 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5081 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5082
5083 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5084 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5085 &lt;/pre&gt;&lt;/blockquote&gt;
5086
5087 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5088 search for SOA records, which behave similar to the forward and
5089 reverse lookups.&lt;/p&gt;
5090
5091 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5092 specify any objectclass names, and instead look for the attributes it
5093 need to generate a DNS reply. This make it able to work with any
5094 objectclass that provide the needed attributes.&lt;/p&gt;
5095
5096 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5097 dnsdomain2 schemas. The latter is used for reverse entries like
5098 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5099
5100 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5101 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5102 attributes) and domainrelatedobject (for associatedDomain). The use
5103 of structural object classes make it impossible to combine these
5104 classes with the object classes used by DHCP.&lt;/p&gt;
5105
5106 &lt;p&gt;There are other schemas that could be used too, for example the
5107 dnszone structural object class used by Gosa and bind-sdb for the DNS
5108 attributes combined with the domainrelatedobject object class, but in
5109 this case some unused attributes would have to be included as well
5110 (zonename and relativedomainname).&lt;/p&gt;
5111
5112 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5113 mode and not use any of the existing objectclasses (dnsdomain,
5114 dnsdomain2 and dnszone) when one want to combine the DNS information
5115 with DHCP information, and instead create a auxiliary object class
5116 defined something like this (using the attributes defined for
5117 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5118
5119 &lt;blockquote&gt;&lt;pre&gt;
5120 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5121 SUP top
5122 AUXILIARY
5123 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5124 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5125 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5126 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5127 A6Record $ DNAMERecord
5128 ))
5129 &lt;/pre&gt;&lt;/blockquote&gt;
5130
5131 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5132 the domainrelatedobject object class, and allow any entity to include
5133 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5134 developers asking for their view on this schema and if they are
5135 interested in providing such schema with PowerDNS, and I hope my
5136 message will be accepted into their mailing list soon.&lt;/p&gt;
5137
5138 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5139
5140 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5141 the object attributes, and then uses the attributes it want. This
5142 make it harder to figure out exactly what attributes are used, but
5143 thanks to the working example in Debian Edu I can at least get an idea
5144 what is needed without having to read the source code.&lt;/p&gt;
5145
5146 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5147 search filter to use to locate the correct dhcpServer entity is
5148 stored. These are the relevant entries from
5149 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5150
5151 &lt;blockquote&gt;&lt;pre&gt;
5152 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5153 ldap-dhcp-server-cn &quot;dhcp&quot;;
5154 &lt;/pre&gt;&lt;/blockquote&gt;
5155
5156 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5157 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5158 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5159 search result is this entry:&lt;/p&gt;
5160
5161 &lt;blockquote&gt;&lt;pre&gt;
5162 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5163 cn: dhcp
5164 objectClass: top
5165 objectClass: dhcpServer
5166 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5167 &lt;/pre&gt;&lt;/blockquote&gt;
5168
5169 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5170 subtree with DHCP configuration. The DHCP configuration subtree base
5171 is located using a base scope search with base &quot;cn=DHCP
5172 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5173 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5174 The search result is this entry:&lt;/p&gt;
5175
5176 &lt;blockquote&gt;&lt;pre&gt;
5177 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5178 cn: DHCP Config
5179 objectClass: top
5180 objectClass: dhcpService
5181 objectClass: dhcpOptions
5182 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5183 dhcpStatements: ddns-update-style none
5184 dhcpStatements: authoritative
5185 dhcpOption: smtp-server code 69 = array of ip-address
5186 dhcpOption: www-server code 72 = array of ip-address
5187 dhcpOption: wpad-url code 252 = text
5188 &lt;/pre&gt;&lt;/blockquote&gt;
5189
5190 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5191 all the DHCP configuration is loaded, it is ready to receive requests.
5192 The subtree in Debian Edu contain objects with object classes
5193 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5194 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5195 and information about netmasks, dynamic range etc. Leaving out the
5196 details here because it is not relevant for the focus of my
5197 investigation, which is to see if it is possible to merge dns and dhcp
5198 related computer objects.&lt;/p&gt;
5199
5200 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5201 of the client (00:00:00:00:00:00 in this example), using a subtree
5202 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5203 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5204 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5205 like:&lt;/p&gt;
5206
5207 &lt;blockquote&gt;&lt;pre&gt;
5208 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5209 cn: hostname
5210 objectClass: top
5211 objectClass: dhcpHost
5212 dhcpHWAddress: ethernet 00:00:00:00:00:00
5213 dhcpStatements: fixed-address hostname
5214 &lt;/pre&gt;&lt;/blockquote&gt;
5215
5216 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5217 The object classes need to have fixed names, and the configuration
5218 need to be stored in a fairly specific LDAP structure. On the
5219 positive side, the invidiual dhcpHost entires can be anywhere without
5220 the DN pointed to by the dhcpServer entries. The latter should make
5221 it possible to group all host entries in a subtree next to the
5222 configuration entries, and this subtree can also be shared with the
5223 DNS server if the schema proposed above is combined with the dhcpHost
5224 structural object class.
5225
5226 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5227
5228 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5229 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5230 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5231 allowing DNS objects to be stored anywhere under the base cn specified
5232 in the configuration.&lt;/p&gt;
5233
5234 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5235 regarding which LDAP schemas to use and which LDAP structure to use.
5236 I guess one could implement ones own schema, as long as the
5237 objectclasses and attributes have the names used, but this do not
5238 really help when the DHCP subtree need to have a fairly fixed
5239 structure.&lt;/p&gt;
5240
5241 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5242 this might work for Debian Edu:&lt;/p&gt;
5243
5244 &lt;blockquote&gt;&lt;pre&gt;
5245 ou=services
5246 cn=machine-info (dhcpService) - dhcpServiceDN points here
5247 cn=dhcp (dhcpServer)
5248 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5249 cn=10.0.2.0 (dhcpSubnet)
5250 cn=group1 (dhcpGroup/dhcpOptions)
5251 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5252 cn=192.168.0.0 (dhcpSubnet)
5253 cn=group1 (dhcpGroup/dhcpOptions)
5254 ou=machines - PowerDNS base points here
5255 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5256 &lt;/pre&gt;&lt;/blockquote&gt;
5257
5258 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5259 entries to be in the dhcpGroup subtrees, the entries can be stored
5260 there instead of a common machines subtree, and the PowerDNS base
5261 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
5262
5263 &lt;p&gt;The combined object under the machines subtree would look something
5264 like this:&lt;/p&gt;
5265
5266 &lt;blockquote&gt;&lt;pre&gt;
5267 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5268 dc: hostname
5269 objectClass: top
5270 objectClass: dhcpHost
5271 objectclass: domainrelatedobject
5272 objectclass: dnsDomainAux
5273 associateddomain: hostname.intern
5274 arecord: 10.11.12.13
5275 dhcpHWAddress: ethernet 00:00:00:00:00:00
5276 dhcpStatements: fixed-address hostname.intern
5277 &lt;/pre&gt;&lt;/blockquote&gt;
5278
5279 &lt;/p&gt;One could even add the LTSP configuration associated with a given
5280 machine, as long as the required attributes are available in a
5281 auxiliary object class.&lt;/p&gt;
5282 </description>
5283 </item>
5284
5285 <item>
5286 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
5287 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
5288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
5289 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
5290 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
5291 DHCP services in Debian Edu to use the same LDAP objects for a given
5292 computer, to avoid the possibility of having a inconsistent state for
5293 a computer in LDAP (as in DHCP but no DNS entry or the other way
5294 around) and make it easier to add computers to LDAP.&lt;/p&gt;
5295
5296 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
5297 information finally found a solution that seem to work.&lt;/p&gt;
5298
5299 &lt;p&gt;The old setup required three LDAP objects for a given computer.
5300 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5301 we switch powerdns to use its strict LDAP method (ldap-method=strict
5302 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5303 merged into one while making it impossible to transfer the reverse map
5304 to a slave DNS server.&lt;/p&gt;
5305
5306 &lt;p&gt;If we also replace the object class used to get the DNS related
5307 attributes to one allowing these attributes to be combined with the
5308 dhcphost object class, we can merge the DNS and DHCP entries into one.
5309 I&#39;ve written such object class in the dnsdomainaux.schema file (need
5310 proper OIDs, but that is a minor issue), and tested the setup. It
5311 seem to work.&lt;/p&gt;
5312
5313 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
5314 for both DNS and DHCP, and even the LTSP configuration I suggested in
5315 an earlier email. The combined LDAP object will look something like
5316 this:&lt;/p&gt;
5317
5318 &lt;blockquote&gt;&lt;pre&gt;
5319 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5320 cn: hostname
5321 objectClass: dhcphost
5322 objectclass: domainrelatedobject
5323 objectclass: dnsdomainaux
5324 associateddomain: hostname.intern
5325 arecord: 10.11.12.13
5326 dhcphwaddress: ethernet 00:00:00:00:00:00
5327 dhcpstatements: fixed-address hostname
5328 ldapconfigsound: Y
5329 &lt;/pre&gt;&lt;/blockquote&gt;
5330
5331 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
5332 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5333 before asking DNS to resolve the fixed-adddress. LTSP will use
5334 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
5335
5336 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
5337 dhcphost in a different location, to allow us to put the objects
5338 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
5339 that. If I can&#39;t figure out a way to do that, we can still get rid of
5340 the hosts subtree and move all its content into the DHCP Config tree
5341 (which probably should be renamed to be more related to the new
5342 content. I suspect cn=dnsdhcp,ou=services or something like that
5343 might be a good place to put it.&lt;/p&gt;
5344
5345 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5346 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5347 </description>
5348 </item>
5349
5350 <item>
5351 <title>Idea for storing LTSP configuration in LDAP</title>
5352 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
5353 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
5354 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
5355 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
5356 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5357 clients, and that this can be used to fetch configuration from LDAP if
5358 Debian Edu choose to store configuration there.&lt;/p&gt;
5359
5360 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
5361 to get configuration from LDAP. The idea is to look up the MAC
5362 address of the client in LDAP, and look for attributes on the form
5363 ltspconfigsetting=value, and use this to export SETTING=value to the
5364 LTSP clients.&lt;/p&gt;
5365
5366 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
5367 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
5368 allowing us to store all information about a computer in one place.&lt;/p&gt;
5369
5370 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
5371 this approach. A real LDAP schema for the ltspClientAux objectclass
5372 need to be written. Comments, suggestions, etc?&lt;/p&gt;
5373
5374 &lt;blockquote&gt;&lt;pre&gt;
5375 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5376 #
5377 # Fetch LTSP client settings from LDAP based on MAC address
5378 #
5379 # Uses ethernet address as stored in the dhcpHost objectclass using
5380 # the dhcpHWAddress attribute or ethernet address stored in the
5381 # ieee802Device objectclass with the macAddress attribute.
5382 #
5383 # This module is written to be schema agnostic, and only depend on the
5384 # existence of attribute names.
5385 #
5386 # The LTSP configuration variables are saved directly using a
5387 # ltspConfig prefix and uppercasing the rest of the attribute name.
5388 # To set the SERVER variable, set the ltspConfigServer attribute.
5389 #
5390 # Some LDAP schema should be created with all the relevant
5391 # configuration settings. Something like this should work:
5392 #
5393 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
5394 # SUP top
5395 # AUXILIARY
5396 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5397
5398 LDAPSERVER=$(debian-edu-ldapserver)
5399 if [ &quot;$LDAPSERVER&quot; ] ; then
5400 LDAPBASE=$(debian-edu-ldapserver -b)
5401 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
5402 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
5403 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
5404 grep &#39;^ltspConfig&#39; | while read attr value ; do
5405 # Remove prefix and convert to upper case
5406 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
5407 # bass value on to clients
5408 eval &quot;$attr=$value; export $attr&quot;
5409 done
5410 done
5411 fi
5412 &lt;/pre&gt;&lt;/blockquote&gt;
5413
5414 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
5415 the while block might end up in a subshell causing the variables set
5416 there to not show up in ltsp-config, but if that is the case I am sure
5417 the code can be restructured to make sure the variables are passed on.
5418 I expect that can be solved with some testing. :)&lt;/p&gt;
5419
5420 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5421 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5422
5423 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
5424 configuration in LDAP that was created around year 2000 by
5425 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
5426 Xperience, Inc., 2000&lt;/a&gt;. I found its
5427 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
5428 personal home page over at redhat.com.&lt;/p&gt;
5429 </description>
5430 </item>
5431
5432 <item>
5433 <title>jXplorer, a very nice LDAP GUI</title>
5434 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
5435 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
5436 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
5437 <description>&lt;p&gt;Since
5438 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
5439 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
5440 LDAP GUI that is even better than luma. The java application
5441 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
5442 moving LDAP objects and subtrees using drag-and-drop, and can
5443 authenticate using Kerberos. I have only tested the Kerberos
5444 authentication, but do not have a LDAP setup allowing me to rewrite
5445 LDAP with my test user yet. It is
5446 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
5447 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
5448 have with it is how it handle errors. If something go wrong, its
5449 non-intuitive behaviour require me to go through some query work list
5450 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
5451 </description>
5452 </item>
5453
5454 <item>
5455 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
5456 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
5457 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
5458 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
5459 <description>&lt;p&gt;Here is a short update on my &lt;a
5460 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
5461 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
5462 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
5463 not reporting the status for KDE, because the upgrade crashes when
5464 aptitude try because of missing conflicts
5465 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
5466 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
5467
5468 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
5469 complete list of the installed packages. Based on this I see these
5470 differences when I did a test run today. As usual, I do not really
5471 know what the correct set of packages would be, but thought it best to
5472 publish the difference.&lt;/p&gt;
5473
5474 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5475
5476 &lt;blockquote&gt;&lt;p&gt;
5477 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
5478 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
5479 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
5480 libgtksourceview-common libpt-1.10.10-plugins-alsa
5481 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
5482 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
5483 python-4suite-xml python-eggtrayicon python-gtkhtml2
5484 python-gtkmozembed svgalibg1 xserver-xephyr zip
5485 &lt;/p&gt;&lt;/blockquote&gt;
5486
5487 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5488
5489 &lt;blockquote&gt;&lt;p&gt;
5490 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
5491 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
5492 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
5493 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
5494 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
5495 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
5496 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5497 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5498 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5499 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
5500 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
5501 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
5502 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
5503 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
5504 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
5505 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
5506 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
5507 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
5508 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
5509 mysql-common swfdec-gnome totem-gstreamer wodim
5510 &lt;/p&gt;&lt;/blockquote&gt;
5511
5512 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5513
5514 &lt;blockquote&gt;&lt;p&gt;
5515 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
5516 python-gnomekeyring python-wnck rhythmbox-plugins xorg
5517 xserver-xorg-input-all xserver-xorg-input-evdev
5518 xserver-xorg-input-kbd xserver-xorg-input-mouse
5519 xserver-xorg-input-synaptics xserver-xorg-video-all
5520 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
5521 xserver-xorg-video-chips xserver-xorg-video-cirrus
5522 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5523 xserver-xorg-video-glint xserver-xorg-video-i128
5524 xserver-xorg-video-i740 xserver-xorg-video-mach64
5525 xserver-xorg-video-mga xserver-xorg-video-neomagic
5526 xserver-xorg-video-nouveau xserver-xorg-video-nv
5527 xserver-xorg-video-r128 xserver-xorg-video-radeon
5528 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
5529 xserver-xorg-video-s3 xserver-xorg-video-s3virge
5530 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
5531 xserver-xorg-video-sis xserver-xorg-video-sisusb
5532 xserver-xorg-video-tdfx xserver-xorg-video-tga
5533 xserver-xorg-video-trident xserver-xorg-video-tseng
5534 xserver-xorg-video-vesa xserver-xorg-video-vmware
5535 xserver-xorg-video-voodoo
5536 &lt;/p&gt;&lt;/blockquote&gt;
5537
5538 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5539
5540 &lt;blockquote&gt;&lt;p&gt;
5541 deskbar-applet xserver-xorg xserver-xorg-core
5542 xserver-xorg-input-wacom xserver-xorg-video-intel
5543 xserver-xorg-video-openchrome
5544 &lt;/p&gt;&lt;/blockquote&gt;
5545
5546 &lt;p&gt;I was told on IRC that the xorg-xserver package was
5547 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
5548 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
5549 No idea when it hits Squeeze, but when it does I hope it will reduce
5550 the difference somewhat.
5551 </description>
5552 </item>
5553
5554 <item>
5555 <title>LUMA, a very nice LDAP GUI</title>
5556 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
5557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
5558 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
5559 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
5560 directory in Debian Edu, and in the process I started to miss a GUI
5561 tool to browse the LDAP tree. The only one I was able to find in
5562 Debian/Squeeze and Lenny is
5563 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
5564 be a great tool to get a overview of the current LDAP directory
5565 populated by default in Skolelinux. Thanks to it, I have been able to
5566 find empty and obsolete subtrees, misplaced objects and duplicate
5567 objects. It will be installed by default in Debian/Squeeze. If you
5568 are working with LDAP, give it a go. :)&lt;/p&gt;
5569
5570 &lt;p&gt;I did notice one problem with it I have not had time to report to
5571 the BTS yet. There is no .desktop file in the package, so the tool do
5572 not show up in the Gnome and KDE menus, but only deep down in in the
5573 Debian submenu in KDE. I hope that can be fixed before Squeeze is
5574 released.&lt;/p&gt;
5575
5576 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
5577 like to move objects and remove subtrees directly in the GUI, but have
5578 not found a way to do that with LUMA yet. So in the mean time, I use
5579 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
5580
5581 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
5582 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5583
5584 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
5585 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
5586 useful GUI alternative. It seem like a good tool, but is unmaintained
5587 in Debian and got a RC bug keeping it out of Squeeze. Unless that
5588 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
5589 </description>
5590 </item>
5591
5592 <item>
5593 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
5594 <link>http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html</link>
5595 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html</guid>
5596 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
5597 <description>&lt;p&gt;A while back, I
5598 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
5599 about the fact&lt;/a&gt; that it is not possible with the provided schemas
5600 for storing DNS and DHCP information in LDAP to combine the two sets
5601 of information into one LDAP object representing a computer.&lt;/p&gt;
5602
5603 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
5604 the dhcpHost object class auxiliary, to allow it to be combined with
5605 the dNSDomain object class, and thus forming one object for one
5606 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
5607
5608 &lt;p&gt;If I understand this correctly, it is not safe to do this change
5609 without also changing the assigned number for the object class, and I
5610 do not know enough about LDAP schema design to do that properly for
5611 Debian Edu.&lt;/p&gt;
5612
5613 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
5614 the
5615 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
5616 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
5617 available today from IETF.&lt;/p&gt;
5618
5619 &lt;pre&gt;
5620 --- dhcp.schema (revision 65192)
5621 +++ dhcp.schema (working copy)
5622 @@ -376,7 +376,7 @@
5623 objectclass ( 2.16.840.1.113719.1.203.6.6
5624 NAME &#39;dhcpHost&#39;
5625 DESC &#39;This represents information about a particular client&#39;
5626 - SUP top
5627 + SUP top AUXILIARY
5628 MUST cn
5629 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
5630 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
5631 &lt;/pre&gt;
5632
5633 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
5634 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
5635 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
5636
5637 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5638 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5639 </description>
5640 </item>
5641
5642 <item>
5643 <title>Calling tasksel like the installer, while still getting useful output</title>
5644 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
5645 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
5646 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
5647 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
5648 installs packages during the normal debian-installer run. Until now,
5649 I have ended up letting tasksel do the work, with the annoying problem
5650 of not getting any feedback at all when something fails (like a
5651 conffile question from dpkg or a download that fails), using code like
5652 this:
5653
5654 &lt;blockquote&gt;&lt;pre&gt;
5655 export DEBIAN_FRONTEND=noninteractive
5656 tasksel --new-install
5657 &lt;/pre&gt;&lt;/blockquote&gt;
5658
5659 This would invoke tasksel, let its automatic task selection pick the
5660 tasks to install, and continue to install the requested tasks without
5661 any output what so ever.
5662
5663 Recently I revisited this problem while working on the automatic
5664 package upgrade testing, because tasksel would some times hang without
5665 any useful feedback, and I want to see what is going on when it
5666 happen. Then it occured to me, I can parse the output from tasksel
5667 when asked to run in test mode, and use that aptitude command line
5668 printed by tasksel then to simulate the tasksel run. I ended up using
5669 code like this:
5670
5671 &lt;blockquote&gt;&lt;pre&gt;
5672 export DEBIAN_FRONTEND=noninteractive
5673 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
5674 $cmd
5675 &lt;/pre&gt;&lt;/blockquote&gt;
5676
5677 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
5678 --without-recommends -o APT::Install-Recommends=no -y install
5679 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
5680 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
5681 laptop task and all packages with priority standard , required and
5682 important, just like tasksel would have done it during
5683 installation.&lt;/p&gt;
5684
5685 &lt;p&gt;A better approach is probably to extend tasksel to be able to
5686 install packages without using debconf-apt-progress, for use cases
5687 like this.&lt;/p&gt;
5688 </description>
5689 </item>
5690
5691 <item>
5692 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
5693 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
5694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
5695 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
5696 <description>&lt;p&gt;My
5697 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
5698 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
5699 finally made the upgrade logs available from
5700 &lt;a href=&quot;http://people.skolelinux.org/pere/debian-upgrade-testing/&quot;&gt;http://people.skolelinux.org/pere/debian-upgrade-testing/&lt;/a&gt;.
5701 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
5702 apt and aptitude, and found their differences interesting. This time
5703 I will only focus on their removal plans.&lt;/p&gt;
5704
5705 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
5706 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
5707 surprising part is that it want to remove xorg and all
5708 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
5709 sure why. When asking aptitude to do the same, it want to remove 129
5710 packages, but most of them are library packages I suspect are no
5711 longer needed. Both of them want to remove bluetooth packages, which
5712 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
5713
5714 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
5715 which seem like a bad idea and xorg the same way as with Gnome. Asking
5716 aptitude for the same, it wants to remove 192 packages, none which are
5717 too surprising.&lt;/p&gt;
5718
5719 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
5720 and avoided, and perhaps others as well. Here are the complete list
5721 of planned removals. The complete logs is available from the URL
5722 above. Note if you want to repeat these tests, that the upgrade test
5723 for kde+apt-get hung in the tasksel setup because of dpkg asking
5724 conffile questions. No idea why. I worked around it by using
5725 &#39;&lt;tt&gt;echo &gt;&gt; /proc/&lt;em&gt;pidofdpkg&lt;/em&gt;/fd/0&lt;/tt&gt;&#39; to tell dpkg to
5726 continue.&lt;/p&gt;
5727
5728 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
5729 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
5730 gnome-desktop-environment gnome-network-admin gtkhtml3.14
5731 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
5732 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
5733 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
5734 serpentine swfdec-mozilla update-manager xorg xserver-xorg
5735 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
5736 xserver-xorg-input-kbd xserver-xorg-input-mouse
5737 xserver-xorg-input-synaptics xserver-xorg-input-wacom
5738 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
5739 xserver-xorg-video-ati xserver-xorg-video-chips
5740 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
5741 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5742 xserver-xorg-video-glint xserver-xorg-video-i128
5743 xserver-xorg-video-i740 xserver-xorg-video-imstt
5744 xserver-xorg-video-intel xserver-xorg-video-mach64
5745 xserver-xorg-video-mga xserver-xorg-video-neomagic
5746 xserver-xorg-video-nsc xserver-xorg-video-nv
5747 xserver-xorg-video-openchrome xserver-xorg-video-r128
5748 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
5749 xserver-xorg-video-rendition xserver-xorg-video-s3
5750 xserver-xorg-video-s3virge xserver-xorg-video-savage
5751 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
5752 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
5753 xserver-xorg-video-tga xserver-xorg-video-trident
5754 xserver-xorg-video-tseng xserver-xorg-video-v4l
5755 xserver-xorg-video-vesa xserver-xorg-video-vga
5756 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
5757 xulrunner-1.9-gnome-support&lt;/p&gt;
5758
5759 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
5760
5761 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
5762 djvulibre-desktop finger gnome-app-install gnome-mount
5763 gnome-network-admin gnome-spell gnome-vfs-obexftp
5764 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
5765 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
5766 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
5767 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
5768 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
5769 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
5770 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
5771 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
5772 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
5773 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
5774 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
5775 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
5776 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
5777 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
5778 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
5779 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
5780 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
5781 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
5782 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
5783 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
5784 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
5785 openoffice.org-writer2latex openssl-blacklist p7zip
5786 python-4suite-xml python-eggtrayicon python-gnome2-desktop
5787 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
5788 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
5789 swfdec-mozilla totem-gstreamer update-manager wodim
5790 xserver-xorg-video-cyrix xserver-xorg-video-imstt
5791 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
5792 zip&lt;/p&gt;
5793
5794 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
5795
5796 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
5797 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
5798 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
5799 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
5800 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
5801 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
5802 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
5803 xserver-xorg-input-kbd xserver-xorg-input-mouse
5804 xserver-xorg-input-synaptics xserver-xorg-input-wacom
5805 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
5806 xserver-xorg-video-ati xserver-xorg-video-chips
5807 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
5808 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5809 xserver-xorg-video-glint xserver-xorg-video-i128
5810 xserver-xorg-video-i740 xserver-xorg-video-imstt
5811 xserver-xorg-video-intel xserver-xorg-video-mach64
5812 xserver-xorg-video-mga xserver-xorg-video-neomagic
5813 xserver-xorg-video-nsc xserver-xorg-video-nv
5814 xserver-xorg-video-openchrome xserver-xorg-video-r128
5815 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
5816 xserver-xorg-video-rendition xserver-xorg-video-s3
5817 xserver-xorg-video-s3virge xserver-xorg-video-savage
5818 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
5819 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
5820 xserver-xorg-video-tga xserver-xorg-video-trident
5821 xserver-xorg-video-tseng xserver-xorg-video-v4l
5822 xserver-xorg-video-vesa xserver-xorg-video-vga
5823 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
5824
5825 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
5826 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
5827 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
5828 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
5829 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
5830 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5831 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
5832 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
5833 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5834 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
5835 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
5836 kghostview khelpcenter khexedit kiconedit kitchensync klatin
5837 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
5838 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
5839 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
5840 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
5841 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
5842 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
5843 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5844 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
5845 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
5846 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5847 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
5848 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
5849 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
5850 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5851 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
5852 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
5853 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
5854 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
5855 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
5856 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
5857 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
5858 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
5859 texlive-common texlive-doc-base texlive-fonts-recommended
5860 xserver-xorg-video-cyrix xserver-xorg-video-imstt
5861 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
5862 xulrunner-1.9&lt;/p&gt;
5863
5864 </description>
5865 </item>
5866
5867 <item>
5868 <title>Automatic upgrade testing from Lenny to Squeeze</title>
5869 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
5870 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
5871 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
5872 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
5873 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
5874 have been discovered and reported in the process
5875 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
5876 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
5877 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
5878 kdebase-workspace-data), and to get a more regular testing going on, I
5879 am working on a script to automate the test.&lt;/p&gt;
5880
5881 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
5882 Gnome or KDE desktop installation inside the chroot before upgrading
5883 it. To ensure no services are started in the chroot, a policy-rc.d
5884 script is inserted. To make sure tasksel believe it is to install a
5885 desktop on a laptop, the tasksel tests are replaced in the chroot
5886 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
5887
5888 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
5889 currently always fail because udev refuses to upgrade with the kernel
5890 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
5891 is created. The bug report
5892 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
5893 this problem do not trigger in a chroot, but I touch the file anyway
5894 to make sure the upgrade go well. Testing on virtual and real
5895 hardware have failed me because of udev so far, and creating this file
5896 do the trick in such settings anyway. This is a
5897 &lt;a href=&quot;http://www.linuxquestions.org/questions/debian-26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-804130/&quot;&gt;known
5898 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
5899 maintainer because he lack the resources to rewrite udev to keep
5900 working with old kernels or something like that. I really wish the
5901 udev upstream would keep udev backwards compatible, to avoid such
5902 upgrade problem, but given that they fail to do so, I guess
5903 documenting the way out of this mess is the best option we got for
5904 Debian Squeeze.&lt;/p&gt;
5905
5906 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
5907 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
5908 trick:&lt;/p&gt;
5909
5910 &lt;blockquote&gt;&lt;pre&gt;
5911 #!/bin/sh
5912 set -ex
5913
5914 if [ &quot;$1&quot; ] ; then
5915 desktop=$1
5916 else
5917 desktop=gnome
5918 fi
5919
5920 from=lenny
5921 to=squeeze
5922
5923 exec &amp;lt; /dev/null
5924 unset LANG
5925 mirror=http://ftp.skolelinux.org/debian
5926 tmpdir=chroot-$from-upgrade-$to-$desktop
5927 fuser -mv .
5928 debootstrap $from $tmpdir $mirror
5929 chroot $tmpdir aptitude update
5930 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
5931 #!/bin/sh
5932 exit 101
5933 EOF
5934 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
5935 exit_cleanup() {
5936 umount $tmpdir/proc
5937 }
5938 mount -t proc proc $tmpdir/proc
5939 # Make sure proc is unmounted also on failure
5940 trap exit_cleanup EXIT INT
5941
5942 chroot $tmpdir aptitude -y install debconf-utils
5943
5944 # Make sure tasksel autoselection trigger. It need the test scripts
5945 # to return the correct answers.
5946 echo tasksel tasksel/desktop multiselect $desktop | \
5947 chroot $tmpdir debconf-set-selections
5948
5949 # Include the desktop and laptop task
5950 for test in desktop laptop ; do
5951 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
5952 #!/bin/sh
5953 exit 2
5954 EOF
5955 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
5956 done
5957
5958 DEBIAN_FRONTEND=noninteractive
5959 DEBIAN_PRIORITY=critical
5960 export DEBIAN_FRONTEND DEBIAN_PRIORITY
5961 chroot $tmpdir tasksel --new-install
5962
5963 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
5964 chroot $tmpdir aptitude update
5965 touch $tmpdir/etc/udev/kernel-upgrade
5966 chroot $tmpdir aptitude -y dist-upgrade
5967 fuser -mv
5968 &lt;/pre&gt;&lt;/blockquote&gt;
5969
5970 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
5971 with aptitude, but I have not had time to look at how they behave
5972 differently so far. I hope to get a cron job running to do the test
5973 regularly and post the result on the web. The Gnome upgrade currently
5974 work, while the KDE upgrade fail because of the bug in
5975 kdebase-workspace-data&lt;/p&gt;
5976
5977 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
5978 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
5979 post, so I will refrain from trying. I can report that for Gnome,
5980 aptitude report 760 packages upgraded, 448 newly installed, 129 to
5981 remove and 1 not upgraded and 1024MB need to be downloaded while for
5982 KDE the same numbers are 702 packages upgraded, 507 newly installed,
5983 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
5984
5985 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
5986 is able to migrate to dependency based boot sequencing and parallel
5987 booting without a hitch. Was unsure if there were still bugs with
5988 packages failing to clean up their obsolete init.d script during
5989 upgrades, and no such problem seem to affect the Gnome desktop+laptop
5990 packages.&lt;/p&gt;
5991 </description>
5992 </item>
5993
5994 <item>
5995 <title>Upstart or sysvinit - as init.d scripts see it</title>
5996 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
5997 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
5998 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
5999 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6000 scripts to migrate (some of) their operations to upstart job while
6001 keeping the init.d for hurd and kfreebsd. The packages with such
6002 needs will need a way to get their init.d scripts to behave
6003 differently when used with sysvinit and with upstart. Because of
6004 this, I had a look at the environment variables set when a init.d
6005 script is running under upstart, and when it is not.&lt;/p&gt;
6006
6007 &lt;p&gt;With upstart, I notice these environment variables are set when a
6008 script is started from rcS.d/ (ignoring some irrelevant ones like
6009 COLUMNS):&lt;/p&gt;
6010
6011 &lt;blockquote&gt;&lt;pre&gt;
6012 DEFAULT_RUNLEVEL=2
6013 previous=N
6014 PREVLEVEL=
6015 RUNLEVEL=
6016 runlevel=S
6017 UPSTART_EVENTS=startup
6018 UPSTART_INSTANCE=
6019 UPSTART_JOB=rc-sysinit
6020 &lt;/pre&gt;&lt;/blockquote&gt;
6021
6022 &lt;p&gt;With sysvinit, these environment variables are set for the same
6023 script.&lt;/p&gt;
6024
6025 &lt;blockquote&gt;&lt;pre&gt;
6026 INIT_VERSION=sysvinit-2.88
6027 previous=N
6028 PREVLEVEL=N
6029 RUNLEVEL=S
6030 runlevel=S
6031 &lt;/pre&gt;&lt;/blockquote&gt;
6032
6033 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6034 sysvinit are not set by upstart. Not sure if it is intentional or not
6035 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6036
6037 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6038 looking for the UPSTART_JOB environment variable seem to be a good
6039 choice.&lt;/p&gt;
6040 </description>
6041 </item>
6042
6043 <item>
6044 <title>A manual for standards wars...</title>
6045 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6047 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6048 <description>&lt;p&gt;Via the
6049 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6050 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6051 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6052 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6053 following the standards wars of today.&lt;/p&gt;
6054 </description>
6055 </item>
6056
6057 <item>
6058 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6059 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6061 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6062 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6063 to get a list of the machine types in use thanks to the DMI
6064 information extracted from each machine. The script to do so is
6065 included in the sitesummary package, and here is example output from
6066 the Skolelinux build servers:&lt;/p&gt;
6067
6068 &lt;blockquote&gt;&lt;pre&gt;
6069 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6070 vendor count
6071 Dell Computer Corporation 1
6072 PowerEdge 1750 1
6073 IBM 1
6074 eserver xSeries 345 -[8670M1X]- 1
6075 Intel 2
6076 [no-dmi-info] 3
6077 maintainer:~#
6078 &lt;/pre&gt;&lt;/blockquote&gt;
6079
6080 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6081 provided in each machine. Here there are Intel machines without model
6082 information listed with Intel as vendor and no model, and virtual Xen
6083 machines listed as [no-dmi-info]. One can add -l as a command line
6084 option to list the individual machines.&lt;/p&gt;
6085
6086 &lt;p&gt;A larger list is
6087 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6088 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6089 provide the basic sitesummary report publicly. In their report there
6090 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6091 their machines, and as sitesummary is available in both distributions,
6092 it is trivial to get all of them to report to the same central
6093 collector.&lt;/p&gt;
6094 </description>
6095 </item>
6096
6097 <item>
6098 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6099 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</guid>
6101 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6102 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6103 start at boot when an NVidia video card is used is handled. The
6104 problem seem to be that the nvidia X.org driver uses a long time to
6105 initialize, and this duration is longer than kdm is configured to
6106 wait.&lt;/p&gt;
6107
6108 &lt;p&gt;I came across two bugs related to this issue,
6109 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6110 against initscripts and passed on to nvidia-glx when it became obvious
6111 that the nvidia drivers were involved, and
6112 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6113 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6114
6115 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6116 problem nvidia video card owners experience and make sure the Debian
6117 distribution work out of the box for these users. The nvidia driver
6118 maintainers expect kdm to be set up to wait longer, while kdm expect
6119 the nvidia driver maintainers to fix the driver to start faster, and
6120 while they wait for each other I guess the users end up switching to a
6121 distribution that work for them. I have no idea what the solution is,
6122 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6123
6124 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6125 </description>
6126 </item>
6127
6128 <item>
6129 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6130 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6132 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6133 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6134 The feature seem to hold up pretty well, but three fairly serious
6135 issues are known and should be solved:
6136
6137 &lt;p&gt;&lt;ul&gt;
6138
6139 &lt;li&gt;The wicd package seen to
6140 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6141 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6142 parallel booting is enabled. No idea why, but the wicd maintainer
6143 seem to be on the case.&lt;/li&gt;
6144
6145 &lt;li&gt;The nvidia X driver seem to
6146 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6147 triggered more easily when parallel booting is in effect. The
6148 maintainer is on the case.&lt;/li&gt;
6149
6150 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6151 sequencing (the shutdown is broken) when old file-rc users
6152 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6153 sysv-rc. One way to solve it would be for file-rc to create
6154 /etc/init.d/.legacy-bootordering, and another is to try to make
6155 sysv-rc more robust. Will investigate some more and probably upload a
6156 workaround in sysv-rc to help those trying to move from file-rc to
6157 sysv-rc get a working shutdown.&lt;/li&gt;
6158
6159 &lt;/ul&gt;&lt;/p&gt;
6160
6161 &lt;p&gt;All in all not many surprising issues, and all of them seem
6162 solvable before Squeeze is released. In addition to these there are
6163 some packages with bugs in their dependencies and run level settings,
6164 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6165
6166 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6167 the BTS, please usertag the report to get it to show up at
6168 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6169 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6170
6171 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6172 </description>
6173 </item>
6174
6175 <item>
6176 <title>More flexible firmware handling in debian-installer</title>
6177 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6178 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6179 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6180 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6181 found time today to return to the project. Having to spend less time
6182 working dependency based boot in debian, as it is almost complete now,
6183 definitely helped freeing some time.&lt;/p&gt;
6184
6185 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6186 include some firmware packages on the Debian Edu CDs, those needed to
6187 get disk and network controllers working. Without having these
6188 firmware packages available during installation, it is impossible to
6189 install Debian Edu on the given machine, and because our target group
6190 are non-technical people, asking them to provide firmware packages on
6191 an external medium is a support pain. Initially, I expected it to be
6192 enough to include the firmware packages on the CD to get
6193 debian-installer to find and use them. This proved to be wrong.
6194 Next, I hoped it was enough to symlink the relevant firmware packages
6195 to some useful location on the CD (tried /cdrom/ and
6196 /cdrom/firmware/). This also proved to not work, and at this point I
6197 found time to look at the debian-installer code to figure out what was
6198 going to work.&lt;/p&gt;
6199
6200 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6201 look revealed that it would only look for firmware packages outside
6202 the installation media, so the CD was never checked for firmware
6203 packages. It would only check USB sticks, floppies and other
6204 &quot;external&quot; media devices. Today I changed it to also look in the
6205 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6206 solve the problem I ran into with Debian edu. I also changed it to
6207 look in /firmware/, to make sure the installer also find firmware
6208 provided in the initrd when booting the installer via PXE, to allow us
6209 to provide the same feature in the PXE setup included in Debian
6210 Edu.&lt;/p&gt;
6211
6212 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6213 activated without asking if the license is accepted, I extended
6214 hw-detect to look for preinst scripts in the firmware packages, and
6215 run these before activating the firmware during installation. The
6216 license question is asked using debconf in the preinst, so this should
6217 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6218
6219 &lt;p&gt;If you want to discuss the details of these features, please
6220 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6221 </description>
6222 </item>
6223
6224 <item>
6225 <title>Parallellized boot is now the default in Debian/unstable</title>
6226 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6227 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6228 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6229 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6230 Debian/unstable for machines using dependency based boot sequencing.
6231 Apparently the testing of concurrent booting has been wider than
6232 expected, if I am to believe the
6233 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6234 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6235 with the feature this weekend, to give us some time to detect any
6236 remaining problems before Squeeze is frozen. If serious problems are
6237 detected, it is simple to change the default back to sequential boot.
6238 The upload of the new sysvinit package also activate a new upstream
6239 version.&lt;/p&gt;
6240
6241 More information about
6242 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6243 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6244 currently possible to disable parallel booting when one run into
6245 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6246
6247 &lt;blockquote&gt;&lt;pre&gt;
6248 CONCURRENCY=none
6249 &lt;/pre&gt;&lt;/blockquote&gt;
6250
6251 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6252 the BTS, please usertag the report to get it to show up at
6253 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6254 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6255 </description>
6256 </item>
6257
6258 <item>
6259 <title>Sitesummary tip: Listing MAC address of all clients</title>
6260 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
6261 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
6262 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
6263 <description>&lt;p&gt;In the recent Debian Edu versions, the
6264 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
6265 system&lt;/a&gt; is used to keep track of the machines in the school
6266 network. Each machine will automatically report its status to the
6267 central server after boot and once per night. The network setup is
6268 also reported, and using this information it is possible to get the
6269 MAC address of all network interfaces in the machines. This is useful
6270 to update the DHCP configuration.&lt;/p&gt;
6271
6272 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
6273 ist all MAC addresses of all machines reporting to sitesummary. Run
6274 this on the collector host:&lt;/p&gt;
6275
6276 &lt;blockquote&gt;&lt;pre&gt;
6277 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
6278 &lt;/pre&gt;&lt;/blockquote&gt;
6279
6280 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
6281 line per machine and with space between the MAC addresses.&lt;/p&gt;
6282
6283 &lt;p&gt;To allow system administrators easier job at adding static DHCP
6284 addresses for hosts, it would be possible to extend this to fetch
6285 machine information from sitesummary and update the DHCP and DNS
6286 tables in LDAP using this information. Such tool is unfortunately not
6287 written yet.&lt;/p&gt;
6288 </description>
6289 </item>
6290
6291 <item>
6292 <title>systemd, an interesting alternative to upstart</title>
6293 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
6294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
6295 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
6296 <description>&lt;p&gt;The last few days a new boot system called
6297 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
6298 has been
6299 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
6300
6301 to the free software world. I have not yet had time to play around
6302 with it, but it seem to be a very interesting alternative to
6303 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
6304 a good alternative for Debian when we are able to switch to an event
6305 based boot system. Tollef is
6306 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
6307 systemd into Debian, and I look forward to seeing how well it work. I
6308 like the fact that systemd handles init.d scripts with dependency
6309 information natively, allowing them to run in parallel where upstart
6310 at the moment do not.&lt;/p&gt;
6311
6312 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
6313 platform support. It only work on recent Linux kernels, and also need
6314 some new kernel features enabled to function properly. This means
6315 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6316 system. Not sure how that will be handled if systemd proves to be the
6317 way forward.&lt;/p&gt;
6318
6319 &lt;p&gt;In the mean time, based on the
6320 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6321 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
6322 decided to enable full parallel booting as the default in Debian as
6323 soon as possible (probably this weekend or early next week), to see if
6324 there are any remaining serious bugs in the init.d dependencies. A
6325 new version of the sysvinit package implementing this change is
6326 already in experimental. If all go well, Squeeze will be released
6327 with parallel booting enabled by default.&lt;/p&gt;
6328 </description>
6329 </item>
6330
6331 <item>
6332 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
6333 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
6334 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
6335 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
6336 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
6337 complete, so complete that it is actually possible to run all the
6338 init.d scripts in parallell based on these dependencies. If you want
6339 to test your Squeeze system, make sure
6340 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6341 based boot sequencing&lt;/a&gt; is enabled, and add this line to
6342 /etc/default/rcS:&lt;/p&gt;
6343
6344 &lt;blockquote&gt;&lt;pre&gt;
6345 CONCURRENCY=makefile
6346 &lt;/pre&gt;&lt;/blockquote&gt;
6347
6348 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
6349 scripts in parallel using the dependency information stored in
6350 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6351 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6352 to try to start the kdm and gdm scripts as early as possible, and will
6353 start the facilities required by kdm or gdm as early as possible to
6354 make this happen.&lt;/p&gt;
6355
6356 &lt;p&gt;Give it a try, and see if you like the result. If some services
6357 fail to start properly, it is most likely because they have incomplete
6358 init.d script dependencies in their startup script (or some of their
6359 dependent scripts have incomplete dependencies). Report bugs and get
6360 the package maintainers to fix it. :)&lt;/p&gt;
6361
6362 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
6363 manage to get the init.d script dependencies complete and correct. I
6364 expect we will get there in Squeeze+1, if we get manage to test and
6365 fix the remaining issues.&lt;/p&gt;
6366
6367 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6368 the BTS, please usertag the report to get it to show up at
6369 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6370 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6371 </description>
6372 </item>
6373
6374 <item>
6375 <title>Debian has switched to dependency based boot sequencing</title>
6376 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
6377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
6378 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
6379 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
6380 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
6381 have been migrated to using dependency based boot sequencing. This
6382 conclude work me and others have been doing for the last three days.
6383 It feels great to see this finally part of the default Debian
6384 installation. Now we just need to weed out the last few problems that
6385 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
6386
6387 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
6388 fixing the more fundamental problem of handing the event based
6389 non-predictable kernel in the early boot.&lt;/p&gt;
6390 </description>
6391 </item>
6392
6393 <item>
6394 <title>Taking over sysvinit development</title>
6395 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
6396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
6397 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
6398 <description>&lt;p&gt;After several years of frustration with the lack of activity from
6399 the existing sysvinit upstream developer, I decided a few weeks ago to
6400 take over the package and become the new upstream. The number of
6401 patches to track for the Debian package was becoming a burden, and the
6402 lack of synchronization between the distribution made it hard to keep
6403 the package up to date.&lt;/p&gt;
6404
6405 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6406 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
6407 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
6408 and Fedora), based on the patches currently in use in these
6409 distributions. We Debian maintainers plan to move to this tarball as
6410 the new upstream as soon as we find time to do the merge. Since the
6411 new tarball was created, we agreed with Werner at SuSe to make a new
6412 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
6413 development there. The project is registered and currently waiting
6414 for approval by the Savannah administrators, and as soon as it is
6415 approved, we will import the old versions from svn and continue
6416 working on the future release.&lt;/p&gt;
6417
6418 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
6419 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
6420 </description>
6421 </item>
6422
6423 <item>
6424 <title>Debian boots quicker and quicker</title>
6425 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
6426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
6427 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
6428 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
6429 people involved in the boot system on Debian and Ubuntu, to see if we
6430 could find more ways to speed up the boot system. This was an Ubuntu
6431 funded
6432 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
6433 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
6434 of boot systems, and ways to handle the increasing number of boot
6435 issues introduced by the Linux kernel becoming more and more
6436 asynchronous and event base. The Ubuntu approach using udev and
6437 upstart might be a good way forward. Time will show.&lt;/p&gt;
6438
6439 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
6440 process in Debian. All of these should be applied to get a quick
6441 boot:&lt;/p&gt;
6442
6443 &lt;ul&gt;
6444
6445 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
6446
6447 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
6448 clock is in UTC.&lt;/li&gt;
6449
6450 &lt;li&gt;Install and activate the insserv package to enable
6451 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6452 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
6453
6454 &lt;/ul&gt;
6455
6456 These points are based on the Google summer of code work done by
6457 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
6458 Villegas&lt;/a&gt;.
6459
6460 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
6461 unstable yesterday. When we tested it, we were able to cut 6 seconds
6462 from the boot sequence. It depend on very correct dependency
6463 declaration in all init.d scripts, so I expect us to find edge cases
6464 where the dependences in some scripts are slightly wrong when we start
6465 using this.&lt;/p&gt;
6466
6467 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
6468 introduced by Raphael Geissert today, one that could affect the
6469 startup speed as well. Instead of starting some scripts concurrently
6470 from rcS.d/ and another set of scripts from rc2.d/, it would be
6471 possible to run a of them in the same process. A quick way to test
6472 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
6473 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
6474 </description>
6475 </item>
6476
6477 <item>
6478 <title>BSAs påstander om piratkopiering møter motstand</title>
6479 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
6480 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
6481 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
6482 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
6483 programvareselskapene som Microsoft og Apple, publisert en rapport der
6484 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
6485 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
6486 dager siden kom
6487 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
6488 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
6489 dagene. Et spesielt interessant kommentar fra Sverige,
6490 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
6491 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
6492
6493 &lt;blockquote&gt;
6494 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
6495 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
6496 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
6497 exakta&quot;, säger BSAs Sverigechef John Hugosson.
6498 &lt;/blockquote&gt;
6499
6500 &lt;p&gt;Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er &lt;a
6501 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
6502 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
6503 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
6504 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
6505
6506 &lt;p&gt;Fant lenkene via &lt;a
6507 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
6508 på Slashdot&lt;/a&gt;.&lt;/p&gt;
6509 </description>
6510 </item>
6511
6512 <item>
6513 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
6514 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
6515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
6516 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
6517 <description>&lt;p&gt;Kom over
6518 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
6519 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
6520 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
6521 jobber til daglig. En rask opptelling forteller meg at vi har 490
6522 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
6523 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
6524 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
6525 </description>
6526 </item>
6527
6528 <item>
6529 <title>Kryptert harddisk - naturligvis</title>
6530 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
6531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
6532 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
6533 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
6534 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
6535 når en tar tap av arbeidstid, fortrolige dokumenter,
6536 personopplysninger og alt annet det innebærer. Det er ingen tvil om
6537 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
6538 til at jeg har kryptert harddisken på både kontormaskinen og min
6539 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
6540 komme på avveie, den første informasjon relatert til jobben min ved
6541 Universitetet i Oslo, og den andre relatert til blant annet
6542 foreningsarbeide. Kryptering av diskene gjør at det er lite
6543 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
6544 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
6545 og en reboot vil gjøre at de ber om passord før de vil starte opp.
6546 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
6547 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
6548 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
6549 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
6550 det er gjort slik jeg gjør det er minimale, og gevinstene er
6551 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
6552 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
6553
6554 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
6555 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
6556 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
6557 er for min del høyere enn gevinsten. Jeg tror oddsene for at
6558 f.eks. etteretningsorganisasjoner har glede av å titte på mine
6559 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
6560 gjøre det vanskeligere for angripere med kompetanse og ressurser er
6561 betydelige.&lt;/p&gt;
6562 </description>
6563 </item>
6564
6565 <item>
6566 <title>Two projects that have improved the quality of free software a lot</title>
6567 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
6568 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
6569 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
6570 <description>&lt;p&gt;There are two software projects that have had huge influence on the
6571 quality of free software, and I wanted to mention both in case someone
6572 do not yet know them.&lt;/p&gt;
6573
6574 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
6575 tool to detect and expose errors in the memory handling of programs.
6576 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
6577 and it will report any problems on stdout. It is even better if the
6578 program include debug information. With debug information, it is able
6579 to report the source file name and line number where the problem
6580 occurs. It can report things like &#39;reading past memory block in file
6581 X line N, the memory block was allocated in file Y, line M&#39;, and
6582 &#39;using uninitialised value in control logic&#39;. This tool has made it
6583 trivial to investigate reproducible crash bugs in programs, and have
6584 reduced the number of this kind of bugs in free software a lot.
6585
6586 &lt;p&gt;The second one is
6587 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
6588 a source code checker. It is able to process the source of a program
6589 and find problems in the logic without running the program. It
6590 started out as the Stanford Checker and became well known when it was
6591 used to find bugs in the Linux kernel. It is now a commercial tool
6592 and the company behind it is running
6593 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
6594 free software community, where a lot of free software projects get
6595 their source checked for free. Several thousand defects have been
6596 found and fixed so far. It can find errors like &#39;lock L taken in file
6597 X line N is never released if exiting in line M&#39;, or &#39;the code in file
6598 Y lines O to P can never be executed&#39;. The projects included in the
6599 community service project have managed to get rid of a lot of
6600 reliability problems thanks to Coverity.&lt;/p&gt;
6601
6602 &lt;p&gt;I believe tools like this, that are able to automatically find
6603 errors in the source, are vital to improve the quality of software and
6604 make sure we can get rid of the crashing and failing software we are
6605 surrounded by today.&lt;/p&gt;
6606 </description>
6607 </item>
6608
6609 <item>
6610 <title>No patch is not better than a useless patch</title>
6611 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
6612 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
6613 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
6614 <description>&lt;p&gt;Julien Blache
6615 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
6616 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
6617 patch allow one to discuss a concrete and proposed solution, and also
6618 prove that the issue at hand is important enough for someone to spent
6619 time on fixing it. No patch do not provide any of these positive
6620 properties.&lt;/p&gt;
6621 </description>
6622 </item>
6623
6624 <item>
6625 <title>Standardize on protocols and formats, not vendors and applications</title>
6626 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
6627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
6628 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
6629 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
6630 very good one to form a long lived computer infrastructure. It is the
6631 simple one, lost by many in todays computer industry: Standardize on
6632 open network protocols and open exchange/storage formats, not applications.
6633 Applications come and go, while protocols and files tend to stay, and
6634 thus one want to make it easy to change application and vendor, while
6635 avoiding conversion costs and locking users to a specific platform or
6636 application.&lt;/p&gt;
6637
6638 &lt;p&gt;This approach make it possible to replace the client applications
6639 independently of the server applications. One can even allow users to
6640 use several different applications as long as they handle the selected
6641 protocol and format. In the normal case, only one client application
6642 is recommended and users only get help if they choose to use this
6643 application, but those that want to deviate from the easy path are not
6644 blocked from doing so.&lt;/p&gt;
6645
6646 &lt;p&gt;It also allow us to replace the server side without forcing the
6647 users to replace their applications, and thus allow us to select the
6648 best server implementation at any moment, when scale and resouce
6649 requirements change.&lt;/p&gt;
6650
6651 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
6652 open formats, but I would never recommend standardizing on a single
6653 application that do not use open network protocol or open formats.&lt;/p&gt;
6654 </description>
6655 </item>
6656
6657 <item>
6658 <title>Returning from Skolelinux developer gathering</title>
6659 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
6660 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
6661 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
6662 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
6663 Edu/Skolelinux development gathering. I got a bit done tuning the
6664 desktop, and looked into the dynamic service location protocol
6665 implementation avahi. It look like it could be useful for us. Almost
6666 30 people participated, and I believe it was a great environment to
6667 get to know the Skolelinux system. Walter Bender, involved in the
6668 development of the Sugar educational platform, presented his stuff and
6669 also helped me improve my OLPC installation. He also showed me that
6670 his Turtle Art application can be used in standalone mode, and we
6671 agreed that I would help getting it packaged for Debian. As a
6672 standalone application it would be great for Debian Edu. We also
6673 tried to get the video conferencing working with two OLPCs, but that
6674 proved to be too hard for us. The application seem to need more work
6675 before it is ready for me. I look forward to getting home and relax
6676 now. :)&lt;/p&gt;
6677 </description>
6678 </item>
6679
6680 <item>
6681 <title>Time for new LDAP schemas replacing RFC 2307?</title>
6682 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
6683 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
6684 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
6685 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
6686 optimal. There is RFC 2307 documenting one way to store NIS maps in
6687 LDAP, and a modified version of this normally called RFC 2307bis, with
6688 some modifications to be compatible with Active Directory. The RFC
6689 specification handle the content of a lot of system databases, but do
6690 not handle DNS zones and DHCP configuration.&lt;/p&gt;
6691
6692 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
6693 we would like to store information about users, SMB clients/hosts,
6694 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
6695 and LTSP configuration in LDAP. These objects have a lot in common,
6696 but with the current LDAP schemas it is not possible to have one
6697 object per entity. For example, one need to have at least three LDAP
6698 objects for a given computer, one with the SMB related stuff, one with
6699 DNS information and another with DHCP information. The schemas
6700 provided for DNS and DHCP are impossible to combine into one LDAP
6701 object. In addition, it is impossible to implement quick queries for
6702 netgroup membership, because of the way NIS triples are implemented.
6703 It just do not scale. I believe it is time for a few RFC
6704 specifications to cleam up this mess.&lt;/p&gt;
6705
6706 &lt;p&gt;I would like to have one LDAP object representing each computer in
6707 the network, and this object can then keep the SMB (ie host key), DHCP
6708 (mac address/name) and DNS (name/IP address) settings in one place.
6709 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
6710
6711 &lt;p&gt;I would also like to have a quick way to map from a user or
6712 computer and to the net group this user or computer is a member.&lt;/p&gt;
6713
6714 &lt;p&gt;Active Directory have done a better job than unix heads like myself
6715 in this regard, and the unix side need to catch up. Time to start a
6716 new IETF work group?&lt;/p&gt;
6717 </description>
6718 </item>
6719
6720 <item>
6721 <title>Endelig er Debian Lenny gitt ut</title>
6722 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
6723 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
6724 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
6725 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
6726 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
6727 Et langt steg videre for Debian-prosjektet, og en rekke nye
6728 programpakker blir nå tilgjengelig for de av oss som bruker den
6729 stabile utgaven av Debian. Neste steg er nå å få
6730 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
6731 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
6732 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
6733 slippes løs på skolene. Takk til alle debian-utviklerne som har
6734 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
6735 bootsekvens tilgjengelig i stabil utgave, vha pakken
6736 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
6737 </description>
6738 </item>
6739
6740 <item>
6741 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
6742 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
6743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
6744 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
6745 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
6746 Oslo. Most of Saturday was used for the general assemly for the
6747 member organization, but the rest of the weekend I used to tune the
6748 LTSP installation. LTSP now work out of the box on the 10-network.
6749 Acer Aspire One proved to be a very nice thin client, with both
6750 screen, mouse and keybard in a small box. Was working on getting the
6751 diskless workstation setup configured out of the box, but did not
6752 finish it before the weekend was up.&lt;/p&gt;
6753
6754 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
6755 the Brazilian group, so that will have to wait for the next
6756 development gathering. Would love to have the Debian Edu installer
6757 automatically detect and configure a multiseat setup when it find one
6758 of these cards.&lt;/p&gt;
6759 </description>
6760 </item>
6761
6762 <item>
6763 <title>The sorry state of multimedia browser plugins in Debian</title>
6764 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
6765 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
6766 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
6767 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
6768 plugins available in Debian Lenny, to see which one we should use by
6769 default in Debian Edu. We need an embedded video playing plugin with
6770 control buttons to pause or stop the video, and capable of streaming
6771 all the multimedia content available on the web. The test results and
6772 notes are available on
6773 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
6774 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
6775 fill this need. My personal video player favorite, VLC, has a really
6776 bad plugin which fail on a lot of the test pages. A lot of the MIME
6777 types I would expect to work with any free software player (like
6778 video/ogg), just do not work. And simple formats like the
6779 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
6780 totem and vlc plugins. I hope the situation will improve soon. No
6781 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
6782
6783 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
6784 be the only one fitting our needs. :/&lt;/p&gt;
6785 </description>
6786 </item>
6787
6788 </channel>
6789 </rss>