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