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